[ROM][arm][addison][unofficial] LineageOS 16 - Moto Z Play ROMs, Kernels, Recoveries, & Other Dev

[ROM][arm][addison][unofficial] LineageOS 16 - Moto Z Play ROMs, Kernels, Recoveries, & Other Dev

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
LineageOS is a free, community built, aftermarket firmware distribution of Android 9 (pie), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
Not Working
Moto mods
broken :
Encryption
Credit/Thanks:
Lineage Team
Alberto97 for device tree, kernel, vendors
Preconditions
Unlocked bootloader
TWRP (3.2.1 or newer)
Oreo modem and bootloader
Installation
make a backup ( with twrp, or simply backup your importants datas )
Place ROM & Gapps in your virtual SD
Reboot in Bootloader Mode
Go to "Recovery" (Vol +/Vol -) and confirm (power)
if you come from an other rom / android Version / 32 bit rom : Wipe Dalvik cache / System / data
Install the ROM zip
Don't reboot
Flash Gapps (Latest Pico Arm Gapps recommended)
Reboot
if gapps setup wizard fc at first boot, just go on, no consequence.
Download
AndroidFileHost
My optionals Twrp Zips :
enable adblock
disable adblock
Sources
Device Tree
Kernel
Sensor HAL
Vendor
XDA:DevDB Information
LineageOS Pie for Moto Z play, ROM for the Moto Z play
Contributors
Alberto97
FableBreton
ROM OS Version: 9.0
ROM Kernel: Linux 3.18
ROM Firmware Required: Unlocked Bootloader & Latest TWRP Recovery
Based On: aosp
Version Information
Status: Stable
Created 2018-12-28
Last Updated 2018-02-10

28 Dec 2018
Initial release :
december security patch
come with Se linux enforced
reduced nav bar height from 48 to 34 ( it was so big )
I have no time to test encryption (and i don't use it) so if you want to test encryption be sure to backup your datas before.
The main lineage features i have noticed :
per apps : control wifi,lte
Display : Live Display (night display ) / Style ( pure black theme ) / Expended desktop / Ambient display gesture
Sound : Increasing ring volume ( start volume and ramp up time )
Security : "Trust" => Privacy Guard (you will notice a warning about public key signature, it's because it's an unofficial build)
System : Buttons / System profiles / Status bar / gesture
Dev Options : Advanced restart

The message app has problems can't send message error 21.i don't know it's only my problem or what.i tried Google message app too but not working

Subhransu90 said:
The message app has problems can't send message error 21.i don't know it's only my problem or what.i tried Google message app too but not working
Click to expand...
Click to collapse
No such problem for me.
Wysłane z mojego XT1635-02 przy użyciu Tapatalka

cuando abres una app cierra otra, la barra de navegacion se corta al entrar a las aplicaciones.

A little issue at first startup with gapps wizzard, i had to click several times on some butons to continue, but after that no other issue

there can be some "force close" with setup wizard at the first boot, it happens on some other device with lineage too.
Just bypass, this is just the gapps wizard and it will continue , there is no consequence.
First post edited

Jhoha90 said:
Tienes fallos , cuando abres una app cierra otra , le falta una animación mas fluida entre ventanas, la barra de navegación, se corta al entrar a las aplicacion de google, trabajala mas . . .
Click to expand...
Click to collapse
Jajajaja «Trabajala mas»? Que, ¿ahora es tu empleado? Por favor, abstente de responder cosas tan inútiles.
Thanks for the ROM! It's great news seeing this device it's still supported. by some devs. I'll be sure to try it out soon

Finally, lineage os 16, one of my favorite custom rom
Flashing and restore the backup from twrp, so far so good, no lags or problem persist
edit:
one problem noticed, cannot record video, when change the camera to video, the camera app is closed

iorme said:
Finally, lineage os 16, one of my favorite custom rom
Flashing and restore the backup from twrp, so far so good, no lags or problem persist
edit:
one problem noticed, cannot record video, when change the camera to video, the camera app is closed
Click to expand...
Click to collapse
Select "ultra HD 4K" in moto cam settings for video

fablebreton said:
Select "ultra HD 4K" in moto cam settings for video
Click to expand...
Click to collapse
Its working now, thank you

Nice ROM with android 9 nev bar. Thnks

I am unable to make it boot for me for some reason. Asks me for a password even after a factory reset. After entering the correct one, it says something along the lines of "Decryption failed. Your password is correct but the data is corrupted." It then asks me to perform a factory reset, to which I do. But after rebooting, it leads back to this problem again.

djdelarosa25 said:
I am unable to make it boot for me for some reason. Asks me for a password even after a factory reset. After entering the correct one, it says something along the lines of "Decryption failed. Your password is correct but the data is corrupted." It then asks me to perform a factory reset, to which I do. But after rebooting, it leads back to this problem again.
Click to expand...
Click to collapse
u need to remove encryption first.... Try format /data in twrp...
encryption may be not compatible yet...
happy new year guys

@fablebreton - thanks a lot for your great work. Please can you share your file "roomservice.xml"? With my file "repo sync" works but build stop: can't find addison. Thanks a lot!

guenterm800 said:
@fablebreton - thanks a lot for your great work. Please can you share your file "roomservice.xml"? With my file "repo sync" works but build stop: can't find addison. Thanks a lot!
Click to expand...
Click to collapse
You don't need bson, already included in Alberto trees. You miss system_qcom

fablebreton said:
You don't need bson, already included in Alberto trees. You miss system_qcom
Click to expand...
Click to collapse
Great, thanks a lot. I will try it.
I tried it, here the error:
including vendor/lineage/vendorsetup.sh
Device addison not found. Attempting to retrieve device repository from Lineage$
Found repository: android_device_motorola_addison
Default revision: lineage-16.0
Checking branch info
Default revision lineage-16.0 not found in android_device_motorola_addison. Bai$
Branches found:
cm-14.1
lineage-15.1
Use the ROOMSERVICE_BRANCHES environment variable to specify a list of fallback$
** Don't have a product spec for: 'lineage_addison'
** Do you have the right repo manifest?
No such item in brunch menu. Try 'breakfast'
OK, there is no addison 16.0 in LinOS. What can I do. I think the sources are local. I attached new roomservice-file.

guenterm800 said:
OK, there is no addison 16.0 in LinOS. What can I do. I think the sources are local. I attached new roomservice-file.
Click to expand...
Click to collapse
Alberto's device tree is tailored to AOSP, not Lineage, so you could use
Code:
brunch aosp_addsion-userdebug
over
Code:
brunch addison
and it should work.
Alternatively, you could change the sources to fit Lineage, which doesn't require many changes to get a build running. That just requires renaming the aosp_addison.mk file to lineage_addison.mk, as well as changing the references to aosp_addison to lineage_addison in both the AndroidProducts.mk and new lineage_addison.mk file.

fireclaw722 said:
Code:
brunch aosp_addison-userdebug
Click to expand...
Click to collapse
Thanks, build starts, but there is the next problem:
Code:
error: vendor/lineage/build/soong/Android.bp:31:8: module "generated_kernel_includes": cmd: unknown variable '$(KERNEL_MAKE_FLAGS)'
ninja: build stopped: subcommand failed.
I attache more information. Can you help?

guenterm800 said:
Thanks, build starts, but there is the next problem:
Code:
error: vendor/lineage/build/soong/Android.bp:31:8: module "generated_kernel_includes": cmd: unknown variable '$(KERNEL_MAKE_FLAGS)'
ninja: build stopped: subcommand failed.
I attache more information. Can you help?
Click to expand...
Click to collapse
Okay, so that actually doesn't work. Interesting... I just modified the files to fit LOS's build system and that worked for me (or at least started to).
Below should got a build running for me, before I ran into SELinux errors (but those could have just been because I'm messing with things).
Alternatively, you could change the sources to fit Lineage, which doesn't require many changes to get a build running. That just requires renaming the aosp_addison.mk file to lineage_addison.mk, as well as changing the references to aosp_addison to lineage_addison in both the AndroidProducts.mk and new lineage_addison.mk file.
Click to expand...
Click to collapse
Also, I noticed your roomservice file put hardware-moto-sensors under hardware/sensors, instead of hardware/moto-sensors. I wouldn't think it's hardcoded, but it wouldn't be the first time I've been wrong.
I'm going to try a clean build later, but hopefully this helps.

Related

[9] LineageOS 16.0 for z3c

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Introduction
LineageOS, an open-source Android distribution, is available for several devices,
with more being continuously added thanks to the biggest, yet ever growing, Android open-source community.
Join us and breathe new life in your device, be it old or new.
Click to expand...
Click to collapse
If you don't know LineageOS and would like to read about it before installing it you can take a look at the official Website.
Images
Here are some Screenshots of this ROM.
Features
Individuality
Customization is paramount to productivity.
That’s why LineageOS promises to push for user personalization and preference.
Everyone is unique and your device should be too.
Click to expand...
Click to collapse
Security
Your data, your rules. With powerful tools such as Privacy Guard, you are in control of what your apps can do whenever you want.
Trust will help you understand the security of your device and warn you about possible threats.
We take security very seriously: that’s why we deliver security updates every month to all our supported devices.
And to make your device more secure, lock everything behind an enhanced lock screen.
Click to expand...
Click to collapse
Longevity
LineageOS extends the functionality and lifespan of mobile devices from more than 20 different manufacturers thanks to our open-source community of contributors from all around the world.
Click to expand...
Click to collapse
Installation instructions
Prerequisites:
Unlocked Sony Xperia Z3 Compact
Fastboot drivers to install TWRP
Micro-USB Cable to connect your phone to your computer
Install:
Reboot to TWRP. *
Wipe cache, dalvik cache, data and system.
Format data to get rid of encryption.
Install ROM.
Install 9.0 Gapps for ARM. **
* recommended TWRP: Post #2
** optional
Update:
Get the latest build
Boot into TWRP
Flash the downloaded build
Reboot, if you don't wipe system backuptool will handle to reapply your modifications, for example: GApps.
Changelog
Code:
Changelog 2019-10-07
* Fixed offmode charging at Wall chargers (previously bright screen)
* Fixed offmode charging at computers (previously reboot loop)
Old Changelogs
Code:
Changelog 2019-10-06
* Fixed camera for everyone
* Set media volume steps to 25 and voice call volume steps to 7
* Actually use our cache partition, previously we were using a link to /data/cache instead of mounting the cache partition as /cache
* Cleanup of rootdir scripts
Code:
Changelog 2019-08-28
* Rolled fingerprint back to Sony's 5.1.1 fingerprint
-> safetynet CTS check works again
* Set original shipping API level to KitKat
* Minor cleaning
Code:
Changelog 2019-08-14
* Singificantly improved GPS
* August Android Security Bulletin
* Cleaned, script generated vendor
Code:
Changelog 2019-08-05
* Attempt to fix ANT+
* Added settings to control the camera button
Code:
Changelog 2019-07-08
* July Android Security Bulletin
* Rebased Linux 3.4.113 Kernel
-> Solved video recording lags with Snap
Code:
Changelog 2019-06-15
* Fixed Audio problems
* LED Notifications work again
* Manual Network selection fixed
Code:
Changelog 2019-06-07
* June Android security Bulletin
* LED seems to work with notifications now
* 4.0 Audio HAL -> NO, this does NOT fix our problems :/
Code:
Changelog 2019-05-10
* Enforcing sepolicy
* Fixed sensors
* Fixed FM Radio
* Fixed EXFat, sdfat and vfat
* Camera works fine
* May Android Security Bulletin
* Sound seems fixed - Maximum Volume still decreases still after a few seconds when using internal speakers
Code:
Changelog 2019-05-06
* Fixed AudioFX
* Fixed Camera
Code:
Changelog 2019-04-24
* Fixed Notification LED
Code:
Changelog 2019-02-19
* Fixed GPS
* Fixed Video Playback
Code:
Changelog 2019-01-09
* Fixed Bluetooth
Downloads
Download the ROM
Sources
DEVICE:
https://github.com/z3c-pie/device_sony_z3c
https://github.com/z3c-pie/device_sony_msm8974-common
https://github.com/z3c-pie/device_sony_shinano-common
KERNEL:
https://github.com/z3c-pie/kernel_sony_msm8974
Addons
OpenGapps
Magisk
SU-Addon
Thanks
Whole LineageOS Team for this amazing ROM
@rcstar6696
@Myself5
@drakonizer
@tomascus
@koron393
@nailyk
@SpiritCroc
I hope I haven't forgot anyone
Bugs
WHAT'S BROKEN
4K Video recording doesn't work in stock camera, but works for example in OpenCamera.
You tell me.
FAQ
Q: Why i can't reboot into the recovery from advanced reboot?
A: Because you have installed Magisk 19.1 which breaks it. Keep up to date here: https://github.com/topjohnwu/Magisk/issues/1418 - fixed by @Myself5 since 2019.05.20
XDA:DevDB Information
[9] LineageOS 16.0 for z3c, ROM for the Sony Xperia Z3 Compact
Contributors
NeoArian
Source Code: https://github.com/LineageOS
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.4.x
Version Information
Status: Stable
Current Stable Version: lineage-16-20190510
Stable Release Date: 2019-05-10
Created 2019-01-05
Last Updated 2019-10-10

TWRP 3.3.1 for our z3c out of an Android 9.0 environment!
Changes:
Code:
3.3.1-0.4-z3c
* Fixed fastboot boot
* Added bootlogo
* Dropped TWRP App
Code:
3.3.1-0.3-z3c
* Fixed encryption when security patch level doesn't match the recovery's
- [url]https://github.com/z3c-pie/twrp_device_sony_z3c/commit/411862532c247aea2c7b48d52aa596b40305e9ea[/url]
Code:
3.3.1-0.2-z3c
* Added a script to handle the CPU
-> increased the battery life significant ([url]https://github.com/z3c-pie/twrp_device_sony_z3c/commit/63f864068ad2f17ae2f1202b4edc311d74e2803d[/url])
Code:
3.3.1-0.1-z3c
* Fixed time
* Further Clean up's
Code:
3.3.1-0-z3c
* Switched from Android 6.0 to Android 9.0 environment
* Completely reworked tree
* Working decryption
The latest build is attached to this post.
Old builds are available here: https://sourceforge.net/projects/ephedraceae/files/z3c/twrp/
Source is available at: https://github.com/z3c-pie/twrp_device_sony_z3c/tree/android-9.0
How to install this build:
Rename the downloaded twrp image to twrp.img
Reboot to fastboot by holding volume up while connecting your device to your computer
Open a terminal and move to the directory with TWRP in it
Type
Code:
fastboot flash recovery twrp.img
Boot into TWRP while the device is powered off press the power and volume down button
Feel free to ask questions or give feedback about TWRP here .
Have a nice day!
Additional information about the recovery on this device:
First of all we should make the basics clear: On our Z3 Compact we have got a bootloader update which can boot a recovery from powered off state by pressing volume down and the power button. Because we haven't ever had this updated bootloader and not all sony devices received the update, there have been some intelligent people who brought a special init binary which can handle recovery boots during a normal boot. This means when using advanced reboot from the ROM or pressing a volume key while the sony logo appears at boot. https://github.com/LineageOS/android_device_sony_common/commits/lineage-16.0
To make this work there is this method to extract the ramdisk: https://github.com/LineageOS/androi...eage-16.0/extract_ramdisk/extract_ramdisk.cpp which uses zlib to decompress it. So far so good, zlib can decompress the default compression for recovery ramdisk which is gzip. However LZMA is more effective to reduce the size so we took it's advantage: https://github.com/omnirom/android_...mmit/885b01223a460d3f2500155ea415bdc8573679bc in order to fit recoverys compiled from recent environments (android-9.0 in my case) into our small FOTAKernel partition.
According to this change the init_sony can't handle the recovery boot anymore because it can't decompress the recovery's ramdisk so nailyk and Diewi (as far as i know) added support to decompress LZMA compressed ramdisk's with this chain: https://github.com/sonyxperiadev/device-sony-common-init/pull/20/commits
However these commits have never been merged into the LineageOS/android_device_sony_common nor the sonyxperiadev/device-sony-common-init. Since your ROM, CarbonROM, is using a fork of LineageOS/android_device_sony_common is missing these commits the recovery boot fails with a kernel panic, like this: https://del.dog/egawososux.htm
So you can either use a recovery which doesn't compress the ramdisk with LZMA (for example the one from here: https://forum.xda-developers.com/z3-compact/development/recovery-twrp-3-2-3-0-aries-t3837192 or ask your ROM developer to pick the according commits into the sony_common tree/use my fork of LineageOS's one https://github.com/z3c-pie/android_...mits/fa85dfcc07f42d73f9a1abf1f4c82d8bf0486a93 which would enable you to use recent TWRP builds with a LZMA compressed ramdisk.
I hope i presented it clearly and in the right way,
Have a nice day!
EDIT: Minimized patch for LZMA is available here: https://review.lineageos.org/c/LineageOS/android_device_sony_common/+/252923
Click to expand...
Click to collapse

Reserved

Hi, I can't open your thread in XDA Labs app, I suppose that's the case of many people and that's why there is not much views and comments on this thread.
I didn't tried yet your ROM but it sound great and will try it ASAP.
Also which recovery do you recommend to avoid errors like error 7 (if I remember) ?
Also will you continue to work on RR ?
EDIT : after posting this comment via browser, I can now open this thread in XDA Labs
EDIT 2 : everything is working

SUPER KOKA said:
Hi, I can't open your thread in XDA Labs app, I suppose that's the case of many people and that's why there is not much views and comments on this thread.
I didn't tried yet your ROM but it sound great and will try it ASAP.
Also which recovery do you recommend to avoid errors like error 7 (if I remember) ?
Also will you continue to work on RR ?
EDIT : after posting this comment via browser, I can now open this thread in XDA Labs
Click to expand...
Click to collapse
I use twrp-3.2.3 from here: https://forum.xda-developers.com/z3-compact/development/recovery-twrp-3-2-3-0-aries-t3837192.
I don't know yet about RR. I wanna see first whether we can get Bluetooth and gps working as soon as possible.

https://sourceforge.net/projects/ep...age-16.0-20190109-UNOFFICIAL-z3c.zip/download
Another build was uploaded with the latest lineageos updates including the January android security bulletin. On the device side Bluetooth was fixed

Installed without any problems
You did a great job!
Installed without any problems. It seems all functions work fine!

update
I've been in lineage, whether for the latest version update I have to hard reset or like the ota update

SUPER KOKA said:
EDIT 2 : everything is working
Click to expand...
Click to collapse
Great to hear!
CDLion said:
You did a great job!
Installed without any problems. It seems all functions work fine!
Click to expand...
Click to collapse
Thanks!
muhibbuddin irsyad said:
I've been in lineage, whether for the latest version update I have to hard reset or like the ota update
Click to expand...
Click to collapse
To be honestly I can't follow you. Do you mean that you don't know how to update the build? For this case you have to download manually and flash it in TWRP. There are no wipes needed.

Hi, thanks for this and how is the battery performance?

Any plans for making an LineageOS for microG rom?

Thanks for the ROM, I am using it right now, everything is working good except the camera. Can take photos, but video is not working. When I'm switching to video, the app is freezing and stuck. I tried to use the stock camera with magisk, it can't take photos or video neither. Tried manual camera too, it can take photos but no video.

etram said:
WOW ... !!!
Great Job.
What about the notification LED?
Click to expand...
Click to collapse
Just tested shortly, it seems to be broken, I will add to broken things list. Thanks to notify (?)

I flash the recovery and I delete assers but I can not install this rom every time updater process ended with error 255 .Can you help me?
my log

frht5382 said:
I flash the recovery and I delete assers but I can not install this rom every time updater process ended with error 255 .Can you help me?
my log
Click to expand...
Click to collapse
I try and I install 20180105 build but I cant install new build why ?
twrp 255 error

frht5382 said:
I flash the recovery and I delete assers but I can not install this rom every time updater process ended with error 255 .Can you help me?
my log
Click to expand...
Click to collapse
frht5382 said:
I try and I install 20180105 build but I cant install new build why ?
twrp 255 error
Click to expand...
Click to collapse
Are you sure that you use the recovery from here?
https://forum.xda-developers.com/z3-compact/development/recovery-twrp-3-2-3-0-aries-t3837192

NeoArian said:
Are you both sure that you use the recovery from here?
https://forum.xda-developers.com/z3-compact/development/recovery-twrp-3-2-3-0-aries-t3837192
Click to expand...
Click to collapse
Solved.I dowloaded false file which 632 mb.Now I re download true file and it work thank you

frht5382 said:
Yes I am sure.I install 2019 01 05 build it work but I try 20190109 fail everytime error code 255
edit
I've just realized I clik download button and if I download latest version green color button I download 631 mb but down of button lineage-16.0-20190109-UNOFFICIAL-z3c.zip 448 mb which one should I download ?
why different size ?
Click to expand...
Click to collapse
The 631mb Rom is for my Xiaomi Mi 6, you have to use the one for z3c

NeoArian said:
Tue 631mb Rom is for my Xiaomi Mi 6, you have to use the one for z3c
Click to expand...
Click to collapse
I installed thank you .How to enable root access? Or magisk work ?

frht5382 said:
I installed thank you .How to enable root access? Or magisk work ?
Click to expand...
Click to collapse
Magisk works.

[ROM][OFFICIAL][kirin][10] LineageOS 17.1

oh btw you might want to use this TWRP for flashing my builds.

LuK1337 said:
oh btw you might want to use this TWRP for flashing my builds.
Click to expand...
Click to collapse
I didn't expect you here mr Luk. I'm gonna test it when I will be at home. I'm glad that Kirin got such a developer

Problem Resolved.
Problem Resolved.

AlexDaBoii said:
Hello! So I tried to install a custom rom called Lineage OS, version 17.1 unofficial for my SOny Xperia 10 through TWRP custom recovery. I then tried installing the GApps and then rebooted the system. Then it came up with a prompt saying that the OS was corrupted and then to factory reset it. I did just that, and then LineageOS booted up just fine. However no Google Apps could be seen. I then tried to boot in to TWRP custom recovery, however it came up with the LineageOS recovery instead. I then tried to flash TWRP and managed to get it up and running, but when I rebnooted the phone, it just brought me in a boot loop.
I tried for hours to fix it and the I finally managed to flash TWRP again, however all of my save files were gone. I then tried to flash the Stock ROM for the Xperia 10 to the "system" folder and then my device powered off. I tried to power it on again and then it came up with a prompt saying "Your device is corrupt. It can't be trusted and will not boot. Powering off in 5 sec.". I got really freaked out at this point and did not know what to do. I know that I am an idiot for doing this, but if there is any fix at all for this that anybody can tell me, then I would be very thankful.
Click to expand...
Click to collapse
If you join irc I may be able to help you:
https://kiwiirc.com/nextclient/irc.freenode.net?channel=#titandev

Flawless on I3123 so far. Really appreciate the work on this device.

Has somebody tried this on I3113?
Are all components working fine?

xXqepXx said:
Has somebody tried this on I3113?
Are all components working fine?
Click to expand...
Click to collapse
Considering this thread is pretty much dead, you may as well just go for it. It /should/ be fine, just make sure to /format data/ instead of wiping it and don't install /twrp app/. If you notice something broken, let me know about it and I'll probably try to fix it.

LuK1337 said:
Considering this thread is pretty much dead, you may as well just go for it. It /should/ be fine, just make sure to /format data/ instead of wiping it and don't install /twrp app/. If you notice something broken, let me know about it and I'll probably try to fix it.
Click to expand...
Click to collapse
Hi, I am using it on a i4113; it seem to work fine - and appreciate this work, htanks Luk1337 - I found two strange behavior (not too critical):
- When the phone is shut down and plug it to charge, it power ON normally instead to keep it on charge only
- Connecting to my car via Bluetooth, I don't see operator and signal strenght... but phone calls, messages, phonebook and call log work fine...
Thanks in advance!

thesandroid said:
Hi, I am using it on a i4113; it seem to work fine - and appreciate this work, htanks Luk1337 - I found two strange behavior (not too critical):
- When the phone is shut down and plug it to charge, it power ON normally instead to keep it on charge only
- Connecting to my car via Bluetooth, I don't see operator and signal strenght... but phone calls, messages, phonebook and call log work fine...
Thanks in advance!
Click to expand...
Click to collapse
>When the phone is shut down and plug it to charge, it power ON normally instead to keep it on charge only
I have a fix for that, I'll release build with it soon (TM).
>Connecting to my car via Bluetooth, I don't see operator and signal strenght... but phone calls, messages, phonebook and call log work fine...
Theoretically SAP is already enabled so I have no idea why it wouldn't work. I'm not going to bother investigating further as this isn't really that important ( and I don't have hardware needed to reproduce this anyway ).

What gapps do you recommend? I have an i3113 and after i flashed opengapps, i always get this weird "Android setup isn't responding" "System UI Keeps crashing" thing. What can i do?

LuK1337 said:
>When the phone is shut down and plug it to charge, it power ON normally instead to keep it on charge only
I have a fix for that, I'll release build with it soon (TM).
>Connecting to my car via Bluetooth, I don't see operator and signal strenght... but phone calls, messages, phonebook and call log work fine...
Theoretically SAP is already enabled so I have no idea why it wouldn't work. I'm not going to bother investigating further as this isn't really that important ( and I don't have hardware needed to reproduce this anyway ).
Click to expand...
Click to collapse
Got that fix, now charging works fine... Great!!
About Bluetooth issue, I can confirm it's not due to SAP profile, it's enabled; here is what I found more:
Using one SIM only it seem to show SIM2 status:
- if SIM is in SIM1 slot, it shows No signal / Emergency calls only as I alreaedy mentioned
- if SIM is in SIM2 slot, it shows operator and signal strength
Using two SIM, it shows operator and signal strength of the SIM selected for calls.

thesandroid said:
Got that fix, now charging works fine... Great!!
About Bluetooth issue, I can confirm it's not due to SAP profile, it's enabled; here is what I found more:
Using one SIM only it seem to show SIM2 status:
- if SIM is in SIM1 slot, it shows No signal / Emergency calls only as I alreaedy mentioned
- if SIM is in SIM2 slot, it shows operator and signal strength
Using two SIM, it shows operator and signal strength of the SIM selected for calls.
Click to expand...
Click to collapse
Yeah that doesn't sound fun. Not going to bother.
On a sidenote, next build will fix Netflix Widevine L1.

Worked perfectly in my I4193. By the way, how do I build the zip via github source code or if there is any document about how to build? I found there is no lineage_kirin-eng in the LineageOS github repository. Here is my command to retrieve Lineage OS.
repo init -u git://github.com/LineageOS/android.git -b lineage-17.1
Thank you very much.

zzz00072 said:
Worked perfectly in my I4193. By the way, how do I build the zip via github source code or if there is any document about how to build? I found there is no lineage_kirin-eng in the LineageOS github repository. Here is my command to retrieve Lineage OS.
repo init -u git://github.com/LineageOS/android.git -b lineage-17.1
Thank you very much.
Click to expand...
Click to collapse
You build it exactly the same you'd be building an official device.

Dear Sir,
The problem is that I can not find lineage_kirin-eng combo in Lunch menu. Is there there anything I missed? Last time I built Android was years ago.
Here is what I saw after start lunch
You're building on Linux
Lunch menu... pick a combo:
1. aosp_arm-eng
2. aosp_arm64-eng
3. aosp_car_arm-userdebug
4. aosp_car_arm64-userdebug
5. aosp_car_x86-userdebug
6. aosp_car_x86_64-userdebug
7. aosp_x86-eng
8. aosp_x86_64-eng
9. car_x86_64-userdebug
10. lineage_arm-userdebug
11. lineage_arm64-userdebug
12. lineage_x86-userdebug
13. lineage_x86_64-userdebug
14. m_e_arm-userdebug
15. mini_emulator_arm64-userdebug
16. mini_emulator_x86-userdebug
17. mini_emulator_x86_64-userdebug
18. qemu_trusty_arm64-userdebug
19. uml-userdebug
Which would you like? [aosp_arm-eng]
LuK1337 said:
You build it exactly the same you'd be building an official device.
Click to expand...
Click to collapse

After running breakfast kirin
There are some error message displayed below:
build/target/product/verity.mk:28: error: _nic.PRODUCTS.[[device/sony/kirin/lineage_kirin.mk]]: "vendor/sony/nile-common/nile-common-vendor.mk" does not exist.
zzz00072 said:
Dear Sir,
The problem is that I can not find lineage_kirin-eng combo in Lunch menu. Is there there anything I missed? Last time I built Android was years ago.
Here is what I saw after start lunch
You're building on Linux
Lunch menu... pick a combo:
1. aosp_arm-eng
2. aosp_arm64-eng
3. aosp_car_arm-userdebug
4. aosp_car_arm64-userdebug
5. aosp_car_x86-userdebug
6. aosp_car_x86_64-userdebug
7. aosp_x86-eng
8. aosp_x86_64-eng
9. car_x86_64-userdebug
10. lineage_arm-userdebug
11. lineage_arm64-userdebug
12. lineage_x86-userdebug
13. lineage_x86_64-userdebug
14. m_e_arm-userdebug
15. mini_emulator_arm64-userdebug
16. mini_emulator_x86-userdebug
17. mini_emulator_x86_64-userdebug
18. qemu_trusty_arm64-userdebug
19. uml-userdebug
Which would you like? [aosp_arm-eng]
Click to expand...
Click to collapse

zzz00072 said:
After running breakfast kirin
There are some error message displayed below:
build/target/product/verity.mk:28: error: _nic.PRODUCTS.[[device/sony/kirin/lineage_kirin.mk]]: "vendor/sony/nile-common/nile-common-vendor.mk" does not exist.
Click to expand...
Click to collapse
hint: themuppets.

Dear Sir,
After
Code:
cd vendor && git clone https://github.com/TheMuppets/proprietary_vendor_sony.git sony
The build system failed on building kernel as shown below. Can I know where can I get the proper kernel source? Thanks very much!
Code:
PRODUCT_SOONG_NAMESPACES=vendor/sony/kirin vendor/sony/nile-common device/sony/nile-common hardware/qcom-caf/msm8998
============================================
out/soong/Android-lineage_kirin.mk was modified, regenerating...
[ 99% 516/517] finishing build rules ...
vendor/lineage/build/tasks/kernel.mk:109: warning: ***************************************************************
vendor/lineage/build/tasks/kernel.mk:110: warning: * Using prebuilt kernel binary instead of source *
vendor/lineage/build/tasks/kernel.mk:111: warning: * THIS IS DEPRECATED, AND WILL BE DISCONTINUED *
vendor/lineage/build/tasks/kernel.mk:112: warning: * Please configure your device to download the kernel *
vendor/lineage/build/tasks/kernel.mk:113: warning: * source repository to kernel/sony/sdm660
vendor/lineage/build/tasks/kernel.mk:114: warning: * for more information *
vendor/lineage/build/tasks/kernel.mk:115: warning: ***************************************************************
FAILED: ninja: 'out/target/product/kirin/kernel', needed by 'out/target/product/kirin/boot.img', missing and no known rule to make it
23:16:16 ninja failed with: exit status 1
#### failed to build some targets (02:54 (mm:ss)) ####
LuK1337 said:
hint: themuppets.
Click to expand...
Click to collapse

zzz00072 said:
Dear Sir,
After
Code:
cd vendor && git clone https://github.com/TheMuppets/proprietary_vendor_sony.git sony
The build system failed on building kernel as shown below. Can I know where can I get the proper kernel source? Thanks very much!
Code:
PRODUCT_SOONG_NAMESPACES=vendor/sony/kirin vendor/sony/nile-common device/sony/nile-common hardware/qcom-caf/msm8998
============================================
out/soong/Android-lineage_kirin.mk was modified, regenerating...
[ 99% 516/517] finishing build rules ...
vendor/lineage/build/tasks/kernel.mk:109: warning: ***************************************************************
vendor/lineage/build/tasks/kernel.mk:110: warning: * Using prebuilt kernel binary instead of source *
vendor/lineage/build/tasks/kernel.mk:111: warning: * THIS IS DEPRECATED, AND WILL BE DISCONTINUED *
vendor/lineage/build/tasks/kernel.mk:112: warning: * Please configure your device to download the kernel *
vendor/lineage/build/tasks/kernel.mk:113: warning: * source repository to kernel/sony/sdm660
vendor/lineage/build/tasks/kernel.mk:114: warning: * for more information *
vendor/lineage/build/tasks/kernel.mk:115: warning: ***************************************************************
FAILED: ninja: 'out/target/product/kirin/kernel', needed by 'out/target/product/kirin/boot.img', missing and no known rule to make it
23:16:16 ninja failed with: exit status 1
#### failed to build some targets (02:54 (mm:ss)) ####
Click to expand...
Click to collapse
Yikes, you're doing so much stupid stuff...
Msg me on irc if you want it done anytime soon.

[ROM][Official][Nightly] LineageOS 18.1 for OnePlus 3/3T

LineageOS is a free, community-built, aftermarket firmware distribution of Android 11, which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Important information:
This thread is for LineageOS 18.1 builds for OnePlus 3/3T. The following will not be supported here:
Custom kernels
Mods
Xposed
We don't support Xposed and any logcat which includes an Xposed module will be ignored. You're kindly invited to not report bugs if you:
Flashed a custom kernel
Installed or did mods from untrusted sources
Modified system files
Tips:
You need at least OxygenOS 9.0.2 firmware, otherwise you'll get error 7 when installing the zip. Latest firmware is recommended.
Installation:
First time flashing LineageOS 18.1 on your device, or coming from another ROM?
Download the zip(s)
Install a compatible Recovery (Official TWRP 3.4+ is highly recommended: https://dl.twrp.me/oneplus3/)
Perform a nandroid backup of your current ROM (Optional)
Wipe data/factory reset
Flash LineageOS
Optional: Install the Google Apps addon package
Reboot
Source code:
https://github.com/lineageos
Credits:
LineageOS Team & Contributors
Code Aurora Forum
......
Changelog and Download:
2021/2/8 (Initial release): https://androidfilehost.com/?fid=17248734326145731516Known issues:
This build is HIGHLY EXPERIMENTAL and NOT WELL TESTED.
Wifi display not work, don't ever attempt to use it or the system will crash.
VoLTE is not tested and I don't know if it ever works, please give feedback if you're able to verify.
2021/4/2: https://download.lineageos.org/oneplus3
Fixed the sensor_SMD wakelock
Fixed ringtone when bluetooth headset connected

Wow !!! , i'm on LOS 17.1 Official now but waiting for LOS 18.1 Official
OP3 is my daily driver..
Thank you @dianlujitao

Thanks for this great Rom.
One issue.
It displays a popup with the following message: "This build was signed with public keys".
Should i ignore it?

Keyvannn said:
Thanks for this great Rom.
One issue.
It displays a popup with the following message: "This build was signed with public keys".
Should i ignore it?
Click to expand...
Click to collapse
Yes, you should

josepmaria said:
Yes, you should
Click to expand...
Click to collapse
Would updating to official builds be possible later on, based on the fact public keys are used?
Other question; is a locked bootloader possible with these builds?
I don't know enough about used keys to be sure...

Jan_L said:
Would updating to official builds be possible later on, based on the fact public keys are used?
Other question; is a locked bootloader possible with these builds?
I don't know enough about used keys to be sure...
Click to expand...
Click to collapse
Yes, the key for signing the build doesn't matter.

My initial testing of this rom is that everything is working (based on my usage): WiFi, phone calls, SMS, NFC (Google Pay) all work.
I had a bit of problem setting the wallpaper initially (FCed), but the problem went away on its own after waiting a bit of time.
I'm missing the settings option to specify the duration of the capacitive key backlight, but that's no big deal.
I'm using Opens Gapps pico 210130 and Magisk 21047.
I've seen evidence of the sensor_SMD kernel wake lock issue that I've seen on all Android 11 roms I've tested previously. I'll post more details on this once I've captured a logcat of the problem.

BillGoss said:
sensor_SMD kernel wake lock issue
Click to expand...
Click to collapse
Nap time by Franco mostly solved this for me.

Sideload TWRP 3.5.0, wipe dalvik & cache, flash 18.1. All good

Jan_L said:
Would updating to official builds be possible later on, based on the fact public keys are used?
Other question; is a locked bootloader possible with these builds?
I don't know enough about used keys to be sure...
Click to expand...
Click to collapse
Update to official build requires a clean install and an unlocked bootloader

raz123 said:
Nap time by Franco mostly solved this for me.
Click to expand...
Click to collapse
Last time I used NapTime, it drains more battery than it should and my phone was almost all the time in idle untouched with WIFI and everything else off

Regarding the sensor_SMD wake lock:
Generally, the rom can go for long periods without this wake lock showing up:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
But the wake lock can start at random times:
And when it starts, it will stop the device from going into deep sleep (look at the "Awake (Screen off)" figures). This will drain the battery a lot faster than normal. See 210209-174541-log.zip for logs.
However, I find that the wake lock will always start when the phone is fully recharged (I usually do this just before I go to bed). See 210209-174541-log.zip for logs.
Fortunately, a reboot gets rid of the wake lock.

josepmaria said:
Update to official build requires a clean install and an unlocked bootloader
Click to expand...
Click to collapse
If the plattform key is changed a clean flash is highly recommended (though not required if you use a migration script or zip - NOT!!! recommended). Since los recovery (as well as current twrp for that matter) and los boot image are signed with aosp verity key, you don't need to unlock bl if you run any version of los with a locked bl.
I've explained the three different keys and signatures used in a single build in depth in the llos 17 thread: https://forum.xda-developers.com/t/...or-oneplus-3-3t.3990061/page-60#post-82568467

BillGoss said:
Regarding the sensor_SMD wake lock:
Generally, the rom can go for long periods without this wake lock showing up:
View attachment 5215977View attachment 5215981
But the wake lock can start at random times:
View attachment 5215983View attachment 5215985
And when it starts, it will stop the device from going into deep sleep (look at the "Awake (Screen off)" figures). This will drain the battery a lot faster than normal. See 210209-174541-log.zip for logs.
However, I find that the wake lock will always start when the phone is fully recharged (I usually do this just before I go to bed). See 210209-174541-log.zip for logs.
View attachment 5215983View attachment 5216001
Fortunately, a reboot gets rid of the wake lock.
Click to expand...
Click to collapse
Nice finding. Just check the source and that should be the Significant Motion Detector if I'm not wrong. Dunno if there are any drawbacks but you should be able to disable it by adding " ro.vendor.sensors.smd=false" to /vendor/build.prop, please try if it helps.

dianlujitao said:
Nice finding. Just check the source and that should be the Significant Motion Detector if I'm not wrong. Dunno if there are any drawbacks but you should be able to disable it by adding " ro.vendor.sensors.smd=false" to /vendor/build.prop, please try if it helps.
Click to expand...
Click to collapse
I set the property as you suggested. After more than 12 hours, including a full recharge, there's no sign of the wake lock. It's looking good.
Thank you!

May be a stupid question and definitely not belonging here, but can not find the answer anywhere else....
When is /vendor/build.prop used and when /system/build.prop?
It seems settings of /vendor/build.prop are used earlier in the boot process and are vendor specific, where afterwards /system/build.prop settings are added later in the boot process and are OS specific.
A lot of people are messing with build.prop settings but have no idea what they are doing and if settings are even working or not. As I see it, some settings put in /system/build.prop are in fact settings which belong in /vendor/build.prop, but I do not know if everything put in /system/build.prop will overrule /vendor/build.prop or the other way around....
In some Android 10 code I found the order default.prop, build.prop, vendor.prop, where /vendor/build.prop is loaded after /system/build.prop, though not sure if this is the default then....
You see, no idea what I am talking about; I hope someone can clear things up...

Jan_L said:
May be a stupid question and definitely not belonging here, but can not find the answer anywhere else....
When is /vendor/build.prop used and when /system/build.prop?
It seems settings of /vendor/build.prop are used earlier in the boot process and are vendor specific, where afterwards /system/build.prop settings are added later in the boot process and are OS specific.
A lot of people are messing with build.prop settings but have no idea what they are doing and if settings are even working or not. As I see it, some settings put in /system/build.prop are in fact settings which belong in /vendor/build.prop, but I do not know if everything put in /system/build.prop will overrule /vendor/build.prop or the other way around....
In some Android 10 code I found the order default.prop, build.prop, vendor.prop, where /vendor/build.prop is loaded after /system/build.prop, though not sure if this is the default then....
You see, no idea what I am talking about; I hope someone can clear things up...
Click to expand...
Click to collapse
First of all: since op3/t has no dedicated vendor partition /vendor is a symlink to /system/vendor.
/default.prop is read first and contains settings necessary for basic boot (historically this file has been part of the root partition which has been ramfs contained in the boot image as cpio archive prior to system as root, which allows to set these props before system was mounted - obviously that's not longer the case with system as root.
/system/vendor/build.prop is read as second source containing vendor specific props. Systematically this should contain settings specific to the vendor(s) of the device and the actual os (which are the same, as long as you use stock roms, but obviously differ if you use an custom source build rom like los).
/system/build.prop is reaf as third source and should contain general android settings.
If the same prop is set in more then one file the last one wins as long as it's no read only prop (ro.*). For ro.* prop the first one wins, because it can't be changed after setting. Exeption: if you use magisk, you can alter ro.* props (by command from the commamdline or a script).
Additionally to these three sources some props are set by init (first os process started by the kernel and controlling the boot process). See:
android_device_oneplus_oneplus3/init_oneplus3.cpp at lineage-18.1 · LineageOS/android_device_oneplus_oneplus3
Contribute to LineageOS/android_device_oneplus_oneplus3 development by creating an account on GitHub.
github.com

nvertigo67 said:
First of all: since op3/t has no dedicated vendor partition /vendor is a symlink to /system/vendor.
Click to expand...
Click to collapse
Thanks for the clear explanation nvertigo!

Does this rom support encryption?

Thank you for your hard work and look forward to the arrival of offical los18.1.

[OFFICIAL] LineageOS 19.1 for Moto G6 Plus

Can I upgrade from the unofficial build to the official - or do I need to wipe all and start from scratch?

I prefer you start clean, but you can try, if you flash mindthegapps as Gapps package, it will be the same as shipped on unnoficial build

works great

Unofficial builds are still the best

@jeferson1979 hola bro es que la rom instalo correctamente pero al arrancar se queda cargando en el logo y dura mas de 5 horas alli y no sigue que hago

FlySwit Designer said:
@jeferson1979 hola bro es que la rom instalo correctamente pero al arrancar se queda cargando en el logo y dura mas de 5 horas alli y no sigue que hago
Click to expand...
Click to collapse
You can press power button with vol - and enter recovery mode, then select format data (hint: you will loose your data), then things should work.
Make sure to follow wiki steps before install anything.

I am on the official build with the recommended gapps (MindtheGapps-latest version) installed.
I am getting the following error with I try to run Google Opinion Rewards:
google opinion rewards won't run without google play service which are not supported on your device
I have tried clearing data/cash for Google Play, Google Play Services and the Opinion Rewards, restarting and that doesn't help.
Any ideas/suggestions? Thank you in advance for your assistance.

ew said:
I am on the official build with the recommended gapps (MindtheGapps-latest version) installed.
I am getting the following error with I try to run Google Opinion Rewards:
google opinion rewards won't run without google play service which are not supported on your device
I have tried clearing data/cash for Google Play, Google Play Services and the Opinion Rewards, restarting and that doesn't help.
Any ideas/suggestions? Thank you in advance for your assistance.
Click to expand...
Click to collapse
How was the install procces? Some people said about similar stuff ( another kind of gapps issues) and what fixed was install rom, finsish this install, reboot to recovery and then install gapps. Otherwise, send us a log here if still remains bugging

jeferson1979 said:
How was the install procces? Some people said about similar stuff ( another kind of gapps issues) and what fixed was install rom, finsish this install, reboot to recovery and then install gapps. Otherwise, send us a log here if still remains bugging
Click to expand...
Click to collapse
Thanks for the assistance. For background, I was coming from the unofficial and upgraded to the official. I believe it was working, but I may have done something (and I don't know what) and it stopped working.
I even tried wiping the system partition and reinstalling - and that didn't help.
I wound up wiping my entire system (flashing back to stock) - and installing the official (including the recommended gapps) - and all is good.
And (by the way) I did reboot to recovery before installing gapps.
Thanks for the help. I guess this one will remain a bit of a mystery (as to what happened) but it is all working now.

ew said:
Thanks for the assistance. For background, I was coming from the unofficial and upgraded to the official. I believe it was working, but I may have done something (and I don't know what) and it stopped working.
I even tried wiping the system partition and reinstalling - and that didn't help.
I wound up wiping my entire system (flashing back to stock) - and installing the official (including the recommended gapps) - and all is good.
And (by the way) I did reboot to recovery before installing gapps.
Thanks for the help. I guess this one will remain a bit of a mystery (as to what happened) but it is all working now.
Click to expand...
Click to collapse
It's the annoying part of a release early days XD

Hi, I've installed both the mod and Gapps following the instructions on the website (I had a PixelExperience ROM before) and - from what I am seeing - all went smooth.
Thanks a lot for your effort.
P.S. Is there a Telegram channel for LineageOS?
edit: the only "weirdness" I've seen: two apps warn me that phone is rooted. For one I can continue the installation, for the other is not possible. Not a big issue, but this did not happen with the Pixel Experience ROM.
Thanks again.

Hello, guys!
I recently installed the official 1.19.1 ROM and the Gapps provided and I'm getting "Offline" even if I am connected on WiFi. Browsing on internet works perfecly, but I get the messages as on the image below:
Also, when I click in Google, from the Settings Menu, I get the message: Unable to start the App.
I think its something related to the Gapps.. Maybe?
Or the issue is because I'm not using a simCard at the moment?
Imma using the MindTheGapps-12.1.0-arm64-20220416_174313, on my Moto G6 Plus Evert, and used lineage-19.1-20220426-nightly-evert-signed zip package to format.
Is this a common issue?
I reinstalled the ROM just to be sure, but I still get this.

I have been on this ROM for a day now - and it is very smooth. No major issues and thanks to the OP for the time and support!
A few small items that I have mostly found workarounds for but wanted to mention them for anybody that is interested:
I really like TWRP over the lineage recovery. On LOS 18.1 I was able to flash TWRP and use it. That doesn't seem to be an option for 19.1. Even though I have turned encryption off (so the encryption is not an issue) - it seems like it doesn't boot properly after installing TWRP. So, I guess I need to live with lineage recovery.
The green flash & dot that comes up when location is used is really annoying. The dot not as much as the flash - especially since I have apps that use location all of the time and the flash is distracting and removes other elements on the notification bar. I was able to use the information https://forums.oneplus.com/threads/android-12-little-green-dot-location.1572637/ and https://forum.xda-developers.com/t/...nsor-indicator-microphone-and-camera.4388359/ to help things, however sometimes after a reboot I have to turn the switch back off in developer options. Bit of a pain, and I have not found a way to turn it off automatically through tasker.
Auto brightness - in dark my screen gets too dark. I have to raise it - and it doesn't seem to be learning to use a higher minimum - like some other versions of android.
Relatively speaking - these are minor and maybe just things that bug me. The ROM is very smooth, fast and much appreciated!

I also want to report what seems a minor bug: when the display auto-rotation is enabled, no icon is shown in the status bar, but instead an icon is shown when it is not. In stock version and Pixel Experience mod the feature had the opposite behavior (so an icon was shown only when auto-rotation was enabled).
Thanks again, all seems to work pretty well.

Mattew Rockstone said:
Hello, guys!
I recently installed the official 1.19.1 ROM and the Gapps provided and I'm getting "Offline" even if I am connected on WiFi. Browsing on internet works perfecly, but I get the messages as on the image below:
View attachment 5604917
Also, when I click in Google, from the Settings Menu, I get the message: Unable to start the App.
I think its something related to the Gapps.. Maybe?
Or the issue is because I'm not using a simCard at the moment?
Imma using the MindTheGapps-12.1.0-arm64-20220416_174313, on my Moto G6 Plus Evert, and used lineage-19.1-20220426-nightly-evert-signed zip package to format.
Is this a common issue?
I reinstalled the ROM just to be sure, but I still get this.
Click to expand...
Click to collapse
Same issue for me and my evert.

For the guys with the "offline" issue: flash rom, then reboot to recovery, then flash mindthegapps. This will solve your connection issue

now, 3 month later finish guarantee, my charger burned out
happy, becase i was in the same room and stop fire, if i wasnt-maybe burnt all house!!!!!
be carefull-when are you charging everething

ew said:
The green flash & dot that comes up when location is used is really annoying. The dot not as much as the flash - especially since I have apps that use location all of the time and the flash is distracting and removes other elements on the notification bar. I was able to use the information https://forums.oneplus.com/threads/android-12-little-green-dot-location.1572637/ and https://forum.xda-developers.com/t/...nsor-indicator-microphone-and-camera.4388359/ to help things, however sometimes after a reboot I have to turn the switch back off in developer options. Bit of a pain, and I have not found a way to turn it off automatically through tasker.
Click to expand...
Click to collapse
It is possible to disable the "green dot" when geolocation is used using the developers' options. I have an Italian-localized OS but it should be the last option in the menu, named sort of "Location indicator in the status bar". When the option is disabled, the green dot doesn't appear anymore and when an app uses the GPS only the standard icon is shown.
This thing has come handy with the last update (2022-05-17) since it introduces an annoying bug that should be fixed with the next update
Phone Services using location even when its turned off. (#4674) · Issues · LineageOS / issues / android · GitLab
Expected Behavior No app should be able to use location when its turned off and phone services app should not keep...
gitlab.com

the_15th said:
It is possible to disable the "green dot" when geolocation is used using the developers' options. I have an Italian-localized OS but it should be the last option in the menu, named sort of "Location indicator in the status bar". When the option is disabled, the green dot doesn't appear anymore and when an app uses the GPS only the standard icon is shown.
This thing has come handy with the last update (2022-05-17) since it introduces an annoying bug that should be fixed with the next update
Phone Services using location even when its turned off. (#4674) · Issues · LineageOS / issues / android · GitLab
Expected Behavior No app should be able to use location when its turned off and phone services app should not keep...
gitlab.com
Click to expand...
Click to collapse
Thanks for your help. I found that the switch in the developer options got reset after reboot.
The following is my solution as implemented in Tasker. I run this at system start.
Task: Green Dot Location Suppress (A12)
<need to have the following commands in the following sequence for it to work:
-device_config put privacy location_indicators_endabled false default
-device_config put privacy camera_mic_icons_enabled false default
-device_config put privacy camera_mic_icons_enabled true default
Per my testing, the commands need to be executed in the sequence listed above - otherwise it does not work.
see https://forums.oneplus.com/threads/android-12-little-green-dot-location.1572637/
https://forum.xda-developers.com/t/...nsor-indicator-microphone-and-camera.4388359/>
A1: Anchor
A2: Run Shell [
Command: device_config put privacy location_indicators_enabled false default
Timeout (Seconds): 0
Use Root: On
Use Global Namespace: On ]
A3: Run Shell [
Command: device_config put privacy camera_mic_icons_enabled false default
Timeout (Seconds): 0
Use Root: On
Use Global Namespace: On ]
A4: Run Shell [
Command: device_config put privacy camera_mic_icons_enabled true default
Timeout (Seconds): 0
Use Root: On
Use Global Namespace: On ]

[ROM][UNOFFICIAL][13] LineageOS 20 for Xperia X Compact

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
About LineageOS
LineageOS is a free, community built, aftermarket firmware distribution of Android 13, which is designed to increase performance and reliability over stock Android for your device.LineageOS is based on the Android Open Source Project, with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.All the source code for LineageOS is available in the LineageOS GitHub organization.And if you would like to contribute to LineageOS, please visit our Gerrit Code Review.You can also view the changelog for a full list of changes & features.Official LineageOS website : http://lineageos.orgAbout LineageOS Legal : http://lineageos.org/legal
Important Information
1. This ROM operates without ODM images, just follow the installation instructions.2. This ROM does not intended to support Google Camera, but you can try to play with some mods.
About FDE and FBEFull-disk encryption (FDE) has been completely deprecated since Android 13, and now we use software implementation of File-based encryption (FBE).FDE and FBE methods are incompatible with each other. FBE cannot decrypt data encrypted with FDE and cannot encrypt existing files. That's why you need to perform factory reset/format data (not just "wipe data") before switching between ROM's with different encryption methods.To make it a bit clear:- FDE (e.g. stock, LineageOS-16/19) -> FBE (LineageOS-20) -> NOT POSSIBLE! Format data is required.- FBE -> FBE -> POSSIBLE! You can update/upgrade using "dirty" installation as before, in case if encryption methods are the sameMoreover, to work with new encryption you need a recovery with appropriate support.Downloads Links
LineageOS 20:Unofficial: https://sourceforge.net/projects/loire-development/files/lineageos-20/kugoGoogle Applications (optional):MindTheGapps: https://androidfilehost.com/?w=files&flid=322935 (Android 13.0 -> arm64)XDA post about GApps: https://xda-developers.com/download-google-apps-gappsRecommended Recovery (optional):TWRP 3.x: https://forum.xda-developers.com/-/-t3793837
Flashing and updating
Before installation, please make sure you have read and understood everything correctly about FDE and FBE encryption methods.LineageOS clean install:
Download the latest build of LineageOS ROM
Full wipe and factory reset (recommended / backup to make sure not to loose data)
Flash the LineageOS ROM zip from the Recovery
Flash the GApps to have the Google Applications (optional)
Every additional zip you want to flash (optional)
Reboot
LineageOS update/upgrade:
Download the latest build of LineageOS ROM
Wipe cache and dalvik cache
Flash the latest LineageOS ROM zip from the Recovery
Every additional zip you want to flash (optional)
Reboot
You can also update using the built-in Updater (requires at least TWRP 3.6.x or LineageOS Recovery)
About the builds:
Kernel sources: https://github.com/Chippa-a/android_kernel_sony_msm8956
Issues and reports
Report issues only if you are using the ROM kernel
If an additional mod is installed, make sure it's unrelated, and mention it
Make sure the issue wasn't discussed earlier in the threads
Grab a logcat right after the problem has occurred
(Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing)
If it is a random reboot, grab /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0
(Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
Also thanks to:
The LineageOS Team
The SODP Team
Everyone involved in working and testing
Contributors
Chippa_a
ROM OS Version: 13.x
ROM Kernel: Linux 4.9.x
Version Information
Status: Beta

FEATURES AND ISSUES
Boot: Ok
Bluetooth: Unknown
WiFi: Ok
WiFi Hotspot: Unknown
RIL - Phone - Data: Ok
GPS: Ok
Camera: Unknown
Camcorder: Unknown
Lights: Ok
MicroSD: Ok
Accelerometer: Ok
Compass: Ok
Gyroscope: Ok
QTI sensors: Ok
Touchscreen: Ok
FM Radio: N/A
Fingerprint: Ok
Vibrator: Ok
Microphone: Ok
Audio & music: Ok
Bluetooth audio: Ok
NFC: Unknown (HCE: Unknown)
Kernel: Ok (WIP)
Graphics: Ok
3D Rendering: Ok
Clock: Ok
DRM: Unknown
Offline Charging: Ok
USB: Ok
USB Tethering: Unknown
USB OTG: Ok
Encryption: Ok
SEPolicies: Enforcing

It's amazing bro, i can't bealive my device got A13

It seems the device is working again - post removed

soomon said:
I installed this system, and at the 2nd reboot my phone is dead. completely dead. seems it has been bricked before I even could log into my google account.
It doesnt even react to power any more.
Of course the phone is old and wasnt used for a long time, so I dont know if it got bricked by the OS or the hardware.
but it's dead.
be careful people!
Click to expand...
Click to collapse
It's almost impossible to brick this device completely just by ROM, unless you're doing something very unusual or developer-related.
This ROM has been tested by user for more than two weeks and everything was fine. It also been tested by Xperia X users since March, there was nothing like that either... and there never was actually.
Anyway, there is no specific in your message, except "It doesnt even react to power any more". Try to get adb/fastboot modes, charge or flash stock firmware. If no luck, I'm pretty sure it's a hardware issue, probably battery or something else.

I was also thinking about this and it was hard for me to believe the custom OS could actually damage the hardware.
I am happy to report it seems to be the device itself that caused the issue and not the rom. Today it was working Since it is an old device I'm assuming it was a hardware issue, so I deleted my old post.
It's working perfectly now. thank you so much!

I'll install this asap. Cant belive that this device is live again. Im using it as main phone. Gonna post my experience with rom here. Cheers
Edit: Cant seems to make it work . i was on latest stock, did full wipe , installed clean los20 , no gapps no additional zipps . it goes past sony logo shows black screen and immediately restarts on that black screen . Any suggestions ?
Edit 2 : I could not boot to twrp , i needed to install it again after los20 zip, like there is no recovry ? Is that normal ?

After install this rom i found bugs on this rom A13 LOS 20:
-WIFI
-HOTSPOT
-TAP TO WAKE NOT WORK
- GPS can't lock
- NFC
Edit : after reinstall from Lineage 19 to Lineage 20 , Wifi , hotspot , Gps , working fine
Thanks for @Chippa_a and team , share and build rom for x compact

Deep sleep pretty good , keep it up

shandu98 said:
Edit 2 : I could not boot to twrp , i needed to install it again after los20 zip, like there is no recovry ? Is that normal ?
Click to expand...
Click to collapse
Do you have the latest TWRP offered on the other thread? If you get a boot loop back into TWRP you can try tapping restart to system which is an option within TWRP. If you still have problems after with a boot loop try a clean install by wiping dalvik, cache, system, internal storage, followed by formatting data, then reboot to TWRP flash the build and tap restart to system when finished.

my device sony x compact is stuck on twrp logo, is there any solution to fix it?
Note: before stuck on twrp logo, i want to downgrade to A12. but after I entered recovery by (power + vol-) the device was stuck at the twrp logo

Tri Akbar Fitriana said:
my device sony x compact is stuck on twrp logo, is there any solution to fix it?
Note: before stuck on twrp logo, i want to downgrade to A12. but after I entered recovery by (power + vol-) the device was stuck at the twrp logo
Click to expand...
Click to collapse
The same here. The solution for me: i flash stock Rom then Twrp and then los20. After flash los20 twrp stuck on logo, but i can use Los20. Many thanks for los20. Its a great rom.

Asta01 said:
The same here. The solution for me: i flash stock Rom then Twrp and then los20. After flash los20 twrp stuck on logo, but i can use Los20. Many thanks for los20. Its a great rom.
Click to expand...
Click to collapse
if I flash it to stockrom, does it need a TA file? because my TA file is missing.

Tri Akbar Fitriana said:
if I flash it to stockrom, does it need a TA file? because my TA file is missing.
Click to expand...
Click to collapse
I flash Stockrom with flashtool. I dont need TA file.

Tri Akbar Fitriana said:
if I flash it to stockrom, does it need a TA file? because my TA file is missing.
Click to expand...
Click to collapse
No.
Try lineage recovery it works for me, with twrp i get black screen

Chippa_a said:
Moreover, to work with new encryption you need a recovery with appropriate support.
Click to expand...
Click to collapse
For those who have issues with recovery after this ROM.
Please make sure you have installed latest unofficial version (3.7.0_12+) with support for the new FBE encryption method, as stated in OP. Older versions cannot decrypt data encrypted with this method!

Chippa_a said:
For those who have issues with recovery after this ROM.
Please make sure you have installed latest unofficial version (3.7.0_12+) with support for the new FBE encryption method, as stated in OP. Older versions cannot decrypt data encrypted with this method!
Click to expand...
Click to collapse
Thanks,with twrp 3.7.0_12 is twrp working.

Thank you chippa _a. The rom is amazing. I haven't found any bugs so far, and it's incredibly fast. A new life for the Xperia x compact. Thanks alot.

Thanks a lot for this rom! I running it for a few days and no bugs so far
I'm wondering which cam app is the best to use?
And I have one app which doesn't run because my phone is rooted, is there a solution for that?

SietZ said:
Thanks a lot for this rom! I running it for a few days and no bugs so far
I'm wondering which cam app is the best to use?
And I have one app which doesn't run because NY phone is rooted, is there a solution for that?
Click to expand...
Click to collapse
For me is Google cam port "MGC_8.2.204_Parrot043_V1" working perfect.

Database Info

welcome