yashsingh1/xdaforums huggingface dataset:
[Treble-Enabled Device Development A/AB ROMS] veloc_h:
Today I flashed

1.) lineage-20.0-20230507-UNOFFICIAL-a64_bvS, stuck at boot-animation, so after that

2.) lineage-20.0-20230507-UNOFFICIAL-a64_bvS-vndklite, the same: stuck at the LOS logo.

In detail (Cubot KIngkong Mini1 mobile phone)

fastboot flash ended without any errors. After that I have deleted the cache partition , LOS starts, but it's stuck at the bootanimation (LOS curve with the moving ball, every 2 seconds.... (I waited for 20 minutes)

I have flashed first nr 1, (plus deleting cache part.), then, because it got stuck during boot (LOS boot animation), I have installed nr. 2 (dirty flashing as well). With the same result

***

1. adb devices

2. fastboot reboot fastboot

3. fastboot devices

4. fastboot flash system SYSTEM.img

***

Via recovery (then vol+ and on/ofI at the same time) I deleted the cache partition.

Before the dirty flashes I had installed Phhusson

Release AOSP 12.1 v416 · phhusson/treble_experimentations

Still July security patch Fixes fingerprint enrolling crashing on gapps variant (only for 64bits, sorry, 32bits will still need to disable Android Setup app after setup wizard) Fixes the huge memo...

github.com

arm32_binder64-ab-vanilla

which worked fine (apart from the missing battery consumption statistics, which is a A12 problem).

Edit:

I managed to install Nr. 2, after I've added three commands to my list. I guess, that fastboot reboot bootloader was necessary in order to mark the boot partition (?). Which ones are necessary?

This time I started with vol+ and on/off then I selected fastboot on the menue

1. fastboot devices

2. ***fastboot flashing unlock (???)

Never executed fastboot flashing lock

3. fastboot flash system SYSTEM.img

4. *** fastboot reboot bootloader

5. ***fastboot reboot

Allthough I did a "dirty" flash on top of the phhusson vanilla rom, apps and personal data are lost.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
If the Phh AOSP A13 gsi booted, then LOS 20 should too, I would think. LOS 20 is largely based on Phh's source code. Maybe try bvn instead of bvs, see if it's still stuck.

And when you say that it's stuck on the logo, do you mean manufacturer logo, or LOS logo? If it gets as far as LOS logo, this at least means that Android has been initialized, to some degree. If stuck on the manufacturer logo, then it's still in the bootloader phase (pre-Android initialization), it could be a vbmeta issue. Maybe disabling verity and verification via fastboot will make a difference.
[Treble-Enabled Device Development A/AB ROMS] veloc_h:
Finally LOS 20 started (it got stuck on the LOS logo (ball tracing a the curve, again and again)

Finally I I added the commands marked with a star:

with vol+ and on/off I selected fastboot mode

1. fastboot devices

2. ***fastboot flashing unlock (???, shoudn't change anything now, because I never executed fastboot flashing lock)

3. fastboot flash system SYSTEM.img

4. *** fastboot reboot bootloader

5. ***fastboot reboot

Andy Yan's ROM seems to be very responsive, the screenshot function works (did not work on the A12 rom from phhusson, which might bes a restriction of A12 as well, I think).

Thanks a million, @AndyYan for all that work!

Why did the apps and the personal data (content of the download folder e.g.) dissapear? I haven't cleared anything apart from cache)? Expected that a flash over Phh wouldn't delete my personal data. However I had flashed consequently the two versions of LOS 20,

1.) lineage-20.0-20230507-UNOFFICIAL-a64_bvS and then

2.) lineage-20.0-20230507-UNOFFICIAL-a64_bvS-vndklite and then

3.) lineage-20.0-20230507-UNOFFICIAL-a64_bvS again with the star marked steps (which worked finally).

Of course my mistake not to create a backup. Not very valuable data, but time consuming data (like the configuration of Osmand).

At he present I haven't installed anything. Would you recommend another clean install (before installing apps and configuration). Is it sufficient to do a "Factory data reset" or should I wipe cache (once again...), data and system?
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
If you're coming from the Phh gsi to LOS, you should always wipe data. They're similar and share alot of the same code, but still different ROMs regardless, you can't just switch between them without clean installing. However, you can upgrade from one LOS release to the next without data wipes. Not wiping is probably why it got stuck like you mentioned.

No need to wipe system, just flash the gsi file. It will automatically overwrite the Phh gsi.
[Treble-Enabled Device Development A/AB ROMS] veloc_h:
Does it mean, that I shouldn't do anything now (don't see any lags at the present)

Thanks, I was told differently. On the LeOS telegram channel e.g. I was told that my personal data would remain installing LeOS... So I thought it's even less risky to install LOS (because of less customizations).
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
If it ain't broke, don't fix it.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
@AndyYan: Unfortunately it seems that BT audio is completely broken in the 5-7 build. I can pair my earbuds, but audio always plays through my speakers regardless. I even selected it to play through the earbuds by default, but it ignores that. This essentially means I can't watch videos or take calls while in public spaces, not without disturbing others.

I can't definitively remember in which build it last worked, since I only use them when needed, not daily. But often enough that I consider it essential.

Before I go downgrading to older versions to find the last working build, any ideas/suggestions (from anyone)? I haven't configured any audio settings in the Phh Treble, and I never needed to before on any LOS 20 build. I've also went poking around in Dev options, having noticed that the disable A2DP offload is missing in Treble settings. It is present in Dev options, but the toggle is grayed out, so I can't try it. On older gsi builds (before A13) I had to use that.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
I've been notified of a new TrebleApp change (not authored by me) earlier, but I was under the impression that it wouldn't affect existing users and didn't pay enough attention. There should be a new "Use System Wide BT HAL" switch in Misc, see if that works for you?
[Treble-Enabled Device Development A/AB ROMS] zyhk:
If you manage to work the BT anyway, try USB SampleRate Changer. This script generates audio policy files for AOSP BT stacks, a2dp hardware offload BT stacks and legacy BT stacks, and overlay them on your original one on the fly. This may work for you.

Edit: I found "sysbta" (System Wide BT HAL?) was sticking to the audio policy in the audioserver, and the above script cannot change the policy.

Edit2: I added "sysbta" support and made "a2dp offload" BT HAL available on A13 GSI's.
[Treble-Enabled Device Development A/AB ROMS] CarlosCMD:
How can i make the internet monitor meter appear on the right. At the center it's being hidden by the notch
[Treble-Enabled Device Development A/AB ROMS] kevinco1:
It's actually been like this since the 70s when globalization first became a thing. The future you speak of has already been here for a few decades
[Treble-Enabled Device Development A/AB ROMS] kevinco1:
The only recent build where bluetooth is fully functional is 2023218
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
Yeah, true, but it's only going to get worse from here. However, because XDA is technical in nature, and not geared for extensive convos on other topics, I won't elaborate further here, other than to say that I do have personal views on this that are deeply felt and that many would consider to be very controversial.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
Can you reference this commit? I just would like to know when it was submitted/approved for inclusion.

Either way, the issue appears to be resolved. I clean-reflashed the 5-7 bvn build, along with a magisk patched boot.img, and a vendor.img that has been patched to disable data partition encryption. After booting it, I expected BT audio to not work again, since the circumstances were similar to the previous ones, I did my best to keep discrepancies to a minumum . To my surprise, it worked immediately and still does. It would seem that custom ROMs are like girlfriends, b****y one day and amiable the next. Too many times I have encountered things that seeming worked fine, only to break in the next moment, and be working again shortly thereafter.

I can't say for certain if the Phh Treble setting you mentioned is affecting my results, but I enabled it and "spoof system props" immediately after the GSI booted, before doing anything else. It didn't seem to have an effect before the clean boot.
[Treble-Enabled Device Development A/AB ROMS] CRCinAU:
@AndyYan - I've installed lineage-20.0-20230507-UNOFFICIAL-arm64_bgN - yet when I install Google Drive, it tells me to sign in. I've already signed in and my account exists in all other Google apps, and when I try to log into my same account, Google Drive app tells me that my account is already present.

It also looks like Google Docs, has the same issue.

I also can't seem to install Google Calendar from the Play Store. I'm not sure why - it errors every time...

I'm using a Lenovo TB-X606F, and installed Magisk + modules to pass safetynet etc etc.

BT Audio seems to work ok, WiFis fine....

Has anyone else had this problem with Google Drive or some other linked apps?

EDIT: Google Docs / Drive seems to revolve / be related to these logcats:

05-13 16:06:40.017 7186 7215 E AccountsCentral: Error accessing 'com.google.work' accounts. Returning empty array.
05-13 16:06:40.017 7186 7215 E AccountsCentral: android.os.RemoteException: Accounts ContentProvider failed: GoogleCertificatesRslt: debug cert rejected: pkg=com.google.android.apps.docs, sha256=[1975b2f17177bc89a5dff31f9e64a6cae281a53dc1d1d59b1d147fe1c82afa00], atk=false, ver=231613044.true (go/gsrlt)
[Treble-Enabled Device Development A/AB ROMS] veloc_h:
compared to LeOS: Does the vanilla from Andyyan comsume more battery than LeOS, because LeOS is more de-googled (so less attempts to contact google in order to transfer personal data to google? Or is it about the same? What are the reasons for more or less battery consumption of the system itself ? I only use f-droid based apps. Still looking for a replacement of google tts engine. espeak sounds pretty synthetic.
[Treble-Enabled Device Development A/AB ROMS] CRCinAU:
Interestingly, I installed the lineage-19.x ROM to test. I could install Google Drive and Docs etc and it worked perfectly.

I still can't seem to install Google Calendar...

Most other things seem to work as far as I can so far though...
[Treble-Enabled Device Development A/AB ROMS] fabioken:
I'm with same problem in Samsung Galaxy Tab A7 Lite
[Treble-Enabled Device Development A/AB ROMS] fabioken:
Oh I switched this and works fine here thanks...
[Treble-Enabled Device Development A/AB ROMS] kevinco1:
The only build where bluetooth is fully functional on Samsung tablets is 20230218
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
It's working for me again on the 5-7, and on a Tab S7+. Just out of nowhere, started working after a reflash. Which I already reported above. To me, "functional" just means that BT audio correctly plays through the paired device instead of the speakers. So I think you are incorrect, it's not necessary to use that old build.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Remove force disable A2DP offload and introduce sysbta HAL [2/2] · TrebleDroid/treble_app@a08f5c6

Related with https://github.com/TrebleDroid/device_phh_treble/commit/de7824d7c19735e24c2c2944e4e1ec2734a7c790

github.com

This has since been amended with another commit that defaults it to true, but as a batch of builds had been rolled out, the damage had been done.

Per #2, I can't/won't help with GAPPS beyond logging in...
[Treble-Enabled Device Development A/AB ROMS] CRCinAU:
I think this is a certificate problem with the A13 builds. PixelExperience also seems to have the same problem.

A12 / Lineage 19.x builds seem to work correctly - so it may well be a regression in the builds going to A13 / L20...
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
Maybe you could try the vanilla vndklite build, then flash MindTheGApps on top of that. This is assuming you have TWRP, the zip can't be flashed without it.
[Treble-Enabled Device Development A/AB ROMS] CRCinAU:
I do have TWRP on there - I'll give this a go...

Am I right in my understanding that using the vndklite image, the gapps parts will go into /system?

It's hard to find concrete information on what limitations exist when trying to figure these bits out.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
By using vndklite, the system partition will be writable as read/write, instead of just read only. You will need to use vndklite if you want to flash MindTheGApps.

I suggest that you use these steps, in this order:

1. Flash gsi img

2. Boot into LOS once

3. Reboot into TWRP

4. Flash MTG zip

5. While still in TWRP, factory reset. If your data partition is encrypted, format it. If not encrypted, you can just wipe data, instead of formatting

6. Boot LOS again, set it up the way you want and test

You will probably get an error if you try to flash the MTG zip in the same go/same time as the gsi IMG. This is because the gsi IMG is resized to the minimum possible size, which leaves not enough room for GApps. Booting the gsi before flashing the zip, gives the system partition a chance to resize its' filesystem to the max size that is possible, which leaves enough room for GApps.

If you still want to flash the zip in the same run as the gsi IMG, open TWRP terminal and run these commands:

e2fsck -f <PathToSystemPartitionBlockHere>

Then:

resize2fs <PathToSystemPartitionBlockHere>

Then run the e2fsck command once more. These commands will resize the system partition filesystem to the max that is allowed by the partition size. In my case, the path to system partition block is /dev/block/dm-0. Yours may be different.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
I decided to do a quick test for you, to see if I get the same results. I used the same IMG file that you used, except I chose the vndklite version. Then I used DSU Sideloader to flash the gsi.

Sorry, but it's mostly just you. Google Drive installs fine for me, and it shows me as being logged in. Same for Google Docs. All other Google apps also recognize that my account is logged in.

I too am unable to install Google Calendar via the Play Store, it just errors. But if I install this apk, it works:

Google Calendar 2023.18.2-529025936-release APK Download by Google LLC - APKMirror

Google Calendar 2023.18.2-529025936-release APK Download by Google LLC - APKMirror Free and safe Android APK downloads

www.apkmirror.com

I am able to launch it, and it shows me as being logged in. If you don't mind manually installing apks, then perhaps this will be an acceptable solution for you.

And I did not try to use MindTheGApps during this test. Just the GApps that are bundled in LOS.
[Treble-Enabled Device Development A/AB ROMS] CRCinAU:
This is interesting - as I saw this across multiple installs and at least this ROM and the PixelExperience one.

I did use the vdnklite one at some point, but had weird things like the icons changing from the default circles to squares etc. I didn't get that on the normal one.

As for the Google apps, things like Maps, Photos, and Play Store worked fine - but Docs and Drive didn't - both throwing that cert error.

I was toying with the non-Google'ed versions and installing the things I use via Aurora Store (obtained via F-Droid), but things like Teams etc require the GSF to do push messages (I think) - so I don't know how functional they'll be without it.

I guess I could always try it and see. Given the device is wifi only anyway, I don't know if the lack of push notifications would really be the end of the world...
[Treble-Enabled Device Development A/AB ROMS] CRCinAU:
I'm trying something slightly different..... I installed: lineage-20.0-20230507-UNOFFICIAL-arm64_bvS-vndklite.img

I'm trying to set up MicroG - and then install the other extensions to it. In the health check, it says the ROM has support for signature spoofing, but for the life in me, I can't figure out how to grant the permission to allow this.

I installed microg via F-Droid and adding the repo https://microg.org/fdroid/repo - then installing microG Services Core.

The self-check says:

System has signature spoofing support: Check

System grants signature spoofing permission: Not checked

System spoofs signature: Not checked.

From what I understand, I need to get those three operational to use MicroG properly?

When I tap the option to try and grant the permission, I see the following in logcat:

E GrantPermissionsViewModel: None of [android.permission.FAKE_PACKAGE_SIGNATURE] in {android.permission-group.NEARBY_DEVICES=[android.permission.BLUETOOTH_ADVERTISE, android.permission.BLUETOOTH_CONNECT, android.permission.BLUETOOTH_SCAN], android.permission-group.LOCATION=[android.permission.ACCESS_BACKGROUND_LOCATION, android.permission.ACCESS_COARSE_LOCATION, android.permission.ACCESS_FINE_LOCATION], android.permission-group.PHONE=[android.permission.READ_PHONE_STATE], android.permission-group.CONTACTS=[android.permission.GET_ACCOUNTS], android.permission-group.STORAGE=[android.permission.WRITE_EXTERNAL_STORAGE, android.permission.READ_EXTERNAL_STORAGE], android.permission-group.SMS=[android.permission.RECEIVE_SMS], android.permission-group.NOTIFICATIONS=[android.permission.POST_NOTIFICATIONS], android.permission-group.READ_MEDIA_AURAL=[android.permission.READ_MEDIA_AUDIO], android.permission-group.READ_MEDIA_VISUAL=[android.permission.READ_MEDIA_VIDEO, android.permission.READ_MEDIA_IMAGES]}
[Treble-Enabled Device Development A/AB ROMS] joaofl:
Could you get the fingerprint working on the S22? Any tips, clues?

I am also missing the typycal 5G, but 4G works alsmos as fast where I live anyway. Feature like tap to wake are also missing ( I guess the whole aways-on-display settings. I am not sure if that is the case for all GSIs.

Apart from that, this is the best alt ROM for the S22 that i've tested so far.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
MG will have be either manually installed into /system/priv-app or via a Magisk module.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
As Andy has said, it needs to be a priv-app, or else spoofing perm will not be granted.

Did you try MindTheGApps on top of vanilla LOS? It worked for me before. I prefer MicroG, but there are certain circumstances where official GApps are better. So I use both when needed, in separate ROM installs. They can't coexist on the same ROM.

If you just need something simple that will flash MicroG into system partition, use this:

[MOD][FLASHABLE] microG unofficial installer

Description microG unofficial installer simplify the installation of microG. IT FEATURE ALSO NON-AROMA LIVE SETUP (now working on all phones). Download microG unofficial installer v1.3.1 beta - Full (Android 2.2 - 13) - MIRROR microG unofficial...

xdaforums.com

Flash the zip in twrp with the instructions I already posted, substituting the MicroG installer in place of MTG.

https://xdaforums.com/t/gsi-13-lineageos-20-trebledroid-based.4517345/post-88534683
[Treble-Enabled Device Development A/AB ROMS] CRCinAU:
Thanks - I ended up getting MicroG going - but it can't restore my purchases on the real Play Store - so I've abandoned that idea.

I did a full reinstall of `lineage-20.0-20230507-UNOFFICIAL-arm64_bvS-vndklite.img` and then formatted userdata and started again.

I booted once, rebooted back into TWRP, and then installed the MTG zip. Rebooted again, and once I allowed Play Store access to the network, everything just started to work.

It looks like there are no problems with app permissions this time. Google Drive works fine now.

I'm still getting everything set up again, but it even seems like it responds better too. Not sure why - or if its just user bias :D :D :D
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
Can't "restore" purchases? You mean your paid apps are showing as not paid? Sometimes it just takes a bit for the store to sync your purchases. You can speed it up by downloading a free app you've already made an in-app purchase in. Try to initiate a purchase in app as if you want to buy something, the app should see that you've already paid. Very soon after, play store should sync your purchases and recognize your paid apps as bought, allowing you to download them. This process only works with non-consumable purchases, like an unlocked feature. Not for purchases involving virtual currencies (coins, gems, etc) that you spend. It might also help to clear the store's data/cache and relaunch it. Download a few free apps, that makes the syncing faster. In my experience play store works fine with MicroG, which includes buying stuff, and downloading apps you've already bought.
[Treble-Enabled Device Development A/AB ROMS] CRCinAU:
Ahhh - you use the actual Google Play Store with MicroG? I was using the 'fake' one. It doesn't really matter - as I end up installing a ton of Google stuff anyway - so its probably saving myself some pain doing the whole Gapps path anyway.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
Well, FakeStore is exactly what it sounds like...an empty package that pretends to be Play Store, but does nothing else. But yeah, I use the real store. Replacing FakeStore with Play Store is trivial. You can also pass Safety net with MicroG, I've done it. Perhaps not right now, but give MicroG another shot later. Just know that it's not 100% compatible with all Google apps. But with the majority of them, yes. It all depends on which ones are important to you, and which you can live without.
[Treble-Enabled Device Development A/AB ROMS] CRCinAU:
Yeah - its been one hell of a learning curve :D :D :D

I also managed to patch lk-verified.img on my device to get rid of the boot wait due to the unlocked bootloader too - so that makes it a much smoother experience.

The last time I tried to go down the whole GSI / Treble path about 6 months ago, I just didn't have the brainspace to figure it all out and just went back to stock everything due to time pressures. This time, I've been able to play around for a few days to get something much more usable.

I'm glad I did - because for a cheapish tablet, this this is pretty damn decent.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
When I first tried gsis on the 2 devices I own now, I knew I could never go back to using Samsung's bloated stock ROMs as my daily driver. Overall, the gsi experience has been very good. And even though there are issues, it doesn't bother me, since they're mostly minor. Either way, it's been a learning experience, I'm always down for that. When problems come my way, I hammer away until I find answers. They may not come quickly, but I will find them. I'm a stubborn, persistent old dog that doesn't give up. Learning is an important part of life. But you don't learn if you don't try. Trial and error is all part of the process.
[Treble-Enabled Device Development A/AB ROMS] jonpjingleheimler:
Hi. I had the same issues as you. I am on a Galaxy Tab A T-510. When I flashed los 19.1 and set it up I did not do the extra "finish setting up your device" and instead prompted for a reminder the next day which btw is today. I went through the set up and it even offered to restore a back up which I did. went through downloading and installing all the apps again and then I was able to get drive open without signing in and Chrome shows as syncing. this held even after a restart. Just wanted to put this out there as something to consider if you are having these issues.
[Treble-Enabled Device Development A/AB ROMS] Jonny:
I have a PR that fixes this
[Treble-Enabled Device Development A/AB ROMS] albertordzcz:
Any way to make android Auto works on this amazing rom?, by the way thanks for all of your efforts!