yashsingh1/xdaforums huggingface dataset:
[Treble-Enabled Device Development A/AB ROMS] bonerserk:
Thanks!

Build 117 works great on Huawei y6 2018.

Calls over bluetooth now work!

Is it possible to temporary unroot? I've installed version with superuser included.

Thanks!
[Treble-Enabled Device Development A/AB ROMS] TheUndertaker21:
s10+ SD and exynos bugs are still present :(
[Treble-Enabled Device Development A/AB ROMS] Nordicus:
Is it really so difficult to download the file you need? :cool:

...vanilla-nosu.img.xz
[Treble-Enabled Device Development A/AB ROMS] bonerserk:
Yes that would be simple :cool: but I need su working for some application but for the rest of time I do not need a rooted device, so I'm asking if there's a simple way to root-unroot as needed.
[Treble-Enabled Device Development A/AB ROMS] Nordicus:
[MENTION=5907085]bonerserk[/MENTION]

Unroot/Delete SU , then install Magisk. And use Magisk Hide ...
[Treble-Enabled Device Development A/AB ROMS] TheUndertaker21:
118/119 works great on s10+ SD model

problem seems to be that speed has taken a beating.

dont think it's getting LTE at all
[Treble-Enabled Device Development A/AB ROMS] RalphMalph:
OEM Unlocked Xiaomi Redmi 7A

Flashed august (also july) version of AOSP 9.0 ( system-arm64-aonly-gapps-su.img.xz)

Both roms are installing good (through fastboot) but after reboot it goes back to fastboot. No possibility of logcat unfortunately.

Any idea?

Would latest version (v119) help maybe?

Ps.

I got in the Redmi 7A thread the following answer....is he correct?

1. You shouldn't be flashing A-only... Although this device is A-only it is also system-as-root so A/B should be flashed

2. You shouldn't be flashing arm64, this device's chipset supports arm64 but the OS is arm32_binder64, so you should be flashing that

Any idea?
[Treble-Enabled Device Development A/AB ROMS] J_E_F_F:
Sorry for the dumb question...

This seems to be the premier and recommended GSI build, but if it is altered is it really GSI or just custom and built from GSI like LineageOS for example?

What are the benefits of this build over the GSI directly from the AOSP website?

I was thinking of installing a GSI on a pair of Umidigi F1 Plays for my in-laws so they have more current software. I searched this thread for "umidigi" and read the few results that showed up, not much on the F1 or F1 Play. Any known issues with Unidigi F1 Play I should be aware of?

when I check the WIKI, it does list the Umidigi F1 / F1-Play, but the link to the specific info page does not work, I'd really like to see that device specific info: https://github.com/phhusson/treble_experimentations/wiki

The F1 Play shipped with Android 9, so I can install system-arm64-ab-vanilla-nosu.img and then OpenGapps ARM64 Nano and should be good to go?

TWRP show's this:

This device uses dm-verity!

This means that swiping to allow system modifications will prevent you from being able to boot if you are using the stock kernel. In order to bypass dm-verity's boot prevention, you will have to install a kernel that has dm-verity disabled in the fstab.

Does this GSI build meet the requirement and come with a kernel that has dm-verity disabled in the fstab.
[Treble-Enabled Device Development A/AB ROMS] daitalos:
https://xdaforums.com/android/software/universal-dm-verity-forceencrypt-t3817389
[Treble-Enabled Device Development A/AB ROMS] phhusson:
You definitely need A/B variant, and it sounds reasonable you might need arm32_binder64 rather than arm64, so those comments look right.

LineageOS GSI aims at providing features.

My AOSP GSI aims at providing hardware support.

For instance, if you take Google's AOSP GSI, on Samsung Galaxy S10, you will have missing sensors, not working light control, broken fingerprint, display is white-ish, mobile networks never report signal level.

I fix support for those features in my AOSP GSI. (I mentioned Galaxy S10, but I really try to make all treble devices work) Then I publish the changes I made on top of Google'S AOSP, so that other ROMs, like Lineage GSI, can use them to benefit from the hardware-related fixes, but still provide many more features than AOSP.

Well, GSIs became so boring that people stopped reporting whether it was working or not, and only come to complain when it doesn't :P

I guess so. Though to reduce headaches, usually I recommend to use my gapps rather than flashing opengapps on top of vanilla.

GSI doesn't provide any kernel, but it disables dm-verity by itself, so you should be okay ignoring this.
[Treble-Enabled Device Development A/AB ROMS] J_E_F_F:
[MENTION=1915408]phhusson[/MENTION] thank you for the detailed response
[Treble-Enabled Device Development A/AB ROMS] Magendanz:
I love how smooth this GSI is on the Samsung Galaxy Tab A 10.1 (2019), and I really appreciate [MENTION=1915408]phhusson[/MENTION] building the arm32_binder64-ab target, which is a rare even though many low-end devices shipping with Android Pie are choosing that config because of the lower RAM and storage footprint.

Two quick questions:

Since vendor is built with release keys and system with test keys, this will cause Google's Play Protect to complain loudly that the device isn't certified. I've tried matching build fingerprints, but that doesn't seem enough. Do you know of any workarounds? (It's great once the GSF ID is registered, but that first-run experience is a nightmare.)

Despite having added the double-tap to wake feature for Samsung devices, this isn't working for me even after setting the option in Phh Treble Settings. Any hints on how I can get this working?
[Treble-Enabled Device Development A/AB ROMS] phhusson:
you can run `adb shell su 0 /system/bin/phh-securize.sh` to disable root, and copy the required properties to look like stock rom

Please open an issue at https://github.com/phhusson/treble_experimentations/issues, with:

- `adb logcat -s PHH` after toggling the option in treble app

- `cat /sys/class/sec/tsp/cmd_list`

- `ls -lZ /sys/class/sec/tsp/*`

- `ls -lZ /sys/class/sec/tsp/ear_detect_enable`

- `ls -lZ /sys/class/sec/tsp/input/enabled`
[Treble-Enabled Device Development A/AB ROMS] RalphMalph:
Unfortunately it is not working.

After successful install by fastboot flash system ...... And reboot device goes back to bootloader
[Treble-Enabled Device Development A/AB ROMS] TheUndertaker21:
Anyone mange to get viper4android to work? Getting abnormal for Spotify Bluetooth
[Treble-Enabled Device Development A/AB ROMS] Magendanz:
I was using vanilla-nosu, but are you saying that if I switch to gapps-su and then run the phh-securize.sh shell script as root that it will make it so that the device is no longer blocked by Google Play services until registered?
[Treble-Enabled Device Development A/AB ROMS] Aeris_One:
Cannot install any GSI on Redmi 6A

I can't install any GSI on Redmi 6A : device reboot infinitively after flashing GSI.

Here's what I do :

1. (Fastboot) wipe userdata & flashing TWRP & reboot to recovery

2. (TWRP) wipe userdata & flashing GSI to System Partition & reboot to system (Bypassing warning message : There is no OS installed...)

3. Phone start, writing "MI" and "Unlocked" message then restart and restart...

4. So I start it to fastboot and reinstall MIUI with Mi Flashing Tool.

All tutorial i've found are generic tutorials but seems they don't work on Redmi 6A (cactus).

There is a page in the wiki, signify that someone has sucessfuly installed any GSI on device can any of these testers explain me how to install ?

Tested with AOSP 8.1 & AOSP 9 by Phhusson.

PS: Sorry for language errors but I'm French.
[Treble-Enabled Device Development A/AB ROMS] GroovyG:
Just a quick THANK you [MENTION=1915408]phhusson[/MENTION] for all the work you have put into this GSI, I think you get way too little appreciation for the effort you are putting into this.

I use it on my K7 with some adaptions, and it works absolutely flawlessy and purely with FOSS apps. There are no glitches, speed and battery life are amazing.
[Treble-Enabled Device Development A/AB ROMS] Magendanz:
Well, it turned out that's exactly what [MENTION=1915408]phhusson[/MENTION] was saying...and it's FRIGGIN AWESOME!! :victory:

In fact, all you need to do for vanilla-nosu builds is the following as root:

touch /system/phh/secure
rm /system/xbin/su
rm /system/bin/phh-securize.sh

I'm anxious to check out what magic he's doing when he sees /system/phh/secure, but it's definitely making Play Protect play nice again.
[Treble-Enabled Device Development A/AB ROMS] Stephelyn:
I have problem after flashing, I can't mount my system partition, after flashing the rom. Even i advanced wipe my system, after flashing same result. I have 8gb ROM only, my system has a 1.13gb total space, however flashing other ROMS like Resurrection Remix and Havok OS, doesn't have any problems on system mount error, flash flawlessly, but can't boot them anyway. I have f2fs data, but I don't if that cause of bootloop.

Since Version build 105 and up, can't mount my system after flashing this build.

Device:

Cherry Mobile Flare Y7 LTE

OS: OREO GO Edition with kernel 4.4.95

Powered by: MT6739WW, 8GB ROM, 1GB RAM

System Partition: 1.13GB only

Unfortunately no logs.
[Treble-Enabled Device Development A/AB ROMS] Fznwolf:
Network speed or overall phone speed? Are you sticking with Phh or going back to that Chinese rom?
[Treble-Enabled Device Development A/AB ROMS] TheUndertaker21:
Back to Chinese rom.

Not able to use viper4android is a turn off...

Network speed is not that good
[Treble-Enabled Device Development A/AB ROMS] OmerFlame:
Bootloop with Galaxy J6 J600G

This doesn't work for the Samsung Galaxy J6 J600G. It makes the entire system fall into a bootloop. PLEASE FIX THIS!

I checked and this is an AONLY officially supported Treble device. I also tried other GSIs and I got the same result. I did exactly how you told us to do it (I did it through TWRP), I did do a factory reset on it. I did EVERYTHING and it won't work. Can you please dig a little into the problem?
[Treble-Enabled Device Development A/AB ROMS] jal3223:
Please don't quote the OP, as it is long and it takes up half the page when you do. Also, it sounds like you're yelling "PLEASE FIX THIS!", like you're demanding something. I'm sure he would be more likely to help if you ask politely.
[Treble-Enabled Device Development A/AB ROMS] OmerFlame:
Sorry, I wasn't noticing or controlling myself, since I was trying to do this for a full day and nada. I was just frustrated...
[Treble-Enabled Device Development A/AB ROMS] jal3223:
No worries man. How did you try to install?

-Did you have a working build running first

-Reboot to twrp and wipe data, system, cache and dalvik

-then change to img flash in TWRP and flash in the system partition?
[Treble-Enabled Device Development A/AB ROMS] :
Please help me to install this rom in my xz3

Bootloop after installation

I try 2 roms this and pixel experience

All instructions are followed correctly

---------- Post added at 05:31 PM ---------- Previous post was at 05:31 PM ----------

Please help me to install this rom in my xz3

Bootloop after installation

I try 2 roms this and pixel experience

All instructions are followed correctly
[Treble-Enabled Device Development A/AB ROMS] TrueNix:
[MENTION=1915408]phhusson[/MENTION] galaxy s9+ exynos

Phone call bug which wasn't on yesterday's build

When you make a call the sound is in a background and you don't have an opinion to cancel it.

edit: reflashed without gapps all fine hmm..
[Treble-Enabled Device Development A/AB ROMS] MCR31:
[MENTION=1915408]phhusson[/MENTION] is there any news about incall audio?
[Treble-Enabled Device Development A/AB ROMS] Gennesÿs_1:
Are problems with audio on Mix 2S solved?
[Treble-Enabled Device Development A/AB ROMS] kearlsaint:
Thanks for your hardwork!

Tested on Huawei P8 Lite 2017(pra). Seems to be working well but apps seem blurry/low resolution except for the homescreen. Wifi, bluetooth, fingerprint, proximity, ambient sensor/auto brightness, sound, etc works. Only hotspot doesn't work. I attached a logcat from opening apps to fingerprint to lockscreen unlock, maybe it can help. I haven't installed gapps yet.

Edit:

Wifi turns on and scans but won't connect.

Fixed the blurry texts by disabling hw overlays on dev opt.

Some random eject-remount of sdcard.
[Treble-Enabled Device Development A/AB ROMS] mikas.vishra:
Help me please with the installation through twrp in Redmi Y2 ... It's an arm device .
[Treble-Enabled Device Development A/AB ROMS] Xdevillived666:
Is this pie aosp?
[Treble-Enabled Device Development A/AB ROMS] cmattern:
Yes!
[Treble-Enabled Device Development A/AB ROMS] CroW_D:
And does gaaps actually work ?
[Treble-Enabled Device Development A/AB ROMS] corkiejp:
Successfully installed on Kenzo, but can not find the option to turn on on screen navbar?
[Treble-Enabled Device Development A/AB ROMS] bariz143:
I used unofficial opengapps and it works ?
[Treble-Enabled Device Development A/AB ROMS] CroW_D:
So you rocking it right atmi guess ?. How is performance on op6 ? I think I'll flash it soon also
[Treble-Enabled Device Development A/AB ROMS] YazumiWuHung:
add this to /vendor/build.prop

qemu.hw.mainkeys=0
[Treble-Enabled Device Development A/AB ROMS] Kookitza:
[MENTION=2208406]bariz143[/MENTION] plz see my private message :rolleyes:
[Treble-Enabled Device Development A/AB ROMS] TheUndertaker21:
[MENTION=1915408]phhusson[/MENTION]

I can confirm my BT and camera has been fixed

along with app crashing

for app crashing, install android webview apk and go to debug setting and set it up

and as for BT crashing, just flash soldier rom , let it boot up then

factory reset( not format, not really needed) , flash rom and reboot then flash any gapps 9.0 to be exact

i'm all set
[Treble-Enabled Device Development A/AB ROMS] phhusson:
Ok, thanks a lot, this confirms the path I'm currently checking to fix this mess.
[Treble-Enabled Device Development A/AB ROMS] karthik km:
I am not having Redmi Y2

By the way flashing procedure is same

1) flash treble ROM

2) wipe all except /vendor and /storage

3) now flash gsi system image

4) reboot

** if your device doesn't have treble compatible recovery then flash gsi via fastboot **

Thank you
[Treble-Enabled Device Development A/AB ROMS] TheUndertaker21:
yeah android webview is preventing users from setting up googleplay and also crashing apps

S9+ forum has a fix for that

Thanks again for your work

looking forward to more updates
[Treble-Enabled Device Development A/AB ROMS] corkiejp:
Thanks for that, gives me access to Menu in TiBu, so I can restore some apps etc.

I wonder does xposed work on this, so I can setup hardware keys shortcuts to the menu option?

No compatible xposed at present, should have guessed!
[Treble-Enabled Device Development A/AB ROMS] TheUndertaker21:
is there a way to change DPI

420 on 6.2 inch screen is so bad LOL

I tried to build prop didn't work

and same with other apps
[Treble-Enabled Device Development A/AB ROMS] meltbanana:
setprop persist.ro.sf.lcd_density 480

?
[Treble-Enabled Device Development A/AB ROMS] RalphMalph:
Official Q is out and in AOSP!

Will we see already soon a release?
[Treble-Enabled Device Development A/AB ROMS] goRt:
Let us know when you're ready to release it ;)
[Treble-Enabled Device Development A/AB ROMS] xsleena:
Official Q works with some Issues like no WiFi on Samsung A50 !!
[Treble-Enabled Device Development A/AB ROMS] FlatOutRU:
How did you boot it? Like what steps to do?
[Treble-Enabled Device Development A/AB ROMS] xsleena:
I've just flashed the newest TWRP, then the dm verity remover and after his, I've flashed from TWRP the system.img as system partition

PS: Our A50 is an AB device !!!!

EDIT: front/back cam, data conn. works, the only that disturbing me to stay with this is that WiFi not working, PLEASE IF YOU ARE ABLE FIX THAT !
[Treble-Enabled Device Development A/AB ROMS] FlatOutRU:
I've got Snapdragon S10 and just thinking what's wrong. However i didn't try dm-verity thing. Not sure if it works with Snapdragon

I'm stuck at android glowing logo
[Treble-Enabled Device Development A/AB ROMS] xsleena:
I forgot to mention, after flashing dm verity blabla, wipe everything (but not your ExternalSD) :)

EDIT: Flash this one : gsi_gms_arm64-QP1A.190771.020-5800535.zip
[Treble-Enabled Device Development A/AB ROMS] FlatOutRU:
Both with vbmeta.img inside it?
[Treble-Enabled Device Development A/AB ROMS] xsleena:
ignore vbmeta.img , only the system.img AND DON'T RENAME IT !
[Treble-Enabled Device Development A/AB ROMS] FlatOutRU:
Okay, thanks! Gonna try this evening. Did you flash this dm-verity? https://xdaforums.com/android/software/universal-dm-verity-forceencrypt-t3817389/amp/
[Treble-Enabled Device Development A/AB ROMS] xsleena:
That one :)

EDIT: I see my file is outdated, please use the newest, I'll do the same later.
[Treble-Enabled Device Development A/AB ROMS] Paulicat:
Hi [MENTION=1915408]phhusson[/MENTION], hoping you could help out with something on a mediatek p60 Umidigi F1.

Seems hardware overlay are not functioning correctly. I have to turn on the switch to "Disable HW overlay" in dev options to get proper performance throughout the UI.

Most notable in Youtube...scrolling through videos, and when minimizing a video and dragging it back up it lags badly if I don't disable HW overlays.

Other than that the F1 is fully working. If there is anything you could suggest that I could try I'd be willing.

I know my way around things, but just unsure of why I'd have to disable the HW overlays.

Thanks for all your hard work!
[Treble-Enabled Device Development A/AB ROMS] RalphMalph:
[MENTION=1915408]phhusson[/MENTION] any idea?

None of the roms you offer are passing fastboot after installing.
[Treble-Enabled Device Development A/AB ROMS] J_E_F_F:
Did you need to disable DM-Verity for your F1, or just install this ROM and good to go?
[Treble-Enabled Device Development A/AB ROMS] Paulicat:
I flashed dm-verity only to stop encryption but the rom works fine without.

Its just that twrp does not decrypt the data partition on the f1.

Another important thing, I use an older dm-verity from December 15 2018 because there was a change at some point in a newer version around May I think that caused some headache with the imeis and wifi/bt mac addresses. I was able to fix it I think by reflashing an old stock rom but I would suggest using the old dm-verity for the F1 as it works 100%.

Heres the link to the one I have used successfully on my F1:

https://www.androidfilehost.com/?fid=1899786940962577323
[Treble-Enabled Device Development A/AB ROMS] axel199513:
Anybody tried it on s10+ exynous?
[Treble-Enabled Device Development A/AB ROMS] drxllxffxct:
My phone is decrypted after flashing this rom. Is there any zip file to encrypt it before booting for the first time or do I have to do anything else to encrypt it? My device is Mi Max 3
[Treble-Enabled Device Development A/AB ROMS] zsylive:
Lenovo k5pro encountered 2 problems, 1. no automatic brightness function 2. no volte...
[Treble-Enabled Device Development A/AB ROMS] :
any fix for bank app when i enter to app its send me a sms in my phone like new phone detected to configure

tried other gsi rom no problem
[Treble-Enabled Device Development A/AB ROMS] nealed:
Your English is a lot better than most on this forum, so bravo pour l'effort!

Try flashing Magisk after flashing the system.img and rebooting to TWRP. For a Mi 8 Pro this is what got it working for me.

I would also suggest flashing the system.img via fastboot. (fastboot flash system c:\...\system.img from a windows PC).

You might want to wipe the system partition and userdata from TWRP to see if that changes anything. Also wipe cache / dalvik cache.
[Treble-Enabled Device Development A/AB ROMS] jajk:
[MENTION=1915408]phhusson[/MENTION] Installed v119 on Samsung Galaxy A20 (Exynos SoC). MTP does not work on Win7 - device is detected but driver fails.

On another topic, why is the webview version so far behind the currently available version?

---------- Post added at 08:45 AM ---------- Previous post was at 08:44 AM ----------

[/COLOR [MENTION=1915408]phhusson[/MENTION] Installed v119 on Samsung Galaxy A20 (Exynos SoC). MTP does not work on Win7 - device is detected but driver fails.

On another topic, why is the webview version so far behind the currently available version?
[Treble-Enabled Device Development A/AB ROMS] Magendanz:
I just fixed this for the Samsung Galaxy Tab A 10.1 (2019) [SM-T510], also an Exynos SoC. The trick was in setting CONFIG_SEC_FACTORY in the kernel defconfig. (This does the same thing as commenting out CONFIG_USB_ANDROID_SAMSUNG_MTP in older Samsung kernels.)

Update: There actually a better, more narrowly scoped, fix here.
[Treble-Enabled Device Development A/AB ROMS] RUNNER75:
[MENTION=1915408]phhusson[/MENTION] version v10.0 v200 not boot Lenovo K5 Note 2018

arm64-aonly, not TWRP, not Root, install image for fastboot method.

Version v119 v9.0 works fine!!
[Treble-Enabled Device Development A/AB ROMS] skdubg:
[MENTION=1915408]phhusson[/MENTION]

AOSP 10 v200a is booting on Axon 7 with kernel and vendor from Speedy (king1990/Baddar)
[Treble-Enabled Device Development A/AB ROMS] coremania:
v 200a arm64 a/b doesn't boot on mi a1 Tissot. Tested with flex latest vendor, boot.img and old boot.img. Tested with lightning kernel too, no success.....
[Treble-Enabled Device Development A/AB ROMS] I1V1A1N:
I have v200 and v200.a running on my Amlogic s905x X96 tv box.But the image goes in solid stripes.I had android 9 in the first builds.Then the image stabilized in the next builds.If you're interested in my dmesg.
[Treble-Enabled Device Development A/AB ROMS] MIcHiJK:
I can confirm, that AOSP v10.0 v200 (Android Q) is booting fine on p8lite 2017 (PRA-LX1) on Oreo Vendor. The Animations are very smooth and the new gesture Animation is working great. As expected many things arent working like it was on pie before, but when some fixes will be released, i think we get a stable Android Q for the p8lite 2017, like we got really fast for Pie. Thats very cool to see, what Treble makes possible. Thanks for that !
[Treble-Enabled Device Development A/AB ROMS] atoyu:
anyone can you help to check ROG 2 phone is A or AB device?

[MENTION=1915408]phhusson[/MENTION]

here's the source code

https://www.asus.com/us/Phone/ROG-Phone-II/HelpDesk_Download/

edit: should be A/B
[Treble-Enabled Device Development A/AB ROMS] eremitein:
special app for check Treble status for you phone

https://play.google.com/store/apps/details?id=tk.hack5.treblecheck
[Treble-Enabled Device Development A/AB ROMS] planet33:
Someone tried Android 10 v200a on Oneplus5?
[Treble-Enabled Device Development A/AB ROMS] artouiros:
Chinese basement (Leagoo S9 if rly interested, stock 8.1, treble enabled default) Mediatek 6750. Latest Q AOSP 10.0 v200.c arm-64 A-OLNLY booted perfectly. Calls / USSD / Internet works well. Animations are sick, very beautiful and fast.

But I still don't have signal level meter on 3G (don't have access to LTE to test). phhusson replied me on github something about MtkSignalStrength in mediatek's hal. But I don't really understand what he meant and where to get mediatek's HAL.
[Treble-Enabled Device Development A/AB ROMS] Steve-Austin:
Hello,

No boot with Teclast M20, AOSP 10.0 v200.c arm-64 A-OLNLY.
[Treble-Enabled Device Development A/AB ROMS] :
motorola one... everything works except NFC, tried patch and it doesn't work

any suggestions?
[Treble-Enabled Device Development A/AB ROMS] Magendanz:
No boot with AOSP 10.0 v200.c (arm-ab) on Samsung Galaxy Tab A 10.1 (2019) [SM-T510]. Just black screen and reboots to recovery.