[ROM] [9.0.0] LineageOS 16.0 [walleye] [unofficial] - Google Pixel 2 ROMs, Kernels, Recoveries, & Other

[ROM] [9.0.0] LineageOS 16.0 [walleye] [unofficial] - Google Pixel 2 ROMs, Kernels, Recoveries, & Other

{
"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"
}
LineageOS is a free and open-source operating system for set-top boxes, smartphones and tablet computers, based on the Android mobile platform.
**** This is an unofficial ROM.. Install at your own risk! ****
The ROM has been stable for me and I use it as a daily driver. However, if you encounter any instabilities or bugs, please do post in this thread.
Installation Instructions
First install, coming from stock
1. Before you start: Backup everything on your device before you start. You will delete all data during the installation.
2. Install the August 2019 factory image for the Pixel 2. I used Deuce's script for flashing.
3. Boot to TWRP (I used twrp-3.3.0-0)
4. Wipe data and 'Dalvik/'Art Cache' in TWRP - Wipe - Advanced Wipe
5. Install the zip and optionally install TWRP and reboot. Take note of the slot you installed the ROM to in the Reboot menu.
Upgrade to new version
1. Boot to TWRP
2. Flash the new zip that you downloaded from the links below (no need to wipe data)
3. Optionally flash TWRP
4. Reboot
What works:
Code:
Everything I have tried so far works:
-Camera/Video
-Phone calls
-Data
-WiFi
-PTP
etc.
August 2020
ROM:
lineage-16.0-20200821-UNOFFICIAL-walleye.zip
MD5: see ROM link
July 2020
ROM:
lineage-16.0-20200715-UNOFFICIAL-walleye.zip
MD5: see ROM link
June 2020
ROM:
lineage-16.0-20200610-UNOFFICIAL-walleye.zip
MD5: see ROM link
Device Sources
Wahoo
Muskie
Kernel Sources
Wahoo
Code:
[B]Changelog[/B]
20200821
+ Synced with LineageOS source
+ August 05, 2020 Android security patch level
20200715
+ Synced with LineageOS source
+ July 05, 2020 Android security patch level
20200610
+ Synced with LineageOS source
+ June 05, 2020 Android security patch level
20200511
+ Synced with LineageOS source
+ May 05, 2020 Android security patch level
20200415
+ Synced with LineageOS source
+ April 05, 2020 Android security patch level
20200311
+ Synced with LineageOS source
+ March 05, 2020 Android security patch level
20200212
+ Synced with LineageOS source
+ February 05, 2020 Android security patch level
20200116
+ Synced with LineageOS source
+ January 05, 2020 Android security patch level
20191214
+ Synced with LineageOS source
+ December 05, 2019 Android security patch level
20191124
+ Synced with LineageOS source
+ November 05, 2019 Android security patch level
20191015
+ Synced with LineageOS source
+ October 05, 2019 Android security patch level
20190927
+ Synced with LineageOS source
+ September 05, 2019 Android security patch level
20190810
+ Synced with LineageOS source
+ August 01, 2019 Android security patch level
20190707
+ Synced with LineageOS source
+ July 05, 2019 Android security patch level
20190610
+ Synced with LineageOS source
+ June 05, 2019 Android security patch level
+ New default LineageOS wallpaper
20190510
+ Synced with LineageOS source
+ May 05, 2019 Android security patch level
20190408
+ Synced with LineageOS source
+ April 05, 2019 Android security patch level
20190308
+ Synced with LineageOS source
+ March 05, 2019 Android security patch level
20190210
+ First release
+ February 05, 2019 Android security patch level
ROM OS Version: Linage 16.0 (Pie 9.0.0)
ROM Kernel: 4.4.116
XDA:DevDB Information
LineageOS 16.0 [walleye], ROM for the Google Pixel 2
Contributors
leqacy
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Based On: LineageOS
Version Information
Status: Testing
Created 2019-02-10
Last Updated 2019-02-10

Thanks:
 @AlaskaLinuxUser
 @jorgen2009
LineageOS Team

Reserved2

Thank you for your effort. Will there ever be an official release? If not, why do they not release even a 8.1 official?
I find it strange that LineageOS has still official nightly builds for even the very old nexus, but for the pixel2 there is nothing official.

RobertQc said:
Thank you for your effort. Will there ever be an official release? If not, why do they not release even a 8.1 official?
I find it strange that LineageOS has still official nightly builds for even the very old nexus, but for the pixel2 there is nothing official.
Click to expand...
Click to collapse
Thanks for your interest.
There will be an official release if a maintainer submits a request for an unofficial build to become official and gets accepted by LineageOS. Maintainers are people like me, who do this as a hobby, not the LineageOS team. So at some point my builds could become official, if I submit a request for review and my request gets accepted. In order to pass the review, the items on the quality control checklist need to be met. You can read more about the process on the LineageOS Website. This could be a starting point:
https://wiki.lineageos.org/device_requests.html
These are the device support requirements:
https://github.com/LineageOS/charter/blob/master/device-support-requirements.md
If you are interested in getting the Pixel 2 on the list of officially supported devices, then assisting me with the quality assurance is a great way to contribute.. Thus, I am grateful for everyone, who flashes my builds and posts feedback in this thread.

great stuff.
personally i dont understand why people want official builds of roms, unofficial are just as good as official. they may not pass the official standards or requirements but as long as everything is working it should not be a problem.
official is just a stamp these days, people need to understand that. the code base is same for official or unofficial. Plus, official means a responsibility on people who do it for fun and for free.
heck even devices with official los members working on them (moto x4, poco f1) dont have official los builds.

Does this come with gapps? If so, would it be possible to get a build without? Also thanks for the release!

Shmi117 said:
Does this come with gapps? If so, would it be possible to get a build without? Also thanks for the release!
Click to expand...
Click to collapse
This build is without gapps.

leqacy said:
The ROM has been stable for me for the short time I've been running it. However, if you encounter any instabilities or bugs, please post in this thread.
Click to expand...
Click to collapse
Well done! Great work! :highfive:

I'll keep looking for any bugs
Substratum and Bluetooth working!
The only problem I have had is with data transfer tool.

Any possibility that you could please compile 15.1 as well? Xposed isn't supported on Pie, and there's a PNG vulnerability looming around.

Lineage OS 15.1
YandereSan said:
Any possibility that you could please compile 15.1 as well? Xposed isn't supported on Pie, and there's a PNG vulnerability looming around.
Click to expand...
Click to collapse
Here is an unofficial build of lineage OS 15.1 for walleye. (Not by this compiler). If they decide not to support 15.1 then this build is relatively stable.
https://forum.xda-developers.com/pixel-2/development/rom-lineageos-15-1-t3781015

YandereSan said:
Any possibility that you could please compile 15.1 as well? Xposed isn't supported on Pie, and there's a PNG vulnerability looming around.
Click to expand...
Click to collapse
Regarding PNG vulnerabilities: These vulnerabilities exist(ed) in both LineageOS 16 and 15.1. They were patched with the February 2019 security patch. This patch is contained in my build, which is linked in the first post.
You can check for the patch level in Settings->About phone->Android version. The current status in my build is: February 5, 2019. The link directs you to the list of monthly updates. If you select February 2019 in the list, you will see the 3 PNG vulnerabilities you are referring to are already patched.
Framework
The most severe vulnerability in this section could enable a remote attacker using a specially crafted PNG file to execute arbitrary code within the context of a privileged process.
CVE References Type Severity Updated AOSP versions
CVE-2019-1986 A-117838472 [2] RCE Critical 9
CVE-2019-1987 A-118143775 [2] RCE Critical 7.0, 7.1.1, 7.1.2, 8.0, 8.1, 9
CVE-2019-1988 A-118372692 RCE Critical 8.0, 8.1, 9
Click to expand...
Click to collapse
I hope that addresses your security concern with the LineageOS 16.0 build.
Adamzapple_ said:
Substratum and Bluetooth working!
The only problem I have had is with data transfer tool.
Click to expand...
Click to collapse
Thank you for testing. I just tested with the data transfer tool on macOS. I was able to transfer files to and from the device without any problems, after setting USB Preferences to "File Transfer".
What problems were you having exactly and on which OS?
I'll address other points in later posts.

leqacy said:
Thank you for testing. I just tested with the data transfer tool on macOS. I was able to transfer files to and from the device without any problems, after setting USB Preferences to "File Transfer".
What problems were you having exactly and on which OS?
I'll address other points in later posts.
Click to expand...
Click to collapse
The transfer tool refused to respond. However I just tried it again and it worked just fine. Don't know what was happening yesterday but it refused to work at all. If I have the problem again I will provide a logcat.

First of all i'd like to thank you for your efforts in building this ROM and sharing your work with the community! It's really cool to have recent updates of LineageOS for the Pixel 2.
You have picked up the great work from Jorgen2009 as it seems but unlike the original thread you do not provide any details on wether if and how this ROM is dependend on a specific(?) version of the vendor partition. I assume that one has to flash Google Factory Image from february in order to use this ROM?
Furtheremore i'd like to know about what Jorgen2009 has called "the Pixel specific bits for unlimited photo upload for instance". Unsure what this means in technical detail but it's definatly something i would want to preseve when moving to this ROM. For example, the ability to install original Google Camera from PlayStore and use all of its Pixel related features seems somewhat tricky to achive. Is this solely related to GApps or is there some relation to the ROM itself? And if so, is that included here?
Last but not least about GApps itself. As i have understood from the former maintainer getting them work with this ROM was also some kind of a challenge. I'm going to install MindTheGApps on top of this so any hints are highly appreciated.
I guess i'll create some backups now and then just give it a try to migrate my device from Jorgen2009's november release to this ROM.

Wow, that was easy! I've successfully migrated my existing installation (almost) without loosing any data.
So here's what i did:
1. Install february factory image walleye-pq2a.190205.002-factory-781881b5.zip without wiping data
2. Boot into twrp 3.2.2-1 via fastboot
3. Flash lineage-16.0-20190210-UNOFFICIAL-walleye.zip without wiping cache nor data
4. Flash twrp-pixel2-installer-walleye-3.2.3-1.zip
5. Flash Magisk-v18.1.zip
6. Flash MindTheGapps-9.0.0-arm64-20190122_071653.zip (official MindTheGapps-9.0.0-arm64-20190203_191233.zip did not work for me probably because of this)
7. Reboot
Only a few Google apps kept force closing such as Maps, Google Camera and YouTube (i dont use any other Google Apps) but PlayStore worked right away so i simply reinstalled them. :victory:

YandereSan said:
Any possibility that you could please compile 15.1 as well?
Click to expand...
Click to collapse
At the moment my focus is on 16.0. If there is more demand for 15.1 I may consider running a build.
bleh815 said:
First of all i'd like to thank you for your efforts in building this ROM and sharing your work with the community! It's really cool to have recent updates of LineageOS for the Pixel 2.
You have picked up the great work from Jorgen2009 as it seems but unlike the original thread you do not provide any details on wether if and how this ROM is dependend on a specific(?) version of the vendor partition. I assume that one has to flash Google Factory Image from february in order to use this ROM?
Click to expand...
Click to collapse
Thank you for your feedback! This is an important point and I edited the installation instructions to include this. I had February 2019 stock installed before flashing my LineageOS build, so I did not encounter any problems with regards to the vendor image, but if you have an older vendor image on your phone you may have problems, since there were some API changes lately.
bleh815 said:
Furtheremore i'd like to know about what Jorgen2009 has called "the Pixel specific bits for unlimited photo upload for instance". Unsure what this means in technical detail but it's definatly something i would want to preseve when moving to this ROM. For example, the ability to install original Google Camera from PlayStore and use all of its Pixel related features seems somewhat tricky to achive. Is this solely related to GApps or is there some relation to the ROM itself? And if so, is that included here?
Click to expand...
Click to collapse
So far my build does not contain the modifications from jorgen2009. I started my build on a clean plate, so in terms of modifications my build does not have a lot in common with jorgen, the LineageOS and device tree is in common, of course. My build does not contain Pixel specific modifications at the moment.
bleh815 said:
Last but not least about GApps itself. As i have understood from the former maintainer getting them work with this ROM was also some kind of a challenge. I'm going to install MindTheGApps on top of this so any hints are highly appreciated.
Click to expand...
Click to collapse
I went down the microG path and got GmsCore working.

Does this contain the squeeze for assistant functionality?
I doubt it but honestly, this is the one feature that's keeping me from switching to a custom rom
Additionally what else would I lose in terms of base features or is it everything?
(Sorry I have a decent amount of experience with Lineage and Custom Roms but this is the first time I have ever been able to get a phone with an unlocked bootloader)

OrangeFlare said:
Does this contain the squeeze for assistant functionality?
I doubt it but honestly, this is the one feature that's keeping me from switching to a custom rom
Additionally what else would I lose in terms of base features or is it everything?
(Sorry I have a decent amount of experience with Lineage and Custom Roms but this is the first time I have ever been able to get a phone with an unlocked bootloader)
Click to expand...
Click to collapse
No custom ROMS support the squeeze feature. I agree with you, I can't give it up. It's too handy! :highfive:

nolimit78 said:
No custom ROMS support the squeeze feature. I agree with you, I can't give it up. It's too handy! :highfive:
Click to expand...
Click to collapse
https://www.xda-developers.com/google-pixel-active-edge-squeeze-feature-custom-roms/
:fingers-crossed:
I may start messing around with this and see if I can get a build of LineageOS 16.0 to work with this

Related

[BETA][ROM][8.1.0][UNOFFICIAL]LineageOS 15.1 [20 Sep 2020]

{
"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"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 8.1 (Oreo), 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. You can also view the Changelog for a full list of changes & features and my sources linked below.
Bugs:
VoLTE (IDK How it broke suddenly, but will be looked at)
SELinux
Note:
LineageOS LiveDisplay does work but I recommend keeping it disabled because it causes lags in many cases.
I don't have any proper fix for it. If you want to use the Night Mode, please use a third party app which utilizes the KCAL driver or overlays.
All these builds are 32 bit.
Moto Camera from Google Play doesn't work, so either use a modded moto camera apk or use the camera app built in.
Instructions :
Download the latest build and gapps
Boot to recovery
Flash the latest build
Boot to recovery again
Flash gapps
Reboot
Downloads :
Builds :
Sourceforge
Root addon :
Latest Stable Magisk Zip
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
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)
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
XDA:DevDB Information
[ROM][UNOFFICIAL][athene][8.1.0] LineageOS 15.1, ROM for the Moto G4/Plus
Contributors
LineageOS Team of course!
Team athene:
rajatgupta1998
Nikit
lcrd512
golden-guy
Jleeblanch
Our former developers:
vache, rahulsnair, SileshNair, Shreps, regalstreak, ashwin007
Other developers: Alberto97, squid2, flar2, oadam11 , LineageOS team and all other contributors whom I might have missed.
All other friends and supporters in the XDA and Motorola Community! :victory:
Source Code:
LineageOS ROM Source
Device specific sources:
Device tree: https://github.com/rajatgupta1998/android_device_motorola_athene
Kernel source: https://github.com/rajatgupta1998/android_kernel_motorola_msm8952
Vendor blobs: https://github.com/rajatgupta1998/vendor_motorola_athene
ROM OS Version: Android 8.1.0 Oreo
Version Information
Status:Beta
XDA:DevDB Information
LineageOS 15.1 Athene, ROM for the Moto G4 Plus
Contributors
rajatgupta1998, @Nikit
Source Code: http://github.com/lineageos
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Latest Stock firmware
Based On: LineageOS
Version Information
Status: Beta
Beta Release Date: 2020-09-20
Created 2018-03-25
Last Updated 2020-09-20

Changelog Timeline
Major items to be concerned about. Can say the HIGHLIGHTS. Check the commits on my Github for more details.
16 Aug 2020
05 Aug 2020 Security Patch
Bluetooth stack update from Stock O 8.1
Add Qcom ANT+ Blobs
Update aptX, aptX HD Blobs
Update power profile from stock O 8.1
Update few overlays from stock O 8.1
07 April 2020
05 April 2020 Security Patch
Enable some missing kernel configs
Regenerate proprietary-files.txt and follow it
Update ADSP
Build Health HAL
Update Alarm and Health blobs
Fix audio callibration files loading
Update Audio blobs and configs
Remove unnecessary code
05 Jan 2020
Camera delays are fixed upto an extent
LiveDisplay is back but still lags. Since few people tend to use it, enabled it anyway. But if you get irritated by the lags, keep it disabled.
December 2019 Security Patches are here
12 Oct 2019
October Security Patches are here
08 Sep 2019
05 September 2019 Security Patch
25 Aug 2019
Kill LiveDisplay (Only Outdoor mode will work from now on, removed the night mode color shift because it causes severe lags in many cases)
Switch to QTI perf stack from stock O
Also add QTI I/O Prefetcher.
Switch back to Motorola's stock kernel for now with basic driver functionality like KCAL Support and fingerprint as home button.
08 Aug 2019
August Security Patch
Fix loading of IMS Shim
Minor code cleanup
04 Aug 2019
Fix video recording and QS Flash light toggle finally.
07 July 2019
July Security Patch merged
Disabled some useless logging
30 June 2019
Update and fix the DRM HAL for playing like Netflix
24 June 2019
Use a binderized biometric HAL
Update fingerprint blobs and JARs from stock O
Update keylayout for FPC1020 Touch fingerprint sensor driver from stock O
Add a custom trim value from stock O
Use CAF QTI Power HAL now
Update Media DRM HAL and QSEECOM
Update ADSP Blobs from stock O, hence the ROM now uses updated Qualcomm's Hexagon DSP blobs for Oreo.
Enable and update Media CAS HAL, Gatekeeper and Keymaster HAL
Update the blobs for the above mentioned HALs
Enable Pinner service: Pins key files into memory to prevent having to fetch from flash after boot. Improves system performance by preventing page cache thrash.
Switch to the Motorola's stock O kernel source (No, Video Camera doesn't work right now :3 )
Merge latest sources from CAF: LA.BR.1.3.7-05010-8976.0
Merge all the relevant patches from AOSP (Google's kernel/common for linux-3.10)
Linux upstream on top of this with msm-3.10 as 3.10.108
All updates to various drivers like cpufreq, mdss, audio and more and more.
Various fixes and updates to the Wifi drivers from CAF Pie sources for Qualcomm Atheros Prima/Pronto WLAN module.
Various patches to the memory subsystem and updates to stuff like ZRAM, ZSWAP, VNSWAP
Updates for Pie's ext O_TMPFILE support
Enable support of SDFAT driver v2.1.8
Multiple changes to the binder interface, kernel functions and other upstream patches.
16 June 2019
June 05 2019 Security Patches
LineageOS upstream
20 April 2019
* Update audio, display, graphics and actuator blobs from stock O
25 March 2018: Initial Changes from Nikit's build
* Merge 5 March 2018 security patch with AOSP 8.1.0_r18 release
* Increase ZRAM to 1 GB
* Disable Speaker Protection
* Disable Auto Brightness and Live Display on first boot
* Fix Safetynet temporarily : Use walleye's (Google Pixel 2) build fingerprint.
* Enable Spectrum Support and port Lightning Blade to Oreo
* Add sound control (maybe broken)
* Allow home button to be changed for various actions.
* Add more CPU frequencies.
* Disable Wakelocks by default
* TCP Congestion Avoidance controls ( not tested )
* Update VoLTE properties
* Use LZMA Compression for Recovery Ramdisk
* Disable add_random from kernel. Not required on SSDs. (eMMCs in our case)
* Enable Arch Power
* Adreno idler ramps down more aggressively now
* Enhance linux topology for multicore decision making
* Enable Arch Power
* Some speed and time efficient changes :3 hard to explain here.
* LineageOS upstream
* Use latest HALs from CAF release LA.BR.1.3.7-03810-8976.0

Reserved
Screenshots

@Nikit Just to confirm, this is correct?
And @rajatgupta1998 when you say "take over" do you mean that nikit is stopping? And can I help out? I have got much of the selinux going on my thread.
Sent from my athene using XDA Labs

hackintosh5 said:
@Nikit Just to confirm, this is correct?
And @rajatgupta1998 when you say "take over" do you mean that nikit is stopping? And can I help out? I have got much of the selinux going on my thread.
Sent from my athene using XDA Labs
Click to expand...
Click to collapse
Yep I have his permission to continue! Also, SE Linux is not on the top most priority right now for me. But yes, surely SELinux will be set to Enforcing soon. Omni and probably your build got it to boot, so yeah; I'll look over it. Hit me up on telegram or email :good:

hackintosh5 said:
@Nikit Just to confirm, this is correct?
And @rajatgupta1998 when you say "take over" do you mean that nikit is stopping? And can I help out? I have got much of the selinux going on my thread.
Click to expand...
Click to collapse
Yes. I don't own this device anymore, so @rajatgupta1998 will continue the development from now.

Ok, thanks for the confirmation!
Sent from my athene using XDA Labs
---------- Post added at 12:20 PM ---------- Previous post was at 12:11 PM ----------
What is "lightning blade / spectrum"
Sent from my athene using XDA Labs

rajatgupta1998 said:
Screenshots
Click to expand...
Click to collapse
can you remove that device is HD capable notification please? & Thanks for the great work to you and Nikit...!

Any chance of getting gcam HDR+ working.

This build has memory leak fixes?

hackintosh5 said:
What is "lightning blade / spectrum"
Click to expand...
Click to collapse
Take a look here, this should explain it.
https://github.com/rajatgupta1998/a...mmit/9e47c5bdff8d5eaed4716b53a9650bfce239031c
BTW maybe you could build an building aliance and help out togehter...
Sent from my Moto G4 using XDA Labs

sgspluss said:
Take a look here, this should explain it.
https://github.com/rajatgupta1998/a...mmit/9e47c5bdff8d5eaed4716b53a9650bfce239031c
BTW maybe you could build an building aliance and help out togehter...
Click to expand...
Click to collapse
Ok, looks like this will need LOTS of work to have sepolicy.
@Rajagupta1998 two things. Can I call you a shorter name as I'm on mobile?, and it would be great to form an "alliance" if you are cool with it!
Sent from my athene using XDA Labs

An aliance is just an idea, bundle both knowlegends in one rom is better, than build 2 roms with different bugs.
Just a thought but you know what you do
Sent from my Moto G4 using XDA Labs

Can i dirty flash this over Nikit's build? I know it's better to clean flash, just asking

Josercl said:
Can i dirty flash this over Nikit's build? I know it's better to clean flash, just asking
Click to expand...
Click to collapse
Yes, you can as it is based off the same sources, although much stuff may not work.
Sent from my athene using XDA Labs

Josercl said:
Can i dirty flash this over Nikit's build? I know it's better to clean flash, just asking
Click to expand...
Click to collapse
hackintosh5 said:
Yes, you can as it is based off the same sources.
Click to expand...
Click to collapse
Not really recommended. Lots of changes from Nikit's build. Check post 2 for details.

The One Plus Camera does not work flawllessy i ger Green Photos and iwhen i tap the preciew of the photn i took it says no photos

Notification bar drop down lags event after turning off live display.

I'm too tempted, is it daily driver capable?

teckgiik101 said:
I'm too tempted, is it daily driver capable?
Click to expand...
Click to collapse
Based on other 8.1 ROMs this one Is pretty good. Same flashlight issue that is on the other ROMs and you can fix the memory leak by making a reboot when its neccesary. Also, the implementation of Spectrum Is helpful.
Any other doubts, ask me, im on it and i will till tomorrow.

[ROM]LineageOS-16.0 + LineageOS-17.1[Joan][Unofficial]

{
"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"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android, 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. You can also view the LineageOS Changelog for a full list of changes & features. For a changelog of changes to my builds, they can be found at this post below.
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.
*/
This is now a "joan" build! This means this is universal and should boot on all LG v30 devices that a custom recovery can be installed to. This includes the illusive h932 model!
The name of "joan" comes from the code name used by LG in a lot of their source code for this device.
BIG SHOUTOUT TO TO SGCMarkus! A lot of this would not be possible without the work he continues to do on these devices.
What's working:
RIL (Calls, SMS, Data)
Fingerprint
Wi-Fi
Bluetooth
Camera
Video Recording
Video Playback
Audio
Sensors
Flash
GPS
DAC
Vibration
Selinux permissive (Selinux has issues.. See FAQ)
What's not working:
VOLTE does not work on either ROM
VOWIFI does not work on either ROM
Wifi display on Lineage 17.1
Tell me
Where are the features?
LineageOS is in development process so don't complain about xyz features missing.
Instructions:
Download the build
Reboot to recovery
Flash the latest build
Reboot
V30 Telegram group chat
Downloads:
17.1: Universal builds can be found at GitHub
This now should boot on any LG v30 including h932!
This release requires pie firmware to be flashed.
Make sure to flash the correct firmware for your model of LG v30.
16.0:
Universal builds can be found at GitHub
This now should boot on any LG v30 including h932!
For now this release requires oreo firmware to be flashed.
Make sure to flash the correct firmware for your model of LG v30.
Sources:
Universal Device Tree: joan
Kernel: msm8998
Vendor: lge
lineage-16.0/17.0 branch
XDA:DevDB Information
[ROM]LineageOS-16.0 + LineageOS-17.0[Joan][Unofficial], ROM for the LG V30
Contributors
ShapeShifter499, https://github.com/LineageOS/
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: Oreo (LOS 16.0), Pie (17.1)
Based On: LineageOS
Version Information
Status: Alpha
Created 2020-01-29
Last Updated 2020-10-03
Donations
This ROM is released for free but a lot of time goes into making this work.
The cost of running a computer 24/7 to compile these builds for everyone isn't free either.
If you'd like to donate to support this project you can do so below.
Ko-fi/Paypal: https://ko-fi.com/shapeshifter499
XDA:DevDB Information
[ROM]LineageOS-16.0 + LineageOS-17.1[Joan][Unofficial], ROM for the LG V30
Contributors
ShapeShifter499, SGCMarkus, rashed97
Source Code: https://github.com/LineageOS/
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Oreo (16.0), Pie (17.1)
Based On: LineageOS
Version Information
Status: Alpha
Created 2020-01-29
Last Updated 2020-10-04

Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
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 dmesg . (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues.
Builds are done nightly if possible. The changelogs below get updated when there is a major change by me that fixes an issue with LG v30s.
Changelogs
LOS 17.1 Release 10.14.2020
Updates LOS Sources (October 2020 Security Patch, and some other features)
Change device fingerprint to pass SafetyNet
LOS 16.0 Release 10.14.2020
Updates LOS Sources (October 2020 Security Patch, and some other features)
Change device fingerprint to pass SafetyNet
LOS 17.1 Release 10.03.2020
Rename build to joan. This is now a unified build that should work universally on all LG v30s there are.
Updates LOS Sources (September 2020 Security Patch, and some other features)
Fix offline charging issue
Downrev audio to 4.0, fixes some audio related crashes
joan-common: Fix qti_whitelist typo
LOS 16.0 Release 10.03.2020
Rename build to joan. This is now a unified build that should work universally on all LG v30s there are.
Updates LOS Sources (September 2020 Security Patch, and some other features)
Set SELinux in kernel to permissive.
LOS 16.0 Release 09.03.2020
Updates LOS Sources (August 2020 Security Patch, and some other features)
Fix AVC reset bug for DAC.
LOS 16.0 Release 06.29.2020
Updates LOS Sources (June 2020 Security Patch, and some other features)
joan-common: Fix qti_whitelist typo
Add Spint APNs fix
LOS 16.0 Release 05.01.2020
Updates LOS Sources (April 2020 Security Patch, and some other features)
Added Samsung sdFAT driver to support exFAT formated SD Cards with help from @SGCMarkus, for both h930 and h932 builds.
Enable F2FS support for both h930 and h932 builds.
LOS 16.0 Release 02.08.2020
Updates LOS Sources (February 2020 Security Patch, and some other features)
joan-common: Readd required vendor prop for oreo blobs
LOS 16.0 Release 02.07.2020
Updates LOS Sources (January 2020 Security Patch, and some other features)
joan-common: Fix FM
LOS 16.0 Release 01.29.2020
Updates LOS Sources (January 2020 Security Patch, and some other features)
joan-common: Fix NFC configuration

Frequently Asked Questions:
Q. Can this ROM be flashed through TWRP?
A. Yes, proceed with the latest TWRP image
Q. Sounds good. How can I contribute to project?
A. Test the build as much as you can and report bugs which can be reproduced with exact steps and are not random.
Q. How to disable "Apps running in background" dialog?
A. When you see the dialog, long press on it and select "Settings". From there, you'll have a toggle to disable it.
Q. Which Models are supported?
A. So far it works well on the H930(G/D/DS), US998, VS996 and LS998. H932 works too, use the .zip for that model. Other devices may bootloop.
Q. Help, my H931/H933 is bootlooping!
A1. For H931 please go to https://forum.xda-developers.com/lg-v30/how-to/running-h930-aosp-rom-us998-converted-t3889320
A2. For H933 please go to https://forum.xda-developers.com/showpost.php?p=78183349&postcount=2
Q. What is up with SELinux?
A. There are a lot of SELinux permissions that have not been properly added. If you experience any issues try setting the kernel to permissive mode first. If you continue to experience issues after that. Then take logs and let me know. To set permissive mode flash this zip in TWRP or other custom recovery: https://zackptg5.com/downloads/Kernel-Sepolicy-Patcher.zip Make sure to select permissive with volume buttons. This should be flashed after every new ROM release unless otherwise stated.
Q. Any other resources I should be aware of?
A. Check out this mega thread on troubleshooting LG v30 issues by @tech_infinity https://forum.xda-developers.com/lg-v30/how-to/detailed-guide-aosp-roms-issues-solution-t4002535

RESERVED

can you please provide rom link ?

toocool4all said:
can you please provide rom link ?
Click to expand...
Click to collapse
I did, they are at my github. https://github.com/ShapeShifter499/LG_v30-LineageOS_Manifest/releases Check the list for the latest build and make sure it's correct for your device. H930 is universal and H932 is ONLY for T-Mobile

Hey,
thx for your time in developing and building this ROM for our beloved LG V30!
Anyway: Why do you build again a new LOS "16.0" and not work together with @SGCMarkus on "17.1" Release?
Just a thought...

FcBayernMinga said:
Hey,
thx for your time in developing and building this ROM for our beloved LG V30!
Anyway: Why do you build again a new LOS "16.0" and not work together with @SGCMarkus on "17.1" Release?
Just a thought...
Click to expand...
Click to collapse
Because @SGCMarkus has moved on to 17.1, so he can work on this 16 and fix stuff. Then, move on to 17.1.
He's still figuring it all out. Something to practice on?
I'm not speaking for the Dev. He can answer himself, but that seems the simplest explanation.

FcBayernMinga said:
Hey,
thx for your time in developing and building this ROM for our beloved LG V30!
Anyway: Why do you build again a new LOS "16.0" and not work together with @SGCMarkus on "17.1" Release?
Just a thought...
Click to expand...
Click to collapse
I was talking with @SGCMarkus and he mentioned wanting to focus all his efforts at getting 17 working. But 16 will still be supported for sometime and doesn't have as many changes in store to work around. It's much easier to iron out and get fully working with little to no bugs. But we are sort of working towards the same goals. If there is anything I happen to find about getting things working I'll let him know, I hope he does the same.

Thanks for doing this. I'm not ready to move on to 17.0 because of the issues and have been a little bummed that the other 16.0 ROM hasn't been updated since I first installed it (I got the phone in August). I've missed the fun of updating the ROM regularly that's part of the reason why I picked this model. Even if I don't notice any differences, it makes me happier knowing that I have a more recent LOS build.

Thank you for the updated builds ?
Is there any chance of Pie blobs builds happening?

mishamosher said:
Thank you for the updated builds ?
Is there any chance of Pie blobs builds happening?
Click to expand...
Click to collapse
+1 Thank You @ShapeShifter499!
gf's H930DS was unfortunately updated to stock pie at some point, so it's either Stock or Alpha LOS17. Would this work, it would be perfect.
@ShapeShifter499
> I was talking with @SGCMarkus and he mentioned wanting to focus all his efforts at getting 17 working.
That's interesting, haven't seen any updates from Markus on git, telegram or xda in a while.

Hujkis said:
+1 Thank You @ShapeShifter499!
gf's H930DS was unfortunately updated to stock pie at some point, so it's either Stock or Alpha LOS17. Would this work, it would be perfect.
@ShapeShifter499
> I was talking with @SGCMarkus and he mentioned wanting to focus all his efforts at getting 17 working.
That's interesting, haven't seen any updates from Markus on git, telegram or xda in a while.
Click to expand...
Click to collapse
Markus made a los17.1 build but that had camera issues so didn't release it.
Don't worry Markus is still maintaining LOS for v30
For los17 is not just change in android version but for v30 we've switched from oreo blobs to pie blobs. That's why there are some issues and are taking time to resolve.

Hujkis said:
+1 Thank You @ShapeShifter499!
gf's H930DS was unfortunately updated to stock pie at some point, so it's either Stock or Alpha LOS17. Would this work, it would be perfect.
@ShapeShifter499
> I was talking with @SGCMarkus and he mentioned wanting to focus all his efforts at getting 17 working.
That's interesting, haven't seen any updates from Markus on git, telegram or xda in a while.
Click to expand...
Click to collapse
Been busy with university (exams and so on...), and during christmas holiday kinda had no motivation todo something lol
But now im on semester break, and already started to prepare to start working on LOS17.1

Markus, first of all thank you for all your hard efforts and dedication to this ROM. I was wondering whether the static noise when video calling was fixed on LOS16. If not I plan on switching over to LOS17. Thank you and God bless ?

jkim204 said:
Markus, first of all thank you for all your hard efforts and dedication to this ROM. I was wondering whether the static noise when video calling was fixed on LOS16. If not I plan on switching over to LOS17. Thank you and God bless
Click to expand...
Click to collapse
That bug is present on both los16 and los17, hasn't been fixed yet.

tech_infinity said:
That bug is present on both los16 and los17, hasn't been fixed yet.
Click to expand...
Click to collapse
Ahh that's sad news. Thank you though. Are all other custom ROMs the same way?

jkim204 said:
Ahh that's sad news. Thank you though. Are all other custom ROMs the same way?
Click to expand...
Click to collapse
All other custom ROMs are based on sources by SGCMarkus so any source bugs will be present on all ROMs!
Basically if something is broken on LOS for v30 then it'll most probably be broken on all other ROMs

tech_infinity said:
All other custom ROMs are based on sources by SGCMarkus so any source bugs will be present on all ROMs!
Basically if something is broken on LOS for v30 then it'll most probably be broken on all other ROMs
Click to expand...
Click to collapse
In Havoc 3.1 when connecting the phone to the usb of the PC does not recognize it, do you know if it is only a Havoc bug or for all Q roms? thanks

Letsweb said:
In Havoc 3.1 when connecting the phone to the usb of the PC does not recognize it, do you know if it is only a Havoc bug or for all Q roms? thanks
Click to expand...
Click to collapse
I've had no issues connecting to PC on Q roms

[ROM][dragon][UNOFFICIAL][crDroidAndroid-13.0][v9.4]

RESERVED

The last crDroid build for the next time ..
It's based on Lineage-17.1 - we use the same device/kernel/vendor sources for dragon.
Including March security updates and DragonParts app for WiFi country code.
Moved to androidfilehost.com now ..
crDroidAndroid-10.0-20200308-dragon-v6.4.zip
There will be no regular updates .. just some builds from time to time !
Cheers

followmsi said:
The last crDroid build for the next time ..
Click to expand...
Click to collapse
First of all, thank you so much for all your work man, I just saw that you not only maintain official LOS for dragon and this crDroid port but also commit to official TWRP. I don't know how you do all this, but I admire and applaud it.
Two quick questions:
1. GApps are optional, right?
2. Do I flash Magisk after first boot (as described in OP under "Pre-Installation") or right after ROM (as described in OP under "First time installation")?
Edit:
Ok, I just couldn't wait and flashed it. To answer my own questions:
GApps are indeed optional and I flashed Magisk only after booting crDroid for the first time.
@ followmsi
So far I encountered the following problems:
1. A lot of artifacts/flickering/flashing of the UI, looks like refreshes/repaints that get stuck half-way. Sometimes it is impossible to e.g. use the keyboard because of this. If you want I can provide photos, but it should be pretty easy and obvious to reproduce this unless there is something seriously wrong with my installation.
2. Booting into crDroid only works every other time or so, it often freezes on the large Google logo screen. Holding the power button until it shuts off mostly fixes the problem and it boots successfully on the next try, but sometimes even a third try is needed.
Apart from these problems, first impression is very good. Nice to see Android 10 with lots of customization on the good old dragon
Thanks again and let me know if I can be of assistance.

One more build ..
crDroidAndroid-10.0-20200424-dragon-v6.5.zip
Changes:
- Google security updates -> April 2020 (android-10.0.0_r33)
- Turned off SoftAP MAC randomization
- Reverted Kernel MAC address hack -> to prevent boot problems.
- Changed kernel config for USB tethering
- Kernel: Added "fix cpu frequency limitation"
- Latest crDroid changes for Android 10
Enjoy

When using Colour calibration in LiveDisplay, the screen will flicker abnormally

followmsi said:
One more build ..
crDroidAndroid-10.0-20200424-dragon-v6.5.zip
Changes:
- Google security updates -> April 2020 (android-10.0.0_r33)
- Turned off SoftAP MAC randomization
- Reverted Kernel MAC address hack -> to prevent boot problems.
- Changed kernel config for USB tethering
- Kernel: Added "fix cpu frequency limitation"
- Latest crDroid changes for Android 10
Enjoy
Click to expand...
Click to collapse
I've been using this since your first test build. One of the better roms out there.
Considering your lack of time with your busy schedule, I really appreciate it!
Thanks! ??

122877087 said:
When using Colour calibration in LiveDisplay, the screen will flicker abnormally
Click to expand...
Click to collapse
Works normally for me.

A few months later ..
crDroidAndroid-10.0-20200811-dragon-v6.9.zip
Changes:
- Google security updates -> August 2020 (android-10.0.0_r41)
- Latest device and kernel changes for dragon.
- Latest crDroid changes for Android 10
Enjoy

followmsi said:
A few months later ..
crDroidAndroid-10.0-20200811-dragon-v6.9.zip
Changes:
- Google security updates -> August 2020 (android-10.0.0_r41)
- Latest device and kernel changes for dragon.
- Latest crDroid changes for Android 10
Enjoy
Click to expand...
Click to collapse
I know you're quite busy and I expect nothing, so I really appreciate this!
Thank you! ??
Edit: Just an FYi, a dirty flash from CR 6.5 to 6.9 was buggy. Might need a clean flash.
Also, Magisk Canary didn't want to flash. Tried multiple methods. Not a big deal because Magisk betta worked just fine.
Everything is running well,
Thanks!

Let's move to Android 11 ..
crDroidAndroid-11.0-20201219-dragon-v7.1.zip
Changes:
- Initial Android 11 build for dragon device
- Google security updates -> December 2020
- Latest device changes for dragon
- Latest crDroid sources
Enjoy

Awesome, Thanks. Just upgraded from Dirty Unicorns. Flashed with Nik Gapps, no problem except prior mentions in the LOS thread. Thank you a gain and have a great holiday!

First of all, thank you for all your work . I have flashed crDroidAndroid-11.0-20201219-dragon-v7.1.zip and Nik gapps. After the display has switched itself off, it switches on again automatically after 5 seconds and so on. If I turn the display off using the button, it won't turn on again. Do I have any setting that causes this?

It's time for a new build ..
crDroidAndroid-11.0-20210414-dragon-v7.5.zip
Changes:
- Google Security updates -> April 2021
- Latest device and kernel changes for dragon
- Backport of Wifi-Display (Miracast) for Android 11
- Latest crDroid changes for Android 11
Enjoy

Thank you @followmsi for your support of this ROM, as I much prefer it with all it's customization over basic LineageOS. It seems to run much better now than before as well. I think there were some RAM-related issues.
But I have run into a grave problem, as I have accidentally turned off WiFi and now the tablet has become unresponsive, as the UI seems to crash repeatedly. Only the status bar and lock screen symbol pop in and out. I tried to turn on WiFi by booting into TWRP and changing "wifi_on" to 1 in "/data/system/users/0/settings_global.xml" but it didn't work. The tablet runs warm and safe mode doesn't work either btw. Any idea?
Edit: I decided to perform a clean install, since it's been a while anyway and we've skipped a couple versions as well. Anyway, I initially tested to turn WiFi off and it worked fine, no crash. I proceed to set up my device somewhat, enable dark mode, change icon shape, go through all crDroid settings etc.; I turn off WiFi once more, from the quick-settings, and it happened again. I'm not sure what setting or customization exactly leads to this, but I guess I'll have to be very careful not to turn it off for now. If I can help troubleshoot this issue, let me know.
Edit2: I think I figured out what it is: Data usage (daily/monthly) in the quick settings. Gotta keep that turned off.

followmsi said:
It's time for a new build ..
crDroidAndroid-11.0-20210414-dragon-v7.5.zip
Changes:
- Google Security updates -> April 2021
- Latest device and kernel changes for dragon
- Backport of Wifi-Display (Miracast) for Android 11
- Latest crDroid changes for Android 11
Enjoy
Click to expand...
Click to collapse
Finally got around to flashing my beloved dragon again today, looking really good! No bugs or glitches so far, just a lot of customizable awesomeness
Once again thank you so much for your ongoing support for this ageing tablet, I would love to send the equivalent of a few coffees or beers yours way if you tell me how.

It's time for a new build ..
crDroidAndroid-11.0-20210810-dragon-v7.9.zip
Changes:
- Google Security updates -> August 2021
- Latest device and kernel changes for dragon
- Backport of Wifi-Display (Miracast) for Android 11
- Latest crDroid changes for Android 11
Enjoy

Maybe it is good chosen one

followmsi said:
It's time for a new build ..
crDroidAndroid-11.0-20210810-dragon-v7.9.zip
Changes:
- Google Security updates -> August 2021
- Latest device and kernel changes for dragon
- Backport of Wifi-Display (Miracast) for Android 11
- Latest crDroid changes for Android 11
Enjoy
Click to expand...
Click to collapse
As always, thank you so much for your ongoing support for the good old dragon!
Just a note in case anyone else stumbles upon this: I could not get this build to boot with OpenGapps and a clean install, tried three times including format data and everything. Then tried NikGapps and it worked like a charm.
ROM itself is awesome, no problems so far, reasonably fast considering the hardware and a lot of cool features.

This is my last crDroid build for Android 11 .. the next build will be based on 12.
crDroidAndroid-11.0-20211214-dragon-v7.13.zip
Changes:
- Google Security updates -> December 2021
- Latest device and kernel changes for dragon
- Latest crDroid changes for Android 11
Enjoy

[UNOFFICIAL][ROM]BETA LineageOS 18.1 for Galaxy Tab E [SM-T560NU] June 9, 2023

This ROM is ONLY for SM-T560NU, NOT SM-T560. I CANNOT make a SM-T560 build as they are different CPU/SoCs.
PLEASE BEFORE YOU decide to try this rom, you MUST read all of post 1, 2, 3 and 4 (about 10 minute read). If you think this is an unreasonable request, then stop reading now and find another rom. Thank you.
I am not responsible for lost data, identity theft, lost money, security vulnerabilities, bricked devices or any other hardware or software malfunctions that comes as a result of flashing this rom.
BACKUP YOUR DATA AND OLD rom BEFORE trying my rom.
If you are NOT an expert in using fastboot, adb, odin, heimdall, twrp, DO NOT use this rom. You must know how to use these tools to revert back to your old rom.
If you are new to flashing custom roms, do NOT attempt this.
If you need your tablet for work and something important, do NOT flash this rom. This rom could result in a bricked device or boot loop or non booting device or you not being able to revert back to your old rom.
What works
1. bluetooth
2. wifi
3. brightness
4. external audio
5. GPS
6. audio through headphone jack
7. audio over bluetooth
8. selinux enforcing
What doesn't work
1. Camera. The stock camera app front camera preview doesn't work. Use opencamera instead. I have no plans to fix the stock camera app as opencamera works fine.
2. Live display. Live display causes a stuck at boot animation/boot loop on SM-T560NU, so I disabled it from the menu option. This feature worked in 17.1, but broken in 18.1.
Thanks
1. LineageOS team for source code.
2. Pre alpha testers for the Samsung Tab A/E roms who provided valuable feedback: lpedia, Schaagi, katochwa, Henrick Grimler
3. Huge thanks to Henrick Grimler https://github.com/Grimler91 for helping me reproduce a major bug in 18.1 which led me to find a solution. Henrick also helped fine tune some of the sepolicy as well.
4. Sebastiano Barezzi https://github.com/SebaUbuntu for giving the msm8916 repo some 18.1 code updates in March 2021.
5. Exynos5420 team for sharing it's knowledge in building roms.
6. msm8916 team for their repos

FAQ - I spent hundreds of hours building this rom. It was frustrating process from Nov 2020 to March 2021 running into bug after bug. The least you can do is spend a few minutes reading everything before posting.
Q1. Where are the source and kernel source files?
A1. The kernel source files are at
GitHub - Galaxy-MSM8916/android_kernel_samsung_msm8916: MSM8916/MSM8929/MSM8939 kernel for Samsung devices.
MSM8916/MSM8929/MSM8939 kernel for Samsung devices. - GitHub - Galaxy-MSM8916/android_kernel_samsung_msm8916: MSM8916/MSM8929/MSM8939 kernel for Samsung devices.
github.com
The device tree files are at
GitHub - retiredtab/android_device_samsung_gtelwifiue: Samsung Galaxy Tab E SM-T560NU Device Tree
Samsung Galaxy Tab E SM-T560NU Device Tree. Contribute to retiredtab/android_device_samsung_gtelwifiue development by creating an account on GitHub.
github.com
GitHub - retiredtab/android_device_samsung_msm8916-common: Common MSM8916 tree for Samsung devices
Common MSM8916 tree for Samsung devices. Contribute to retiredtab/android_device_samsung_msm8916-common development by creating an account on GitHub.
github.com
GitHub - retiredtab/msm8916_sepolicy_vendor
Contribute to retiredtab/msm8916_sepolicy_vendor development by creating an account on GitHub.
github.com
The vendor tree files are at
GitHub - retiredtab/vendor_samsung_msm8916-common
Contribute to retiredtab/vendor_samsung_msm8916-common development by creating an account on GitHub.
github.com
GitHub - retiredtab/vendor_samsung_gtelwifiue
Contribute to retiredtab/vendor_samsung_gtelwifiue development by creating an account on GitHub.
github.com
In addition, there is a repo diff file for device specific tweaks needed to work and a roomservice.xml (local manifest file) file so you can build this rom yourself.
Q2. Is this BETA rom suitable as a daily driver?
A2. It can be depending on your requirements. I can't test every app so you try it yourself to see if it's suitable. I've been using this rom myself since mid March 2021 with no major issues.
Q3. What if my app, xyz, doesn't work?
A3. I won't answer questions regarding why your app doesn't work. If your app, whatever it is, doesn't work, then go back to your old rom. It's difficult enough building and maintaining these roms. Remember, I'm an unpaid volunteer making a rom for free for your benefit.
Q4. Your rom is laggy and buggy.
A4. If you find the above, then go back to your old rom. There's only so much software can do on a 2015 budget level tablet. Remember a budget tablet will have the slower SoC/CPU and less DRAM than a top of the line model. Your tablet will also run slower when you use gapps (google apps). You can run a lot of software without using gapps. Research fdroid, newpipe, Aurora store etc.
Q5. What TWRP should I use?
A5. You MUST use 3.2.3 below
https://msm8916.com/?view=downloads&tag=TWRP-3.2.3-lineage-15.1_j4_20180921_gtelwifiue
OR my 3.5.2_9 TWRP build
https://sourceforge.net/projects/retiredtab/files/SM-T560NU/TWRP/
Q6. Why should I use this rom?
A6. You don't. If you don't like this rom, then don't use it. Yes, it's that simple.
Q7. Will you offer monthly updates with security patches?
A7. I will try to offer monthly security patches, but that all depends on if I continue to have high speed Internet in the future.
Q8. Can you help me? I'm a newbie. Can you provide step by step instructions?
A8. Do your own research. There are lots of tutorials, videos, etc on how to flash roms. Newbie questions must be posted in the Questions and Answers forum, not here.
Q9. Can I report a bug with respect to the rom?
A9. Yes, but you need to supply the following information. If you don't, I won't look at it.
You must provide an adb logcat of the problem and tell me how to reproduce it. Note I will not be downloading any apps that require money or an userid/password. For example, if you have problems with Netflix, I cannot help you since I don't have a paid subscription. If you use some app that requires an userid/password, I cannot help you as I'm not willing to create another userid/password even if it's free.
To get a logcat, open up a terminal window.
Code:
# clear the logcat first
adb logcat -c
# start logcat trace
adb logcat > problem.txt
# reproduce problem
# wait until problem has occured, then stop trace by hitting ctrl-c
Q10. Will you still build 17.1 for this device?
A10. Yes, for now, but I will probably discontinue building 17.1 at the end of 2021. I will likely be trying to build 19.0 once it's released so I don't want to maintain 3 releases.
Q11. Do I need to erase everything and format my data?
A11. Yes, you MUST erase all the partitions (system, data, dalvik/art cache, cache) using TWRP and MUST format your data before installing 18.1 when you are coming from stock or an earlier version of LineageOS or from another custom rom. If you get stuck at the boot animation for more than 5 minutes, it's likely because you didn't follow the instructions I just wrote. Dirty flashes from stock, other custom roms or older LineageOS versions are not supported and not likely to work.
Q12. What gapps should I use?
A12. I don't use gapps anymore. I use Aurora Store. As of Nov 6, 2021, I no longer make recommendations on which gapps to use as your mileage may vary. It's reported that opengapps does no testing on their daily builds and some version results in bootloops, bitgapps may run out of disk space will installing apps and Mindthegapps as causing overall slowdown of the system.
The only recommendation I can make is to use the SMALLEST version of gapps which is PICO or equivalent naming convention. DO NOT use anything other than PICO. That is, do not use nano, mini, stock, etc.
If you are going to install gapps, flash the rom first, reboot into system/OS, reboot to recovery, flash gapps, reboot into system/OS. That is, do not flash/install the rom and gapps at the same time.
Q13. I'm having problems with gapps, can you answer why it's not working?
A13. I will not answer any questions regarding gapps. This thread is about the rom, not gapps and I don't use gapps so I cannot help you. Android does not depend on gapps in order to work.
Q14. Why isn't my post answered?
A14. It's probably because it's answered in the FAQ or not relevant to the rom. Again, I do not run Windows OS or use gapps. Questions already answered in the FAQ will be completely ignored.
Q15. Can I turn off the on screen navigation keys?
A15. To turn off on screen navigation, go to settings, system, advanced, gestures, system navigation, gesture navigation. It's enabled by default because I find it useful. If you don't like it, you only need to disable once and your preference will be remembered. If you want to invert the onscreen keys, goto settings, system, buttons and enable invert layout
Q16. What speed up/optimization tips do you suggest?
A16.
1. Turn off animations. Go into developer settings, scroll down to the drawing section, and set window, transition and animator scale all to "off".
2. If you don't have a google account, don't install gapps. Use Aurora Store to get your apps as you can get all the same apps from the play store using an anonymous login.
3. Dont' run more than 2 apps at the same time. You can probably listen to music in the background and use a web browser at the same time, but don't expect great performance from a 2015 entry level tablet.
4. Use a web browser like Brave that has built in adblock and privacy features.
5. Use newpipe to watch your streaming content. It has built in adblock so you don't have to watch forced ads.
6. Look for apps that are open source, ad free and lightweight.
Q17. Does this rom support Magisk?
A17. I don't use Magisk myself so I don't know and Magisk is always being updated to fool Google's certification process. Others have reported Magisk as working, but I won't answer any questions regarding it.
Q18. Will this rom ever become official?
A18. Never. I don't want the responsibilities that come with being an official maintainer. In addition, I know my device trees, code organization and git commits will NOT meet LineageOS standards. Remember, I'm an unpaid volunteer doing this in my free time and sharing my work with you for free so you can get hundreds of hours of enjoyment from this tablet.
Q19. What is the difference between this rom and others?
A19. This rom tries to be pure LineageOS with little to no modifications. Other roms may have different UI, different bundled apps, etc. Use whatever meets your requirements.
Q20. Will there be any major 18.1 code modifications in the future?
A20. I don't anticipate any major modifications. There may be some slight tweaking to the sepolicy, small bug fixes and minor code cleanup, but all the hard work in getting the rom up and running and fixing all the major bugs have been done completed. This doesn't mean the code is perfect or well organized, but I won't be doing any major changes now that 18.1 is working. Any major changes will be done in 19.0.
Q21. Why did you fork the device and vendor trees for 18.1?
A21. The msm8916 repos seem geared towards phones and sometimes do not work or cause boot animation loops for tablets so I decided to fork their repos. In other words, what's deemed as msm8916-common code isn't common to all devices.
In addition, since I'm building SM-T350, SM-T550, SM-P550 and SM-T560NU (all use the same msm8916 code), it seems easier to maintain all of them if I can control my own code repos and not worry if my changes affects the phones or not. I still have not figured out the best way to manage all my repos and it's a work in progress.
Q22. Can you build a variant of this device? For example, a LTE or S-pen version.
A22. If I don't physically have the device, I cannot and will not build it unless I can boot and test it myself. Even then, there's no guarantee that I can get those variant features working.
Q23. Can I load this rom on a variant devivce like LTE or S-pen version?
A23. The rom is built for the device explicitly listed. If you are an advanced user and understand TWRP, adb, odin, heimdall, you can try loading it on a LTE or S-pen variant by modifying the updater-script, but it may cause a bricked device, bootloops or non functionality of LTE/S-pen. You have been informed and warned!
Q24. Will this run on the SM-T560 or SM-T561?
A24. No, the SM-T560 and SM-T561 use a different CPU/SoC. The SM-T560NU rom will NOT work on SM T560/SM-T561.
Q25. Okay, I understand the consequences and that this is BETA rom and willing to take the risks outlined, now where can I find the rom?
A25. Downloads are at
retiredtab - Browse /SM-T560NU/18.1 at SourceForge.net
sourceforge.net

NOTE: All builds that I upload have been personally tested on my device to boot and function as described in post #1. Having said that, there's still a chance it won't work on your device due to human error, your configuration, your apps, etc. If it won't boot, always start with a complete wipe of everything and format your data. This is known has a clean install. Backup your data before a clean install.
June 9, 2023 release notes
1. June 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2023-06
2. Whatever LiineageOS changed since last May release (about 5,300 files had to be recompiled).
May 7, 2023 release notes
1. May 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2023-05
2. Whatever LiineageOS changed since last Apr release (about 7,200 files had to be recompiled).
Apr 14, 2023 release notes
1. Apr 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2023-04
2. Whatever LiineageOS changed since last Mar release (about 4,500 files had to be recompiled).
Mar 19, 2023 release notes
1. Mar 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2023-03
2. Whatever LiineageOS changed since last Feb release (about 24,500 files had to be recompiled).
Feb 12, 2023 release notes
1. Feb 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2023-02
2. Whatever LiineageOS changed since last Jan release (about 12,500 files had to be recompiled).
Jan 8, 2023 release notes
1. Jan 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2023-01
2. Whatever LiineageOS changed since last Dec release (about 4,500 files had to be recompiled).
Dec 10, 2022 release notes
1. Dec 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-12
2. Whatever LiineageOS changed since last Nov release (about 5,000 files had to be recompiled).
Nov 10, 2022 release notes
1. Nov 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-11
2. Whatever LiineageOS changed since last Oct release (about 5,000 files had to be recompiled).
Oct 6, 2022 release notes
1. Oct 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-10
2. Whatever LiineageOS changed since last Sept release (about 7,600 files had to be recompiled).
Sept 10, 2022 release notes
1. Sept 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-09
2. Whatever LiineageOS changed since last August release (about 35,000 files had to be recompiled).
Aug 5, 2022 release notes
1. Aug 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-08
2. Whatever LiineageOS changed since last July release (about 35,000 files had to be recompiled).
3. Fix stock camera issue where preview is not shown after first picture is taken. See
https://github.com/retiredtab/andro...mmit/e72b8f7d91b80517f3e47556a8f6e8e13410ee63
July 7, 2022 release notes
1. July 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-07
2. Whatever LiineageOS changed since last June release (about 1,900 files had to be recompiled).
June 11, 2022 release notes
1. June 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-06
2. Whatever LiineageOS changed since last May release (about 37,500 files had to be recompiled).
May 6, 2022 release notes
1. May 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-05
2. Whatever LiineageOS changed since last April release (about 37,000 files had to be recompiled).
April 9, 2022 release notes
1. April 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-04
2. Whatever LiineageOS changed since last March release (about 36,000 files had to be recompiled).
Mar 11, 2022 release notes
1. Mar 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-03
2. Whatever LiineageOS changed since last February release (about 5,700 files had to be recompiled).
Feb 11, 2022 release notes
1. Feb 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-02
2. Whatever LiineageOS changed since last January release (about 34,500 files had to be recompiled).
Jan 20, 2022 release notes
1. Jan 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-01
2. Whatever LiineageOS changed since last December release (about 35,000 files had to be recompiled).
Dec 9 release notes
1. Dec 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2021-12
2. Whatever LiineageOS changed since last November release (about 10,500 files had to be recompiled).
3. Stock Camera fixed thanks to patches contributed by DJABHipHop as per https://github.com/retiredtab/andro...mmit/d7138f96159cd5dd54fc89f500b33119d92e54b4
Nov 7 release notes1. Nov 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/318560
2. I enabled zram swap with size 512MB. I noticed that the last couple of months that Clash Royale would crash/close and logs showed
Code:
10-28 14:26:01.412 0 0 I [2: kswapd0: 91] lowmemorykiller: Killing 'ell.clashroyale' (6730), adj 0,
Hopefully, by enabling zram, that will stop Clash Royale from crashing/closing.
Zswap is enabled on stock Nougat SM-T350 (part of the Samsung Tab A/E family that uses same msm8916 kernel code)
https://github.com/retiredtab/andro...mmit/2a6bf385e6dfe6073fe328b7b1c563ccd60a5ede
https://github.com/retiredtab/andro...mmit/438d5d3ad20cbc98f0f8c18eb610b6268de19395
This code uses the in kernel low memory killer (lmk). I tried using the Android OS lmk, but it doesn't work very well and shows this in the log.
Code:
E lowmemorykiller: /proc/zoneinfo parse error
E lowmemorykiller: Failed to get free memory!
3. Whatever LineageOS changed since last Oct release (about 8,000 files had to be recompiled). One of these changes has removed the built in terminal program from LineageOS as AOSP deprecated this app as per
https://review.lineageos.org/c/LineageOS/android_vendor_lineage/+/304043
Oct 10 release notes
1. Oct 1 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/317001
2. Added https://review.lineageos.org/c/LineageOS/android_frameworks_base/+/316839 to fix landscape mode system UI. This patch is not yet officially merged as of Oct 10 release.
3. Whatever LiineageOS changed since last September release (about 7,200 files had to be recompiled).
Sept 9 release notes
1. Reverted the patch to https://github.com/retiredtab/andro...mmit/a32c7a0bed536281d20b7c1cf8d41c84a268cc80
Removing systemUI from pinner services causes a 4 to 6 delay in bringing up the home screen. This is seen when loading or playing a game for about 20 minutes and then either hitting the recents or home button. By reverting this commit, pressing recents or home button brings up the systemUI right away.
2. Sept 5 security patches as per https://review.lineageos.org/c/LineageOS/android/+/315661
3. Whatever LiineageOS changed since last August release (about 6,000 files had to be recompiled).
Aug 8 release notes
1. Fix battery status icon. When you plug in AC adapter, settings, battery does not show it charging even though it is. This is due to the sepolicy being too restrictive. I added https://github.com/retiredtab/msm89...mmit/c1eca9f7740b6a384d4fab8a1e8d812f59c17a99
2. Aug 5 security patches as per https://review.lineageos.org/c/LineageOS/android/+/314477
3. Whatever LiineageOS changed since last July release (about 23,000 files had to be recompiled).
July 9 release notes
1. Initial public release to XDA. This is an ALPHA build.
2. July 5 security patches as per https://review.lineageos.org/q/topic:"android-11.0.0_r39"+(statuspen OR status:merged)
3. Small bug in settings, battery where the charging lightning symbol is not displayed when AC adapter is plugged in. This will be fixed in the August security patches.

Reserved.

Just installed this ROM on my tablet, runs great. I'm glad the weird font bug is fixed on this version, it infuriates me but I got to used with it. However, there is a bug on Quick Settings Panel while playing music on background in Landscape. I'll put the screenshot below, I think you can fix it by making QS Panel wider.
{
"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"
}

Fruse said:
I'm glad the weird font bug is fixed on this version, it infuriates me but I got to used with it.
Click to expand...
Click to collapse
I wrote and suspected that it was a 17.1 LineageOS bug since it appeared on multiple devices, not just the msm8916 platform. It didn't bother me, but I'm glad they fixed in 18.1.
Fruse said:
However, there is a bug on Quick Settings Panel while playing music on background in Landscape. I'll put the screenshot below, I think you can fix it by making QS Panel wider.
Click to expand...
Click to collapse
I can replicate your finding, however, it also appears on 3 non msm8916 devices running 18.1 so I think it's another possible LineageOS bug. Or it's a new feature in landscape mode. 2 of the 3 non msm8916 devices that show the same behaviour are LineageOS OFFICIAL 18.1 releases. Either way, if it's a bug, I will have to wait for LineageOS to fix it. If it's a feature, get used to it.

retiredtab said:
I wrote and suspected that it was a 17.1 LineageOS bug since it appeared on multiple devices, not just the msm8916 platform. It didn't bother me, but I'm glad they fixed in 18.1.
I can replicate your finding, however, it also appears on 3 non msm8916 devices running 18.1 so I think it's another possible LineageOS bug. Or it's a new feature in landscape mode. 2 of the 3 non msm8916 devices that show the same behaviour are LineageOS OFFICIAL 18.1 releases. Either way, if it's a bug, I will have to wait for LineageOS to fix it. If it's a feature, get used to it.
Click to expand...
Click to collapse
Thanks for response. I'll get used to it.

I just found out that the stock camera is partially working (Both 17.1 and 18.1) but still recommended to use Open Camera.
What works on stock camera:
Panorama
QR code scanning
What partially works:
Video capturing (Recorded videos are broken)
What does not work:
Taking pictures

New build called lineage-18.1-20210808-UNOFFICIAL-gtelwifiue.zip
Aug 8 release notes
1. Fix battery status icon. When you plug in AC adapter, settings, battery does not show it charging even though it is. This is due to the sepolicy being too restrictive. I added https://github.com/retiredtab/msm89...mmit/c1eca9f7740b6a384d4fab8a1e8d812f59c17a99
2. Aug 5 security patches as per https://review.lineageos.org/c/LineageOS/android/+/314477
3. Whatever LiineageOS changed since last July release (about 23,000 files had to be recompiled).
4. 18.1 continues to be my daily driver since March 2021.

Does that work for sm t560?

JPA1 said:
Does that work for sm t560?
Click to expand...
Click to collapse
This is answered in Q24 of the FAQ in post #2:
Q24. Will this run on the SM-T560 or SM-T561?
A24. No, the SM-T560 and SM-T561 use a different CPU/SoC. The SM-T560NU rom will NOT work on SM T560/SM-T561.

New build called lineage-18.1-20210909-UNOFFICIAL-gtelwifiue.zip
NOTE: All builds that I upload have been personally tested on my device to boot and function as described in post #1. Having said that, there's still a chance it won't work on your device due to human error, your configuration, your apps, etc. If it won't boot, always start with a complete wipe of everything and format your data. This is known has a clean install. Backup your data before a clean install.
18.1 continues to be my daily driver since March 2021.
Sept 9 release notes
1. Reverted the patch to https://github.com/retiredtab/andro...mmit/a32c7a0bed536281d20b7c1cf8d41c84a268cc80
Removing systemUI from pinner services causes a 4 to 6 delay in bringing up the home screen. This is seen when loading or playing a game for about 20 minutes and then either hitting the recents or home button. By reverting this commit, pressing recents or home button brings up the systemUI right away.
2. Sept 5 security patches as per https://review.lineageos.org/c/LineageOS/android/+/315661
3. Whatever LiineageOS changed since last August release (about 6,000 files had to be recompiled).

Fruse said:
However, there is a bug on Quick Settings Panel while playing music on background in Landscape. I'll put the screenshot below, I think you can fix it by making QS Panel wider.
View attachment 5362587
Click to expand...
Click to collapse
@Fruse, it looks like there may be a LineageOS 18.1 fix for the above. I was just looking through the LineageOS gerrit where new proposed changes are listed and I spotted this change request (CR).
https://review.lineageos.org/c/LineageOS/android_frameworks_base/+/316839
"SystemUI: Don't use horizontal quick settings on large screens On large screens such as tablets, the horizontal quick settings isn't necessary as we have enough room for the normal quick settings and media player. It also seems to have issues on large screens, on my v1awifi I can't swipe to a different quick settings page and the media player album art overlaps the media controls."
When I make the next 18.1 build with the Oct 5 security patches, this CR may be approved by then. If not, I can add it in manually, it's easy enough to add and test.

New build called lineage-18.1-20211010-UNOFFICIAL-gtelwifiue.zip
NOTE: All builds that I upload have been personally tested on my device to boot and function as described in post #1. Having said that, there's still a chance it won't work on your device due to human error, your configuration, your apps, etc. If it won't boot, always start with a complete wipe of everything and format your data. This is known has a clean install. Backup your data before a clean install.
18.1 continues to be my daily driver since March 2021.
Oct 10 release notes
1. Oct 1 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/317001
2. Added https://review.lineageos.org/c/LineageOS/android_frameworks_base/+/316839 to fix landscape mode system UI as reported in post #5 by @Fruse . This patch is not yet officially merged as of Oct 10 release.
3. Whatever LiineageOS changed since last September release (about 7,200 files had to be recompiled).

Hey man, just wanted to say how much I appreciate what you're doing for this device and keep up the good work.

Pitch Black Recovery For gtelwifiue & gtesqltespr
/* *Disclaimer * * Your warranty is now void. * * We're 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...
forum.xda-developers.com

I have the t560nu, as is indicated in setting and small print on the back of my device, but when I try flashing your 17.1 and 18.1 ROMs I get an error message stating that the rom is for the "...t560nu and your device is [blank] ." I tried with various version of twrp and I get the same error, when I tried with you custom twrp, I didn't have an option to install from the SD card. Fortunately I made a twrp backup first with an older version and I was able to restore my device. Any advice?

kewecuminer said:
I have the t560nu, as is indicated in setting and small print on the back of my device, but when I try flashing your 17.1 and 18.1 ROMs I get an error message stating that the rom is for the "...t560nu and your device is [blank] ." I tried with various version of twrp and I get the same error, when I tried with you custom twrp, I didn't have an option to install from the SD card. Fortunately I made a twrp backup first with an older version and I was able to restore my device. Any advice?
Click to expand...
Click to collapse
Is it this error?
http://www.lineageosdownloads.com/fix-error-7-lineage-os/
I saved this link in my notes for my Samsung tablet, so I must have run into this at some point while trying to flash it...

Sigster said:
Is it this error?
http://www.lineageosdownloads.com/fix-error-7-lineage-os/
I saved this link in my notes for my Samsung tablet, so I must have run into this at some point while trying to flash it...
Click to expand...
Click to collapse
It appears to be. But now I can't even restore my backup. I love a good challenge, but this isn't what I was hoping for on a Friday afternoon
Looks like I just needed something newer than twrp 3.1.1. Kind of dumb on my part, it was right there

[RECOVERY][3.5.2_10][gtelwifiue][gtesqltespr] TWRP Recovery is Live
[RECOVERY][3.5.2_10][gtelwifiue][gtesqltespr] TWRP Recovery
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and...
forum.xda-developers.com

[ROM] LineageOS 17/18/19 UNOFFICIAL - (Update: 2023-06-17)

LineageOS 17/18/19 for Sony Xperia XZ1 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"
}
RELEASE
This is an alternative ROM for the Sony Xperia XZ1 Compact.
Creating this to honor the great work of modpunk and derf elot from https://forum.xda-developers.com/t/rom-lineageos-18-1-unofficial-2-0-update-2021-01-20.4047763/ which seems to be discontinued. Posting an own thread to keep the latest versions visible, I'm NOT claiming authorship over the ROM.
I basically just build the ROM using the latest changes from upstream LineageOS/Google and kernel updates (usually incorporated by derf elot ) See my post.
FEATURES
Signed with dev keys
EAS kernel
Passes SafetyNet out of the box (thanks Rooted_Ansh, Havoc-OS Team and kdrag0n)
Seedvault (Video)
IMS support (thanks to Rooted_Ansh and also Shujath)
17.1 has stock Sony camera (not possible on 18+)
DOWNLOAD
You can download the latest release here.
HINT: Download both the ZIP and md5sum file so TWRP can check the consistency of the upload/download.
Make sure you download the right version, vanilla LineageOS is named lineage-*UNOFFICIAL-lilac.zip while the MicroG version is named lineage-*-MICROG--lilac.zip
REQUIRED FIRMWARE: 47.2.A.11.228
IMPORTANT: I only test the 17.1 releases myself. The 18.1/19.1 are build from mostly the same sources and hopefully work. I only test them roughly.
Backup download
INSTALLATION
IMPORTANT: Magisk seems to cause issues (bootloops) on update, so remove it first and reinstall if required. Note that Magisk is usually not required unless you want root.
Put the zip file of the ROM on your SD card or internal store and boot into recovery.
When coming from stock ROM, do a full wipe (i.e. factory reset) via "Wipe". You don't need to wipe system. When flashing the stock ROM you can select to not keep user data which is equivalent to this step.
Go to "Install", select the zip file and add optionally the gapps zip. Then flash it.
After updates you may now wipe cache&dalvik (option after install)
I suggest to use modpunks TWRP recovery. Again: Don't forget the md5sum file!
TWRP 3.3.1-0 by modpunk / derf elot
Or use the latest TWRP for 17.1/18.1 or TWRP for 19.1.
3.7.0 Seems to work well with latest updates (decryption working) but LineageOS 19.1 (Android 12) requires the ones with "_12" suffix, e.g. 3.6.2_12.
For ease of use I suggest to flash this recovery (only required once):
Boot in Fastboot mode: Hold "Volume Up" while connecting the USB cable to phone and PC
Flash TWRP by running this on the PC: fastboot flash recovery twrp-3.3.1-0-lilac-android10-1.img
(adjust the filename if necessary)
From now you can boot TWRP by turning on the phone with "Volume Down" + Power
I heavily recommend to make a full backup before any installation so you can go back in case of issues. Flashing an older ROM usually helps to recover bootloops etc.
Upgrades between versionsDirty-flashing (e.g. from 17.1 to 18.1) works well but you have to also flash a GApps version matching the Android version or the device will bootloop.
For the upgrade to 19.1 you may need to fully remove OpenGapps by wiping /system and install e.g. MindTheGapps.
SUPPORT
There is NONE. If you have any issues or question ask in the thread so maybe someone else knows the answer.
I'm just providing the ROM (Lineage 17.1 variant) I use myself for others to try to and just build the Lineage 18.1 ROM without much testing.
If you prefer to use a more well-tested Android 11 ROM, I suggest to look at Havoc-OS.
Contributions to the sources are welcome and likely get integrated into the next release.
Contributors
modpunk, derf elot, Rooted_Ansh, Flamefire, linckandrea
Source Code: https://github.com/Flamefire/android_device_sony_lilac, Original: https://github.com/whatawurst/
If you want to buy me a coffee/beer, I'll appreciate it but it is not necessary.
Also please consider donating to the original authors too or to local charities as requested by @modpunk
Special thanks to landsome for donating a test phone for bug hunting and development.
ROM OS Version: Android 10/11/12
ROM Kernel: Linux 4.4.x
Based On: LineageOS
GApps: None included, except for the MICROG builds. Recommended is OpenGApps for 17/18 and MindTheGapps for 19.

CHANGELOG
2023-06-16
June security patches (backports from 18.1 to 17.1)
Kernel updates (CIP tag -st41)
Fix noise when calling with a headset
Configurable fingerprint sensor when screen is off (Settings->Lockscreen)
2023-05-19
Fix Play Integrity checks --> Google Wallet works
Minor improvements that were missed earlier
May security patches (backports from 18.1 to 17.1)
Kernel updates (CIP tag -st40)
2023-04-30
April security patches (backports from 18.1 to 17.1)
Kernel updates (CIP tag -st39)
2023-03-31
March security patches (backports from 18.1 to 17.1)
Kernel updates (CIP tag -st38)
Fix possible camera issues on 18.1
2023-02-25
February security patches
Kernel updates (e.g. CIP tag -st37, also add some missing patches to 19.1 kernel)
Use newer compiler (Clang 12.0.7) for kernel, possibly improving performance/battery life
Add "Re-apply Modem" setting to XperiaParts to help with connection/modem-crash issues
Clear some space on /system & /vendor partitions by removing files no longer needed
Attempt to fix Android Auto connection (untested)
2023-01-20
January security patches
Kernel updates
MicroG builds added (build date 31st Jan, but same sources)
2022-12-27
December security patches
AGPS fix (using Google servers)
Kernel updates (e.g. Wireguard v1.0.20220627, improved security against stack attacks)
2022-11-15
November security patches
WLAN driver update
Huge APN update
2022-10-13
October security patches
Kernel update
APN for DIGI HU
Option to switch temporarily to 2G on boot
2022-09-29
September security patches
Kernel update
APN update
2022-08-12
August security patches
Kernel update (CIP st20)
2022-07-25/28
July security patches
Kernel update
2022-06-30
June security patches
Kernel update
Backport fix for CVE-2021-39686
Workaround fixing bootloop with recent OpenGapps (20220503 tested)
2022-05-16
May security patches
Fix mic volume issue with wired headsets
Known issue: OpenGapps after 15/2 result in bootloop
2022-05-03
April security patches
Kernel update (CIP st5-tag)
Removed LineageOS updater (unused application here)
Added Sony identification packages (Compatibility for some Sony apps from other sources)
2022-03-20
March security patches
Updated some carrier configs (mostly Indian&Chinese) for IMS (VoLTE...)
Better support for flip covers
Allow disabling battery optimizations for the SMS app
2022-02-20
February security patches
Kernel 4.4.302 (final LTS kernel)
Re-enable VoLTE toggle switch (there were reports of modem crashes when VoLTE is disabled, can't reproduce this, hence added the setting back)
2022-01-23
January security patches
Kernel 4.4.299
Wireguard v1.0.20211208
Enhanced display brightness range
Experimental Ultra-Dim mode
2021-12-19
December security patches
Kernel 4.4.295
QCom driver updates
Fix some permission issues
Reset phone ID to XZ1C
2021-11-29
November security patches
Kernel 4.4.291
Fix IMS on 17.1
Fix/enhance Wifi-Display
Fix some power hints
Update APNs
2021-10-19
October security patches
Kernel 4.4.288
2021-09-18
September security patches
Include some more security patches from AOSP
Clang 11 for LOS 17.1 version (same as 18.1, improved optimizations)
Misc bugfixes backported from Android 11 to Android 10
Kernel 4.4.283
2021-08-11
August security patches
Fix bug with switch 3G->4G in XperiaParts not working on slow boot
Include some more security patches from AOSP
Kernel 4.4.279
2021-07-20
July security patches
Kernel 4.4.275
2021-07-03
June security patches
Update to Linux Kernel 4.4.272
Updated APNs

reserved2

Thank you for keeping this rom up to date for this small but loyal userbase! A miracle come true for me cause I can't build roms on my own.

Thank you so much!! Can anyone report to me if flashing the new 18.1 directly over the previous version of 18.1 works?
I would test myself, but right now I cant afford to need to totally reset my phone if it doesn't work.

Dean F said:
Thank you so much!! Can anyone report to me if flashing the new 18.1 directly over the previous version of 18.1 works?
I would test myself, but right now I cant afford to need to totally reset my phone if it doesn't work.
Click to expand...
Click to collapse
All I can say dirty flashing works well over the latest/previous 17.1 by Flamefire, which in turn works well over the latest modpunk (1.7). So it's worth a try.
More generally, although these ROMs are hardly as well tested as HavocOS, there are satisfied reports over on the original LOS17.1/18.1 thread.

Dean F said:
Thank you so much!! Can anyone report to me if flashing the new 18.1 directly over the previous version of 18.1 works?
I would test myself, but right now I cant afford to need to totally reset my phone if it doesn't work.
Click to expand...
Click to collapse
Dirty flash from 17.1 to 18.1 and all work fine!

rez78 said:
Dirty flash from 17.1 to 18.1 and all work fine!
Click to expand...
Click to collapse
Exactly. Just not the other way around.

Updated with the July security patches.
Note: AndroidFileHost was quite quirky today, so use the md5sum files to verify the integrity of the files

Dirty flash. Work perfect!

Flamefire said:
Updated with the July security patches.
Note: AndroidFileHost was quite quirky today, so use the md5sum files to verify the integrity of the files
Click to expand...
Click to collapse
Thanks. Tried it for a couple of hours - dirty flashed over the 0702 version - and it works just as well so far.
I had one brief moment of panic: upon first boot the phone was stuck right on hitting the desktop for some 10 seconds (did not happen on the many previous dirty flashes); but then everything proceeded well.
Again, great work.

@Flamefire Regarding the information to TWRP: There is an official TWRP version (maintained by @modpunk & @derf elot ): https://twrp.me/sony/sonyxperiaxz1compact.html
Maybe you can update the information in your header.

banana(x) said:
@Flamefire Regarding the information to TWRP: There is an official TWRP version (maintained by @modpunk & @derf elot ): https://twrp.me/sony/sonyxperiaxz1compact.html
Maybe you can update the information in your header.
Click to expand...
Click to collapse
Your suggestion would be valuable if you share your experience:
- encrypted partition mount and decryption compatibility with LineageOS 17.1/18.1
- partition backup / restore - single / batch - with / without password protection
- other version differential bug report

Im running 18.1 ROM now and its working great. It works so much better than the previous January release, because the network connects properly now after restarting. There is no need to fiddle in the settings to switch to 3G, then switch back to 4G.
I really like it.

Ok, I was bored and I made a mess, I could use some help.
I was on the latest and last 17.1 by modpunk. I updated TWRP to the latest official one. I tried to flash the latest 18.1 by Flamefire (I had to disable zip signature verification. I know ). Upon reboot it spends about a minute on the LOS animated logo then reboots to TWRP. I then downgraded TWRP to the latest by modpunk and flashed his latest 18.1 from January. This bootloops to recovery without ever reaching the LOS logo.
I know this is my fault. This said, what's my best chance (if any) not to have to wipe everything? I read in a post above that downgrading from 18.1 to 17.1 won't work, otherwise that would be my next idea.
Thanks in advance to anyone replying!
EDIT: Silly me. I had just forgotten to flash 11.0 gApps. All is well with the dirtiest flash ever.

It was not possible to boot LOS 17.1 with TWRP version from first post. (fresh flash, etc... ) However when using latest official twrp https://twrp.me/sony/sonyxperiaxz1compact.html everything works well.

OUTSTANDING!
Thanks for bringing life to this amazing work, you are the best!
Much appreciated.

@Flamefire
Im confused so u continue with updating the security patches every month correct ?
Im confused about the 18.1 u also only update it with securitypatches or also other stuf like making stable and fixing problems orwhatnot ?
Thank you for keeping our trusty xz1 compact alive a little longer.

megaice said:
It was not possible to boot LOS 17.1 with TWRP version from first post. (fresh flash, etc... ) However when using latest official twrp https://twrp.me/sony/sonyxperiaxz1compact.html everything works well.
Click to expand...
Click to collapse
Does it respond to volume up button presses and in special system restart recovery mode? Prompts for a pin/pattern during login and successfully mount and decrypt the partition? So far no one else has reported using it and so far we knew 17.1 / 18.1 requires a different version. Your experience will help us a lot please share as much experience as possible about the new twrp.

7alvoo said:
Does it respond to volume up button presses and in special system restart recovery mode? Prompts for a pin/pattern during login and successfully mount and decrypt the partition? So far no one else has reported using it and so far we knew 17.1 / 18.1 requires a different version. Your experience will help us a lot please share as much experience as possible about the new twrp.
Click to expand...
Click to collapse
i forgot to mention - i'm using lineage-17.1-20210702-UNOFFICIAL-lilac.zip build (not the latest ..20210720..)
TWRP version 3.5.2_9.0
Magisk 20.4 -> 23
Entering recovery works well, pwr+vol down, vol up after pwr, or when set in Developer submenu - advanced reboot. I have active pin and fingerprint. When entering recovery, twrp asks for password for user 0, using my pin works and twrp decrypts FBE. i can mount and read user data by File Manager in twrp.

Develop Bugs

welcome