[GSI][13] LineageOS 20 "Light"
- Thread starter AndyYan
- Start date
Thanks for your answers.
Is Treble and GSI not the same?
I ask because expression "Treble" and "GSI" is mentined on the github-account from phhusson
github.com
On the list, there are many different images. In first post I also read that phhusson will not spend so much time for this than before.
Is this basis of all GSI the same? Will this continue?
Back to Andy's images
Because of "light", of course i though that something is missing. But then, I had a look on size of the files, and it's almost the same file-size.
So I didnt see what is missing.
Still questions, are:
- what is an old-device, what isnt it?
- what is the mentioned functionalities in TD, which are not included in light?
what is TL, and what is DR
TD ist TrebleDroid, right?
Is Treble and GSI not the same?
I ask because expression "Treble" and "GSI" is mentined on the github-account from phhusson
Generic System Image (GSI) list
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
On the list, there are many different images. In first post I also read that phhusson will not spend so much time for this than before.
Is this basis of all GSI the same? Will this continue?
Back to Andy's images
Because of "light", of course i though that something is missing. But then, I had a look on size of the files, and it's almost the same file-size.
So I didnt see what is missing.
Still questions, are:
- what is an old-device, what isnt it?
- what is the mentioned functionalities in TD, which are not included in light?
Correct me if I am wrong: GSI (Generic System Image) is the Google's cross-device format for system image files, developed during the course of their "Project Treble". TrebleDroid is the community project started by Pierre-Huges Husson (aka phhusson or phh) with the goal to create a set of scripts (plus some additional open-source data and software) so that any Android-based system could be compiled as a GSI image, thus making it cross-device for the devices which support Project Treble (aka "treble updates").Thanks for your answers.
what is TL, and what is DR
TD ist TrebleDroid, right?
Is Treble and GSI not the same?
I ask because expression "Treble" and "GSI" is mentined on the github-account from phhusson
Generic System Image (GSI) list
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
On the list, there are many different images. In first post I also read that phhusson will not spend so much time for this than before.
Is this basis of all GSI the same? Will this continue?
Back to Andy's images
Because of "light", of course i though that something is missing. But then, I had a look on size of the files, and it's almost the same file-size.
So I didnt see what is missing.
Still questions, are:
- what is an old-device, what isnt it?
- what is the mentioned functionalities in TD, which are not included in light?
Too Long Didn't Read, basically asking for a summary.
So far it seems only I have decided to walk down a different path ("Light", but I still offer TD-based in parallel); everyone else still exclusively uses the same PHH/TD base.
I think it's safe to say PHH won't turn back. After all, who doesn't like more free time and less trouble?
The OS itself ("platform") contributes to most of the size, what we've done are but drops in the ocean. Not the right way to analyze this...
Devices that came with >=A10 as their first Android version are required to be SaR (you don't really need to know what this is), as well as generally more compliant with Treble's specs. For now, I see devices pre-(factory-)A10 as "legacy". Other concepts mentioned (A-only, VNDKLite) are even more ancient.
I don't want to make you go through my patchsets, but in short, there are lots of fixes tailored to legacy devices, Samsung, Huawei, non-QC/MTK SoCs (e.g. Spreadtrum) that I simply skip in "Light".
You're already in here but somehow missed the "spoof system properties" checkbox right below... Tick that and reboot.
Well, I've done it. Only issue so far is battery is almost 50% miscalculated. I will let it drain naturally until it auto powers off, then I will charge it to full with it remaining off.
Also, when flashing vbmeta got a warning and something about 'anti rollback' protection or something... does my vbmeta need updating? Everything seems to be working fine. Haven't tried headphones yet but I'm betting they will work just fine.
Oh. On a Moto G Power (2021) and using the Gapps version. Installed Magisk. Side note: it was with glee that I notice the brazen lack of useless bloat.
PS: battery seems to be recalibrating on its own.
PPS: oh right, I wanted to ask. When it comes time to update do I have to go through the process of making phone vanilla again then flashing, or can I just flash the update directly on top? Would I need the gapps version again, or just a plain version?
PPPS: I love the rounded copy/paste popup.
PPPPS: the battery seems to've completely recalibrated. Doubt it'll be an issue anymore.
Also, when flashing vbmeta got a warning and something about 'anti rollback' protection or something... does my vbmeta need updating? Everything seems to be working fine. Haven't tried headphones yet but I'm betting they will work just fine.
Oh. On a Moto G Power (2021) and using the Gapps version. Installed Magisk. Side note: it was with glee that I notice the brazen lack of useless bloat.
PS: battery seems to be recalibrating on its own.
PPS: oh right, I wanted to ask. When it comes time to update do I have to go through the process of making phone vanilla again then flashing, or can I just flash the update directly on top? Would I need the gapps version again, or just a plain version?
PPPS: I love the rounded copy/paste popup.
PPPPS: the battery seems to've completely recalibrated. Doubt it'll be an issue anymore.
Last edited:
Flash an updated image of the same variant without wiping anything.
Are there devices which are SaR, but nevertheless are not usable for GSI?
Is there an Treble-App which is saying if a device is a-only, or VNDKLite. Treble Info from Hackintosh Five is not.
Huawei/Honor? lol
No? It tells you up front about SaR (which is "A-only/AB" in GSI terms), seamless (which is "A-only/AB" in proper Android terms) and VNDK/Lite, and even suggests you an image from PHH/TD (from the filename of which you can also tell the above). The VNDKLite indication could've been a bit clearer though, I'll raise him a suggestion.
I wasn't aware of that SaR is nothing else than AB-Partitions and nonSAR = A-only
I though SaR would be something additionally
sorry for that, that was my fault.
Why is there a separate point "seamless"?
Is seamless relevant for GSI?
Are there device which are A/B, but not seamless?
I let my phone auto power off with 0% battery with the intention of charging to to full from zero while the power is off in an effort to refresh/recalibrate the battery sensor. Its been plugged in for an hour and 15 minutes so far and the indicator still says 0%... the usb plug is warm so I am guessing its charging just fine and its just an inane glitch.
I'll let it charge for a full 4 hours before turning it on.
Side note: Really like that you kept the charging logo. not a fan of the one for TDb.
PS: turned it on after 3 hours and 50 minutes (indicator still said 0%). powered up fine and said battery was at 85%. I turned it off again to charge it to 100% with power off. the power off charging logo now says 85%.
PPS: 24 minutes later, charger still says 85%.
PPPS: 45 minutes later, still said 85%. Turned it on, was at 100%. Does the powered off charging logo work for other people? Is that why TD-b changed theirs?
I'll let it charge for a full 4 hours before turning it on.
Side note: Really like that you kept the charging logo. not a fan of the one for TDb.
PS: turned it on after 3 hours and 50 minutes (indicator still said 0%). powered up fine and said battery was at 85%. I turned it off again to charge it to 100% with power off. the power off charging logo now says 85%.
PPS: 24 minutes later, charger still says 85%.
PPPS: 45 minutes later, still said 85%. Turned it on, was at 100%. Does the powered off charging logo work for other people? Is that why TD-b changed theirs?
Last edited:
Actually I believe offline charging display isn't working at all, and whether it charges while the logo freezes depends on the device. This is known but seems so deep/device-specific that I never intended to take it on.
In "Light" I didn't do any special treatment to offline charging, whereas TD-based does have a few related patches.
Seamless updates means having actual AB partitions (either physical/fixed or virtual/CoW); "AB" in GSI terms only indicates system-as-root, and the device doesn't necessarily support Seamless updates.
We only get to use one slot, so I'd say no.
Sammy hasn't adopted Seamless updates to this day...
Andy
I worked a lot on the subject on all huawei last year. I fixed the problems on the td with several patches but which don't seem to work on the lineage td. I'm looking to do it, I'll message you if I manage to make everything work
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
1@AndyYan , on my Xiaomi Note 12 4G (https://www.gsmarena.com/xiaomi_redmi_note_12_4g-12188.php) on your GSI images:
trebledroid-based
- audio does not work in calls
lineageos light
- cannot receive text messages (sending works without issues, including MMS)
I don't have A2DP offload from phh settings mentioned in common issues here: https://github.com/phhusson/treble_...-fixes#cant-listen-to-anything-on-phone-calls
on the xiaomi.eu version https://sourceforge.net/projects/xi...i_TOPAZ_V14.0.3.0.TMGMIXM_v14-13.zip/download everything works.
I've been looking at https://github.com/phhusson/treble_experimentations/issues/976 as well but installing the latest IMS apk or switching to 3G doesn't help :/
ideally I'd like to fix the LOS light image, what can I do? I'm a devops engineer so able and willing to give you any kind of log to help but I don't know the first thing about Android OS builds.
edit: ok so my phone service provider did... "something" on their end and now text messages work. it's insane, but they've been bad so I'm not entirely surprised. disregard this then, the LOS light GSI works perfectly well. -
30
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
- 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
https://paypal.me/AndyCGYan9There'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:
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.Code:adb shell settings put global restricted_networking_mode 0
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.7This 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
- VoLTE on Motorola Qualcomm S vendors - waiting for T to re-evaluate situation
- 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
7Updated all variants with Android 13 QPR1 and December security patches. [Insert obligatory backup-and-test warning here]
As usual with "feature drops", things can change or break majorly.
Newly implemented:
- Disable A2DP offload
- Alternative audio jack detection
- Signature spoofing for priv-app (just like 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
Rejected:
- Force headset audio (slightly harder to implement, and not proven effective outside of Huawei)
- lptools
7Updated all variants with November security patches. [Insert obligatory backup-and-test warning here]
As teased a few days ago, here's a gN build with MindTheGapps, plus both vN and gN are now "integrally securized", for better chances (but not guaranteed) to pass SN. OP will be updated to reflect these changes.
A "personal" build has also been uploaded to Testing.
I'd like to once again remind you that "light" will remain a selfish approach. For other needs e.g. Samsung oddities, please wait for the TD-based batch which I'll make a thread for shortly, see if that would scratch your itch instead.
