yashsingh1/xdaforums huggingface dataset:
[Treble-Enabled Device Development A/AB ROMS] usmantahir:
Has anyone with an HTC U11+ managed to get this rom running?
[Treble-Enabled Device Development A/AB ROMS] harvey186:
On my Mi Max3 nitrogen no camera is working. Any idea how I can resolve that issue ?

Can't find anything. could you point me to the section please ?
[Treble-Enabled Device Development A/AB ROMS] woofwoof75:
Congratulations on your graduation!
[Treble-Enabled Device Development A/AB ROMS] iner7:
At Lineage OS 17.1 GSI not work BlueTooth icon in navbar

Hi!

My device: Xiaomi Redmi Go (8 GB)

ARM 32-bit, A-only

Lineage OS 17

If BlueTooth is turned on, icon of Bluetooth is not show in navigation bar.

How to fix??
[Treble-Enabled Device Development A/AB ROMS] WalterCool:
Hi everyone

There is some step for Samsung devices to run this build? I tried installing it for my Samsung S4 Tab (arm64-A) and I only got bootloop. Also tried arm64-AB just in case but same result Those are my current steps:

- Download the build / Make the build (tried both)

- Install TWRP on my device (recovery replaced)

- Inside TWRP, install image as System.

- Wipe Data + Factory Reset

Do someone knows if for Samsung devices should I do any extra step (clear vbmeta, remove encryption, other?). Also tried this with Lineage 16 version, but same problem.

Thanks!
[Treble-Enabled Device Development A/AB ROMS] Magendanz:
Has anyone been able to get LiveDisplay working with this GSI ROM? On my SM-T510, changing the Display Mode has no effect, and the ADVANCED settings group is completely blank.
[Treble-Enabled Device Development A/AB ROMS] petruvsvetr:
Hello, using this gsi on my max 3 and camera is working fine with default app, though I had to reboot the device a few times since flashing cuz camera froze. Using build from 20200607.

Did you flash the zip with fixes for max 3 gsis from the thread over in the max 3 section here on xda?
[Treble-Enabled Device Development A/AB ROMS] alvinprimo:
Congrats for your graduation, and thanks for the update smooth as before..
[Treble-Enabled Device Development A/AB ROMS] veekay:
Have you already tried getting with phhusson to see why exfat doesn't work on these builds, yet works fine on his?
[Treble-Enabled Device Development A/AB ROMS] harvey186:
No, don't know about this fixes.

Can't find the fixes. Could you please point me to the section ? Thx
[Treble-Enabled Device Development A/AB ROMS] Spaceminer:
Last time I checked it worked for me. I have a Moto G7 Play. I know previously it was selinux issue. Setting it to permissive and remounting should get it to show up though. What device are you rocking?
[Treble-Enabled Device Development A/AB ROMS] veekay:
Samsung Tab S4
[Treble-Enabled Device Development A/AB ROMS] Spaceminer:
I took a look through Phh's GitHub. It seems that you can fix it by copying /system/bin/vold from his GSI over to whatever GSI you're running. It appears to work for the note 10, so I'd imagine it works on most if not all Sammy devices. Let me know if it fixes it. You can convert a GSI to a raw image using my binaries from the treble discussion section. I'll link it if you need me to. There's instructions on how to mount a raw image on device in that thread as well. It'll avoid needing to flash anything. [MENTION=4467696]AndyYan[/MENTION] might want to check this out.

Here's where I found that.

https://github.com/phhusson/treble_experimentations/issues/1250

Please let us know if it works!
[Treble-Enabled Device Development A/AB ROMS] veekay:
Copying over vold makes the tablet take about 5 minutes to boot and then it immediately restarts as soon as Android starts up.

I did this via TWRP file explorer (flashed phh gsi and copied the file and then flashed this), so I'm not sure if that is the correct method.

I did also try making sure permissive was enabled (https://www.xda-developers.com/selinux-switch-toggle-permissive/), but no change.
[Treble-Enabled Device Development A/AB ROMS] WalterCool:
Just a question, does someone faced an issue with a Samsung device and lockscreen?

After installing, mostly everything works for my S4 Tab (understanding minor issues), but can't set a password on it. Each time I set some security, I got a "java.security.InvalidKeyException: Keystore operation failed", and after reboot password is always incorrect.

Some lines above the mentioned exception, shows this particular line: "keymaster_swd: keymaster_swd [ERR] (tz_check_oem:28) Device is compromized: fuse loc=5,status=0,sw_fuse_blown=1", is this okay?

Thanks!
[Treble-Enabled Device Development A/AB ROMS] cRaZy-bisCuiT:
Thank you very much [MENTION=4467696]AndyYan[/MENTION]! Would it be possible for you to make builds with MircroG which have feature parity to LineageOS for MicroG (so basically an unofficial LOS MicroG build)? :)
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
The builds already include signature spoofing patch from MicroG, just not MG itself (which can be simply installed I heard). Keeping the experience close to vanilla LOS.
[Treble-Enabled Device Development A/AB ROMS] starbright_:
Can you tell me what to patch (maybe a link to it)? I have a non-GSI LOS ROM for my device where I would like to add it.
[Treble-Enabled Device Development A/AB ROMS] tchmit:
Hi, I have problems with the GPS wakelock, once started it does not stop until I restart the device so it never goes into deep sleep

Any solution ?, this happens to me with all ROMs, Lineage, AOSP, HAVOC, CAOS, etc.

Everything else works perfectly, I have a Blackview BV5800 PRO
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
See OP.

See #2 for reporting bugs common to PHH-based GSIs.
[Treble-Enabled Device Development A/AB ROMS] neeraj797:
Query

Does it supports volte?
[Treble-Enabled Device Development A/AB ROMS] harvey186:
[MENTION=4467696]AndyYan[/MENTION]

Since over a week I'm trying to build this rom. But it always fails at 78% with this error:

system/bt/stack/btm/btm_acl.cc:1211:6: error: function-like macro 'BtmBypassExtraAclSetup' is not defined

#if (BTM_BYPASS_EXTRA_ACL_SETUP == FALSE)

device/phh/treble/bluetooth/bdroid_buildcfg.h:52:36: note: expanded from macro 'BTM_BYPASS_EXTRA_ACL_SETUP'

#define BTM_BYPASS_EXTRA_ACL_SETUP BtmBypassExtraAclSet

When using the /system/bt sources from PHH, my build finished, but it stucks at boot. It's booting direct to fastboot.

Could you pls check ? It seems that your last build is from August 08. There the sources where also working for me. But now it's failing

I'm using the way you have posted here https://github.com/AndyCGYan/treble_build_los

thx
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
I've made a build just fine without touching anything on my side.
[Treble-Enabled Device Development A/AB ROMS] harvey186:
Oh wow, 110 minutes? Cool, I need on my 2011 iMac 11hours for 1 GSI.

And sorry, I'm totally dumb. I have forgotten to clone the treble_experimantations. I could shoot myself.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
My laptop isn't exceptionally fast either, esp. compared to the lab PC. Turn on ccache or don't clean for much faster subsequent builds.
[Treble-Enabled Device Development A/AB ROMS] PoochyX:
So basically smali patcher is not needed

([emoji88]Caos GSI[emoji88])

---------- Post added at 09:19 AM ---------- Previous post was at 09:15 AM ----------

Andy Yan I really like your bulids is just with my device magisk is buggy with your patches (Moto G7 Play) apps like titanium backup and 3C toolbox don't receive root permissions and modules act up (don't appear in my downloaded modules menu) when I use other GSIs I don't have these issue's with magisk however others have replied good experience of functional magisk with your bulids any idea what this could be

([emoji88]Caos GSI[emoji88])
[Treble-Enabled Device Development A/AB ROMS] Spaceminer:
Did you set permissions on vold to 0755?
[Treble-Enabled Device Development A/AB ROMS] veekay:
I did. Things might just not work when done that way, since restoring the original file does the same thing. No ADB once booted though, so can't do it from within the OS.

For the heck of it, tried even using the vold from the official Samsung image, same thing. A few minutes of black screen on the bootloader, lineage boots up for a split second and then restarts the process.
[Treble-Enabled Device Development A/AB ROMS] PredatorCorp:
I have some problem with rounded corners

anyway to change the corners sizes?
[Treble-Enabled Device Development A/AB ROMS] eremitein:
try Phh settings > misc > display
[Treble-Enabled Device Development A/AB ROMS] gerber.19:
Hello developer

I installed it on cubot P20 cubot.net/Smartphones/p20/21

very nice work for lineageos. Thank you

instructions:

Download arm64 (not binder) from

xz -d lineage-17.1-20200808-UNOFFICIAL-treble_arm64_avN.img.xz

$ adb reboot bootloader

$ fastboot devices

$ fastboot flashing unlock

fastboot erase system

fastboot flash system lineage-17.1-20200808-UNOFFICIAL-treble_arm64_avN.img

Very likely the complete 64GB space is NOT recognised.

Reboot to recovery using

adb reboot recovery

or

Shutdown phone. Press and hold Volume UP and power

In the recovery menu:

Wipe cache partition

Wipe data/factory reset

Restart phone

Thank you very. all things working (now).
[Treble-Enabled Device Development A/AB ROMS] MerlinTop1:
Has anyone tried it on Redmi note 9/Redmi 10x 4g(Merlin)??
[Treble-Enabled Device Development A/AB ROMS] arko7123:
mi 10 lite 5g bootloop into twrp, Quack Phh works
[Treble-Enabled Device Development A/AB ROMS] carlosic961@gmail.com:
Booted in a Moto g6 Ali works fine keep updating
[Treble-Enabled Device Development A/AB ROMS] flotus1:
This may be a stupid question.

Is it possible to encrypt data after install this rom?

I installed on my redmi 7a. When I look at Settings -> Security it says it's encrypted, but when I go in TWRP, I can browse all files without typyng any password. I tried to format DATA, wipe system, dalvik cache, but no success, still detected as encrypted. Sorry about my poor english.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
In your state it's encrypted with a default password. Set a lockscreen password to have it "actually encrypted" (in our mindset). Whether your TWRP would be able to handle this encryption is another thing.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Recently I've been getting pings about building with PHH-SU integrated - the reason as I see it is mainly more devices are released with Android 10, and Magisk and GSI don't seem to play well together on many such devices. I understand your needs (I build bvS privately for my A51 5G actually), but at the same time I still want to keep the experience clean and the download page less cluttered. I've opened a poll embedded in this thread to collect your thoughts. Do note that I won't necessarily end up going the way that gets the highest votes :P

Ultimately I'd say blame LOS, they just abandoned their own system-based, trusty and non-intrusive SU like that...
[Treble-Enabled Device Development A/AB ROMS] brackenhill_mob:
Yes please. I have an Honor 6X which refuses to boot any GSi since March with any version of Magisk
[Treble-Enabled Device Development A/AB ROMS] theincognito:
Glad you did it, after that discussion in the group! :D
[Treble-Enabled Device Development A/AB ROMS] pastorbob62:
I cannot seem to get open gapps installed. I have the correct version of both Lineage 17 and opengapps, but no matter how I do it I always get error 64 and the gapps install aborts. I have gone completely through installing everything without trying to install gapps and it works great. But no luck getting gapps.

I am on a Samsung Tab S4 T813.
[Treble-Enabled Device Development A/AB ROMS] imabdul:
Magisk

Modified magisk not working with this gsi image nor default magisk is working. Otherwise rom is working good on emui 8 devices.
[Treble-Enabled Device Development A/AB ROMS] Yepi69:
Any ideas on how to install it on my Alcatel 1S 2019? I assume its the same device as yours, any special installation or just a regular one like on the first post?

Thanks
[Treble-Enabled Device Development A/AB ROMS] Wattsensi:
I struggled with the same problem for months, turns out Android 10 doesn't work with Magisk on EMUI 8 devices. I'd appreciate a phh-su build.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
After buying another Android 10 device and once again getting Magisk incompatibility, I've made up my mind - I'll be building *vS (PHH-SU) exclusively from now on. It won't come with the SU app out of the box (just install it), so the experience should stay the same - shell-only root if you don't install the SU app, full root if you do, and you can still install Magisk on top on devices that could use it. I reckon this is the solution most would like to see.

Do note that Substratum (even its fallback root mode) doesn't seem to work on PHH-SU.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Updated all variants with September security patches. [Insert obligatory backup-and-test warning here]

As stated in the last post, all archs are now *vS, meaning they come shell-rooted with PHH-SU. For full root, install the accompanying app and you'll be good to go.

As for Android 11, PHH outed his first test build only hours ago (hit the TG group if you want to test), and LOS upstream will take their time to port stuff, so it's still a bit too early to talk about it.
[Treble-Enabled Device Development A/AB ROMS] Matty1993:
Hey mate,

I think its great youve decided to add phh-su by default been having major trouble with magisk not working on GSI's

Anyhow getting 404 page not found when trying to download the phh-su app from the link provided not to sure if your aware.

Keep up the fantastic work anyhow currently running your lineage 17.1 on Konka SP3 sporting MT6580 with 1G ram and oreo GO vendor runs beautifully even without debug.sf.latch_unisgnaled=1

Cheers
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Fixed, thanks.
[Treble-Enabled Device Development A/AB ROMS] klausb65:
Is this build working on a Doogree x95 phone? Currently there is Android 10 go Edition installed.
[Treble-Enabled Device Development A/AB ROMS] Gomeman:
THANKS FOR THE GSI

Tryed this GSI latest build but couldnt get root.

Since AOSP quake by default has built in root and version manager 1.0.3.3 apk , i tryed to install both, Phhs superuser a-only.zip and version 1.0.3.3.

I removed phh-supersu and Installed modified Magisk PHH 20.3 and magisk-manager 7.5.1.apk . Got Root.

Like all other GSI if i try to install anything that it is not PHH , it gets in to a stuck boot animation.

The manager asks to update , but it will get stuck.

To pass safetynet , by default fails both tests. Just like QUAKE

Still the best GSI for A-only ARM64 is HAVOC 3.8 GSI. Easyer even to pass safetynet.

Since by default it passes basic integrity test . Only have to install modules and do some teminal root stuff. Since phone is not on the list i have to choose Google pixel 3. And there you go , pass CTS profile.

CAOS GSI is ok aswell

All GSI in comun has that fingerprint sensor doesnt work.

Can someone tell me what files would be needed from STOCK rom or even AOSP 9(working) to copy them to IMG. to get fingerprint sensor working? please

thx

Pd: Still 404 page.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
One more thing: I've mentioned a "private" build that I use on my own devices, and having shared that with a few users who are interested and getting positive response, I'm opening one up for you to experiment - download for 64B here. You should be able to switch between public/private builds without wiping anything.

Notable features are Lollipop-style lockscreen, vertical card recents, 3-position multi window size adjustment in landscape, and (most recently) forcing all apps to render into the cutout zone in landscape (i.e. no letterboxing).

The reason I've been keeping this private all this time is they're mostly adjustments I made to sweeten my daily usage, and aren't to everyone's liking, so the builds themselves will remain private in the future. However, I'm thinking of making the changes public, so others can take what they need from me, and that's why I'm here to collect some more response.
[Treble-Enabled Device Development A/AB ROMS] ariadnejro:
I've tried your private build but I can't see any differences, for example the recent apps are displayed in the same way. Are you sure that you have uploaded the right file?

Anyway, thank you for your builds. They are working great in my Alldocube X Neo tablet.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Installing it on top of an existing installation probably kept your recents style preference, but if you don't use Android 10 gestures it should show up. Other features should be pretty obvious, esp. the lockscreen (which was most controversial).
[Treble-Enabled Device Development A/AB ROMS] ariadnejro:
Yes, I am using Android 10 gestures and if I freeze Trebuchet gestures get disabled in Nova. For me gestures are a must. May I still get your vertical card recents?
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
No, these don't go together unfortunately. I'm a stubborn supporter of 3-key navbar myself.
[Treble-Enabled Device Development A/AB ROMS] ariadnejro:
Thank you, with a physical keyboard attached I can use the vertical card recents pressing Alt-Tab.
[Treble-Enabled Device Development A/AB ROMS] franco619:
apparently root causes pubg to close without any error message, securize doesn't work, does anyone know if there is another way to unroot?
[Treble-Enabled Device Development A/AB ROMS] knoelli:
I compared the new bvS build with the previous bvN build and found the following additional files and symlinks that are related to root:

/bin/phh-su

/etc/init/su.rc

/system/bin/phh-su

/system/etc/init/su.rc

Deleting those files should unroot the rom. However, I hadn't yet time to test this.

Another change that I found might or might not be related to root, maybe AndyYan can clarify things here?!

The change is in one of the SELinux configuration files: /etc/selinux/plat_seapp_contexts

previous rom without root had:

...
user=_isolated domain=isolated_app levelFrom=all
user=_app seinfo=app_zygote domain=app_zygote levelFrom=all
...

the new rom contains:

...
user=_isolated domain=isolated_app levelFrom=user
user=_app seinfo=app_zygote domain=app_zygote levelFrom=user
...

I'm not sure if this is root related or if this change is coming from upstream Lineage update or a new patch.
[Treble-Enabled Device Development A/AB ROMS] franco619:
everything works perfect only I can't play games because they close without showing errors with aosp the same thing happens maybe it's my device
[Treble-Enabled Device Development A/AB ROMS] faiizaah:
September build (latest version) give me both false on cts and basic integrity on my Cepheus (Mi 9 ). It didn't happen on August build. Its not sure because off inbuild root maybe....??
[Treble-Enabled Device Development A/AB ROMS] janhammer504:
Hi,

does the Inscreen Fingerprint (FOD) work in the latest build ?
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Regarding compatibility of PHH-SU with Play and such (including "securize" / a way to properly unroot), since I don't use GAPPS at all, I can't be of help here. If you couldn't figure it out on your own after all, join the PHH Treble Telegram group for help from members there.
[Treble-Enabled Device Development A/AB ROMS] janhammer504:
Please, is the inscreen fingerprint (FOD) working for Mi 9 ??? I heard that the default AOSP xiaomi FOD was replaced by the one from LOS !
[Treble-Enabled Device Development A/AB ROMS] faiizaah:
Work in August build. On latest didn't try it
[Treble-Enabled Device Development A/AB ROMS] janhammer504:
Thanks a lot ! :)
[Treble-Enabled Device Development A/AB ROMS] faiizaah:
Now , I can pass safetynet check after flash magisk and remove phh su ( by tap securize on phh treble setting) . Thank for the advice sir... ?

I can confirm that fod work on latest build.... (Get maximum brightness when enroll fp ☹️)
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
New 64B build uploaded - the only change is that it supposedly fixes boot on recent Mi devices (Mi 10 / Lite, K30 / Pro, etc.). Thanks to [MENTION=5351691]PeterCxy[/MENTION] for the original change and [MENTION=8281637]eremitein[/MENTION] for tracking down and finally figuring out!
[Treble-Enabled Device Development A/AB ROMS] klausb65:
What version is the correct one for a Doogee X95 phone?
[Treble-Enabled Device Development A/AB ROMS] koyo:
The built in phh superuser breaks magisk. I can't use Titanium Backup
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
What's the exact problem? Force close? No SU detected? As usual try PHH AOSP as well.
[Treble-Enabled Device Development A/AB ROMS] veekay:
I'm not sure if this is the same issue or not, but does this cause the left side of the screen to only display black when using any of the apps or even settings?

Portrait is fine, but in landscape mode I lose maybe 5% of the screen
[Treble-Enabled Device Development A/AB ROMS] cmglng:
I came from phh AOSP ROM. Been using LOS for the last couple of days and just found out that in call audio doesnt work on my device. Redmi 8A. No gapps installed.
[Treble-Enabled Device Development A/AB ROMS] ariadnejro:
Hi Andy, I've found an issue with my device and maybe you can help me. I can't connect a bluetooth headset because the bluetooth connection switches off and on continuously and the Bluetooth app crashes. I've tried two different headsets with the same result. I can pair and use other bluetooth devices like a mouse and a gamepad.
[Treble-Enabled Device Development A/AB ROMS] landsome:
Same problem in both AOSP (gapps, vanilla, go) and LOS on my Cubot KingKong Mini, with or without gapps installed.
[Treble-Enabled Device Development A/AB ROMS] cmglng:
Well I went back to AOSP phh and it was working. Im using BlissROM GSI (LOS based) now and its also working. Still observing it just in case I lose the in call audio functionality again.
[Treble-Enabled Device Development A/AB ROMS] ExqlVR:
This rom works great! I am using a Samsung A10s (A107M) and it works flawless. But how can I install gapps with Twrp (there is no Twrp for A107M) ? Can I install magisk?

Thank you. :)
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Sounds like letterboxing, a normal notch/cutout behaviour. If you don't like it and you have a 64B device, try the private build I posted a while ago, where I forcefully killed letterboxing.

Again, standard procedure, try PHH AOSP.

Thanks for isolating the issue, next up maybe grab a logcat from when you initiate a call?

I can't help you with GAPPS. Magisk situation is device-dependent, try and you'll see.
[Treble-Enabled Device Development A/AB ROMS] veekay:
It only does it to one side of the screen, depending on the rotation. 96 pixels stay black. It is like it is trying to keep the status bar. I even made an overlay for my device, but no change.

Is there a way I can forcefully kill whatever is causing the issue as well?
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Yes, sounds like the "correct" behaviour - it's avoiding your defined cutout. You can kill the cutout definition (config_mainBuiltInDisplayCutout in overlay) and see if that's what you like - not the same effect as my private build, but rather easy to do.
[Treble-Enabled Device Development A/AB ROMS] veekay:
By kill, do you mean just remove the line from the strings.xml? Which for me is:

<string name="config_mainBuiltInDisplayCutout">M 0,0 H -58 V 42.57142857142857 H 0 V 0 Z [MENTION=275090]dp[/MENTION] [MENTION=252765]right[/MENTION]</string>[COLOR="Silver"]

Edit - must not be that, no change. I do notice when changing between device default and hide that it does fill the screen for a short moment.

I tried your private build and that does fix the issue, so I just need to be able to reproduce that on what I'm running (Havoc)
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Do you still have your vendor overlay in place? It could still contain the definition.