yashsingh1/xdaforums huggingface dataset:
[Treble-Enabled Device Development A/AB ROMS] jhjhjhjhjhjh:
Wow thanks for your work .

This is the second of 100 GSI Roms I've tried that has volte MMS gps and Bluetooth working

I'm using this gsi on a Motorola G Stylus 5 G 2022

Question can this ROM be built with r/w access?

Other than that I have no issues to report.

Great Job!!
[Treble-Enabled Device Development A/AB ROMS] wetito:
u can install microg, works fine and is better than google play services
[Treble-Enabled Device Development A/AB ROMS] Captain_cookie_200:
although if you use google services alot like discover etc. you might wana wait for the Gapps build otherwise micro g is epik
[Treble-Enabled Device Development A/AB ROMS] rigibaa4444:
Realme 8i

Helio G96

Rui 3 based

Dont working incall audio
[Treble-Enabled Device Development A/AB ROMS] Avraham Tsaban:
On "legacy devices", do you mean a-only and arm64 binder?
[Treble-Enabled Device Development A/AB ROMS] orangestate:
i hereby voice my interest in both.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
I've experimented GAPPS with at least some success - I was able to log in, and YASNAC reports basic integrity pass. Again, as a Chinese who's not invested in big G's ecosystem, I'm not sure how useful that'll be for you all. The upcoming batch will have an "integrally securized" gN build for trying out.
[Treble-Enabled Device Development A/AB ROMS] YoShake:
How can I enable all rear camera lens for apps? Lets's say for open camera.

adb shell setprop vendor.camera.aux.packagelist net.sourceforge.opencamera

worked on other GSI roms I have tried so far, but it doesn't seem to work in this one.

Also adding to /system/build.prop

vendor.camera.aux.packagelist=net.sourceforge.opencamera,org.lineageos.aperture

neither granted me access to all cameras, nor in LoS aperture, nor in opencamera.

Since treble settings are cut down to bare minimum I can't even try with enabling camera options.

Any ideas how to enable even temporary?

I wanted to make the first option with setprop persistent in /data/property/persistent_properties but neither the setprop option did work, and messing with encoding in this system file often ends in bootloop :\

btw. Any chances for making this rom OTA capable? I would gladly stick with it as most things (apart from cam) seems to work ok, cause there's no chance for any official custom A13 for moto G8. If not, what method of future updates not to loose everything should I go with?

Just dirty new flash system img without erasing it and resetting userdata with fastboot -w?
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
This I can answer you immediately - not only will I not implement OTA in "light", I will remove it from TD-based as well. PHH's OTA, while a wonderful feat, renders Magisk unusable; II'd also like GSI users to remain aware of the "proper" way of flashing them, and the dangerous nature of them, at all times.

As for how to update without - simply flash an updated image without doing anything else.
[Treble-Enabled Device Development A/AB ROMS] spider1163:
You can dirty flash any GSI with same Android version
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
I gave LineageOS's MotoActions a shot, and interestingly it not only worked out of the box to an extent, but also for non-Moto devices. However, without going into the code, I can tell that it might require device-specific work to interface with requisite sensors. As of now, the one you care about, "chop-chop", isn't working at all, and other motion-based gestures aren't being registered on non-Moto.

This is all interesting discovery, but due to the device-specific and non-must-have nature, I'll put this on a lower priority. In the meantime I feel you could find alternatives such as Tasker?
[Treble-Enabled Device Development A/AB ROMS] YoShake:
oh snap, I completely forgot about that path. All things one have to consider so badly complicates them.

I'm fine with manually flashing, just need to have a boot.img somewhere nearby in case I would need to get a root. Still got a dilemma wheter root, and go with microg or not, as only banking app keeps me away from going fully foss.

Nevertheless, I applaud the approach. Any sort of leaving the stock software path isn't a oneclick solution, and warning about this is a good approach in my opinion.

btw, Glad to read that you had an approach to motogestures thing. Admit if more out of a curiosity? ;)

Could you maybe shred some light about supporting all rear camera lenses in photo apps?

I think I have reached a dead end, and after trying out all possible solutions I've found on xda, stackexchange, reddit, github and any possible places my experience is still too low to find a working solution.
[Treble-Enabled Device Development A/AB ROMS] 3mel:
looking for end user help rather than dev fixes here.

2 huge power drains that could be linked. I'm using a backup of Vanced (that I've tried with 3 versions of Vanced MicroG) it draws massive amounts of power. also BBS always shows a wakelock for PowerManagerService.wakelock and PowerManagerService.suspend

both usually running at 100% or very high.

if anyone has a suggestion for cutting down the wakelocks or for a good Vanced replacement that isn't power hungry on this lite build I'd be grateful.

also if I have report background ANRs ticked in dev options NFC Service and SecureElementApplication are always popping up as stopped. I've disabled them both but I also wonder if they could be linked to the PowerManager wakelocks.

this SS doesn't show all the usual wakelocks as it's just come off charge.
[Treble-Enabled Device Development A/AB ROMS] ildar_prophet:
thanks a lot for your efforts for community's sake!

Now a couple of questions:

1. You said that you use this ROM as your daily driver. Is this the ROM in lineage-20-light folder? as I don't see a proper ROM in Testing folder.

2. Asking because I seek for the ROM with "patches_platform_personal" ON.

Thanks.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Interesting to know someone still wants one of these... I'll have one uploaded to Testing when the November update is ready.
[Treble-Enabled Device Development A/AB ROMS] wetito:
actually is the only gsi that on my device enable ims full features correctly. i think this rom have a great future
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
You probably missed this...
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Updated 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.
[Treble-Enabled Device Development A/AB ROMS] ped1609:
hello there is an error connecting to google services, a rom that I really like, I use redmi note 11s,.I have factory reset but it does not connect to google servers.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
#9
[Treble-Enabled Device Development A/AB ROMS] ped1609:
Gracias,Thank you.
[Treble-Enabled Device Development A/AB ROMS] wetito:
i have read, but on my mtk device work fine (i have a redmi note 10 5g). when i enter into phone setting with code *#*#4636#*#* volte setting is enabled and high lighted. is the only gsi with this full functionality. i have tested with dsu sideloader. if u think could be helpfull, i will post a screenshot for confirm what i'm saying. on my actual gsi, i have updated phh app with your version, and volte icon appeared on status bar. maybe it's fake, but probably volte could work also in mtk devices with a13. what do u think about? i hope my feedback will be helpull for you
[Treble-Enabled Device Development A/AB ROMS] Soble_:
Installed new version (Googled variant). Cant connect to adb, tried two different PCs, internet not working too (because of cant write command to adb).

P.S Fastboot works fine. Any command to make internet workable from it?
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
On "secure", USB Debugging has to be toggled on each reboot. I'm adding this to Notes now.
[Treble-Enabled Device Development A/AB ROMS] Soble_:
I tried turn off-on the toggle. Doesn't work for me (Helio G96)
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
To help narrow down the cause, please state your device, and also try and report what happens on one of PHH's A12 "secure" builds.
[Treble-Enabled Device Development A/AB ROMS] michael_hamada:
THX for your great work!

Running so smooth and stable(y)

This is the best GSI for my moto g30:)

THX so much indeed!!

Regards;
[Treble-Enabled Device Development A/AB ROMS] wetito:
i confirm that actually is the only one of all latest a13 gsi that boot on my mtk devices. i have made a little test of your personal gsi u have shared. my first impression is very positive. thanks for your incredible work that you share for free with this community
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
A gN test builds has been uploaded to Testing, the only change inside which is removing the ADB part of Securize - might help with USB Debugging issues some are having, but might in turn break GAPPS. cc @Soble_
[Treble-Enabled Device Development A/AB ROMS] Soble_:
What is the difference between TD and light versions? Sorry if this is written somewhere (most likely), I was just busy, now I went back to download the firmware and saw a new folder)
[Treble-Enabled Device Development A/AB ROMS] Soble_:
I will test and let you know if there are any problems
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Sounds like you skipped OP's must-read. TL;DR is, "light" will almost certainly be worse than TD in terms of compatibility/functionality, but has cleaner code and saves me brain cells.
[Treble-Enabled Device Development A/AB ROMS] hacker812c:
Thank you for light version
[Treble-Enabled Device Development A/AB ROMS] pbgapski:
A quick feedback on flashing your GSIs on poco f4 (munch). It is A/B device with dynamic partitions.

These were the GSIs I tried:

lineage-19.1-20221011-UNOFFICIAL-arm64_bgS.img.xz

lineage-20.0-20221109-UNOFFICIAL-gsi_arm64_gN-secure.img.xz

lineage-20.0-20221111-UNOFFICIAL-arm64_bgN-secure.img.xz

I first tried the light lineage-20.0-20221109-UNOFFICIAL-gsi_arm64_gN-secure.img.xz, however the device bootlooped.

Both lineage-19.1-20221011-UNOFFICIAL-arm64_bgS.img.xz and lineage-20.0-20221111-UNOFFICIAL-arm64_bgN-secure.img.xz booted fine.

Thanks for your work on building and caring for these GSIs.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
And how was it? I've been waiting on your response to decide whether to backport this change to LOS19...
[Treble-Enabled Device Development A/AB ROMS] Heeni:
I've been using your GSIs on two WiFi-only tablets, both with the same SoC if that's of any relevance. Thanks very much for your work.

The only issue of any significance (to me, anyway) is getting the internal speaker to turn off when a headset is plugged in. On 19.1, I need to set Misc features->Force headset switch (Huawei default) and Misc features->Use alternate way to detect headsets to ON. The alternate audio policy setting doesn't seem to do anything, even though the devices have Qualcomm SoCs.

I can appreciate that you don't want to go on adding settings ad infinitum. So, is there any way that I can set this using adb shell? I'm willing to do this, but I do need to know where the configs are and how to set them.

Or, if anyone knows of another way to manually turn off the internal speaker and leave the headset active, please let me know.

Edit: To clarify, I've upgraded one of the tablets to version 20, and I can't get the internal speaker to turn off when the headset is plugged in.
[Treble-Enabled Device Development A/AB ROMS] 3mel:
do the TD builds dirty flash over the LITE personal build ?
[Treble-Enabled Device Development A/AB ROMS] michael_hamada:
I did it without any issue.

GSIs based on same version of Android, you can switch them by dirty flash.
[Treble-Enabled Device Development A/AB ROMS] 3mel:
just gave it a try and it didn't boot, I went from lite to bVN vndklite !?
[Treble-Enabled Device Development A/AB ROMS] michael_hamada:
Well, so that isn't the issue caused by dirty flash. It's the issue of compatibility of your device and the ROM.

I was able to switch between ArrowOS, crDroid, LOS 20 TD and LOS 20 Lite with dirty flash without any issue on my Moto g30.

But other GSIs I tried won't boot even with clean flash.
[Treble-Enabled Device Development A/AB ROMS] 3mel:
most GSIs boot for me unless they need a modded vendor... will try a clean flash later today.
[Treble-Enabled Device Development A/AB ROMS] ildar_prophet:
hi! just installed.

1. experienced failing Networking, fixed with restricted_networking_mode off

2. Bluetooth headset doesn't play music. I remember fixing it on LOS-19 by disabling a2dp offload. Now I see it disabled by default [persist.sys.phh.disable_a2dp_offload]: [true]. Hmm. What shall I do?

Having MTK phone (A11 vendor). Model AGM H3. ROM Testing 20221109-personal

@AndyYan , thanks a lot for this ROM!
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
I've had a bunch of reports of "Light" failing on Xiaomi/Redmi devices, but none detailed enough (log while bootlooping would be nice). My own Civi is working well, but it's on a slightly older MIUI12 R vendor. It does interest me when "modern" devices wouldn't boot "Light" - perhaps I should grab one of the reported devices and see for myself...

Unimplemented yet, I'll check if they're as simple as a prop + a single platform-side change, and if so I'm okay with adding them next.
[Treble-Enabled Device Development A/AB ROMS] selo28:
I'm stuck at the boot screen
[Treble-Enabled Device Development A/AB ROMS] 3mel:
could just be me but I've now downloaded lineage-20.0-20221111-UNOFFICIAL-arm64_bvN-vndklite-secure.img twice, first time I dirty flashed, the 2nd time was clean. both times the rom wouldn't boot for me.
[Treble-Enabled Device Development A/AB ROMS] pbgapski:
I am not sure this is related or not, but I just tried to DSU the light GSI as a simple way to grab some logs. But it just fails.

The command I used was:

adb shell am start-activity -n com.android.dynsystem/com.android.dynsystem.VerificationActivity -a android.os.image.action.START_INSTALL -d file:///storage/emulated/0/Download/system.img --el KEY_SYSTEM_SIZE 3350601728 --el KEY_USERDATA_SIZE 8589934592

And I immediately get a failed update notification.

Has anyone been able to boot this GSI in this way?
[Treble-Enabled Device Development A/AB ROMS] ildar_prophet:
It's actually implemented. But there's a bug: https://github.com/phhusson/treble_experimentations/issues/2480

So setting to false fixed the issue.
[Treble-Enabled Device Development A/AB ROMS] ildar_prophet:
@AndyYan , the ROM misses the lptools. So I cannot expand the partition to install the MicroG. Help!

Nevermind, I got the binary from the TrebleDroid and it works just fine.

Anyway, I suggest having lptools in the ROM.
[Treble-Enabled Device Development A/AB ROMS] ildar_prophet:
But the real big problem is that it seems to not support the Signature Spoofing a.k.a. FAKE_PACKAGE_SIGNATURE. So MicroG doesn't work.

Right?
[Treble-Enabled Device Development A/AB ROMS] 3mel:
I'm using zygisk LSPosed module and fake gapps module with the light build, everything seems to be working OK, all boxes ticked. I'm using nogoolag microG tho.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
DSU immediately failing likely indicates something's wrong with your parameters - logcat should tell you exactly what.

It's not... It's a "phh"-series prop, and had such been implemented in "Light", they'd be under a different name.

Noted, but again, I'd prefer not to expand "light" excessively. If TD-based works better for you, simply switch to that.
[Treble-Enabled Device Development A/AB ROMS] ildar_prophet:
1. lptools is a matter to ~50kB. Shouldn't disturb the "lightness" ))

2. MicroG is very honored in FOSS community, strongly recommended. And again, AFAIK it's a very light patch, yet strongly recommended.

I'll definitely try the TD LOS20 but I'm sure I'll miss your "personal" patches because my FP sensor is crap.

thanks!
[Treble-Enabled Device Development A/AB ROMS] ildar_prophet:
a little too insisting, sorry. Vote results at https://xdaforums.com/t/gsi-12-lineageos-19-x-gsi-a64b-64b.4358041/

I don't use GAPPS at all: 42%
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Not using GAPPS doesn't mean needing MG ¯\_(ツ)_/¯

(Case in point, China)
[Treble-Enabled Device Development A/AB ROMS] pbgapski:
I have just tried it again and it worked. The main difference is that previously I was on stock, now on ArrowOS, but I cannot rule out some error on my side previously.

The GSI used was lineage-20.0-20221109-UNOFFICIAL-gsi_arm64_gN-secure.

For the record:

adb shell am start-activity -n com.android.dynsystem/com.android.dynsystem.VerificationActivity -a android.os.image.action.START_INSTALL -d file:///storage/emulated/0/Download/gsi.img.gz --el KEY_SYSTEM_SIZE 3350601728 --el KEY_USERDATA_SIZE $((8*1024*1024*1024))

As for the debug part, could you please point to docs or explain how to generate useful logs in this scenario?
[Treble-Enabled Device Development A/AB ROMS] ildar_prophet:
My short report on testing the ROM on my AGM H3 (MTK):

1. Works almost perfectly.

2. BT stack crashes with some headsets. Similar to https://github.com/phhusson/treble_experimentations/issues/376 but I didn't check the logcat yet.

3. BLE doesn't connect until scanned, https://github.com/phhusson/treble_experimentations/issues/2413

4. NFC not detected, https://github.com/phhusson/treble_experimentations/issues/1073

Actually the bugs are the same as with the Phh's AOSP 12 and TD ROMs.

If anyone has an idea how to fix those, plz raise the voice. Thanks,
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
I've implemented this month's backlog (except for lptools) in a personal build - these are outside of my "selfish" usecases, implemented blindly and in some cases differently from the original, and need at least some testing before rollout.

@Heeni - Alternative audio jack detection, Force headset audio

@ildar_prophet - Disable A2DP offload, MicroG for priv-app, optional FP lockout (set persist.sys.fp.lockouts.disable to true)

And to everyone - now that there are TD-based builds, if you feel "light" doesn't do your device justice, please just use TD-based instead. Keep requests here minimal and show me their worth. I'd rather have only myself using "light", than blowing it like a balloon and having it explode in my face when Android U comes.
[Treble-Enabled Device Development A/AB ROMS] Heeni:
Thank you. I've done some testing and discovered that Force headset audio won't stay turned on. As soon as I exit the GSI config screen, it disables itself.

However, it doesn't appear to be needed. Just Alternative audio jack detection on its own lets me listen using the headphones without having the speakers also running. So I can now listen to my music or podcasts without annoying everyone else in the same room :) . That, really, is all I need.

I discovered another change, which I can live with, but thought I'd mention anyway. The Trebuchet app drawer no longer opens to the full height of the screen when I swipe up. I can still see the dimmed-out clock above the top of the app drawer.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Good. That one was the most involved of the bunch, and historically was only supposed to be used on Huaweis, so I might as well exclude it.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Updated 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
[Treble-Enabled Device Development A/AB ROMS] leonardoncm:
SMS does not work.

MotoG52, snapdragon680
[Treble-Enabled Device Development A/AB ROMS] pbgapski:
I have briefly tested this GSI on munch. The main issue is that I have no buttons for navigation, nor working gestures. Swipe down from the top works, but I cannot go back, return to launcher or switch apps.

The previous light image had this same behavior on my device, while TD works fine.
[Treble-Enabled Device Development A/AB ROMS] Captain_cookie_200:
epikk!!! now waiting for td. light still doesnt have some stuff in the settings for me. so i am waiting for td instead
[Treble-Enabled Device Development A/AB ROMS] Captain_cookie_200:
hey there andy. tysm for adding those things in treble settings! although some things are still keeping me from switching. there is a toggle in phh settings under misc called "Allow setting brightness to lowest option" which fixes my brightness bar. its broken on this gsi currently. second is dt2w. its not fatal but would be nice havin it. is there a temp workaround for the two or the first one? otherwise the gsi is runnin smoothly your work is awesome!
[Treble-Enabled Device Development A/AB ROMS] MPK99:
Two strange issues:

1. Auto rotate doesn't seem to work. Anyone confirm this ?

2. During media playback, when a notification sound arrives, it drops media volume levels to half & doesn't regain until I restart the player (volume decibels, not the volume slider)
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
This could do with the fact that I configured the overlay to have all hardware keys, to expose their settings universally. Unfortunately I can't kill that (you never know what kind of bizarre devices are out there), but I think I can try finding and killing the checks guarding the navigation options.
[Treble-Enabled Device Development A/AB ROMS] DerTeufel1980:
so, i have tried selfcompiled lineageOs20-gsi, selfcompiled aosp-13-gsi, official 13-gsi and finally your build. With all i come to bootanmation, but don't get adb (it also does not boot, hence i need adb). Any ideas what could be wrong?

android 12 GSIs all boot just fine
[Treble-Enabled Device Development A/AB ROMS] AltairFR:
What's your phone model ?
[Treble-Enabled Device Development A/AB ROMS] DerTeufel1980:
it's lenovo x606fa (running android 10 by default)
[Treble-Enabled Device Development A/AB ROMS] DerTeufel1980:
'td' version is booting. what's the difference with this?
[Treble-Enabled Device Development A/AB ROMS] AltairFR:
Lineage 20 light don't include the same patch that TD
[Treble-Enabled Device Development A/AB ROMS] ildar_prophet:
Would you be so kind to read the 1st and the 2nd messages of this thread and LOS-TD's thread ? Thank you
[Treble-Enabled Device Development A/AB ROMS] DerTeufel1980:
i have read what Td stands for... this does not explain differences in code. There has to be some (or more) specific changes, which

a) make adb work on TD build, compared to the light version (and any other version I have tried/compiled)

b) make it also boot up compared to the light version (and any other version I have tried/compiled)

if this was already mentioned there, I appologize... would you be so kind, to point me to it?

edit: but yes, my initial question about the difference was not that detailed :/
[Treble-Enabled Device Development A/AB ROMS] MPK99:
No one ?
[Treble-Enabled Device Development A/AB ROMS] MPK99:
Light is just the one with minimal phh patches cherry picked by Andy. TD is the one with all phh patches.
[Treble-Enabled Device Development A/AB ROMS] jmfindorff:
For Auto Rotate, do you have that turned on? It's turned off by default, that's why I'm asking.