yashsingh1/xdaforums huggingface dataset:
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Continuing the progress tracking post in LOS20 "Light" here...

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 MediaTek T vendors - few unlockable devices at this time

FOD/UDFPS (commonly known as in-display fingerprint) for certain OEMs - when I have time and energy...

Known but will not implement/fix:

Compatibility with legacy (pre-A10) devices, A-only, VNDKLite

MediaTek kernel BPF bug (workaround)

VoLTE on Motorola Qualcomm S vendors (workaround)

VoLTE on non-Qualcomm/MediaTek vendors

Samsung/Huawei oddities
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Notes:

I now have a rather taxing day job, and can't devote nearly as much time/energy into this as I did as a student, or even a year ago. Expect one-way communication - I might go silent for a month or more when life takes priority.

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 LOS20 "Light" #9 for explanation/workaround of an MediaTek-specific kernel bug that causes no internet.

Refer to #17 for a workaround of SMS reception issue on Qualcomm S vendors, necessary for Motorola devices but also helpful for others.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
TD-based LOS21 will be offered, again, at a later date. Both have been ready for a bit, except it took a good while for LOS upstream to merge changes to the point that no picklists are needed.
[Treble-Enabled Device Development A/AB ROMS] Hatrackman:
can it be 'dirty' flashed onto 20 Light, or should I factory reset my device and start fresh?

EDIT- Yup. seems it. on Moto G Power (2021) that doesn't use a sim card or anything financial.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
I always start fresh, I see this as a yearly chance to flash the latest stock / update the vendor base.

(This time I also switched device so it's mandatory anyway...)
[Treble-Enabled Device Development A/AB ROMS] Hatrackman:
'Spring cleaning' has it's place. Is there anything I should keep my eye out for not starting fresh? Phone is working great so far after dirty flash.
[Treble-Enabled Device Development A/AB ROMS] jack_shelack:
Great work as always, much appreciated!

Which device did you upgrade to, if you don't mind me asking?
[Treble-Enabled Device Development A/AB ROMS] scottyrick2:
Easy dirty upgrade to Android 14 {Lineage 21). Device is Lenovo Tablet tb-x606f. My initial impression is the tablet now is faster and has less error messages than Android 13 (Lineage 20). Thanks again for helping me keep this tablet up to date.
[Treble-Enabled Device Development A/AB ROMS] Hatrackman:
In retrospect, I'm getting weird little freezes. Gonna factory reset and give another go.
[Treble-Enabled Device Development A/AB ROMS] ykom:
Is "light" good on VNDKLite devices?

Self reply. No good. Sorry.
[Treble-Enabled Device Development A/AB ROMS] Hatrackman:
Actually, didn't factory reset, just wiped after flashing (thats what she said). Working great now. fresh and clean. Had little issue getting TextNow to work (re: google play protect... this link solved that problem- https://www.xda-developers.com/how-to-fix-device-not-certified-by-google-error/). Then just disabled play store, play services and google.
[Treble-Enabled Device Development A/AB ROMS] Marinkovicc:
Hey, did anyone tested this on Galaxy A12 SM-A127F/DSN. How will it work on this device?
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Usually I don't mind revealing (I have the fleet as my signature), but right now I still haven't decided one to settle on, and as I don't want to delay testing/releasing anymore, I grabbed a random modern device, with the last (Mi 13 with LOS20) as backup in case LOS21 fails badly.

Legacy, Samsung, etc. should wait for TD-based. I hope I have time to get it out there tomorrow.
[Treble-Enabled Device Development A/AB ROMS] Marinkovicc:
Alright. Thanks. I had problem with LOS20, when i installed it device was stuck on loading screen forever. So i hope LOS21 will fix that.
[Treble-Enabled Device Development A/AB ROMS] Hatrackman:
Have a feeling this is what the toggle in Treble Settings 'Spoof System Properties' is for.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
If your device uses QC AIDL IMS (SD8G1 and newer), and has SMS reception issues even after setting up IMS properly, this workaround might help...

Turn on Airplane mode

Reboot

After boot, wait a bit (30sec?)

Turn off Airplane mode

SMS reception would then work until the next reboot.
[Treble-Enabled Device Development A/AB ROMS] ykom:
arm64_bgN can not be installed on VNDKLite device that got "

FAILED (remote: 'Not enough space to resize partition')

fastboot: error: Command failed". *needless to say, partition product was deleted.

bvS is installed on it and works nicely but BT is not working.

still great ROMs ! happy to wait for next.

Thanks,
[Treble-Enabled Device Development A/AB ROMS] tennyleaz:
Successfully installed bgN on iPlay 50. Need to manually delete product_a first.
[Treble-Enabled Device Development A/AB ROMS] FedeDT:
I see 3 different lite roms, which one is for my Lenovo m10 x606fa tab?
[Treble-Enabled Device Development A/AB ROMS] FedeDT:
Hello to all

I tried to install LineageOS21 light, reboot and now the tablet won't turn on again

I hear "connect - disconnect" on my PC but the tablet won't turn on...

Even Recovery or FastBoot won't work... I don't know what i must do to wake up again...

I also tried with Lenovo Rescue And Smart Assistant but alwais go to "FAIL"

Your help is appreciated
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
"Light" isn't for such devices - try TD-based.
[Treble-Enabled Device Development A/AB ROMS] ykom:
Sorry, I meant TD-based ROMs. Thanks anyway.
[Treble-Enabled Device Development A/AB ROMS] Hatrackman:
Dirty flashed and functioning like a gosh darn space Fabergé egg from the future. Cheers Andy.
[Treble-Enabled Device Development A/AB ROMS] gunar74:
Does VoWifi work on Snapdragon (Galaxy S23 G911B) devices? (On Yettel Hungary).
[Treble-Enabled Device Development A/AB ROMS] golf174:
Hello! Thanks for your wonderful firmware, everything works very well! But there is a small bug that will occur in both versions 20 and 21. When the screen is split into two applications, trying to minimize them (exit to the desktop) or open task manager - trebuchet error... Only the back gesture works. It can be fixed?
[Treble-Enabled Device Development A/AB ROMS] ykom:
(y)
[Treble-Enabled Device Development A/AB ROMS] pvdeejay:
Dear @AndyYan

I am trying to boot this lineage-21.0-20240212-UNOFFICIAL-gsi_arm64_vN.img on a Xiaomi Redmi 9. This is 2020 device code named lancelod or 3GB ram variant galahad. I do have that 3GB variant. It came with android 10. I have tested with the original android 10 vendor and also I have tried upgrading through fastboot to the latest available stock rom which is Android 12.

When booting I am getting a crash, this is my logcat. I am unable to figure out what's wrong and if I can do something to resolve it on my own.

lineage 20 is working fine on this device.

Can you help please?

Edit: It turns out lineage 20 boots but does not detect my SIM card. So perhaps I have broken something during my flashing experiments.

Greetings

P
[Treble-Enabled Device Development A/AB ROMS] patrickfrei:
Hi,

I've installed the firmware for LineageOS

21

(lineage-21.0-20240212-UNOFFICIAL-gsi_arm64_vN.img) on my old Nokia 2.2 TA-1188 but the ROM is stuck at the LineageOS boot logo animation, i.e. the animation never stops running.

In the logcat, I can see a lot of "Failed to parse..." and "No Compatibility callbacks set..." warnings. Attached the logcat dump from lineage-21.0-20240212-UNOFFICIAL-gsi_arm64_vN.img during the stuck boot sequence (about 5 minutes).

Does someone have any idea what the problem could be? I can try to investigate by myself, but some ideas would be helpful.

BTW:

The same firmware for LineageOS

20

(lineage-20.0-20240215-UNOFFICIAL-gsi_arm64_vN.img) is working on the same device without any issues.

Both TD variants (LOS 20 and 21) didn't boot and caused the device to be stuck in a bootloop.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Light won't take care of Sammy shenanigans - please turn to TD-based GSIs.

Acknowledged/backlogged. While I think it's an LOS upstream issue, it does also slightly impact my own use...

This crashes on BPF, perhaps Google has tightened down that part harder on A14 even harder.

See if the "persistent fix" here works for you; otherwise, recommend you turn to TD-based instead.
[Treble-Enabled Device Development A/AB ROMS] pvdeejay:
Well on Lineage 20 light I have noticed no networking issues so far. I'll try out patching the kernel tonight and I'll see. Unfortunatelly there is no more up to date boot image from the vendor than Android 12.

Thanks for the advice
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
@patrickfrei Forgot to quote yours - same underlying BPF issue as pvdeejay's above, and thus same tips for you.
[Treble-Enabled Device Development A/AB ROMS] pvdeejay:
Sorry for a lot of questions. Mine is 4.14 kernel and it appears to be supported by the suggested patcher.

It extracts the kernel from the boot image, patches it and saves it as a gz file. Now I need to find a way on how to mount and replace the kernel inside the boot image. I can't just mount the original boot.img on my linux computer.

Have you got another suggestion for me please?
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Android Image Kitchen?
[Treble-Enabled Device Development A/AB ROMS] FedeDT:
Is there an option to enable the default feature on Lenovo rom that the dock is auto-enabled when I put the tablet on it?
[Treble-Enabled Device Development A/AB ROMS] patrickfrei:
@pvdeejay

Could you please tell me how you extracted the kernel, applied the MKT BPF patcher and put it back again? I'd like to make lineage-21.0-20240212-UNOFFICIAL-gsi_arm64_vN.img boot on my Nokia 2.2 (TA-1188).
[Treble-Enabled Device Development A/AB ROMS] pvdeejay:
I have used the patcher as is running it on the original boot image.

Then instead of Android image kitchen I have used this tool instead as I am on linux https://github.com/ndrancs/AIK-Linux-x32-x64

However my device does not boot with the patched kernel, so I need to investigate if that's because of the kernel or perhaps I did something wrong while doing it so I will try again.

I have never had access to MTK based nokia however I assumed Nokia does not allow unlocking the boot loader. Now there are apps such as mtkclient where you have full control over your mediatek device so perhaps this might be a way. Or perhaps there is a different way already.
[Treble-Enabled Device Development A/AB ROMS] patrickfrei:
Hi @pvdeejay, many thanks for your reply.

I've successfully unlocked the bootloader with mtkclient a while ago and could flash LOS 20 (vN Version). This one is booting and is working perfectly. But LOS 21 is causing headaches because it's stuck at the LOS boot logo animation. That's why I'd like to apply the MKT BPF patcher. I've found the following kernel extractor / patcher: https://github.com/cfig/Android_boot_image_editor

Maybe, that one will work for you?

BTW: Does it really work if we directly patch the boot image? Shouldn't we first extract the kernel from the boot image, patch it and then put the kernel back into the boot image again?

UPDATE: Just extracted the kernel from boot.img (stock ROM) and applied MKT BPF patcher. It doesn't work:

Detected KERNEL_BIN for boot!
Unable to find a match for any of the sequences :(

The kernel of my stock ROM (4.9.117) is not supported. I don't really understand why this patcher should help in case of such an old ROM.
[Treble-Enabled Device Development A/AB ROMS] patrickfrei:
@AndyYan I've applied the MKT BPF patcher as suggested but the kernel of my stock ROM is much older (4.9.117) and the patch therefore doesn't work. So, lineage-21.0-20240212-UNOFFICIAL-gsi_arm64_vN.img is still hanging at the LOS boot animation. Do you have any other idea?
[Treble-Enabled Device Development A/AB ROMS] asylor:
I am happy to confirm that my phone dirty flash from GSI Light 20 to 21 vanilla works without issue (I am lazy and don't want to reset everything). But I am from vanilla so it was expected, and this is the main reason why I stick to vanilla.

I also have a tablet dirty flashed from GSI TD 20 to 21 vanilla everything working fine except third party software keyboard, Light version dose not have this issue though. Anyone knows if there is a work around? Both TD 21 and Light 21 are based on AOSP 14 but somehow in TD it will say app unsupported.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
With A14 QPR2, Google moved to trunk-based development, significantly changing the codebase. While I haven't had time to take a look at it yet, I've read from other devs that adapting to it was more or less like dealing with a new major Android version. Compounded with the usual day job, a March release will likely be far delayed or skipped for April instead. Just an FYI in case you're expecting...
[Treble-Enabled Device Development A/AB ROMS] PTuT:
Thx for heads up. Will the next release be on QPR2? If not, when are you expecting to move to it? Appreciate your work.
[Treble-Enabled Device Development A/AB ROMS] energykriger:
Will the xiaomi 13 ultra work with this gsi?
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
By now it's pretty much certain that March will be skipped and some time in April will be QPR2.

BTW, a second warning - from what I read so far, QPR2 might even ditch some A11 vendor devices. TD would try to save them, but depending on the difficulty and amount of changes needed, Light might not.
[Treble-Enabled Device Development A/AB ROMS] energykriger:
If not i can pay for xiaomi 13 ultra support.
[Treble-Enabled Device Development A/AB ROMS] nmajin:
Will this work for the Alldocube 50 mini? Looking to get A14 now since PE GSI is no longer being worked on :(
[Treble-Enabled Device Development A/AB ROMS] patrickfrei:
Does that mean you simply executed...

fastboot flash system lineage-21.0-20240212-UNOFFICIAL-gsi_arm64_vN.img

...and nothing else?
[Treble-Enabled Device Development A/AB ROMS] Hatrackman:
I did that and it was a bit wonky re: stutters. Redid with wiping and works fine. Just had to make backup of personal files and apks. Like spring cleaning... tidying playlists etc. On Moto G Power (2021)
[Treble-Enabled Device Development A/AB ROMS] patrickfrei:
Ok thanks. Will give it a try. Cause I'm still wondering why LOS 21 is hanging at the boot animation and LOS 20 is working perfectly on my Nokia 2.2
[Treble-Enabled Device Development A/AB ROMS] asylor:
Yes you are right, I upgraded from the latest lineage light 20 rom by that. If your phone is relatively new and was using Light 20 vanilla (no GApps no root) it should work. If the phone is old then try the TD 21 vanilla instead. If both fail to work then you will have no choice but to wipe data (rollback to old rom and backup files before flashing).

Normally flashing plus wiping data usually works, flash only may not especially with GApps. That was the main reason I switched from LineageOS with GApps to vanilla, upgrade is easier without copying files to PC by adb then back to phone after upgrade.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Updated all variants with Android 14 QPR2 and April security patches. [Insert obligatory backup-and-test warning here]

Final warning - A14 QPR2 can and WILL break devices (old or new)! Treat it like a new major Android version! If your device can boot GSIs via DSU, absolutely try this update in DSU environment first! And regardless of status on DSU, backup important data before commencing update!

LOS upstream merged their own way of allowing signature spoofing, see Gerrit for details; most GSIs have switched to using this one, though with the debuggable requirement removed. For those who are using MicroG for the intended purpose, it should be a seamless transition, and perhaps even allow you to install MG as a user app.

I'd like to reiterate that, while it's my work keeping this GSI alive, it's mostly other people's work keeping it useful. With QPR2, the LOS team made lots of platform-side reverts and fixes to try to keep their own official roster of legacy devices up, and PHH, PeterCxy, ponces, etc. have also contributed significantly. Without their attention to compatibility, Light on top of QPR2 would probably have killed most of my current devices.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
So far with QPR2:

It broke my former daily driver (a rather modern OnePlus - glad I tried it in a DSU!). I've further tested and confirmed that a number of modern OPlus devices are likewise broken, even without "Light" changes - I think this violates Google CTS or some other certification?

It conflicted with light mode QS. Google thought it was good timing to introduce some color spec updates in the middle of a major Android version. As A15 likely will come with significant UI changes, I felt it wasn't worth the trouble to amend the light mode QS changes to the new specs, and reverted them - things look good as it is.

Dual-pane mode for tablets is somehow gone, despite building the same supporting lib as before - device-specific ROMs are experiencing the same.
[Treble-Enabled Device Development A/AB ROMS] Heeni:
I tried it on my Lenovo X505F. Unfortunately, it doesn't boot, even after going through the procedure for clean flashing a new ROM. (Just hangs at the Lenovo logo.) I was able to replace the last working (February) version, and I'll wait and see what happens in the next few months.

The tablet is probably close to end of life and has sustained some damage, so if no future version will work with it, I won't be too bothered. Thank you for having kept it working as long as it has.
[Treble-Enabled Device Development A/AB ROMS] asylor:
Have you tried the GSI LineageOS 21 TD version instead of Light? https://xdaforums.com/t/gsi-14-lineageos-21-trebledroid-based.4654132/

It has better support for tablets, at least my tablet can only run TD version but not light.
[Treble-Enabled Device Development A/AB ROMS] Heeni:
Thanks, it's worth trying, especially now when I haven't spent any time on setting it up.
[Treble-Enabled Device Development A/AB ROMS] asylor:
Now you mention it I notice there is DSU for my phone, I usually just flash first then rollback if it fails.

My dirty flashed Poco F5 (vanilla version) is working fine after flashing QPR2 for a week. All old bugs are still there but nothing that cannot be fixed with old workarounds (like missing 5G in network setting option but can use third party network setting app to change, or that might be simply my ISP's network type issue). I am happy to report that all basic functions work (phone calls, SMS, WIFI, 5G/LTE, tethering, bluetooth, camera, split screen, apps etc. at least for things that I use so far).

And was the default "Gallery" app replaced or something? The old shortcut was gone after flashing and I just made a new one.

Some of the minor things fixed in later versions of LineageOS 20 Light are back, like minimum volumn of bluetooth headphone is too loud (3.5mm jack is fine), but then I can always change the volume setting in apps as long as they allow it. Cannot use "Disable absolute volume" option as it will simply disable all audio. I guess it might be phone model issue.
[Treble-Enabled Device Development A/AB ROMS] sso003:
Just a quick heads up for others with physical fingerprint sensors (rear or side), for some reason Light doesn't seem to detect that a fingerprint sensor is available while with TD, it works perfectly.
[Treble-Enabled Device Development A/AB ROMS] PTuT:
Thanks @AndyYan for explanation. Due to compatibility with my oldie Samsung, I am currently on TD.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
TD on QPR2 should be up soon; you can test out TD AOSP or Ponces' one to preview the compatibility.

LOS upstream made a new gallery app called Glimpse. It lacks editing capability though...

Indeed. Considering there's also UDFPS (tough device-specific nut to crack), I should really start working on integrating face unlock next...
[Treble-Enabled Device Development A/AB ROMS] Pro Cal:
Hi. Im a bit confused regarding lineage os 19 and up for my galaxy A8 2018 as per the description it says that A-Only is deprecated since Android 12. does it means I cannot get it or that I can use B version and it will be compatible with A-Only devices such as mine ?

based on treble check i have A-Only Arm64 but I don't seem to understand which version to choose exactly as there no A-Only version any more

can you please help me choose the correct Version for my Phone

Thanks
[Treble-Enabled Device Development A/AB ROMS] Eula13:
you can't use light, use trebledroid based instead.
[Treble-Enabled Device Development A/AB ROMS] FedeDT:
Hello team! I have a Lenovo M10 2gen X606FA

Is it possible to add the original Lenovo feature that enables dock pairing only when the tablet is docked?

Only with this feature voice commands works when plays some audios features without this feature the volume doesn’t permit the mic to catch what you are asking for (Alexa show mode)

Thanks
[Treble-Enabled Device Development A/AB ROMS] Justin Yang:
I flashed lineage-21.0-20240212-UNOFFICIAL-gsi_arm64_vN.img to my OnePlus 11 (SM8550, PHB110 CN), and have installed IMS apk+enable 5G+override VoLTE. But I find that the phone call audio is not stable, which always doesn't have any sound, be it in-going or out-going. The only workaround is to reboot it, but after rebooting for a while, it doesn't have sound again while calling.

I uploaded the logcat in attachment. Anyone could shed light on me please?
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Updated all variants with May security patches. [Insert obligatory backup-and-test warning here]

Tried integrating face unlock, wasn't so straightforward, will retry later.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Any potential fixes would have to be built into QPR2, but as modern OPlus devices don't boot QPR2 at the moment, you won't be able to evaluate the fix anyway...

And uh... OP11 has official device-specific LOS, I suggest just using that.
[Treble-Enabled Device Development A/AB ROMS] Justin Yang:
Thanks bro. I have been back to official LOS for now. But I still love your gsi rom. From my personal limited experience, your gsi consumes less battery than official LOS. Anyway, keep it going!;)
[Treble-Enabled Device Development A/AB ROMS] Themjbrand:
Hi heeni I've the same tablet as you also i tried this version and I've a situation like you so can you provide me a link to that February build