[GSI][13] LineageOS 20 "Light" - Treble-Enabled Device Development A/AB ROMS

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS GitHub repo. And if you would like to contribute to LineageOS, please visit Gerrit Code Review.
Click to expand...
Click to collapse
MUST-READ BACKGROUND - Android 13 and the two approaches:
As some of you already know, due to various reasons, @phhusson , who kickstarted the GSI trend and committed to it over the years, is backing out from future development - there won't be any AOSP 13+ builds or patches directly from him. He did most of the heavylifting for fixing bugs and implementing features, and selflessly supported more than his AOSP GSIs and more than devices he own. For the situation of GSIs today, we owe him a big thank-you.
Since PHH made up his mind, a number of existing builders incl. myself have formed the TrebleDroid organization, with PHH himself helping us in technical issues. TD will forward-port PHH's final patches (v415) onto Android 13 and attempt to fix new issues. This is still a new and ongoing process, but if done right, will have compatibility and feature-completion on par with past PHH-based GSIs.
Meanwhile, I'm aware that at least I myself am not as capable as PHH, and won't be able to look after the myriad of patches and devices, esp. legacy ones (pre-A10). Therefore, inspired by @PeterCxy , I'm taking a different approach - start over from AOSP's generic gsi_* target, add in the minimum amount of fixes needed for my own devices, shaking off much of the legacy burden in the process and making it easier for myself to follow/maintain. This is a radical, selfish approach that by definition won't work for legacy devices anymore, and won't work as well as PHH-based GSIs that you've come to love either. However, I've fixed it up to my own daily-driver standards, and I figured it should still be of use to many. For now, I call this the "light" approach.
Disclaimer:
No flashing instructions will be offered. If you're here in this forum, you should know what you're doing.
No guarantees that everything would work. This is a GSI, bugs are bound to happen.
The selfish nature of this approach means I can and will ignore certain bugs as I see fit. Deal with it or kindly go try something else.
Download:
https://sourceforge.net/projects/andyyan-gsi/files/
Scroll down for the naming rules of variants.
Compressed as .xz archives - extract first.
Stuff on GitHub (builders-only):
Most things should be self-explanatory. Not the cleanest code, but should help if you need some clues.
lineage_build_unified - my unified script for building
lineage_patches_unified - my unified patches for building
device_lineage_gsi - my device tree that extends native generic targets
Thanks to:
The LineageOS team - helping me out even when they don't offer GSIs themselves
@phhusson - shaped the treble community, and even the "light" approach uses his fixes/infra extensively
@PeterCxy - inspired me with his personal-use GSI, and coded critical fixes such as sysbta
...and more
Donate?
https://paypal.me/AndyCGYan

---

This post documents my progress on top of the native generic targets.
Already implemented/fixed:
Built-in root (PHH-SU)
Device overlays
Screen resolution & refresh rate - improved upon PHH's implementation
Alternative audio policy (Qualcomm)
Disable soundvolume effect (Qualcomm)
Alternative backlight scale (MediaTek)
resetprop/copyprop tool
In-call audio
BT audio
VoLTE on Qualcomm/MediaTek pre-S vendors
VoLTE on Qualcomm/MediaTek S vendors - new, backported to PHH-based
GAPPS - using MindTheGapps for now
Securized - "on-demand" reversible toggle
Disable A2DP offload
Alternative audio jack detection
Signature spoofing - limited to priv-app for the same security reason as in PHH/TD-based
Optional FP lockout (set persist.sys.fp.lockouts.disable to true to disable timeout on failed FP attempts)
Built-in PHH-SU app for *S variant
Override minimum brightness
Override navbar availability
Exfat
In-call audio on Snapdragon 8 Gen 2 (SM8550) and newer Qualcomm devices
To be implemented/fixed at a later time:
VoLTE on Motorola Qualcomm S vendors - situation did not improve with stock T, lowering priority
Known but will not implement/fix:
Compatibility with legacy (pre-A10) devices, A-only, VNDKLite
FOD/UDFPS (commonly known as in-display fingerprint) - not skilled enough for it and not interested either
MediaTek kernel BPF bug (#9)
VoLTE on non-Qualcomm/MediaTek vendors
Samsung/Huawei oddities

---

Notes:
I now have a rather taxing day job, and can't devote nearly as much time/effort into this as I did as a student, or even a year ago.
No A-only or VNDKLite builds. These are concepts that don't exist natively.
GAPPS builds are offered as-is without guarantees. As a Chinese I can't/won't help with GAPPS/SN issues - please help each other out.
ADB is intentionally insecure, even on first boot (turned on by default and no authentication needed). GSIs are more fragile compared to device-specific custom ROMs, both on first boot (no-boot issues) and on subsequent boots (after tuning certain Treble settings), and I insist that no-auth ADB is a must-have for debugging and general fail-safe.
Signature spoofing (MicroG) is supported, but only for priv-apps. This is a security consideration from PHH.
Refer to #9 for explanation/workaround of an MediaTek-specific kernel bug that causes no internet.

---

TD-based LOS20 will be offered as well, but at a later date - I've only made a first test build of it today. At its current state though, it doesn't work as well as PHH-based A12 either, so don't get your hopes up too high.

---

Good job!

---

Yay!!!

---

yay!!!! thank you!!!!

---

Thank you very much for your great work. I've been waiting for this for a long time.
I ran into a very, very strange bug.
I have a Qin F21PRO (MT6761).
This model has two sub-models:
4GB RAM + 64GB storage
3GB RAM + 32GB storage.
My device is
4GB RAM + 64GB storage
But after flashing this GSI, it is shown that there is only 32GB storage.
edit: after factory reset via twrp, i getting 64GB storage

---

There's a known kernel bug in some recent MTK devices that breaks BPF badly, resulting in broken networking features since Android 13, and no-boot since r11 (Google decided to tighten the check). I've reverted the no-boot, but the actual bug can't be fixed from platform-side.
This affects LOS in that it has Restricted Networking Mode turned on by default, and with the bug in place, apps cannot be added to the allow list, resulting in no internet in even system apps.
If you own an MTK device and notice such a thing, as a temporary workaround, you can turn the feature off manually with:
Code:
adb shell settings put global restricted_networking_mode 0
If you're on the gN variant, SetupWizard would also have no internet, so just skip the setup entirely, turn on USB Debugging once you're in the OS, run the above, then re-initiate the setup from the status bar.
As for a more persistent fix - thanks to @Rortiz2 , there's now a way to manually patch the kernel binary, however I no longer have an affected device for testing this. Feel free to try out the patcher here.
There might be other broken networking features that I'm unaware of. In the long term, the one true solution is to upgrade to a newer vendor base, hoping that the OEM has merged the kernel-side fix.

---

AndyYan said:
TD-based LOS20 will be offered as well, but at a later date - I've only made a first test build of it today. At its current state though, it doesn't work as well as PHH-based A12 either, so don't get your hopes up too high.
Click to expand...
Click to collapse
There is no Navigation key or gesture options, How to do it?, I can install it on my Samsung device but without navigation, no home/back key

---

redymedan said:
There is no Navigation key or gesture options, How to do it?, I can install it on my Samsung device but without navigation, no home/back key
Click to expand...
Click to collapse
Ugh, a Samsung oddity. I didn't implement the force overide switch - if a non-Samsung hits this as well, I might.
If you know how to, try adding "qemu.hw.mainkeys=0" to /system/build.prop. These images are EXT4 unshared blocks, so as long you have verity disabled and root, you should be able to edit/save it.

---

redymedan said:
There is no Navigation key or gesture options, How to do it?, I can install it on my Samsung device but without navigation, no home/back key
Click to expand...
Click to collapse
AndyYan said:
Ugh, a Samsung oddity. I didn't implement the force overide switch - if a non-Samsung hits this as well, I might.
If you know how to, try adding "qemu.hw.mainkeys=0" to /system/build.prop. These images are EXT4 unshared blocks, so as long you have verity disabled and root, you should be able to edit/save it.
Click to expand...
Click to collapse
Same problem with Redmi Note 10 (mojito)

---

@redymedan @spider1163 Can you give me the full result of "getprop" from shell? Paste it to e.g. Pastebin.

---

D
AndyYan said:
Ugh, a Samsung oddity. I didn't implement the force overide switch - if a non-Samsung hits this as well, I might.
If you know how to, try adding "qemu.hw.mainkeys=0" to /system/build.prop. These images are EXT4 unshared blocks, so as long you have verity disabled and root, you should be able to edit/save it.
Click to expand...
Click to collapse
Done! I just added "qemu.hw.mainkeys=0" to /system/build.prop and the navigation keys enabled. also in Gesture menu "System navigation" option appeared. It works now on my Galaxy A50, Thanks
Other problem: Google Play Protect certified "This device isn't Play Protect certified"

---

amazing! waiting for gapps variant now.

---

redymedan said:
Done! I just added "qemu.hw.mainkeys=0" to /system/build.prop and the navigation keys enabled.
Click to expand...
Click to collapse
Thanks for confirming it's that simple! Given that "light" won't look back on legacy devices, I think I'll just enable this prop globally in the next releases.

---

This is exactly what I was waiting for, it will be fun to test on my old Huawei P smart 2019 with Android 9 vendor so let's see what happens. Any result of this experiment will be shared here.

---

THX for your great work.
But how can I install gapps?
I've tried to install BitGApps with Magisk as a Magisk module, but it says 'insufficient partition size'.
There's no working TWRP for my device

---

michael_hamada said:
THX for your great work.
But how can I install gapps?
I've tried to install BitGApps with Magisk as a Magisk module, but it says 'insufficient partition size'.
There's no working TWRP for my device
Click to expand...
Click to collapse
you wait... ..

---

THX for your great work. but auto brightness not working Is this expected behavior？