yashsingh1/xdaforums huggingface dataset:
[Treble-Enabled Device Development A/AB ROMS] psychofaktory:
Thank you for your explanations.

That was very informative. It is a pity that I was not aware of this earlier.

Further above you wrote that after flashing the vbmeta.img a factory reset (cleaned cache/data partitions) would be necessary.

Does this also apply when changing the vbmeta.img from Google/generic to the patched vendor vmbeta?

This is the same constellation that I have been using successfully so far.

Basically everything works for me.

Only occasionally there are problems that I can not really explain and for which I could not find a solution.

FolderSync can not be started or installed from the PlayStore at all.

In Swift Backup, there are problems with the Google login (in other places, however, it works).

And the app CallRecorder from skvalex also does not start.

In all cases, the respective developers said it was related to problems with Google services.

I use lineage-20.0-20230218-UNOFFICIAL-arm64_bgN-vndklite.img, where Google services are already implemented. But the errors already existed with the previous versions. Others do not seem to have these problems with these builds. Therefore, the cause of the error must lie elsewhere.

Could this be due to the wrong signature of the vbmeta.img?
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
If the vbmeta you're flashing happens to be identical to what's installed, no reset is necessary. However, in my experience, once the values at offset 123 have changed, android will detect this and not boot without a reset. That's definitely true for my stock firmware ROMs. Maybe gsis are more permissive. I honestly am not sure, vbmeta is one of those things I flash and forget, a 1 time deal. It will stay as is, unless you flash stock firmware. I just prefer not to screw with it, once I've settled into gsis and got everything working.

Vbmeta is separate from the vendor partition, at least on my devices it is. Patching the vendor fstab file to disable encryption should have no effect on vbmeta, or vice versa.

If you're going to play with modifying vbmeta, I suggest making backups of important stuff.

I've never used FolderSync, but if you mean the pro version, you must buy it. If you've paid but play store is still showing a price tag instead of an install button, that just means your purchases haven't been synced yet. Just now, I was able to install and open the free version without issues.

I haven't had login issues with Swift, yet. Did you buy the premium features? It definitely sounds like a play store/play services issue.

My only suggestions would be to manually update these 2 apps to the latest versions and try again.

Or you could uninstall their updates, the latest versions should automatically be installed, given a little time.

Also, try removing your Google account and signing in again.

So far, I've tested Swift with the combos of MicroG/play store, and official play services/play store, on 2 devices. In both scenarios, login works, as well as premium features/cloud sync.

If all that fails, and you're using the LOS gapps variant, i'd suggest a cache/data wipe (factory reset).

I really, highly doubt that vbmeta signatures have any relation at all to Google login issues. It just seems very implausible.
[Treble-Enabled Device Development A/AB ROMS] psychofaktory:
OK. I would not exchange the vbmeta for the time being if no improvements are to be expected in this case.

I was talking about the Lite version.

When I try to install from the PlayStore the installation fails.

When I try to install the APK manually, the installation can be performed, but the app will not launch afterwards.

Yes, I have purchased the premium version.

The app itself works. However, to activate the premium features, I have to enter my Google account in the app, which is not possible.

Both apps are already up to date.

Both apps have also been completely removed and reinstalled several times.

I had already tried that as well.

Yes, I am using the LOS gapps variant.

Unfortunately, I cannot use another variant, since there is no custom recovery available for the Sony Xperia 10 III.

The problem occurred right after the installation of the fresh LOS. Thus, I assume that there would be the same error after a factory reset.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
You should be able to use any LOS gsi that's compatible. You say you don't have twrp, so I'm guessing you probably used fastboot instead, to install the gsi.
[Treble-Enabled Device Development A/AB ROMS] psychofaktory:
Exactly. The installation was done via fastboot.

Since no TWRP (or other recovery) is available, there are unfortunately hardly any options to use LOS + GAPPs.

The GAPPs cannot be flashed via fastboot and installing them later, e.g. via Magisk, also had serious disadvantages in a previous test.

Thus, the GSI image of LineageOS incl. GAPPs seems to be the most reasonable choice.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
I won't buy any device unless a working root method/custom recovery are already available, it's just not worth my time or money. I also won't buy devices that are hot off the factory line and new to the market, at that point there is little or no development for them, and nothing is guaranteed in the future.

Root and custom recovery are musts to me.
[Treble-Enabled Device Development A/AB ROMS] psychofaktory:
I basically see it the same way.

However, it is difficult to find a suitable device for my requirements for which there is also custom ROM support.

What alternatives would there be for a device with (sorted by priority):

Notification LED on the front

microSD slot

display max. 6" / less than 155mm height; OLED, HDR

NFC

min 128 GB storage (min UFS 2.1)

min 4 GB RAM

fingerprint sensor

5G

For my needs, the Sony Xperia 10 III still seems to be the best possible option.

Or are there better suggestions here?
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
I can't answer with suggestions, since I'm predisposed to Samsung, most of my experience is with that. I've owned zte, huawei, and lg in the past, bad exp with all except Axon 7.

I thought LEDs were a thing of the past, do phones even still have those?

Unfortunately microsd slots are slowly going away too. While that is a must for me too, it's getting harder to find. A lot of budget devices still have them, but in flagship devices they're becoming rarer. For me there must be a minimum of 500gb internal storage, to make me OK enough to not care so much about a microsd.

Can't say I share your "smaller is better" philosophy, I love huge screens.....how TF can anyone spend half their day staring at a tiny screen? It's got to be hard on the eyes. Bigger screens strain my eyes less. I'm used to desktop PCs with massive monitors, so I'm spoiled.

NFC....could care less, I've never used it.
[Treble-Enabled Device Development A/AB ROMS] psychofaktory:
This is how the requirements differ.

I need NFC to describe NFC tags, for the online function of ID cards and for mobile payment.

Notification LEDs are actually installed less and less often. Sony is the only established manufacturer that still uses them.

Nevertheless, it is a very important feature for me.

And as for the display size:

It is important for me that the device can be operated well and safely with one hand and that it fits well in the pocket.

I've already had devices that were too big and bent in my pocket...

Yes, there is the one-hand mode. But why a large display if only a part of it is used anyway? A large device cannot be held better in one-hand mode.

Moreover, I do not have any use cases where I would need a larger display due to clarity or legibility. On the contrary, it could even be smaller.

Smaller displays also tend to consume less battery.

Basically, I am very happy with my Sony Xperia 10 III in combination with the LOS-GSI.

However, there are still the aforementioned small issues that do not work and for which I unfortunately could not find a solution yet.

I don't know if it would be better if I would use a native ROM or TWRP would be available for my device...
[Treble-Enabled Device Development A/AB ROMS] uluruman:
It seems that the problem was fixed. I hope that the changes will make into the next LOS td update.
[Treble-Enabled Device Development A/AB ROMS] atlantix1:
Sorry for the delayed reply! I just saw that the magisk module was updated in the loki kernel / gsi telegram channel.
[Treble-Enabled Device Development A/AB ROMS] psychofaktory:
Currently, I use a Sony firmware based on Android 12 on my Sony Xperia 10 III under the GSI for LOS20.

Would it be possible that the problems disappear if I perform the recently released update to Android 13, so that firmware and vendor again match the Android version of the GSI?

Does anyone know how to do a firmware update without losing the GSI and data?
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
Updating the Sony firmware on top of an already installed gsi, and without a reset? Sorry, not possible.

I suggest that you flash the stock firmware, then get back to gsis when you can. If you're going to do that, flash the modded vbmeta right after the stock firmware, just to get it over with. Then you can flash a Magisk patched boot.img. and from there, fastboot your way back to a gsi.

As for whether the problem will go away...who knows? Test and see for yourself. Unfortunately for you, this is something for which noone will be able to give you a definitive answer.

It seems like what you're really trying to say is this:

"I want to flash STOCK firmware. But I'm currently running a gsi. However, my data partition is populated with gsi-related data from my current ROM. And is most likely encrypted."

Tell me, even if you flash the stock firmware without wiping/formatting data partition, what do you think will happen when you try to boot the stock firmware. I'll tell you...A BOOTLOOP. The data of the 2 ROMs are incompatible, you can't just boot into stock with the gsi data intact. 100% guaranteed, it won't work. The current encryption, if any, is yet another barrier.

I suggest that you back up your data and just flash stock. Instead of pondering on how to flash stock without "losing" it.
[Treble-Enabled Device Development A/AB ROMS] psychofaktory:
Thanks for your assessment @AnonVendetta

The thought came to me because I had read elsewhere some time ago that the vendor security patch level could only be raised by updating firmware/vendor and that this was probably possible.

Unfortunately I could not find any info on how to proceed.

Here it is also mentioned that it is possible. But also here is not mentioned how exactly to proceed:

https://xdaforums.com/t/guide-phh-gsi-flash-aosp-12.4328891/page-3#post-85996823

Unfortunately, the people who could provide answers in the subforum of the device no longer seem to be very active.

Basically I share your opinion that it would make more sense to flash the latest Sony firmware clean and then flash the GSI together with the modded vbmeta afterwards.

My inhibition at the moment is that I have no TWRP available and both FolderSync, as well as Swift Backup and Titanium Backup do not work. So I can't easily make a clean backup and then just restore it.

Thus, it will be a significantly more complex endeavor....
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
You're rooted. How big is your data partition/internal storage? 128GB? If you have that much free space available on a PC, then you could connect via USB and make a data partition backup via adb and root access. The native Linux dd command is excellent for copying entire partitions. You would just need to get the exact location/path of your data partition. Then it's just a simple matter of mounting the partition image and extracting data from it. Preferably from a Linux based OS.

Also, it would help to know if your data partition is encrypted. Because if so, good luck getting any data from the backup image.

For now, maybe you can just use the free version of Swift and do a local backup only. Copy that to PC for safekeeping.

Instead of FolderSync, copy the folders manually. Again, store the backup on a PC.

I'm surprised to hear that titanium doesn't work. Clear the data of the app and its' addon app. Grant all permissions to both. Make sure you give it root access. And enable usb debugging in developer options. Titanium has never failed me, ever. I like Swift more, but its' explicit dependency on a Google account/play store can potentially make it unreliable when you need it to work.
[Treble-Enabled Device Development A/AB ROMS] bpham1:
I plan to try this approach with a Sony Xperia 1iii. On paper it should work, but any missteps can lead to data loss. I'm more concerned about how long it would take me to restore my working apps. So, if this method works, then it would save me lots of time.

1) Download stock firmware with XperiFirm

2) Flash with Newflasher with option to keep userdata

3) Immediately flash GSI
[Treble-Enabled Device Development A/AB ROMS] psychofaktory:
Hello bpham1,

the downtime and duration for the recovery also scare me.

I would be grateful for a report on your experience if you were able to perform the action successfully.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
I use a similar approach as what @bpham1 outlined to upgrade the stock base of most of my devices, but please only ever think of attempting it if you're sure you can enter bootloader/recovery with key combo from a hot rebooting state. Even then there's still a minute but real possibility that hot rebooting after flashing stock is different from regular hot rebooting.

For devices where I can't take such risks, I simply stick to a certain stock base until GSIs receive the next major Android update, by then I'd simply start over from a newer stock base.

Also keep close attention on the flashing progress and reboot timing to interrupt it in time, otherwise stock ROM will try to boot and (even if it boots) ruin userdata.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
Attempting this on either of my devices is tricky. Samsung disabled the ability to boot into recovery via button combos....UNLESS....you're USB connected to a PC when doing it. You absolutely have to have the cable plugged in and PC powered on while holding the relevant buttons, or it just won't work. This has been an issue since as early as Android 11. However, you can still use ADB commands or root to boot directly from Android into recovery/bootloader/download mode.

And even if the hot rebooting works, bypassing booting the stock firmware, I still have to manually flash TWRP/patched vbmeta/Magisk boot.img, since flashing stock firmware overwrites those. Flashing the firmware also re-enables encryption, so I still have to manually patch the fstab file in vendor partition, or else my data partition will re-encrypt as soon as Android tries to boot.
[Treble-Enabled Device Development A/AB ROMS] bpham1:
The method works successfully on my Sony. I don't use encryption, so your mileage may vary. Just be sure you are familiar with the Newflasher walkthrough.

I struggle with what combination to boot into fastboot. I keep forgetting not to connect the USB-C cable. Using the cable gets you into Flash mode, and without the cable gets you into Fastboot when you press and hold Volume Down button.

Good luck!
[Treble-Enabled Device Development A/AB ROMS] needmypandora:
Is bluetooth fixed in March build?
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
Was it ever broke in any of the LOS 20 builds? It's always worked fine for me.
[Treble-Enabled Device Development A/AB ROMS] Hatrackman:
Good day. Been using LineageOS version 19-20220410-UNOFFICIAL-arm64_bgs since it came out (on my Moto G Power 2021). Am aiming to upgrade to this (ideally march release... either way I don't use banks or bluetooth so not super essential... I digress).

Is there such thing as a 'dirty flash'? AKA just flashing this right on top? Or is best practice to revert to original device OS (is Android 11) and then install this from there?

PS: I'd really rather not have any encryption of my Android folder. And have not been using TWRP.

Side note: The following are rudimentary instructions I made on installing on my device (about a year ago). If there are glaring inconsistencies I'm hoping someone could point them out. I've also included a screenshot from Treble Info.

PPS: also I don't use a sim card, only wifi.
[Treble-Enabled Device Development A/AB ROMS] m0byn:
Actually, I am having the same question as well. I installed this GSI on my Samsung Tab S6 and everything works really well. However, should the split screen mentioned just work out of the box, or is it only available in ROMS specifically tailored to certein devices? I am asking since it would be indeed a very nice feature!
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Fixed and tested, will be in the next update.
[Treble-Enabled Device Development A/AB ROMS] wojtekojtek:
how to patch it to get rw system?
[Treble-Enabled Device Development A/AB ROMS] Adanaliisot:
Will this rom work on arm64_ab ? Or it work only arm64_a
[Treble-Enabled Device Development A/AB ROMS] m0byn:
That is amazing to hear! I do have 4 follow up questions though:

Here I found a tip how to fix the S-Pen showing as a mouse pointer for the Tab S4. When trying to save the edited file using TotalCommander it gives me the error EROFS (Error read only file system). Do I need Magisk or something similar to do that? Would it be maybe possible to add this line in the GSI (given it is possible and that it does not interfere with anything else...)

Apparently, the unlock with fingerprint popup is misplaced. To be specific, when unlocking an app using the fingerprint, then the circle in the popup is above (too high) the actual fingerprint sensor. I am happy to provide any details on that needed for fixing this issue!

Do you by any chance know whether the Samsung Keyboard Covers for tablets work with this GSI?

Is there any way to get the two top speakers working?
[Treble-Enabled Device Development A/AB ROMS] m0byn:
I installed LineageOS 20 TD on my Samsung Galaxy Tab S6. Everything works fine besides two issues:

There is no toggle in settings to switch on auto-brightness.

Often, but not always, when switching the tablet to standby mode (either by auto-standby, or by pressing the power button once), LineageOS seems to be restarting. To be specific, the LineageOS logo shows up and I have to reenter the code to unlock. It seems to me that it is related to having apps open while locking.

Does anyone know how to approach these issues? The auto-brightness is not such a big deal, whereas the restarting problem is more severe.

I am happy to provide any logs or additional information if necessary!

EDIT: restarting issue was related to S-Pen (see following posts) and disappeared with March updated
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
You don't patch it. Use the vndklite versions.

On the technical side of things, you could remove the shared_blocks filesystem attribute from the img. You would just need to use a tool that removes that attribute and repacks the image without it. But why go through all that effort, when using vndklite is much easier?
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
Yes.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
Same issue here regarding brightness. But it's the same for all gsis I've tried. I've heard that you would need to create an overlay to make auto brightness work. For now, I use an app called Velis to work around this. Gives you auto brightness even though it doesn't natively work in the ROM. Can get it from Play Store, or find an apk and sideload it. It does have in-app purchases for Tasker/widget functionality, but those are totally optional, the app's core functions will work regardless. And it's ad-free.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
Pen works fine for me as a mouse pointer. And in 3rd party pen apps, it works as a stylus, IN THOSE APPS. Outside of them, it will be recognized as a mouse pointer.

Pen also appears to charge fine when placed in the appropriate slot. But there's no way to know for sure what the battery level is. I intentionally used it until it stopped working, then placed it back in the slot for an hour. It worked again. So i can only logically conclude that charging works, despite not being able to prove it or check the %.
[Treble-Enabled Device Development A/AB ROMS] m0byn:
Thank you very much for this tip! Apparently, the LineageOS 20 "light" supports auto-brightness on my Galaxy A50 phone...not sure if it does not work on tablets only...

Do you have the same experiece with the restarting and standby? The second point I mention.
[Treble-Enabled Device Development A/AB ROMS] m0byn:
In principle, it is OK with the pen showing as a mouse. However, I would prefer a different symbol, if possible in any way.

In my preferred third party notes taking app, Saber Handwritten Notes, the pen shows as a mouse as well!
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
If it works on the A50, then it already has the needed overlay.

I don't have the restart/standby issues.
[Treble-Enabled Device Development A/AB ROMS] m0byn:
So, apparently it is implemented in the light version but not in the TD version.

Hm...interesting!
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
If you're sure auto brightness works in light but not TD, try comparing the overlay directories. I'm pretty sure it should be in /system/product/. Or just search system partition for "overlay" to find the right directory. See if one has APKs that the other is missing.

Then it's just a simple matter of "transplanting" the correct overlay apk. Be sure to set the right permissions/ownership and SELinux contexts.

If you're rooted and are using a vndklite img, copying the files should be trivial. If not using vndklite, you'll have to create a Magisk module that systemlessly places the file.
[Treble-Enabled Device Development A/AB ROMS] m0byn:
I'll see if i can manage that. I am pretty new to all that so cannot say for sure!
[Treble-Enabled Device Development A/AB ROMS] m0byn:
Do you know if the log protocol of lineage could help? Do you even know where to start looking for this problem?
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
If you mean logcat, probably. But you will need to submit your logs to the maintainer. I've been lucky to not have restart/standby issues. It hasn't happened on any gsi I've tried, for either of my Samsung devices. Ever since I started using gsis last year, I've liked the experience so much that I have no incentive to return to stock, besides temporarily when upgrading firmware. The very few disadvantages are far outweighed by the advantages, my experiences have been mostly positive so far. Not just with LOS, but gsis generally.
[Treble-Enabled Device Development A/AB ROMS] kevinco1:
Hello, I've had this installed on my SM-X200 for the last month.

My system says my status for DRM is L1 but when I use Netflix it's L3 in which I can only watch SD quality.

How can I get Netflix to see the system for what it is... L1?
[Treble-Enabled Device Development A/AB ROMS] Hatrackman:
Just installed lineage-20.0-20230218-UNOFFICIAL-arm64_bgN-vndklite. Only difference from 19.1 so far is that I cannot center my clock.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
You mean the status bar clock? Or some kind of clock widget? Or maybe you mean on the homescreen?
[Treble-Enabled Device Development A/AB ROMS] Hatrackman:
Forgive me. The status bar clock. Only has left and right placement options (and I'm on a moto g power (2021) with the camera in the screen which obscures the left placement).
[Treble-Enabled Device Development A/AB ROMS] Hatrackman:
PS: any way of disabling 'Trust' and removing encryption?