yashsingh1/xdaforums huggingface dataset:
[Treble-Enabled Device Development A/AB ROMS] uschipower:
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.

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?
[Treble-Enabled Device Development A/AB ROMS] uluruman:
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").
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
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".
[Treble-Enabled Device Development A/AB ROMS] tom.android:
Can't to sign-in , how to fix? thanks
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
You're already in here but somehow missed the "spoof system properties" checkbox right below... Tick that and reboot.
[Treble-Enabled Device Development A/AB ROMS] tom.android:
Thank you , if you can please enable "DT2W".
[Treble-Enabled Device Development A/AB ROMS] Hatrackman:
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.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Flash an updated image of the same variant without wiping anything.
[Treble-Enabled Device Development A/AB ROMS] uschipower:
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.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
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.
[Treble-Enabled Device Development A/AB ROMS] uschipower:
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?
[Treble-Enabled Device Development A/AB ROMS] Hatrackman:
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?
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
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.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
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...
[Treble-Enabled Device Development A/AB ROMS] AltairFR:
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
[Treble-Enabled Device Development A/AB ROMS] dellwit:
Hi, I can use the "Light" version? I'm not quite sure. My treble info:

hallelujah I got it, I can install any rom from gsi list phusson that is: system-arm64-ab.img.xz
[Treble-Enabled Device Development A/AB ROMS] muil:
My tablet (mediatek) turns the screen on and keeps showing the battery icon while charging. Any way to solve this? I have light version.
[Treble-Enabled Device Development A/AB ROMS] DeadlyPlyz:
@AndyYan hii, sorry i installed the lineageOS 20 vndklite on my Samsung A6 Plus. the rom installed successfully but now for the first boot, it’s stuck on the booting animation for 20 minutes now. any ideas why?
[Treble-Enabled Device Development A/AB ROMS] bentalebnordine:
Hi guys, something weird happened with me, the previous version booted and it worked perfectly fine but the latest did not, I wonder why?

I have OnePlus n100 e2013
[Treble-Enabled Device Development A/AB ROMS] kevinco1:
This light build has never worked for any Samsung tablets since the dev has expressed his disinterest in making it compatible.

Sure, it flashes successfully...but it always does get stuck on the boot screen. There is nothing that can be done at this point
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Pretty sure you're in the wrong thread, as Light doesn't have VNDKLite builds. cc @kevinco1
[Treble-Enabled Device Development A/AB ROMS] kevinco1:
Missed the VNDKLite part, but the fact remains this does not work with Samsung tablets. Users should install regular Lineage 20 build instead
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Updated all variants with April security patches. [Insert obligatory backup-and-test warning here]

All modern Xiaomi/Redmi devices should be able to see high refresh rates now (if supported), without having to spoof properties globally.
[Treble-Enabled Device Development A/AB ROMS] Hatrackman:
Hey Andy. just tried lineage-20.0-20230417-UNOFFICIAL-gsi_arm64_gN.img without wiping anything but came back with error (thank goodness didn't affect current setup)

These are my general install instuctions for a moto g power (2021)-

---

adb reboot bootloader

fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

fastboot reboot fastboot

fastboot delete-logical-partition system_a

fastboot delete-logical-partition system_b

fastboot create-logical-partition system_a 100000

fastboot create-logical-partition system_b 100000

fastboot flash system [mygsi).img

reboot recovery

use "factory reset / wipe data"

reboot

---

Does the deleting of partitions wipe my phone anyway? I realize you said wiping was unnecessary but that was maybe alluding to the 'use "factory reset / wipe data"' instruction. Does vbmeta still need to be done? Do I have to reestablish Magisk?
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Came back with... what? I admit I didn't test this public release before uploading, but I just did and I was able to boot / use el Goog just fine.
[Treble-Enabled Device Development A/AB ROMS] Hatrackman:
Guess i could be more explicit...

Since I was under the impression i wasn't supposed to wipe i also did not remake partitions, or that thing with vbmeta, because... I basically have no idea what Im doing... How would you flash it?
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Supposedly you just flash the updated image to system and don't remake/wipe/flash anything else. If this dirty flashing goes wrong I'd be the first to notice, as I do update my daily driver in the same manner, ahead of public release.
[Treble-Enabled Device Development A/AB ROMS] Hatrackman:
Well, it gave me an error and stopped the process from initiating after I...

fastboot flash system lineage-20.0-20230417-UNOFFICIAL-gsi_arm64_gN.img

Should I be in the fastbootd thing when I do this?
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
ofc
[Treble-Enabled Device Development A/AB ROMS] Broswell:
EDIT: My bad, this is happening in TD Based i don't know if light, but i commented here by mistake

EDIT 2: Trying Latest Light version, clean install, this bug isn't here

Anyone has issues regarding GMS Accounts? (Gmail crashing, Maps asking for login but Account already exists
[Treble-Enabled Device Development A/AB ROMS] Hatrackman:
You mispelled 'of course'.
[Treble-Enabled Device Development A/AB ROMS] Hatrackman:
Ok. Did it all proper. Works magnificently. You rule.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
The post on the MTK no-internet issue (#9) has been updated with a more persistent fix, courtesy of @Rortiz2 .
[Treble-Enabled Device Development A/AB ROMS] Rummyy2003:
Trying it now my kernel is 4.19
[Treble-Enabled Device Development A/AB ROMS] veloc_h:
Is this guide

https://xdaforums.com/t/discoveryan...ng-gsis-for-all-android-devices-2021.4348851/

ok for flashing your custom rom?
[Treble-Enabled Device Development A/AB ROMS] zenfone selfie:
any chance of this rom working on JLQ soc? https://www.gsmarena.com/xiaomi_poco_c40-11468.php

currently waiting the 5 day period for unlocking the bootloader so i can't try it yet.
[Treble-Enabled Device Development A/AB ROMS] CRCinAU:
Tried the Light version

lineage-20.0-20230506-UNOFFICIAL-gsi_arm64_gN.img

- but only managed to get the Lineage OS logo repeating.

Device is a Lenovo TB-X606F...

Is there a way to get this to boot?

The lineage-20-td builds boot fine - but as posted in that thread, I'm having tons of errors on BT audio as well as problems with using Google Drive / Docs etc etc...
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
This is a "legacy" (pre-A10) device and Light isn't meant for it.
[Treble-Enabled Device Development A/AB ROMS] jianjin9987:
银行应用启动就闪退，提示原因是带root,但是我刷入的是不带root的版本，能修复它吗The bank application flashed back when it was started, indicating that the reason was root, but I swiped in the version without root. Can I fix it?
[Treble-Enabled Device Development A/AB ROMS] jianjin9987:
银行应用工作不友好

banking apps are not working fine
[Treble-Enabled Device Development A/AB ROMS] jianjin9987:
banking apps are not working fine
[Treble-Enabled Device Development A/AB ROMS] Le Vagabond:
@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.
[Treble-Enabled Device Development A/AB ROMS] AltairFR:
Salut le vagabond.

Do you have try trebledroid gsi or leaos ?
[Treble-Enabled Device Development A/AB ROMS] Le Vagabond:
@AltairFR I've tried a few of them, but not those two specifically. why?
[Treble-Enabled Device Development A/AB ROMS] SnowTag:
Hello there. I can't boot the GSI on my Motorola One Fusion (came with Android 10, latest vendor ROM is Android 11, VNDK, A/B so it should be supported)

Any ideas on what this could be? I mounted the .img and there are overlays for my device so I'd expect it to work. Also, the TD version works without changing much (just clean flashing).

I'll try building the GSI myself or make a non-Lineage based custom one.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Simply use TD-based then, nothing wrong with that.

Can't say I'm interested in finding out exactly why, but my guess is the old (A8-era) SDM710 SoC means it's actually running an A10 system on an <A10 vendor.
[Treble-Enabled Device Development A/AB ROMS] Λαβιθήραν:
is it okay if i use ab rom on an a only device ?

are there any problems because i am not going to update it and ab is require only if there are automatic updates right ? but i am going to manually flash it so is it okay for me to use ab rom on an A only device
[Treble-Enabled Device Development A/AB ROMS] 1NSN:
20-20230506-UNOFFICIAL gsi_arm64_vS

Redmi Note 11

Perfect!

Nice work!

THANKS!
[Treble-Enabled Device Development A/AB ROMS] ArtemKiss24:
Hi, on the latest lineage light firmware, I don’t have a mobile network at all and don’t search manually, there is only Wi-Fi ... What should I do and is there a fix?) Xiaomi 12t android 13 device
[Treble-Enabled Device Development A/AB ROMS] lemon07r:
I get the "This device isn't Play Protect certified" notification on the Legion Y70, using the gapps version.
[Treble-Enabled Device Development A/AB ROMS] V0latyle:
Your CTS profile probably isn't valid.

See this thread regarding Play Integrity issues. If your device is failing DEVICE_INTEGRITY, Play Protect will report uncertified.
[Treble-Enabled Device Development A/AB ROMS] lemon07r:
Yup fails CTS check on all the GSI roms I've tried so far.
[Treble-Enabled Device Development A/AB ROMS] V0latyle:
Try using the module I've linked in the thread. Install it, reboot, wait 5 min or so before you recheck Play Integrity.

If it still fails, use MagiskHide Props Config to change your CTS profile to a valid one.
[Treble-Enabled Device Development A/AB ROMS] lemon07r:
Gives me not found error, but im assuming you were trying to link universal safety net fix. I had that installed on my last gsi rom but it still didn't pass CTS, I guess I need to try the props config.
[Treble-Enabled Device Development A/AB ROMS] V0latyle:
Sorry about that, the link shold be fixed now.

There's two versions of USNF. The original by kdr@gon isn't being consistently maintained and doesn't fix Play Integrity. You have to use the Displax mod, which I had linked. For simplicity's sake, here you go
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
A-only is legacy and Light doesn't support those.
[Treble-Enabled Device Development A/AB ROMS] xdalover69:
NO HEADPHONE DETECTION

Hi there,

First off all i want to say a big thanks to Andy, PHH, and anyone who has made this project working.

I switched to the light version on my a53 5g, because bluetooth was not working on the TD version.

PROCESS:

With the light the bluetooth version works fine, but the device does not recognize the headphones when connected, which the TD version did, after toggling: use alternative audio policy. Which is greyed out in my settings.

My settings do have the: use alternative audio jack detection, which toggling still does not make the phone recognize the headphones.

I hear a faint blimp connecting the headphones, but audio still play's through the speakers.

Can i enable the greyed out option: use alternative audio policy, in my settings easily to try?

What else can i try ?

Any help is greatly appreciated.

Again big thanks guys! I feel awesome thanks to this alternative option.

I am amazed by the community and what it is achieving.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Updated all variants with Android 13 QPR3 and June security patches. [Insert obligatory backup-and-test warning here]

As usual with "feature drops", things can change or break majorly.

Not much on Light's side - it's nearly time to prep for U. Got an all-new building setup ready for that action.
[Treble-Enabled Device Development A/AB ROMS] tabithamoon:
On post #2 on this thread it is mentioned that

VoLTE on Motorola Qualcomm S vendors - waiting for T to re-evaluate situation

is still "To be implemented", is this still the case? Will it be fixed eventually if it still is pending? It does say "waiting on Tiramisu" but we're now waiting on U already, apparently.

I can send but I cannot receive SMS messages on my Motorola Edge 30 Pro, and IMS does not work according to the IMS info menu in the Phone information app. It says it is not registered.

VoLTE itself does not seem to work either, force enabling it in settings makes the option appear but connection still drops to 3G when a call is established.

I have a retbr (Brazillian Retail) device, on the TIM Brasil carrier.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Thanks for reminding that I should update this - for the worse, unfortunately.

VoLTE itself always worked for us, the only glaring issue is SMS reception, but even on device-specific ROMs, that only works after some "telephony injection" magic (which I've never seen needed for any other OEMs), and still doesn't reliably work for everyone, AND that magic isn't immediately available to the GSI usecase (we don't have the target jars, and it doesn't sound reasonable to have these in a generic image).

I wasn't really interested in chasing down this issue to begin with, as there are few Moto users out there and Moto's SW feels close to AOSP. Now with stock T I only got more discouraged, and will deprioritize or just ignore this, unless in the future Moto outs a device so compelling that I want to main it and have to solve its basic issues, like what I did for Xiaomi 13.
[Treble-Enabled Device Development A/AB ROMS] tabithamoon:
That's a shame. I've been looking to use LOS to get away from Google services and GSI was my only choice since there are no custom ROMs for this device. Plus, at least on my particular unit, stock A13 introduced horrible Bluetooth bugs, poor battery life and a lot of graphical glitches in a lot of apps (most notably React Native ones like Discord, and in Android's native PiP)

Is it at all possible to at least hack this together on a device by device basis after installing the GSI? I'd really rather not have to use stock right now 😥
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
I know more than one dev was making experimental X30/E30P builds based on X30P/E30U findings, although I didn't keep track of how that went. Or, just downgrade to stock S (via a fastboot package, you know).
[Treble-Enabled Device Development A/AB ROMS] tabithamoon:
In danger of going dangerously out of topic (and bothering you too much, sorry), do you happen to have any more info on this patch, some sort of lead I could follow? Research proved largely inconclusive, and I'd be willing to at least try to chase this down myself and build my own customized GSI for this device (adding this patch to the GSI seems easier than making a custom LOS build more or less from scratch, the only trees I could find are for AOSP and they are largely abandoned). It's really the only thing wrong with this ROM for me.

I'm honestly willing to keep using it despite the SMS issues, since I don't really use it for anything other than 2FA on the small handful of apps that don't offer a TOTP option so it comes up very rarely. It's the kinda thing I can wait to get home and then pop my SIM card on a old backup phone to receive the codes if I have to.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
If you're so interested, check out the core magic on device-specific ROMs: https://review.lineageos.org/q/topic:13-qcom-telephony-injection

Honestly, having spent big unnecessary bucks on an X30P/E30U, I myself am quite frustrated with Moto's way, both in GSI (this SMS BS) and sparse and late stock software upgrades. The device itself is kinda likable, so I guess I'll keep it for some longer, but won't pursue this issue again until maybe after A14's formal release.
[Treble-Enabled Device Development A/AB ROMS] M1ST0R:
Any Gapps support? I always have problem about System Partition
[Treble-Enabled Device Development A/AB ROMS] Hatrackman:
Another successful update. Much appreciated, Andy.
[Treble-Enabled Device Development A/AB ROMS] GroovyG:
Gave light a shot too after being happy with TD, but light is even better! I have a 120Hz screen and the implementation for that is indeed way better than in TD, extremely smooth and quite a lot easier on battery as well. Just awesome!