yashsingh1/xdaforums huggingface dataset:
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
I really honestly want to enjoy this ROM, but I just can't. It says my exfat Microsd is corrupt. I have over 350gb of files on there, it would take forever to back it all up.

Exfat is working for me in phhhusson GSIs, and also in Pixel Experience. Why it is such a big issue for LOS to work with it? This filesystem is widely accepted on Android and it has been around for a long time.

I'm not about to use adoptable storage, I just don't need it. My tablet has 500gb internal storage, it's not needed.

This is the 1st time I've tried an LOS GSI on my Tab, and I'm already a bit peeved by this.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
The big issue is I don't even know where to start. I've tried using either LOS's exFAT implementation or Relan's (used in PHH's AOSP) and nada. That's why I have the issue noted in #2 asking for help.

I also lack incentive, as most phones nowadays have abandoned SD card slots, and I haven't seen a likable Android tablet in years...
[Treble-Enabled Device Development A/AB ROMS] AltairFR:
Andy

Try to look my repo aosp, I have an implementation of extfat that works, you also have to take a patch from my patch repo
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
FYI for you all who anticipate an update around this time - Google is releasing tags in a weird schedule since Android 12, which disrupts LOS and then us downstream. This month, the latest tags are still being uploaded as of writing, so there's at least one week to go until one of them is reviewed and merged in LOS.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Updated all variants with December security patches and in sync with PHH v400.d. [Insert obligatory backup-and-test warning here]

This can be called the "I take back my words" release:

- LOS merged r18 much quicker than I expected, invalidating the post above.

- After too many queries regarding GAPPS through various channels, I've given up resisting and will build some. However, as already stated in #10, these are offered entirely at your request, as-is, without guarantees, and you'll have to help each other out on GAPPS-related/-induced issues.

One more thing - PHH introduced yet another variant called "secure", which is the same as clicking "Securize" after booting, however it's effective on first boot and therefore avoids certain data breakage. This variant is generated with sas-creator, and as long as you have a Linux PC, it's trivial work (doesn't require building environment), so for the few that might need it, do it yourself.

OP has been updated with some of the above info as necessary; SF has also been updated with a readme that better explains the naming rules of variants.
[Treble-Enabled Device Development A/AB ROMS] Avraham Tsaban:
Could you please explain the difference between vndklite and vndk variant?

(it looks like there is another difference in addition to read-write system partition)
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Uh, literally? It's for devices with a VNDKLite vendor. Treble Check will tell.
[Treble-Enabled Device Development A/AB ROMS] Avraham Tsaban:
Isn't vndklite gsi compatible with vndk device (and usable if RW system is needed)?
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
#2 already noted this.
[Treble-Enabled Device Development A/AB ROMS] ada12:
thanks for sas-creator its very usefull

Also thanks for building gapps variant for user its easy when we have only stock recovery. sadly in my country ( France ) gapps is too mutch dependant for app needed in work...
[Treble-Enabled Device Development A/AB ROMS] WazaBe162:
Hello team!

I have flashed ROM for years, since HTC Hero, and it's the first time for me flashing a GSI ROM.

I just wanted to make sure that all the steps I plan to follow are correct.

1) As I have Pixel 3, I download: lineage-19.0-20211216-UNOFFICIAL-treble_arm64_bvS-vndklite.img.xz

2) I download latest TWRP for mi Pixel 3

3) I flash and enjoy?

Thanks for confirming, is there any telegram group to discuss this ROM?
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Sounds weird to push away users, but may I interest you in a device-specific LOS, freshly out of oven yesterday? IMO Pixel users should stick to device-specific ROMs and not bother with GSIs.
[Treble-Enabled Device Development A/AB ROMS] WazaBe162:
You are definitely right, Andy.

Unfortunately, the official build is on LOS 18.1 and within the xda community, I see a lot of Android 11 and 10 ROMs and not a lot of great LOS 19 stuff.

It also seems that TWRP recovery is not supported which seems to make things more complex, but I will follow up closely the post in the Pixel 3 LOS threads

Thanks
[Treble-Enabled Device Development A/AB ROMS] mikefnz:
Working nicely on the Xiaomi Mi Pad 5 but I get the "Abnormal State" message in Magisk. Anyone know how I can remove the "other unsupported su"? My searching doesn't provide an obvious answer... TIA
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Just ignore that.
[Treble-Enabled Device Development A/AB ROMS] Avraham Tsaban:
Anyway, GSI ROMs are discussed on Telegram here: @phhtreble
[Treble-Enabled Device Development A/AB ROMS] herplyderply:
Which version did you put on your CMR-W09 and are you still using it? How has it been?
[Treble-Enabled Device Development A/AB ROMS] Toprak123:
I currently have Redmi Note 9 and if anybody is interested in this device's current state with this gsi here are the problems:

1. This gsi doesn't pass safety net. It keeps giving me notifications about this device being not certificated.

2. There are stutters here and there but that is probably because system was busy spamming me with notifications. It is not as good as Android 11 gsi's though.

3. Brightness slider doesn't work correctly but this has a workaround.

Other than these problems, if this gsi gets stable it will be a joy for me to use it but at this state (i can use the system with small stutters but safetynet problem makes the experience way worse.) the gsi is not usable.
[Treble-Enabled Device Development A/AB ROMS] birdibird:
If you have TRWP, mount system, go to the file manager and delete su in the /system/system/xbin folder (you will need the vndklite version or remount system as rw)
[Treble-Enabled Device Development A/AB ROMS] mikefnz:
No TWRP but as Andy suggested, I'm just ignoring it :)
[Treble-Enabled Device Development A/AB ROMS] karlkluwe001:
still using it - works fine, not using finger sensor ; better battery life, use the December sec. update
[Treble-Enabled Device Development A/AB ROMS] birdibird:
haha, yes. If you have the vndklite version you can also delete the file with a root file manager..
[Treble-Enabled Device Development A/AB ROMS] mishak750:
i cant add my google account on microg (signature spoofing installed). In aosp 12 phh account can be added. what i do wrong? (motorola defy 2021 snap 662).
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
I see. It's strange that exfat works in all the AOSP roms I've tried, but not LOS. And yet you say that you've tried AOSP's implementation but it doesn't work. Weird, honestly.

At its' core, LOS is directly based on AOSP, but with other stuff added in. Barebones AOSP is where most if not all Android firmwares derive from.

Fat32 isn't ideal for MicroSDs that are over 32gb, and are thus classified as SDXC rather than SDHC (32gb or less=SDHC). OSes like windows will complain if it detects a Microsd over 32gb that is using FAT32. And it won't even let you format it as fat32 if that's the case. Being able to share the card with my PC OSes is important to me, so adoptable storage isn't a good solution either.

Exfat has worked for me on LOS in the past, but not on this GSI/device.

On the upside, I tried formatting a spare Microsd as both ext4 and f2fs. Your LOS reads those just fine. But those are permissioned Linux filesystems, and also aren't ideal to be used as portable storage on a Microsd.

It may not be important to you, but there are plenty of devices out there that still have a card slot. If you ever find a solution, it would benefit many. With 500gb internal storage, I only use my Microsd for backup purposes, and internal for apps and their data. Like if I have to format the data partition, I lose everything in internal storage.

I'll sniff around out there and see if I can't dig up a solution, or at least a lead you can try. I'm no bona fide dev, but I do have a nose for finding info.

I'm actually amazed at how well the Tab S7+ runs GSIs. I've heard that the newer model Tab S8 runs them well too. Maybe give them a look if you're looking for a big screen device.

Either way, thanks for your work. I'm just trying LOS right now, I haven't settled on any GSI in particular. And I'm just as likely to return to a non LOS AOSP ROM. But I'll gladly test and report as long as I'm using this.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
Really? Cool, man. I hope that patch works, if Andy is willing to merge it.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Noted, thanks, I'll contact you in TG about it if I need further info.

Actually, quite the opposite, I'm looking for a small but decently-specced Android tablet.

After several years of Android ignoring this niche, I've given up and got an iPad mini 6 when it came out last year. But that's off-topic here.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Right now, for people who don't want built-in SU, I make post-processed "secure" builds. During post-processing they lose EXT4 shared blocks and therefore become a lot larger (~1.7GB -> ~2.5GB). I wonder if any of you have really small, non-dynamic (i.e. can't be resized) /system that can actually benefit from a "natively" no-SU build, e.g. *N? I've experimented with "securizing" at build time with success, so I'm ready to build such.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
@AnonVendetta I just got to check up on the exfat situation, with 2 devices I have that still has an SD slot (one Lenovo P vendor, one Motorola R vendor), and you know what, a freshly formatted exfat card just works in them. And it works on LOS20 "light" too, where I didn't even touch vold. Honestly sounds like another Samsung shenanigan. I'll have to look further...
[Treble-Enabled Device Development A/AB ROMS] AltairFR:
With or without my patches ?
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Tested without - just PHH's vold patches + LOS's exfatprogs.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
And in attempting to try it on a 3rd device (a Samsung), its card tray somehow got stuck, likely needing a disassembly, rendering it half-useless.

Sorry @AnonVendetta , but now I neither have a suitable device for, nor am in the mood to debug exfat on Samsung.

I now hate Samsung even more...
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
Hmm....shared blocks removed, sounds good to me. I prefer to have direct write access to partitions like system/vendor. The filesystem would be bigger, but that's a tradeoff I'm willing to make. Which is why I only use vndklite GSIs.

I've never much cared for passing SN, so in practice secure builds are useless to me. But more and more apps are checking it, so if it can be passed with little effort then that's a plus. I've tried securizing a few GSIs in the past, but they softbricked, and even a formatted data/wiped cache wouldn't make them boot again.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
Freshly formatted with what tool? Android's built in formatter? Windows? Linux? TWRP?
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
I'd be willing to test for you. That's only logical, since I and some others would benefit if a solution were found. I don't see why it doesn't work on Samsung, I'm using an Android 12 vendor. And exfat works on the stock firmware out of the box. Of course, that kind of goes out the window once you replace the stock system with a GSI, but vendor is still the same.

@AltairFR offered you the patch, yet you're not willing to try it. That's your choice, if you don't have the time or whatever. If you're willing to give up so soon, then there's no point in me trying to convince you. But when I'm faced with a problem, I like to try as many solutions as possible. Instead of just throwing up my hands in despair, while knowing there's a potential solution that I never tried. As long as that's the case, there would be a nagging thought and I just can't rest.

exfat also doesn't work for me in Corvus OS, which is based on Phh aosp sources. I'm starting to think s/he is using some LOS sources though. So far, it has worked in every GSI except Corvus and your builds. So in the future, I guess I'll just have to actively avoid any GSIs that are using your LOS source. Spending several hours copying my content to PC, formatting the card, and then putting it all back is downtime to me.
[Treble-Enabled Device Development A/AB ROMS] jinxt:
Thanks for the suggestion. similar story for me. I couldn't flash any other gapps on lenovo tablet, getting either unsupported device or not enough free space. Only bitgapps worked after treble gsi rom install
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Windows.

Technically yes, however I prefer hands-on debugging whenever I can, to the point I shelled out ~$600 for a suitable device for another ongoing issue. In the case here though, I'll defer the whole thing to at least after I pop the tray open again.

It could be Samsung uses sdfat and, although PHH has a patch for it, LOS's impl needs more work.

Don't jump to conclusions. Replacing LOS's impl with relan's was the first thing I did a few years ago, and it didn't work back then, hence I wrote down #2. And now, I didn't even get to try it again - I was confirming the status quo when the stuck card tray happened, and now the card is inside the device in some sort of bad contact state that even when flashed back to stock it no longer shows up.

Now, hear me out. You were upset about no exfat, I heard it but chose to ignore it at first, that's my bad. Then you voiced it more clearly (not just in this thread but also in other ROMs'), I heard it, thought about it from time to time while I worked a day job and prioritized an A13 release. Now I finally started looking into it after a day's work, and right as I was about to discover something, I broke one of my devices to probably beyond my own repair skills. Now I'm the one who's upset, and you don't seem to get me this time.

I understand that as a user-facing release I'm bound to face user issues that I myself will never encounter, however this is the first time I felt so pushed to resolve one...

And finally,

I'm not affiliated to the LOS team. But yes, other ROMs can still be based on LOS or use components from it. Given that exfat support is of paramount importance to you, just stick to one you tried and know working.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
I tried formatting through several different tools, and several OSes, including the rom's built in formatter. And guess what? It (rom's formatter) stupidly chooses to format as exfat, and yet in the next moment says it's corrupt. Both your GSI and corvus do that. They refuse to accept the very filesystem that they themselves have created! That's just retarded!

Sorry, I meant to say that Samsung stock firmware reads exfat just fine. And also has no issues creating/formatting it. Was a typo on my part.

For now, I'm moving on. For every 10 GSIs I can try, I'd say around 8 of those 10 will read exfat fine. Yours and Corvus are quite simply in the minority on this. And because you have pretty much stated that you don't care if it works, then I have no reason to believe that you'll put a sincere effort into this. After all, why bother, when you yourself have said that you don't care about MicroSDs? I know I wouldn't put effort into fixing something I don't care about.

On the other hand, you've said exfat works for your other devices. So there's (from your POV) nothing to fix. You have pretty much blamed this on Samsung. Yet that still doesn't account for the fact that the stock ROM supports exfat, and so does almost every other GSI I've tried. Honestly, I'm more tempted to think something in LOS is to blame. Not you personally, but something in your sources.

Since I have enough other GSI options available that are very good, there is (and never was) a compelling reason for me to use LOS. I was never committed to it, just trying it out. And because of this problem, I became unmotivated to keep it after the end of the 2nd day.

In the future, I may test for you again, but there has to be something substantive to test before I can be bothered to wipe out a perfectly good ROM on a whim. It doesn't really matter at this point, since I'm no longer considering LOS as my daily driver ROM.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
As long as you acknowledge this, or at least a possibility of it - that I didn't do anything on my end to deter exfat - I think we have an understanding.

I'll get my Samsung fixed somehow, and if/when I ping you again about it some time in the future, it'll be after I make sure exfat works on it.

Supposedly DSU Sideloader will allow you to "live" test other images without touching the installed one. I've even heard that while it doesn't work on stock Samsung, it does on GSIs, which sounds perfect for your usecase. Not saying that you should try LOS/-based again (I know you're reluctant by now), but offering this as a general tip.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
I know you wouldn't deter it. It's a common enough FS on Android, sooner or later someone like me would post about it. Although with the increasing prevalence of devices that are omitting a Microsd slot, it may not matter much in a few yrs time, except for older legacy devices that are running custom GSIs like yours. You think of Microsd as outdated and slow. I think of it as an option to store backup copies of files I'd rather not lose. If the internal storage is encrypted and I have to reset for whatever reason *AND* can't boot into android, I just lost access to all my files on internal storage. And it can fail, like any storage medium. SSDs, HDDs, MicroSDs die all the time. That's why I don't trust internal storage as my sole storage option. And nor do I trust cloud providers for my backups.

I know about dsu Sideloader, but I don't like that it's limited to one secondary ROM. To me it's not a true multiboot solution. As soon as I want to try another gsi, I have to wipe out the one I had previously. I recognize that this is a Google limitation, and outside the control of that app's dev. I'd love to see someone port EFIDroid or Dual Boot Patcher to modern devices running modern Android versions. Those are far superior to dsu in most ways.
[Treble-Enabled Device Development A/AB ROMS] tosiaczus:
Hello. I have black screen, it is broken.

ADB on booted system says that adb is unauthorized.

I have only access via recvoery ADB.

Where can I set to enable by default MTP?

In which one of the starting script can i use to put pubkey for ADB?

echo "key" > /data/misc/adb/adb_keys

I tried to put this command to:

/system_root/system/bin/phh-on-data.sh

but it does not work.

There is my actual settings:
[Treble-Enabled Device Development A/AB ROMS] nisfta:
I can say that DSU sideloader works fine on stock Samsung
[Treble-Enabled Device Development A/AB ROMS] WalterCool:
It is possible to build as user instead of userdebug?

I kinda don't like to make my device too open. SELinux matters.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
LineageOS official also ships userdebug though?
[Treble-Enabled Device Development A/AB ROMS] WalterCool:
I been doing my own Galaxy S10 LineageOS builds (Linux4 maintainer) with "user", it works fine.

Now, every LineageOS is different, some of them remove SELinux to avoid breakage with certain modules, specially old devices.

Will make some tests with "user" build by disabling SELINUX_IGNORE_NEVERALLOWS and let you know.
[Treble-Enabled Device Development A/AB ROMS] WalterCool:
OK, seems like the issue is related to Mediatek, who requires SELinux.

FAILED: out/target/product/phhgsi_arm64_ab/obj/FAKE/sepolicy_neverallows_intermediates/sepolicy_neverallows
/bin/bash -c "(ASAN_OPTIONS=detect_leaks=0 out/host/linux-x86/bin/checkpolicy -M -c 30 -o out/target/product/phhgsi_arm64_ab/obj/FAKE/sepolicy_neverallows_intermediates/sepolicy_neverallows.tmp out/target/product/phhgsi_arm64_ab/obj/FAKE/sepolicy_neverallows_intermediates/policy.conf ) && (out/host/linux-x86/bin/sepolicy-analyze out/target/product/phhgsi_arm64_ab/obj/FAKE/sepolicy_neverallows_intermediates/sepolicy_neverallows.tmp neverallow -w -f out/target/product/phhgsi_arm64_ab/obj/FAKE/sepolicy_neverallows_intermediates/policy_2.conf || ( echo \"\" 1>&2; echo \"sepolicy-analyze failed. This is most likely due to the use\" 1>&2; echo \"of an expanded attribute in a neverallow assertion. Please fix\" 1>&2; echo \"the policy.\" 1>&2; exit 1 ) ) && (touch out/target/product/phhgsi_arm64_ab/obj/FAKE/sepolicy_neverallows_intermediates/sepolicy_neverallows.tmp ) && (mv out/target/product/phhgsi_arm64_ab/obj/FAKE/sepolicy_neverallows_intermediates/sepolicy_neverallows.tmp out/target/product/phhgsi_arm64_ab/obj/FAKE/sepolicy_neverallows_intermediates/sepolicy_neverallows )"
device/phh/treble/sepolicy/mediatek.te:2:ERROR 'Duplicate declaration of type' at token ';' on line 69574:
type hal_graphics_allocator_default, domain;
#line 1 "device/phh/treble/sepolicy/mediatek.te"
checkpolicy: error(s) encountered while parsing configuration

That's the reason.
[Treble-Enabled Device Development A/AB ROMS] hdfgdfhsg:
works on galaxy a10s

magisk doesnt work on stock os android 12 but it does in lineage android 12

Edit: alot of apps crash and doesnt get detected in adb

Edit 2: Backup your system in twrp or you can't go back!
[Treble-Enabled Device Development A/AB ROMS] WalterCool:
Can confirm it works pretty good at Xperia 5 IV. All cameras work fine, fingerprint works great.

UI may be laggy at start, you may need to configure FPS manually and will work nice. Once you configure this once, you can leave it at default again if needed.
[Treble-Enabled Device Development A/AB ROMS] psychofaktory:
What are the steps to update Lineage-GSI / Sony-Fimware when Magisk is installed?
[Treble-Enabled Device Development A/AB ROMS] WalterCool:
No idea. I do not use Magisk.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Updated all variants with November security patches and in sync with PHH v416. [Insert obligatory backup-and-test warning here]

Now building vN/gN natively, and they're "integrally securized". Also, on LOS20 there were 2 reports of *N killing USB Debugging altogether, which I wasn't able to replicate. I've made test builds for them that stops securing the USB bits, but they weren't able to confirm for me. Therefore, I've applied the same to this batch of LOS19, in hopes of finding out. Even though I'm not well-suited to deal with GAPPS/SN issues, let me know nonetheless if you hit regressions.
[Treble-Enabled Device Development A/AB ROMS] vassiliszacharis:
A question please, I can't find bgs.img on Andy Yan leaneage OS 19 and 20 please help, that was the only one that worked on my Lenovo tablet 🥺 was it substituted with another one? Andy Yan can you upload them again please, 🙏 both GSI bgs.img, leaneage 19 and leaneage 20...I would be very grateful
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Use gN (or its vndklite sub-variant). gS is quite meaningless as PHH-SU is bound to interfere with GAPPS.
[Treble-Enabled Device Development A/AB ROMS] vassiliszacharis:
I did installed BGN leaneage 20 on Lenovo tablet X606F and works like charm... The only negative that I have noticed tablet is not charging while it is powered off...
[Treble-Enabled Device Development A/AB ROMS] MarcoP.A.:
I Isaac,you have to unrar/unzip the .IMG.xz , than became the .IMG you need to install.