Develop Bugs

[UNOFFICIAL][ROM]BETA LineageOS 18.1 for Galaxy Tab E [SM-T560NU] June 9, 2023 - Samsung Galaxy Tab E ROMs, Kernels, Recoveries, &

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 notes​1. 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

Related

NLOS is an unofficial LineageOS build with many additions. These additions started small and have grown large over the month. So, it's time to name it NLOS - which still is an UNOFFICIAL LineageOS build.
Thanks to @UnbracedTundra NLOS has it's own logo, bootanimation and wallpapers.
LineageOS is a free, community built, aftermarket firmware distribution of Android 7.1.2 (Nougat), which is designed to increase performance and reliability over stock Android for your device.
My priorities are stabillity, battery, performance - in that order. At the moment this means this build is optimized for oneplus3t - and it runs only on oneplus3t.​In addition this rom contains two patches (https://github.com/microg/android_p...aster/patches/android_frameworks_base-N.patch and https://github.com/microg/android_p...aster/patches/android_frameworks_base-N.patch) to be microG ready - this means freedom of choice to flash either gapps or install (microG How to use Android without Google Apps). Since LineageOS lacks a theme engine this rom comes with OMS patches applied and is Substratum ready.
NLOS is shipped with Camera2 (atm I recommend the modded Google Camera from Modded Google Camera with HDR+, 60FPS video and Slow Motion by @S4turno or the modded OnePlusCamera from my downloads - do NOT! install both the same time: it's GCam XOR OPCam.
The kernel is prepared for Wireguard VPN - to use Wireguard for vpn-tunnels you need to get the WireGuard-apk from playstore. WireGuard developer @zx2c4 runs a dedicated Wireguard Thread.
Currently known issue can be found here.
If you find an issue, follow these instructions: https://forum.xda-developers.com/showpost.php?p=58239877&postcount=3
Everybody has his very own definition of "clean flash" or "dirty flash". I use these phrases like descriped in this posting: https://forum.xda-developers.com/showpost.php?p=58239877&postcount=2
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
#include <std_disclaimer.h>
/*
* Your warranty isn't void: we are on an oneplus device.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
This thread is for Unofficial LineageOS 14.1 builds for oneplus3t - it is not for oneplus3. The following will not be supported here:
Custom kernels
Mods
Xposed
gapps packages bigger then opengapps-nano (read this.)
I don't support Xposed and any logcat which includes a Xposed module will be ignored. You're kindly invited to not report bugs if you:
Flashed a custom kernel
Installed or did mods from untrusted sources
Modified system files (i.e. by using gapps bigger then opengapps-nano)
First time flashing LineageOS 14.1 on your device, or coming from another ROM?
Download the ROM below in the downloads section (or from a mirror; see posting #2)
If you have downloaded a build with "firmware" in it's name, the needed firmware is included and installed while flashing. If you have downloaded a build without "firmware" in it's name, you need to flash the needed firmware BEFORE flashing the rom. You'll find the firmware flashable zips near the end of this posting. New files are added on top of the list.
Download exactly Beans Dynamic Mini Gapps (Note that any other version of Google Apps are known to have wide spread side effects - see posting #4; section "gapps' known issues"
Install exactly this TWRP.
Reboot into recovery.
Backup your current ROM and make sure you have backups of your data you want to keep.
Flash firmware if not using a build with "firmware" in it's name.
Wipe system, data and cache. (Before flashing anything, make sure the system partition is NOT mounted: TWRP-home->mount->uncheck system)
Flash LineageOS
Flash Google Apps (see posting #4; section "gapps' known issues") If you want to use microG skip this step and install microG (How to use Android without Google Apps).
Reboot (as usual: first boot takes loooooong )
Updating this rom
Dirty flashing should work just fine: reboot into recovery and flash a newer LineageOS zip. Settings, apps and even google apps should be preserved.
Important: if you encounter any issues, a clean install is recommended and even required if you need support.
I won't build on a daily (or nightly) basis. I will publish new builds, if I fixed something, important upstream changes or new security patchlevels.
LineageOS changelog: https://www.cmxlog.com/14.1/
Since my time is quite limited till end of October, the update frequency is reduced to 7 to 10 days.
Build 20180309
Releasenotes:
This build requires firmware OpenBeta 15 (aka ob15). As always an archive of all firmwares can be found below in the firmware section of Downloads - the flashable firmwares are the original (file names starting with oxygenos* hold original fw files) OnePlus fw images. NLOS and 'old'-style bootlogos can be found down in this posting.
This is most propably the last NLOS-14.1 build. I want to say "Thanx" to all users. Please feel invited to to use NLOS-15.1!
EOL.
Changelog:
Sync to upstream: March Security Patch.
boeffla_wl_blocker: defconfig: enable wl_blocker. — nvertigo
wl_blocker: add more wakelocks to the default block list — Francisco Franco
boeffla_wl_blocker: update to wakelock blocker driver v1.1.0 — andip71
boeffla_wl_blocker: update to wakelock blocker driver v1.0.1 — andip71
boeffla_wl_blocker: add generic wakelock blocker driver v1.0.0 — andip71
WG: squash WireGuard-0.0.20180304. — nvertigo
Bootlogo choices
nlos_bootlogo-v0.1.zip
back_in_black_bootlogo-v1.0.zip
[SIZE=+2]DOWNLOAD[/SIZE]​
Happy flashing!
History
Build 20180214
Releasenotes:
This build requires firmware OpenBeta 15 (aka ob15). As always an archive of all firmwares can be found below in the firmware section of Downloads - the flashable firmwares are the original (file names starting with oxygenos* hold original fw files) OnePlus fw images. NLOS and 'old'-style bootlogos can be found down in this posting.
There has been some confusion on twrp versions, lately. For nlos always use the "original nougat twrp-3.2.1-0".
If you have issues with bootloops or access to data with some apps, use "original nougat twrp-3.2.1-0" to FORMAT(!) the data partition of the device:
Backup all your data (eveything under /sdcard/; i.e. Downloads, Vodeo, DCIM, etc...)
Boot to "original nougat twrp-3.2.1-0".
Tap on "Wipe".
Tap on "Format Data".
Confirm with swipe. This actually clears your complete data partition, including all data and encyption.
Check if the newly created fs is the type you want (ext4 and f2fs is supported) - eventually change it to your liking.
Just follow the OP's procedure for first installs from OP's "Installation" section (clearing data is allready done, of course).
Changelog:
Sync to upstream: Feb. Security Patch
Bootlogo choices
nlos_bootlogo-v0.1.zip
back_in_black_bootlogo-v1.0.zip
[SIZE=+2]DOWNLOAD[/SIZE]​
Happy flashing!
Build 20180206
Releasenotes:
This build requires firmware OpenBeta 15 (aka ob15). As always an archive of all firmwares can be found below in the firmware section of Downloads - the flashable firmwares are the original (file names starting with oxygenos* hold original fw files) OnePlus fw images. NLOS and 'old'-style bootlogos can be found down in this posting.
There has been some confusion on twrp versions, lately. For nlos always use the "original nougat twrp-3.2.1-0".
If you have issues with bootloops or access to data with some apps, use "original nougat twrp-3.2.1-0" to FORMAT(!) the data partition of the device:
Backup all your data (eveything under /sdcard/; i.e. Downloads, Vodeo, DCIM, etc...)
Boot to "original nougat twrp-3.2.1-0".
Tap on "Wipe".
Tap on "Format Data".
Confirm with swipe. This actually clears your complete data partition, including all data and encyption.
Check if the newly created fs is the type you want (ext4 and f2fs is supported) - eventually change it to your liking.
Just follow the OP's procedure for first installs from OP's "Installation" section (clearing data is allready done, of course).
I have reintroduced lineageos Snpdragon Camera (Snap), because of it's new implemented QuickReader - the issue with crashes on one of the first ff-cammtaken pics is still present. Wiping system and reflashing BeansGapps-Mini-7.1.x-20170725.zip is highly recommended!
Changelog:
op3: Address SELiunx denials — dianlujitao
op3: Unbreak perfd — dianlujitao
Revert "Drop LineageOS/CAF SnapCam aka Snap." — nvertigo
qcacld-2.0: Update to LA.UM.5.5.r1-06700-8x96.0 — dianlujitao
Merge tag 'LA.UM.5.5.r1-06700-8x96.0' into cm-14.1 — dianlujitao
ANDROID: xattr: Pass EOPNOTSUPP to permission2 — Daniel Rosenberg
ANDROID: sdcardfs: Move default_normal to superblock — Daniel Rosenberg
ANDROID: sdcardfs: Fix missing break on default_normal — Daniel Rosenberg
f2fs: Reset to v4.14-rc1-3.18 — dianlujitao
Bootlogo choices
nlos_bootlogo-v0.1.zip
back_in_black_bootlogo-v1.0.zip
[SIZE=+2]DOWNLOAD[/SIZE]​
Happy flashing!
Build 20180131
Releasenotes:
This build requires firmware OpenBeta 15 (aka ob15). As always an archive of all firmwares can be found below in the firmware section of Downloads - the flashable firmwares are the original (file names starting with oxygenos* hold original fw files) OnePlus fw images. NLOS and 'old'-style bootlogos can be found down in this posting.
Changelog:
Mantainance: synced to los.
Bootlogo choices
nlos_bootlogo-v0.1.zip
back_in_black_bootlogo-v1.0.zip
[SIZE=+2]DOWNLOAD[/SIZE]​
Happy flashing!
P.S.: chagallwifi build is updated as well - f2fs for cache and data fixed.
Build 20180120
Releasenotes:
This build requires firmware OpenBeta 15 (aka ob15). As always an archive of all firmwares can be found below in the firmware section of Downloads - the flashable firmwares are the original (file names starting with oxygenos* hold original fw files) OnePlus fw images. NLOS and 'old'-style bootlogos can be found down in this posting.
Changelog:
Revert "Track our own version of android_vendor_codeaurora_telephony." — Nvertigo
Update WireGuard to 0.0.20180118.
Bootlogo choices
nlos_bootlogo-v0.1.zip
back_in_black_bootlogo-v1.0.zip
[SIZE=+2]DOWNLOAD[/SIZE]​
Happy flashing!
Build 20180116
Releasenotes:
This build requires firmware OpenBeta 15 (aka ob15). As always an archive of all firmwares can be found below in the firmware section of Downloads - the flashable firmwares are the original (file names starting with oxygenos* hold original fw files) OnePlus fw images. NLOS and 'old'-style bootlogos can be found down in this posting.
Changelog:
Xtra Fixes - https, version check & version 3 — Wyatt Riley
January security update.
Bootlogo choices
nlos_bootlogo-v0.1.zip
back_in_black_bootlogo-v1.0.zip
[SIZE=+2]DOWNLOAD[/SIZE]​
P.S.: chagallwifi build is updated as well - aptx enabled.
Happy flashing!
Build 20180109
Releasenotes:
This build requires firmware OpenBeta 15 (aka ob15). As always an archive of all firmwares can be found below in the firmware section of Downloads - the flashable firmwares are the original (file names starting with oxygenos* hold original fw files) OnePlus fw images. NLOS and 'old'-style bootlogos can be found down in this posting.
Some new fs, fs-crypt and sdcardfs patches has been merged upstream. Perhaps these also solve the remaining issues with bootloops, though I have only very little hope these will avoid the necessity of reformatting the user-data partition.
Changelog:
fscrypt: move to generic async completion — Gilad Ben-Yossef
crypto: introduce crypto wait for async op — Gilad Ben-Yossef
fscrypt: lock mutex before checking for bounce page pool — Eric Biggers
fscrypt: new helper function - fscrypt_prepare_setattr(
fscrypt: new helper function - fscrypt_prepare_lookup(
fscrypt: new helper function - fscrypt_prepare_rename(
fscrypt: new helper function - fscrypt_prepare_link(
fscrypt: new helper function - fscrypt_file_open(
fscrypt: new helper function - fscrypt_require_key(
fscrypt: remove unneeded empty fscrypt_operations structs — Eric Biggers
fscrypt: remove ->is_encrypted(
fscrypt: switch from ->is_encrypted(
fs, fscrypt: add an S_ENCRYPTED inode flag — Eric Biggers
fscrypt: clean up include file mess — Dave Chinner
fscrypt: fix dereference of NULL user_key_payload — Eric Biggers
fscrypt: make ->dummy_context(
ANDROID: sdcardfs: Add default_normal option — Daniel Rosenberg
ANDROID: sdcardfs: notify lower file of opens — Daniel Rosenberg
Bootlogo choices
nlos_bootlogo-v0.1.zip
back_in_black_bootlogo-v1.0.zip
[SIZE=+2]DOWNLOAD[/SIZE]​
P.S.: chagallwifi build is updated as well.
Happy flashing!
Build 20180106
Releasenotes:
This build requires firmware OpenBeta 15 (aka ob15). As always an archive of all firmwares can be found below in the firmware section of Downloads - the flashable firmwares are the original (file names starting with oxygenos* hold original fw files) OnePlus fw images. NLOS and 'old'-style bootlogos can be found down in this posting.
I've done some testing with toolchains: I couldn't find any advantage using Snapdragon llvm, so I decided to stay with laos stock clang. I also found that using a gcc-6 based cortex-a53 toolchain on the kernel (instead of 4.9) makes the resulting kernel a very little bit more bat friendly. But I did NOT found any advantage of UBERTC/Linaro compared to plain (no Linaro patches and enhancements) gcc-6 build for cortex-a53.
Considering those observations, I decided to use:
kernel: cortex-a53 optimized gcc-6.4.1 (crosstool-ng, config: https://bitbucket.org/nvertigo/aarc...og.bz2?at=master&fileviewer=file-view-default)
All other c- and c++-code in the rom: stock laos llvm/clang
Your milleage may vary, but to me this combination is CURRENTLY giving the best ballance of performance and bat life. Let me know your impressions.
Changelog:
Remove Snapdragon LLVM. — Nvertigo
Add aarch64-linux-android-6.4: stock gcc version 6.4.1 20171215 (crosstool-NG crosstool-ng-1.23.0-288-gadaa3a5d
Remove aarch64-linux-android-6.x. — Nvertigo
Remove aarch64-linux-android-5.x. — Nvertigo
Remove aarch64/aarch64-linux-android-4.9. — Nvertigo
Remove aarch64-linux-android-4.9-kernel. — Nvertigo
Fix derp in opting in LINEAGE_VERSION_APPEND_TIME_OF_DAY. — nvertigo
Opt in LINEAGE_VERSION_APPEND_TIME_OF_DAY. — nvertigo
Use GNU gcc 6.4.1 for kernel building. — nvertigo
gcc-6.4.1: disable unused-const-variable warnings. — nvertigo
gcc-6.4.1: remove unsed variable fsm_en. — nvertigo
gcc-6.4.1: fix a bunch of (misleading) indents. — nvertigo
bluetooth: hci_sock: Fix warning detected by gcc 5.3.1 — NewEraCracker
tfa9890: tfa_container: Fix warnings detected by gcc 5.3.1 — NewEraCracker
treewide: Fix code errors detected using Linaro GCC 6.3.1 — Sultan Alsawaf
treewide: Properly fix use of uninitialized variables — Sultan Alsawaf
Bootlogo choices
nlos_bootlogo-v0.1.zip
back_in_black_bootlogo-v1.0.zip
[SIZE=+2]DOWNLOAD[/SIZE]​
Happy flashing!
Build 20171230
Releasenotes:
This build requires firmware OpenBeta 15 (aka ob15). As always an archive of all firmwares can be found below in the firmware section of Downloads - the flashable firmwares are the original (file names starting with oxygenos* hold original fw files) OnePlus fw images. NLOS and 'old'-style bootlogos can be found down in this posting.
Changelog:
mcpu: use cortex-a53 with stock clang/llvm. — nvertigo
Revert "msm: camerav2: isp: Reserve rdi ub based on image size" — nvertigo
Revert "msm: camera: Synchronize v4l2 subscribe and unsubscribe event in camera.c" — nvertigo
Revert "msm: camera: isp: Allocate kernel page and map to userspace" — nvertigo
Bootlogo choices
nlos_bootlogo-v0.1.zip
back_in_black_bootlogo-v1.0.zip
[SIZE=+2]DOWNLOAD[/SIZE]​
Happy flashing!
May the source be with you and yours in 2018!
Build 20171223 (xmas-firmware)
Releasenotes:
This build requires firmware OpenBeta 15 (aka ob15). As always an archive of all firmwares can be found below in the firmware section of Downloads - the flashable firmwares are the original (file names starting with oxygenos* hold original fw files) OnePlus fw images. NLOS and 'old'-style bootlogos can be found down in this posting.
Changelog:
Firmware requirementsnhave not changed, but to avoid unneseccary hussles during Xmas I included the firmware (with nlos bootlogo) again for this build.
disable SDCLANG and UBERTC for now (to minimize any issues).
Bootlogo: add NLOS bootlogo. — nvertigo
net/wireguard: add wireguard importer — nvertigo
Revert "msm: mdss: Do not attempt to request TE irq again if already requested" — dianlujitao (laos/cm-14.1
op3: Regen defconfig — dianlujitao
ANDROID: ion: Fix uninitialized variable — Daniel Rosenberg
drivers: staging: Update qcacld-2.0 driver — Luca Stefani
Merge tag 'LA.UM.5.5.r1-06400-8x96.0' of https://source.codeaurora.org/quic/la/kernel/msm-3.18 into cm-14.1 — dianlujitao
sepolicy: allow apps to stat processes. — nvertigo (nvertigo/nlos-14.1, github/nlos-14.1, nlos-14.1
sepolicy: allow cameraserver to search mpctl socket directories. — nvertigo
sepolicy: add a bunch of denials need for different apps. — nvertigo
sepolicy: allow hostapd to access diag_device. — nvertigo
gps: update to LA.UM.5.5.r1-06400-8x96.0. — nvertigo
Revert "IMS: fix derp: remove some test settings again." — nvertigo
sepolicy: allow time_daemon to connect to unix_stream_socket. — nvertigo
sepolicy: allow mediacodec to search mpctl. — nvertigo
sepolicy: allow system_server to use setsched. — nvertigo
init: set downmigrate after upmigrate. — nvertigo
init: remove some artefacts from eas. — nvertigo
oneplus3: Enable framework sched boost — Sultanxda
BoardConfig.mk: remove out-commented SDCLANG. — nvertigo
Bootlogo choices
nlos_bootlogo-v0.1.zip
back_in_black_bootlogo-v1.0.zip
[SIZE=+2]DOWNLOAD[/SIZE]​
Happy flashing!
Firmware
NVertigo's Oxygen Firmware Archive
Renamed blobs (for use with custom kernels build for unified roms)
NVertigo's UniBlob Archive
TWRP
https://forum.xda-developers.com/oneplus-3/development/recovery-official-twrp-oneplus-3-3t-t3543391
Google Apps:
Beans Dynamic Mini Gapps
Source and toolchains
https://github.com/LineageOS/
https://github.com/nvertigo/local_manifest/tree/cm-14.1 (If you want to build this rom yourself, consult the file named README)
Aytex, who made all of the banners on this post.
team-exynos5429 for the OP templete.
All the LineageOS-Team.
@Lord Boeffla for patiencely answering my questions.
@koenkk
@Sultanxda
@TheFrozen4 for documentation and optimizing this OP.
@m0d hipp¥ for mirroring.
@mad-murdock for first testings.
The microG Team
Nathan Chancellor for LineageOMS, especially for this wonderfull piece of software.
@joshuous for introducing and explaing EAS to me and making VoxPopuli public. Last and not least for running EAS-Project.
@RenderBroken for providing EAS patches for EAS-Project's LineageOS based kernel.
@UnbracedTundra for all the awesome NLOS-ArtWork.
@zx2c4 for Wireguard VPN (dedicated Wireguard Thread)
...and everybody I forgot.
Happy flashing!

I will be putting the latest mirror's of nvertigo67's rom on here.
Additional Files​OxygenOS - ob8 firmware - http://x-null.net/xda/nvertigo67/Other/oxygenos-ob8-firmware.zip
OxygenOS - ob7 firmware - http://x-null.net/xda/nvertigo67/Other/oxygenos-ob7-firmware.zip
OxygenOS - ob6 firmware - http://x-null.net/xda/nvertigo67/Other/oxygenos-ob6-firmware.zip
OxygenOS - ob5 firmware - http://x-null.net/xda/nvertigo67/Other/oxygenos-ob5-firmware.zip
OxygenOS - ob4 firmware - http://x-null.net/xda/nvertigo67/Other/oxygenos-ob4-firmware.zip
4.0.3 firmware - http://x-null.net/xda/nvertigo67/Other/oxygenos-4.0.3-firmware.zip
TWRP 3.0.4-1 - http://x-null.net/xda/nvertigo67/Other/twrp-3.0.4-1-oneplus3.img
TWRP 3.1.0-1 - http://x-null.net/xda/nvertigo67/Other/twrp-3.1.0-1-oneplus3t.img
Open Gapps Nano 01-20-2017 - http://x-null.net/xda/nvertigo67/Other/open_gapps-arm64-7.1-nano-20170120.zip
Newest will be on top​
June 6 2017​http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170606-UNOFFICIAL-nvertigo-oneplus3t.zip
June 6 2017​http://www.x-null.net/xda/nvertigo6...06-UNOFFICIAL-nvertigo-gps-test-oneplus3t.zip **GPS TEST**
June 2 2017​http://www.x-null.net/xda/nvertigo6...02-UNOFFICIAL-nvertigo-firmware-oneplus3t.zip
May 24 2017​http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170524-UNOFFICIAL-nvertigo-oneplus3t.zip
May 18 2017​http://www.x-null.net/xda/nvertigo6...18-UNOFFICIAL-nvertigo-firmware-oneplus3t.zip
May 15 2017​http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170515-UNOFFICIAL-nvertigo-oneplus3t.zip
May 9 2017​http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170509-UNOFFICIAL-nvertigo-oneplus3t.zip
May 3 2017​http://www.x-null.net/xda/nvertigo6...03-UNOFFICIAL-nvertigo-firmware-oneplus3t.zip
Apr 26 2017​http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170426-UNOFFICIAL-mad-murdock-EXP-oneplus3t.zip *Experimental with OMS*
Apr 22 2017​http://www.x-null.net/xda/nvertigo6...NOFFICIAL-nvertigo-EXP-firmware-oneplus3t.zip *Experimental*
Apr 18 2017​http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170418-UNOFFICIAL-nvertigo-oneplus3t.zip
Apr 11 2017​http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170411-UNOFFICIAL-mad-murdock-oneplus3t.zip
Apr 7 2017​http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170407-UNOFFICIAL-mad-murdock-oneplus3t.zip
Apr 4 2017​http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170404-UNOFFICIAL-mad-murdock-oneplus3t.zip
Apr 1 2017​http://www.x-null.net/xda/nvertigo6...01-UNOFFICIAL-nvertigo-firmware-oneplus3t.zip
Mar 30 2017​http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170330-UNOFFICIAL-nvertigo-oneplus3t.zip
Mar 28 2017​http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170328-UNOFFICIAL-mad-murdock-oneplus3t.zip
Mar 24 2017​http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170324-UNOFFICIAL-nvertigo-oneplus3t.zip
Mar 20 2017​http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170320-UNOFFICIAL-nvertigo-oneplus3t.zip
Mar 16 2017​http://www.x-null.net/xda/nvertigo6...16-UNOFFICIAL-nvertigo-firmware-oneplus3t.zip
Mar 12 2017​http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170312-UNOFFICIAL-nvertigo-oneplus3t.zip
Mar 7 2017​http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170307-UNOFFICIAL-nvertigo-oneplus3t.zip
Mar 4 2017​http://www.x-null.net/xda/nvertigo6...04-UNOFFICIAL-nvertigo-firmware-oneplus3t.zip
Mar 1 2017​http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170301-UNOFFICIAL-nvertigo-oneplus3t.zip
Feb 25 2017​http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170225-UNOFFICIAL-nvertigo-oneplus3t.zip
Feb 24 2017​http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170224-UNOFFICIAL-nvertigo-oneplus3t.zip
Feb 18 2017​http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170218-UNOFFICIAL-nvertigo-oneplus3t.zip
Feb 14 2017​http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170214-UNOFFICIAL-nvertigo-oneplus3t.zip
Feb 10 2017​http://www.x-null.net/xda/nvertigo6...10-UNOFFICIAL-nvertigo-firmware-oneplus3t.zip
Feb 6 2017​http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170206-UNOFFICIAL-nvertigo-oneplus3t.zip
https://mega.nz/#!aYNkERIb!QyFzj6IZAchSL0TqIn-ZDIrsZulStkbDZi0RF1oyJcg - credit to @t-shock
Feb 3 2017​http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170203-UNOFFICIAL-nvertigo-oneplus3t.zip
Feb 1 2017​http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170201-UNOFFICIAL-nvertigo-oneplus3t.zip
https://mega.nz/#!jRdB1aRZ!-QzqNBaP_7QWZPxpuFQz1X3a7IghVy21xLDqyTlJew8 - credit to @t-shock

3T only - why that?
Since the latest changes in init and overlay, I don't think this posting is true any longer.
I don't like to publish a rom for a device I have not my hands on. So this is still 3t-only.
I completely understand all devs doing unified builds. I completely understand it was so annoying, that oneplus launched 3T half a year after 3, and devs wanted to preserve their work, or don't want to buy just another device. So if you think unified builds are your way, I understand and appriciate that!
For me, on the other hand, it looks like this: I've come from bacon to 3t, I have no 3 and my personal policy is building only for devices I have my hands on. I like OOS - indeed for me it's one of the best stock roms I've ever seen - but it lacks some features I learned to love in cm times, like privacy, app-ops, automatic do not disturb rules and much more.
I lurked some time around in the threads, build OSS from source and tried to dig in the sources. I tried hard to understand the differences of 3 and 3t. What I found in most of the sources was @Sultanxda's and @Graraks patches to load different adreno firmware.
Then I pulled blobs from OOS-4 for 3t and ran diff against the onplus3 blobs from themuppets. I don't say they were completely different, but they differed in about 4/5th of the files (as you can see in this commit: https://github.com/nvertigo/proprie...mmit/17c7609f79167c02041736306b18f52bca5b9ac6). Then I compared the specs of 3 and 3t - surprise: they are different...
Let me give you an example: the battery is different. That means power_profile.xml has to be different for 3 and 3t, too. If you got traped by the hoax, that the 3t comes with a 3000 mAh battery read this.
So I decided to build a rom with all blobs beeing native and configuration optimized for 3t. To my surprise my first attempt ended in a build so smooth with all features I missed, that I fell in love instantly. So I spent even more time on this, added busybox (not as toybox' replacement, but just as binary in /system/xbin/busybox) and used native qcom SnapDragon llvm for CLANG and UBERTC/linaro for kernel.
At this point @mad-murdock tested the build. I wasn't sure about my own perception, because it was my own rom. He ensured me though, it was stable and smooth. So I was happy with the build.
I don't say it's not possible to achieve all this with an unified build. But I'm absolutely sure, that 3 and 3t differ in more aspects then graphic blobs. These differences need to be addressed in unified builds (RR seems to be a step ahead compared to laos). This is far behind my scope (and to stick to my personal policy to build only for devices I have hands on, I would need to get a 3 and a second sim), so here we are: LineageOS for 3t only.
I surely don't want to start a religous debate on "the right way" of building roms for 3 and 3t - there are always many ways to build awesome roms - this is just my way for the moment.

Known Issues
General known issues
If you want to report an new issue provide logs. If you don't know what logcat is or how to deal with it this posting is for you.
The following stroked isaues may or may not be present on Snap - to avoid all Snap hazards, NLOS is shipped with Camera2 (atm I recommend the modded Google Camera from Modded Google Camera with HDR+, 60FPS video and Slow Motion by @S4turno or the modded OnePlusCamera from my downloads - do NOT! install both the same time: it's GCam XOR OPCam:
camera: continuous shot not working select sports mode[/STRIKE]
camera: HDR on front camera just produces a green picture
camera: front camera in HAL1 mode: one of the first two or three shots, let the camera server crash - following shots are perfectly ok til next reboot.
Workarounds:
The ugly one: use OnePlusCamera or Snap and take pictures (mostly one to three) til camereserver crashes, wait 7 seconds and use your prefered HAL1 cam as usual.
The more elegant one: use a cam app that supports HAL3 (api2) like opencamera by @mdwh (recommended: it's opensource and free of charge - don't forget to donate, if you decide to use it on a regular basis) or one of the closed source apps.
camera: first still while taking a video is broken.
sRGB-Mode is not setable from Settings; workaround: https://forum.xda-developers.com/showpost.php?p=70799426&postcount=53You find sRGB as color mode in LiveDisplay
encrypting an unencrypted data partition is currently NOT working - no matter if ext4 or f2fs. Workaround: restore your oos nandroid, encrypt your phone by setting pin or password to something new, and tap on "secure phone on startup" (might not be the accurate phrase, but you know, what I mean when you see it.)
Gapps known issues
You can easily avoid all of this - and propably much more - if you stick to the recommended gapps package!
The notification slider isn't working.
webview is stuttering and lagging
first time setup can't be completed.
dialer is not working as expected
unpredictable behavior of UI
random (or not so random) fc's of system components (apps and/or services)
I did not flash the correct Google Apps version!
Some Google App versions overwrite critical system components, which leads up to all kind of random issues. One of the most obvious issues, is gapps preventing Lineage setup to start, and will instead guide you through the AOSP Setup Wizard. This will cause issues, amongst others the Alert Slider on the left side of the phone will not work. If you encounter this or other problems, you need to wipe system, data and caches, before you reflash the ROM and the suggested version of Google Apps linked in the download section of OP. After initial setup, the google apps will update via playstore so don't worry about that. With this package installed, you can install all your missing gapps from playstore. The great advantage is, that the added gapps from playstore will be installed as user-apps and therefore won't mess up your system.
HOWTO: build this rom from source
See the README in
https://github.com/nvertigo/local_manifest

UPDATED: Camera Mods
To give the user more freedom of choice, OnePlusCamera and onePlus Gallery are removed from the rom. In this posting I provide additionally installable apks, to allow the user to install them as any other apk.
@kxzxx's mod (use to get the same cam setup we use for four months - callbacks removed):
https://drive.google.com/open?id=0B_f72wz8rwc6SV9VTXRXMVdfeFk
This should work on all laos based roms. Recommended, if you want the very same setup as before.
Update Version 1.5.0 (ob14): https://drive.google.com/file/d/0B_f72wz8rwc6dEpHUGVlQ2hYY28/view?usp=drivesdk
Plain stock OOS gallery - op3/t (dng support):
https://drive.google.com/file/d/0B_f72wz8rwc6QWNWUDhpQWhJa3M/view?usp=drivesdk
This should work on any rom without OnePlusGallery not installed.
Update Version 1.8.4 (ob14): https://drive.google.com/file/d/0B_f72wz8rwc6S2VkV1VsaHNNYzA/view?usp=drivesdk
Some candy:
Plain stock OOS 4.5.x cam - op5 (sometimes glitchy, flash not working reliable - raw working [set iso and shutter manually in pro-mode]):
https://drive.google.com/file/d/0B_f72wz8rwc6UzBoUlNhT0NabWs/view?usp=drivesdk
Outdated and obsoleted - just for reference: If you want to check this out on our current rom, needs to remove OnePlusCamera&Gallery first. Flash this in recovery:
https://drive.google.com/file/d/0B_f72wz8rwc6b2xUSUZQMXNuck0/view?usp=drivesdk
@homebuilders and all interessted people:
This is neither a HOWTO, nor a script (op3t/op5 is hardcoded, because I havn't parsed arguments), but gives at least an impression on what is needed to make a other roms system app an user installable app. As you can see, I sign the apk with laos test keys. The key does not really matter, as long as the apk is signed at all.
Code:
cat build.sh
#!/bin/bash
S1="-decompiled"
S2="-unaligned-unsigend.apk"
S3="-unaligned.apk"
S4="-v1.4.0-op3-nvertigo.apk"
for i in $*; do
apktool d -f -v -t oxy -o $i$S1 $i.apk
cp -av lib $i$S1
apktool b -f -o $i$S2 $i$S1
../.signing/sign.sh $i$S2 $i$S3
zipalign -f -v 8 $i$S3 $i$S4
done
cat sign.sh
#!/bin/bash
java -Xmx2048m -Djava.library.path=/mnt/export/data/src/cm14/out/host/linux-x86/lib64 -jar /mnt/export/data/src/cm14/out/host/linux-x86/framework/signapk.jar -w /mnt/export/data/src/cm14/build/target/product/security/testkey.x509.pem /mnt/export/data/src/cm14/build/target/product/security/testkey.pk8 $1 $2
@kxzxxx: if you still read here and if you have plenty of (spare-)time, would you be so awesome to look into op5 cam for callbacks on flash? I tried based on op3 cam, but failed. No need to hurry. Thanx in advance.
You should also checkout these:
MI5 camera mods (by @Arnova8G2): https://forum.xda-developers.com/mi-5/themes/app-collection-camera-modded-t3591177
OxygenOS Camera Mod (by @siankatabg): https://forum.xda-developers.com/oneplus-3/themes/port-oxygenos-stock-camera-cm-t3451721
Pixel Google Camera: https://www.xda-developers.com/google-camera-hdr-ported/

nvertigo67 said:
Since my time is quite limited till end of October, @mad-murdock is providing you with new builds.
Click to expand...
Click to collapse
I build these ROMs from source for quiet a while for myself. So I am the build slave or OP now. I use nvertigo's sources unchanged. Using the 141-work branch - in case you want to build yourself.
Mirror: posting #2. I assume @m0d hipp¥ will update it like usual.
Build 20170522
Some advice on Theme/OMS/Substratum users. You can ignore this, if you don't use themes:
Make sure you disable all overlays in substratum BEFORE dirty flashing.
If you ignore this, you get a force close of system-ui on boot.
To fix such errors, flash /sdcard/substratum/SubstratumRecovery.zip in TWRP. This will remove any OMS overlays and allow you to boot again.
To enable your Theme again, you must BUILD it, not only enable. Enabling it without building will make system-ui force-close again and requires you to flash the recovery zip in TWRP.
Changelog
I am a bit confused about changes. This part will be updated soonish.
Updated to latest LaOS and OMS sources.
Note on firmware: This build requires OOS beta 7 firmware. If you get an TZ error while flashing, make sure to flash OOS beta 7 firmware first. It was included for users having flashed lineage-14.1-20170518-UNOFFICIAL-nvertigo-firmware-oneplus3t.zip.
ROM: lineage-14.1-20170522-UNOFFICIAL-mad-murdock-oneplus3t.zip
MD5: 4f6208f56b4a1fce39a34830f03ec294
Mirror: posting #2
Happy flashing!
Experimental Build 20170426
This is an updated experimental build with OMS. See nvertigo's post of last build for details.
Some advice on Theme/OMS/Substratum users. You can ignore this, if you don't use themes:
Make sure you disable all overlays in substratum BEFORE dirty flashing.
If you ignore this, you get a force close of system-ui on boot.
To fix such errors, flash /sdcard/substratum/SubstratumRecovery.zip in TWRP. This will remove any OMS overlays and allow you to boot again.
To enable your Theme again, you must BUILD it, not only enable. Enabling it without building will make system-ui force-close again and requires you to flash the recovery zip in TWRP.
Changelog
I don't have changes. Shame on me. Rebooted Windows for gaming.
Of course updated to latest LaOS and OMS sources.
Note on firmware: This build requires OOS beta 5 firmware. If you get an TZ error while flashing, make sure to flash OOS beta 5 firmware first. It was included for users having flashed lineage-14.1-20170422-UNOFFICIAL-nvertigo-EXP-firmware-oneplus3t.zip.
ROM: lineage-14.1-20170426-UNOFFICIAL-mad-murdock-EXP-oneplus3t.zip
MD5: 8aa8df7ed35999ec47c8ea23d659f78e
Mirror: posting #2
Happy flashing!
Build 20170411
It's that time again to update your ROM. No side-effect reported from last test-build, so we consider it stable.
Changelog
No changes, except updated to latest LaOS sources
Note on firmware: This build requires OOS beta 4 firmware. If you get an TZ error while flashing, make sure to flash OOS beta 4 firmware first. It was included for users having flashed lineage-14.1-20170401-UNOFFICIAL-nvertigo-firmware-oneplus3t.zip.
ROM: lineage-14.1-20170411-UNOFFICIAL-mad-murdock-oneplus3t.zip
MD5: 6b76cd3366c9beb3df1aa30d6a8deb2a
Mirror: posting #2
Happy flashing!

Thanks!!
your rom is best!!

Thanks guy ! Great

Great to see you started your own thread afterall. Going to flash this today, also because @mad-murdock approves this rom so much . Can't wait!
edit: found a small typo in the instructions. Check the year @nvertigo67 :
"Install the Google Apps addon package (Optional. Use opengapps nano package from 20160120)"

Update: Wipe before you install.
You might want to know that I flashed this ROM dirty over koenkk's ROM.
I have no problems doing so. Be advised though, that this isn't recommended and can result in stuff not working. You can try a dirty flash, if it works, fine. If not, just wipe as in official instructions.

Just flashed your Rom. Fluent and feels natural! Thanks Developer

Glad to see you posting a thread on XDA

mad-murdock said:
You might want to know that I flashed this ROM dirty over koenkk's ROM.
I have no problems doing so. Be advised though, that this isn't recommended and can result in stuff not working. You can try a dirty flash, if it works, fine. If not, just wipe as in official instructions.
Click to expand...
Click to collapse
I like experimenting, I like dirty flashing, I like custom kernels (indeed I'd love to see Boeffla cm/laos-14.1 kernel) and I want to encourage everybody to home-build, experiment, dirty flash, try mods, kernels or what ever: he, who never bricked an android device, has not flashed hard enough.
The only problem with that is support: I can't test any combination, reproduce issues and so on. Also if everybody reports on his very own combination, the thread becomes unreadable/unundestandeble.
So I kindly ask you to try whatever you want; but if reporting an issue, stick to OP rules, please.

HOWTO: build this rom yourself
The "homegrow"-howto is here in the file named README.

nvertigo67 said:
break for me now.
Click to expand...
Click to collapse
Well deserved. Take care.

Has anyone installed this ROM after formatting system and cache to F2FS?

System and cache as f2fs is rare. No idea which Roms support this. I would say, just try, if it won't work, format system and cache. It's no extra effort.
Just make sure not to reboot recovery while system is blank, since TWRP pulls crypto lib from system

nvertigo67 said:
I surely don't want to start a religous debate on "the right way" of building roms for 3 and 3t - there are always many ways to build awesome roms - this is just my way for the moment.
Click to expand...
Click to collapse
Hi. I like the way, that you chose. Hope you will doing it in future. Like and you, I came from oneplus one.
Btw. What about sRGB mode? Is it here ? I'm hate oversaturated colors. After opo it's looks so ****ty..

sorry to be a pain but how long does it take for first boot? I've been waiting for 15 mins so I'm not sure if I've done something wrong...

hassan_1000 said:
sorry to be a pain but how long does it take for first boot? I've been waiting for 15 mins so I'm not sure if I've done something wrong...
Click to expand...
Click to collapse
it depends on how many apps you had installed. still, 15 minutes sounds pretty long. did you dirty flash without wiping? if so, you should probably go and wipe now.

Here’s my build of LineageOS 14.1 for Raspberry Pi 3 Model B. It is unofficial and unsupported by the LineageOS team. It’s for advanced users only.
{
"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"
}
https://konstakang.com/devices/rpi3/CM14.1/
lineage-14.1-20180817-UNOFFICIAL-KonstaKANG-rpi3.zip
https://www.androidfilehost.com/?fid=1322778262903982504
md5:affa35dd70b51e4b70c9acb996f7304b
Sources:
lineage-rpi
Thanks:
peyo-hd and everyone who’s contributed to android-rpi
LineageOS team & everyone who’s been working on CM14.1

How to install:
Follow the official Raspberry Pi instructions for writing the image to the SD card (Linux, Mac, Windows).
FAQ:
Q: I can’t find developer options, why?
A: Settings -> About phone -> Click ‘Build number’ several times
Q: I don’t have reboot options in power menu, why?
A: Settings -> Developer options -> Advanced restart
Q: I have no root, why? What is that hashtag on my status bar?
A: You need enable root access under Settings -> Developer options -> Root access. Root management is now integrated as part of LineageOS’ Privacy Guard and you can manage per app permissions under Settings -> Developer options -> Manage root access. You’ll have a persistent notification in the status bar when you’re running an app that uses root permissions.
Q: I have official 7” LCD display and touchscreen. What should I do?
A: Execute following commands in ‘adb shell’/serial console/terminal (you can enable built-in terminal app from Settings -> Developer options -> Local terminal) and reboot your device:
Code:
su
rpi3-display.sh
Q: Settings -> Storage shows xx GB used by system. There’s unallocated space on my sdcard. What should I do?
A: This is a 4 GB image, remaining space on your sdcard will remain unallocated. Settings app shows unallocated space as used by system which in reality it is not. You can use e.g. GParted and extend /data partition (/dev/block/mmcblk0p3) to cover the unallocated space. Resizing the partition manually will break support for encrypting /data. Format /data in TWRP recovery (Wipe->Format data) after resizing to leave required space for crypto footer.
Q: Raspberry Pi doesn’t have power button, how do I power off/reboot my device?
A: Following keyboard keys work as Android buttons: F1 = Home, F2 = Back, F3 = Multi-tasking, F4 = Menu, F5 = Power, F11 = Volume down, and F12 = Volume up. You can also use one of many third party reboot applications.
Q: How to boot to TWRP recovery?
A: There’s currently no proper way to boot between Android and TWRP, but this can achieved by renaming the ramdisk you want to boot. Execute following commands in ‘adb shell’/serial console/terminal (you can enable built-in terminal app from Settings -> Developer options -> Local terminal) and reboot your device:
Code:
su
rpi3-recovery.sh
If mouse cursor doesn’t appear, try replugging your mouse.
Q: How to boot out of TWRP recovery?
A: Flash my recovery2boot zip in TWRP.
Q: How to install Google apps?
Download open_gapps-arm-7.1-pico-xxxxxxxx.zip and save it to your device’s internal storage or use an external USB drive
Boot to TWRP recovery (see FAQ)
Install open_gapps-arm-7.1-pico-xxxxxxxx.zip from your selected storage
Wipe->Factory reset!
Boot out of recovery (see FAQ)

Merged commits not mentioned in the changelog.
17.8. changelog:
include TWRP 3.2.3-0 custom recovery (see FAQ how to boot)
fix Gallery app crashing (and likely various third party apps as well)
add support for encrypting the device
merge AOSP kernel/common android-4.4-n branch to have proper Android Nougat kernel
update to Linux 4.4.148 kernel and patch known vulnerabilities (CVE-xxxx-xxxx, and more)
Android security patch level: 5 August 2018 (merged)
15.6. changelog:
add support for USB webcams (UVC) with third party USB webcam apps
default to noop I/O scheduler
update to Linux 4.4.137 kernel and patch known vulnerabilities (CVE-xxxx-xxxx, and more)
Android security patch level: 5 June 2018 (merged)
15.4. changelog:
update audio HAL (fix USB microphone, etc)
add support for external USB GPS dongles (1546:01a7 U-Blox AG, etc - GPS dongle must be plugged-in while booting the device)
update to Linux 4.4.127 kernel and patch known vulnerabilities (CVE-xxxx-xxxx, and more)
Android security patch level: 5 April 2018 (merged)
18.1. 2018 changelog:
add support for I2C devices
enable Android low-RAM configuration
add lights HAL to control display brightness from Android on offical RPI display (version 1.1)
update to Linux 4.4.112 kernel and patch known vulnerabilities (CVE-xxxx-xxxx, and more)
Android security patch level: 5 January 2018 (merged)
17.11. changelog:
fix wifi reconnect on boot (thanks to Google)
update to Linux 4.4.97 kernel and patch known vulnerabilities (CVE-xxxx-xxxx, and more)
patch recently disclosed BlueBorne and KRACK vulnerabilities (merged)
Android security patch level: 5 October 2017 (merged)
10.8. changelog:
update to Linux 4.4.80 kernel
merge AOSP kernel/common android-4.4 branch to have proper Android kernel
enable sdcardfs
add BFQ i/o scheduler and enable it by default
Jelly browser (merged)
Android security patch level: 5 August 2017 (merged)
16.4. changelog:
add support for wifi tethering
add support for Widevine DRM
improve Play Store compatibility
Android 7.1.2 (merged)
Android security patch level: 5 April 2017 (merged)
11.4. changelog:
initial relase
Previous builds:
AndroidFileHost

I cannot boot out of recovery after installing Gapps in TWRP. When I run rpi3-recovery.sh boot I got Segmentation Fault error. Please help. Thanks

Project999 said:
I cannot boot out of recovery after installing Gapps in TWRP. When I run rpi3-recovery.sh boot I got Segmentation Fault error. Please help. Thanks
Click to expand...
Click to collapse
Please read the FAQ! It doesn't say to run the same script, it says to flash recovery2boot zip in TWRP.
I'm aware of the segfault.

Ok, I was doing both ans will only flash the zip file next try.

Yes. It worked this time after only flashing the recovery2boot zip file. Thank you.

Its possible to update ROM via recovery?

laharl_22 said:
Its possible to update ROM via recovery?
Click to expand...
Click to collapse
No, not currently. Partition structure (especially boot partition) on this device is different than on Android devices usually (well, as Raspberry is not an Android device to begin with). It would require some quite significant modifications to LineageOS build system to build recovery flashable ROM zips for this device (it's all open source so you're welcome to have a crack at it). There's also no proper way to cold boot (from power off) to recovery which makes it less useful than on other devices. I only included TWRP recently and it's currently mostly just used for installing gapps.

KonstaT said:
No, not currently. Partition structure (especially boot partition) on this device is different than on Android devices usually (well, as Raspberry is not an Android device to begin with). It would require some quite significant modifications to LineageOS build system to build recovery flashable ROM zips for this device (it's all open source so you're welcome to have a crack at it). There's also no proper way to cold boot (from power off) to recovery which makes it less useful than on other devices. I only included TWRP recently and it's currently mostly just used for installing gapps.
Click to expand...
Click to collapse
So no way for updating ROM without loose data?

laharl_22 said:
So no way for updating ROM without loose data?
Click to expand...
Click to collapse
No, not currently and who said there was going to be any updates.
Well, you can actually restore your previous /data partition in TWRP after you've installed a new image.

Sorry, double post.

Hi.
Is there a GPIO support? Everything is working great, but I build it into my car, and I have some pushbuttons connected. I would like to use it for opening apps or shutdown etc. Any ideas? couldn't find anything on google? Thanks

ulfdogg said:
Hi.
Is there a GPIO support? Everything is working great, but I build it into my car, and I have some pushbuttons connected. I would like to use it for opening apps or shutdown etc. Any ideas? couldn't find anything on google? Thanks
Click to expand...
Click to collapse
Yes, that should be possible but you need to do a little work for that.
4.4 kernel used in LineageOS 14.1 doesn't have gpio-key overlay (https://github.com/raspberrypi/linux/commit/7bc9c88a0eb043c5387a23d4ade23359749398e0) but I have already enabled KEYBOARD_GPIO that is also needed for this. So you need to build that overlay, copy it to device, and configure it in config.txt depending on what GPIO pins you're using. There's also another similar approach (different overlay) that's been reported working. https://stackoverflow.com/questions/50224010/using-gpio-keys-interrupt-to-wake-up-screen-on-rpi3

Does this build support 3b+?If not,how to ?

zhengyw said:
Does this build support 3b+?If not,how to ?
Click to expand...
Click to collapse
No, you can use LineageOS 15.1 build instead.
This build uses Linux 4.4 kernel and Broadcom added support for 3B+ only on later kernel versions (4.9 and 4.14). 4.4 is actually the newest that Android Nougat supports (https://android.googlesource.com/kernel/common/) and there's some network issues using newer ones. 4.9 is the newest for Oreo and 4.14 for Pie. So the Linux kernel in LineageOS 15.1 is actually too new for the Android version. There's no major changes between Oreo and Pie kernels, though.
Android kernel versions lag behind mainline because chipset manufacturers (Qualcomm, etc) need to make significant modifications to support their hardware. Android devices usually stay with the Linux kernel version they initially shipped with so there also needs to be quite long support time (4.4 is still supported with Pie).

KonstaT said:
No, you can use LineageOS 15.1 build instead.
This build uses Linux 4.4 kernel and Broadcom added support for 3B+ only on later kernel versions (4.9 and 4.14). 4.4 is actually the newest that Android Nougat supports (https://android.googlesource.com/kernel/common/) and there's some network issues using newer ones. 4.9 is the newest for Oreo and 4.14 for Pie. So the Linux kernel in LineageOS 15.1 is actually too new for the Android version. There's no major changes between Oreo and Pie kernels, though.
Android kernel versions lag behind mainline because chipset manufacturers (Qualcomm, etc) need to make significant modifications to support their hardware. Android devices usually stay with the Linux kernel version they initially shipped with so there also needs to be quite long support time (4.4 is still supported with Pie).
Click to expand...
Click to collapse
Thank you..So I have to wait till los 15.1 go stable

Hi, thanks for this build, I might have done something wrong as I can't past the setup wizard, after security setup it comes back to lineageOS startup screen and the begin button to start again the setup wizard

s1lex said:
Hi, thanks for this build, I might have done something wrong as I can't past the setup wizard, after security setup it comes back to lineageOS startup screen and the begin button to start again the setup wizard
Click to expand...
Click to collapse
I've heard about this but can't reproduce it myself and I haven't seen any logs (logcat). You could try using another faster sdcard. Some people have also removed the SetupWizard apk from the image manually.

Hi there,
Thanks for amazing work!
The only issue I'm experiencing is some flickering in graphic heavy and full screen apps. Am I doing something wrong or it's a known issue?
I just noticed that it's happening more when I use: "dtoverlay=vc4-fkms-v3d,cma-256"
But with dtoverlay=vc4-kms-v3d,cma-256 composite video output is not there. Any solutions?

This thread is discontinued - please visit the LineageOS 17.1 sucessor thread
This thread aims at providing LineageOS 16.0 builds for the Sony Xperia Z1 compact with current security patches.
You can consider this thread as a successor of our LineageOS 15.1 thread, where you may also find some useful information.
This is the joint effort of 115ek and MSe1969 (contributions welcome).
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you. Hard & a lot.
*
*/
We offer two build variants:
A. Standard LineageOS 16.0 build
This build flavor aims at providing LineageOS 16.0 "as is" with most recent security patches.
If you want to install Google Apps (GApps) you have to use this build variant.
GApps are optional, of course. The smaller the GApps package, the better (pico). If you want "Okay google" support you need at least nano.
Just check the package comparison to see what fits your needs.
B. Pre-installed microG build variant with additional security patches
For the security/privacy focused (more details about below feature list, see here)
Pre-installed microG and F-Droid same as the LineageOS for microG project
Pre-installed AuroraStore
eSpeak TTS engine (FOSS TTS solution)
Additional security hardening features listed below
Access to /proc/net blocked for user apps
Bundled netmonitor app to allow network monitoring
Enhanced Privacy Guard: Switches for motion sensors and other sensors
Cloudflare as default DNS (instead of Google)
Privacy-preferred default settings
Optional blocking of Facebook- and Google-Tracking
Optional disable captive portal detection
Increased max. password length of 64
No submission of IMSI/phone number to Google/Sony when GPS is in use
Default hosts file with many blocked ad/tracking sites
Privacy-enhanced Bromite SystemWebView
Additional restriction options for secondary users
Constified JNI method tables
Status
List template by AdrianDC
Code:
- Boot : Ok
- Partitions (Data, Cache) : Ext4 and F2FS supported
- Bluetooth : Ok
- WiFi : Ok
- WiFi Hotspot : only 2.4 GHz
- RIL - Phone - Data : Ok
- GPS : Ok
- Camera : Ok
- Camcorder : Ok
- Lights : Ok
- MicroSD : Ok
- Accelerometer : Ok
- Compass : Ok
- Gyroscope : Ok
- Touchscreen : Ok
- FM Radio : Ok (mono)
- ANT+ : Ok
- Vibrator : Ok
- Microphone : Ok
- Audio & music : Ok
- Bluetooth audio : Ok
- MHL: broken
- NFC : Ok
- Kernel : Ok
- Graphics : Ok
- 3D Rendering : Ok
- Clock : Ok
- Offline Charging : Ok
- USB : Ok
- USB OTG : Ok
- Encryption : Ok
- SEPolicies : Enforcing
Limitations
Following limitations are known:
NFC-HCE does not work (needed for example for google pay)
FM does not work in stereo mode (mono works fine, though)
Problems with some 5 GHz Wifi channels (can be avoided by not using autochanneling) fixed with 20190408 build
MHL does not work
5 GHz hotspot does not work (2.4 GHz hotspot works fine)
ANT+ does not work fixed (see FAQ)
installing Magisk 19.1 prohibits entering recovery fixed with 20190521 build
GPS gets wrong time due to GPS week rollover since 3rd November 2019 (of importance when you record GPS tracks for example).
This also happens on stock and several other legacy devices. fixed with 20190611 build
Click to expand...
Click to collapse
Download
SourceForge
Click to expand...
Click to collapse
FAQ
What recovery system to use?
Please use this TWRP if you want to use OTA updates and/or encryption.
Click to expand...
Click to collapse
What about root access?
Root isn't included per default (except root over adb, but it's off by default).
If you want to gain root access to your apps use one of these (depending on your taste/needs):
Official Lineage Add-on https://download.lineageos.org/extras use su (arm) 16.0 here and flash via TWRP
Magisk https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Please note there is an issue starting with Magisk 19.1 which leads you to being unable to boot to recovery in any way. More info
Click to expand...
Click to collapse
ANT+ isn't working?
You need the 2 apps:
ANT Radio Service (Github) / (Google play)
ANT+ Plugin Service (Github) / (Google play)
afterwards setting proper permissions is essential!
Go to Apps & Notifications -> See All Apps
Select 'ANT Radio Service'
Select Permissions
Select Additional permissions
Slide switch to allow using of ANT hardware
This refers to those instructions which worked for me
Click to expand...
Click to collapse
I've got problems AND have magisk/exposed installed
I won't support anything related to magisk/exposed/other heavily system modifying things.
If you're encountering problems please make sure you're using a clean installation (at most gapps) to verify/reproduce the issue.
Click to expand...
Click to collapse
Bugreports
You'll find information about logging here.
Please also note how you got the error or how it can be reproduced.
Click to expand...
Click to collapse
Sources
Kernel: https://github.com/lin16-microg/android_kernel_sony_msm8974
Manifest: https://github.com/lin16-microg/local_manifests
Click to expand...
Click to collapse
Credits
SpiritCroc: big thanks to him for maintaining the device trees and a lot of very useful hints
rcstar6696
SuperLamic
drakonizer
AdrianDC
munjeni: thanks for tips and tricks
nailyk: thanks for tips and tricks
All the other contributors on Sony msm8974 platform
LineageOS team
Click to expand...
Click to collapse
Installation instructions
Please see the OP of our (deprecated) LineageOS 15.1 thread or also here
Click to expand...
Click to collapse
Changelog
13.12.2020
ASB Security string 2020-12-01 (this month, no kernel updates found)
Webview updates for both builds (microG build on M87)
microG build only: F-Droid updated to 1.10-alpha1-114
microG build only: microG updated from upstream to 0.2.14.204215-15 (picked until 720b089)
Expand for older changelogs:
10.11.2020
ASB Security string 2020-11-05
Fix for CVE-2020-15999
AOSP E-Mail widget fixed
Webviews upodated to/within M86
microG build only: microG - fixes in EN API and GCM
microG build only: Replaced weak F-Droid signatures with ROM's V2 signatures
13.10.2020
ASB Security string 2020-10-05
microG build only: Bromite Webview on M86
microG build only: microG 0.2.12.203315 - including "Exposure notification API" for use of Covid tracing apps
microG build only: Additional hardening: constified JNI method tables
13.09.2020
ASB Security string 2020-09-05
Webviews on M85
microG build only: Added eSpeak TTS engine (microG build variant)
09.08.2020
ASB Security string 2020-08-05
Webviews on M84
microG build only: Location of firewall UI now in Network => data usage (Settings menu)
12.07.2020
ASB Security string 2020-07-05
microG build only: updated prebuilt microG GmsCore fom /e/ project (fixed FCM registration issues)
microG build only: F-Droid updated to 1.8 / F-Droid privileged extension updated to 0.2.11
microG build only: Aurorastore updated to 3.2.9 / AuroraServices updated to 1.0.6
11.06.2020
Security string 2020-06-05
GPS improvements / modernisation
Enable MIDI support
microG build only: Bromite Webview on M83
microG build only: Netmonitor exception in SEPolicy f. "Tracker Control" app
09.05.2020
Security string 2020-05-05
Standard build only:System Webview on M81
microG build only: AuroraStore updated to 3.2.8
11.04.2020
Security string 2020-04-05
Fix for CVE-2020-8597 (external/ppp)
Kernel: CVE-2019-10638 siphash 128bit for IP generation
microG build only: AuroraStore updated to 3.2.4
microG build only: Bromite Webview on M81
07.03.2020
Security string 2020-03-05
System Webviews on M80
2nd build variant 'hardened microG build' (known from 15.1 thread) available
microG build only: AuroraStore updated to 3.2.0
19.02.2020
fixed DRM (we now have widevine Level 3, Netflix for example runs fine)
fixed TWRP time bug
added option to prevent USB gadgets working when screen locked (trust HAL)
enabled changelog (can be accessed under /settings/system/updater/changelog)
synced LineageOS sources (security patch level February 05, 2020)
16.01.2020
synced LineageOS sources (security patch level January 05, 2020)
13.12.2019
synced LineageOS sources (security patch level December 05, 2019)
13.11.2019
fixed unreliable SMS/MMS receiving (https://review.lineageos.org/c/LineageOS/android_vendor_lineage/+/262653)
synced LineageOS sources (security patch level November 05, 2019)
19.10.2019
synced LineageOS sources (security patch level October 05, 2019)
13.09.2019
bring back wifi display
three finger screenshot gesture
synced LineageOS sources (security patch level September 05, 2019)
12.08.2019
fixed manual mobile network selection (once again)
synced LineageOS sources (security patch level August 01, 2019)
07.07.2019
synced LineageOS sources (security patch level July 05, 2019)
fixed AudioFX effects completely (thanks @NeoArian)
03.07.2019
start signing builds (please check this if you want to update)
enable OTA updates (thanks @NeoArian)
10.06.2019
synced LineageOS sources (security patch level June 05, 2019)
21.05.2019
fixed recovery issue introduced by Magisk versions starting with 19.1 (thanks @Myself5)
11.05.2019
synced LineageOS sources (security patch level May 05, 2019)
08.04.2019
fixed manual mobile network selection (thanks @SpiritCroc)
fixed problems with 5 GHz Wifi channels
added aptX/aptXHD
synced LineageOS sources (security patch level April 05, 2019)
11.03.2019
fixed alarm delay (came with new lineage sources)
fixed some more offline / USB charging problems (thanks @SpiritCroc)
synced LineageOS sources (security patch level March 05, 2019)
17.02.2019
fixed occasional camera problems (thanks @SpiritCroc)
various kernel patches (thanks @SpiritCroc)
synced LineageOS sources (security patch level February 05, 2019)
15.01.2019
fixed video playback for some applications (thanks @SpiritCroc)
fixed offline charging (thanks @SpiritCroc)
fixed FM radio (thanks @SpiritCroc)
updated webview to version 71 (thanks @MSe1969)
synced LineageOS sources
04.01.2019
initial release
Click to expand...
Click to collapse
XDA:DevDB Information
Lineage OS 16.0 for Xperia Z1 compact - amami, ROM for the Sony Xperia Z1 Compact
Contributors
115ek, MSe1969, SpiritCroc, drakonizer, rcstar6696, SuperLamic, AdrianDC, nailyk, LineageOS team
Source Code: https://github.com/lin16-microg/local_manifests
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.4.x
Version Information
Status: Stable
Stable Release Date: 2020-11-10
Created 2019-01-04
Last Updated 2020-12-13

Changelog
The changelog was moved to the OP due to xda not allowing secondary thread owners to edit this post

Tips & Tricks
microG initial configuration after 1st install (microG build variant only)
After the first installation of this ROM, you need to setup microG.
Please read the instructions given on the LineageOS for microG site, section "Post Install - UnifiedNlp"
OTA Updates on an encrypted device
In case your device in encrypted and you have flashed apps creating "survival scripts" in /system/addon.d (e.g. Magisk), there *may* be a dependency to files in the data partition.
An OTA update until current TWRP 3.3.1 does not decrypt the data partition, as this is usually not needed - under specific circumstances however, this may lead to unwanted effects (up to a non-booting device!) during an OTA update, if such scripts aim at modifying files located in the data partition. If unsure, rather perform the update manually as dirty-flash in TWRP or - which in general is a good practice - regularly perform backups in TWRP. If you haven't flashed anything on top of my build (except for the LineageOS root addon, which is no problem), there shouldn't be any issue.
(This commit in TWRP indicates, that this potential issue will be solved in future TWRP releases).

Ok ok .

new build
New build:
15.01.2019
fixed video playback for some applications (thanks @SpiritCroc)
fixed offline charging (thanks @SpiritCroc)
fixed FM radio (thanks @SpiritCroc)
updated webview to version 71 (thanks @MSe1969)
synced LineageOS sources
https://androidfilehost.com/?fid=11410963190603900297

Important announcement:
There were problems with FM radio in lineage-16.0-20190114 which was linked one post above.
Please use lineage-16.0-20190115 from here: https://www.androidfilehost.com/?fid=11410963190603901105

Took a while, but last night I flashed this. And it's fabulous! Some observations, regarding your list in the OP (couldn't test everything, though):
GPS: not just OK but I had the fasted 3D fix since I moved away from stock! Much faster than with signed LOS 15.1 or munjeni's LOS 7.1.2 (well below 10 seconds from my living room window, down from sometimes 90 - 120 seconds!)
WiFi Hotspot: working good and reliably
Compass: somewhat working but GPS Test says "unreliable", and indeed compared to my tablet directions are off by several degrees (pointing to NNW where the tablet says N); attempts to calibrate didn't have any effect
FM radio: working but mono (you wrote that already)
USB OTG: working good and at least reading is about as fast as with other ROMs (USB stick is formatted NTFS, btw)
===
I flashed together with Magisk 18 and openGapps 9 pico
During first boot phone froze completely during boot animatoin; had to hard reset, then it booted fine into system
Google initial setup was a bit weird, had a FC first, then a short loop through the initial three screens, but after a few attempts it finally ran through.
Didn't do much more now, as I need my phone for, well, what you usually need a phone for , so I'm going back to 15.1 now. But the first few steps were extremely promising. Probably will be testing a bit more over the weekend.
Can't wait to use this as a daily driver! :good::good::good:

Using 15/01/2019.
Dirty flashed over last 15.1 (wiped cache/dalvik/system but kept data).
Working really well so far.
One thing I've noticed is that the UI seems a bit slower/somewhat choppier than 15.1, very slightly though. Barely noticeable, but the UI does seem to be a bit slower.
Other than that it's really impressive and is going to be my daily driver until/if something goes bad.
Another thing is twrp 3.2.3 backup restore of this rom seems to result in bootloop, but that might as well be because of me keeping data from 15.1.

lingowistico said:
Using 15/01/2019.
Dirty flashed over last 15.1 (wiped cache/dalvik/system but kept data).
Working really well so far.
One thing I've noticed is that the UI seems a bit slower/somewhat choppier than 15.1, very slightly though. Barely noticeable, but the UI does seem to be a bit slower.
Other than that it's really impressive and is going to be my daily driver until/if something goes bad.
Another thing is twrp 3.2.3 backup restore of this rom seems to result in bootloop, but that might as well be because of me keeping data from 15.1.
Click to expand...
Click to collapse
It's just my impression, but I've seen that sometimes the sense of slow UI may be just due to the speed of animations. Try changing the 3 scale animations on developer settings from 1x to 0.5x as is a common value

Sorry if this is the wrong place to ask this but: when using Dir file manager (super clean and light weight) I can't add home screen shortcuts to files for some reason. This worked on stock lollipop but not on Lineage 15.1 or 16.
How do I make this work again?

lingowistico said:
Sorry if this is the wrong place to ask this but: when using Dir file manager (super clean and light weight) I can't add home screen shortcuts to files for some reason. This worked on stock lollipop but not on Lineage 15.1 or 16.
How do I make this work again?
Click to expand...
Click to collapse
It's definitely a problem with the app itself.
I just tested my preferred file manager - Total Commander - and it worked fine.
Also ES did the job.
Only your mentioned Dir file manager wasn't able to do it.
It seems there is a new api to access shortcuts? Maybe they don't support it? Did you tried on an other device with Android >=8 ?
I just made a screenshot how it should look like (the confirmation dialog).
EDIT:
Yes. Had the right suspicion: https://github.com/veniosg/Dir/issues/126
It's a known app problem.

115ek said:
It's definitely a problem with the app itself.
I just tested my preferred file manager - Total Commander - and it worked fine.
Also ES did the job.
Only your mentioned Dir file manager wasn't able to do it.
It seems there is a new api to access shortcuts? Maybe they don't support it? Did you tried on an other device with Android >=8 ?
I just made a screenshot how it should look like (the confirmation dialog).
EDIT:
Yes. Had the right suspicion: https://github.com/veniosg/Dir/issues/126
It's a known app problem.
Click to expand...
Click to collapse
Thanks a lot for replying. For some reason, I assumed that Total Commander for Android was shareware/adware.
Hopefully Dir will be updated soon enough, meanwhile I'll be using Total Commander.
Thanks again for looking this up for me and for suggesting alternatives. :highfive:

After 1 month using this version 15.1.2019 every day, i have found this critical problems:
- camera (force closing)
- audiofx (not good working)
- sms app (when i receive sms phone is still vibrating)
- sometimes graphic artefacts on navigation buttons
- sometimes freezing when i use more apps
This rom is pretty, clean, without unuseful functions and this is why i like LineageOS. :good:

Jerri7 said:
After 1 month using this version 15.1.2019 every day, i have found this critical problems:
- camera (force closing)
- audiofx (not good working)
- sms app (when i receive sms phone is still vibrating)
- sometimes graphic artefacts on navigation buttons
- sometimes freezing when i use more apps
This rom is pretty, clean, without unuseful functions and this is why i like LineageOS. :good:
Click to expand...
Click to collapse
Concerning camera: I have this problems too (unregular) although I can't reproduce them. A reboot should help. @SpiritCroc has merged a commit that may be connected to this http://gerrit.aicp-rom.com/c/AICP/device_sony_msm8974-common/+/84248 though I'm not sure if it solves the problem. We'll see.
Concerning AudioFX: It's buggy in my opinion - independent of devices and android version. I also had issues with it on Oreo and on totally different devices. If someone has got a hint: feel free to share
Concerning SMS app: I also have issues here but I think it's related to the lineage code and nothing device specific. Keep in mind that Lineage 16 isn't officially released until now. If the next build is also buggy please provide a log.
Concerning the rest: Same as above --> LOS 16 isn't released and there are still issues left to fix.
I'll upload a new build soon. Let's see what it brings.

115ek said:
@SpiritCroc has merged a commit that may be connected to this http://gerrit.aicp-rom.com/c/AICP/device_sony_msm8974-common/+/84248 though I'm not sure if it solves the problem. We'll see.
Click to expand...
Click to collapse
If you didn't have that before, it should help; AICP didn't need it at first in comparison to lineage, but we included it now for a cleaner approach, see discussion here http://gerrit.aicp-rom.com/c/AICP/frameworks_base/+/84029

SpiritCroc said:
If you didn't have that before, it should help; AICP didn't need it at first in comparison to lineage, but we included it now for a cleaner approach, see discussion here http://gerrit.aicp-rom.com/c/AICP/frameworks_base/+/84029
Click to expand...
Click to collapse
Great! Thanks again for finding that
The new build is now available:
17.02.2019
fixed occasional camera problems (thanks @SpiritCroc)
various kernel patches (thanks @SpiritCroc)
synced LineageOS sources (security patch level February 05, 2019)

Micro Gapps
First: Thanks for the Update.
My question:
Mostly the Rom-Providers not using MicroG recommend Pico-Gapps for their builds.
I am using them too for all LOS-related Roms without problems.
Is there a special reason/need for your Rom to recommend Micro-Gapps instead?

CyanoFriend said:
First: Thanks for the Update.
My question:
Mostly the Rom-Providers not using MicroG recommend Pico-Gapps for their builds.
I am using them too for all LOS-related Roms without problems.
Is there a special reason/need for your Rom to recommend Micro-Gapps instead?
Click to expand...
Click to collapse
Yes, you're right. Generally spoken the smallest gapps package (pico) is the best in terms of performance (apart from no gapps package ).
Additionally you can easily install missing google apps from playstore afterwards (e.g. maps, youtube...). But there are apps/functionalities you can't get from the playstore, for example "Okay Google".
I just checked the gapps comparison again https://github.com/opengapps/opengapps/wiki/Package-Comparison
It seems nano is sufficient to get these functionalities (so with pico you won't get them). Maybe that was micro earlier... I don't know
But thanks for your hint, I'll update the thread accordingly.

115ek said:
It seems nano is sufficient to get these functionalities (so with pico you won't get them). Maybe that was micro earlier... I don't know
But thanks for your hint, I'll update the thread accordingly.
Click to expand...
Click to collapse
Since I opened my Z1c some 18 months ago I'm running the nano packages and am very happy with that. Same applies to my recently opened tablet z.

Hello.
sorry to interrupt you for a reason not directly related to this topic...
Does anybody of you know AdrianDC (who was part of the team of this Z1 ROM version also) and the way how to reach him?
Maybe you, 115ek?
I have a Sony Ericsson mobile (SEMC 2011 devices) and he was the one having released the only Lineage 14.1 ROM Nougat version for those models (cm13 has been released by 'LegacyXperia' group on basketbuild.com before). It runs perfectly except two remaining issues of the camera's audio function which should be the very last bug fix at it.
Unfortunately my direct messages on XDA to him don't seem to reach him (no read status).
Does anybody can help me to reach him?
I don't even know if the LegacyXperia team is still existing or where those developers have been moved to.
Thank you so much for any hint you can give to me!

{
"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

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
crDroidAndroid-13.0-20230426-dragon-v9.4.zip
Features:
https://github.com/crdroidandroid/crdroid_features/blob/13.0/README.mkdn
Known issues: (13.0)
- Camera is not working.
- Encryption is not working .. pls do not encrypt your data partition.
- SELinux - we are still permissive !
- Our "old" Nivida codecs do have problems playing videos in Chrome browser.
- Network traffic monitoring is broken due to old kernel version.
- As it looks like Widevine L1 has been revoked by end of August 2020.
Flashing Instructions:
Pre-installation:
TWRP (Download from here)
gapps (Download from here)
Magisk 21.x or newer for root - (Download from here)
First time installation:
1. Boot into TWRP
2. Wipe SYSTEM and DATA partitions ! (If you are encrypted, pls format DATA partition !)
3. Install ROM.zip
4. install gapps (arm64)
5. install Magisk.zip (25.2)
6. Wipe CACHE and DAVLIK
7. Reboot into system
Update installation:
1. Boot into TWRP
2. Install ROM.zip
3. Wipe CACHE and DAVLIK
4. Reboot into system
Sources:
ROM: https://github.com/crdroidandroid
Kernel: kernel url
Manifest: manifest url
Download:
https://androidfilehost.com/?w=files&flid=289293
https://drive.google.com/drive/fold...oaU1iazg?resourcekey=0-4krcBcSF3tnMFvgcP4kMvw
There will be no regular updates .. just some builds from time to time !
Visit official website @ crDroid.net
crDroid <device> Telegram
crDroid Community Telegram
Donate to help our team pay server costs
Enjoy

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