yashsingh1/xdaforums huggingface dataset:
[Treble-Enabled Device Development A/AB ROMS] bariz143:
My wi-fi didnt work on the first build but got fixed in second build. Im using Oneplus 6 so this instructions below are for Oneplus 6 only.

Flashed from STOCK OOS 5.1.11

unlock bootloader

factory reset in recovery

boot to bootloader

fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

fastboot flash system_a system-arm64-ab-vanilla-nosu.img

fastboot flash system_b system-arm64-ab-vanilla-nosu.img

Reboot ?
[Treble-Enabled Device Development A/AB ROMS] Kookitza:
[MENTION=2208406]bariz143[/MENTION] Where did you got vbmeta.img? :confused:
[Treble-Enabled Device Development A/AB ROMS] jackrip5:
For my part, I had no trouble to install this rom coming from stock MIUI 10 8.8.4 - not rooted -.

But I used fastboot method. I only used twrp for the gapps.

Trying to install a patched_boot file afterwards with twrp, always resulted in bootloops.

Overall, i have the same remarks than other mix 2s users, crackling sound, visual artefacts while scrolling on the top and down of the display.

Gapps : The initialisation assistance process does not work properly, so a restore from cloud is not possible. I tried MindtheGapps and Opengapps, makes no difference.
[Treble-Enabled Device Development A/AB ROMS] pravsterrr:
Are notches getting recognised for other devices. My Xiaomi Mi 8 SE still has notification icons going over the notch.

Having really tinny audio through speakers and headphones.

But this is a really good build. WiFI finally works
[Treble-Enabled Device Development A/AB ROMS] vandiaz_sairavinz:
help flash

how flashing patch fix slir?

in twrp error format .zip
[Treble-Enabled Device Development A/AB ROMS] Xdevillived666:
Volte?
[Treble-Enabled Device Development A/AB ROMS] technoboi1:
I have sometime visual glitches in opening apps. Its not fluid.
[Treble-Enabled Device Development A/AB ROMS] ibbi.ir7:
Which gapps do you falshed i tried it with open gapps and BITgapps but didn't work the rom boots but without google services that's why reverted back to semi Gsi and can u please show me your about phone as when i flashed it, it was showing pixel Xl 2 as my device
[Treble-Enabled Device Development A/AB ROMS] bariz143:
Using old vbmeta someone shared in another thread. I have no clue what that vbmeta does through ?
[Treble-Enabled Device Development A/AB ROMS] zidane2005:
Doogee Y8

Hi all,

I found an article ( title: "How to Install AOSP 9.0 V114 on Doogee Y8" ) about that this AOPS fork supports Doogee Y8 device. Could you confirm it? I did not find any information about it in the change logs.

Thanks!
[Treble-Enabled Device Development A/AB ROMS] exzemat:
hello,

to confirm that v119, su-gapps, works on huawei nova 2 (PIC-LX9) : everything (bluetooth, wifi, camera, fingerprint...)

Just mess "use of the battery since the last complete charge"

But need to rollback last original EMUI build (with jun security patch) to older emui 8, before flash.

if not, freeze to boot and reboot

without su-gapps, v119 failed to install (TWRP error 255).

Merci
[Treble-Enabled Device Development A/AB ROMS] danielfrancisarthurs:
Has anybody tried running a treble GSI on the samsung galaxy A80? Cant seem to find any custom roms anywhere and really want to try AOSP on this device. My guesses is if it boots that the camera will probably likely not*work as it should*and fingerprint in display will not? Thanks.
[Treble-Enabled Device Development A/AB ROMS] VyktorJonas:
wrong thread
[Treble-Enabled Device Development A/AB ROMS] alusher:
For the security patch do I have to have the same or can it be a earlier one. That's the only thing I need to know before I try this rom and thanks

Edit. I found my answer
[Treble-Enabled Device Development A/AB ROMS] YL-Li:
Unable to start. Red font warning
[Treble-Enabled Device Development A/AB ROMS] m4r0v3r:
mi mix 3 5g just bootloops none stop. not sure why tbh. tried flashing the disabled verity.
[Treble-Enabled Device Development A/AB ROMS] TureX:
Hi, i have installed aosp 9 v121 but i got problem with fingerprint and NFC. My device is Huawei p20 lite. Some time audio doesn' t switch between speaker and front speaker(speaker "for calls") .Installed version with gapps.tell me of you Need logs.thanks. Sorry for my english
[Treble-Enabled Device Development A/AB ROMS] russel5:
Hi. I'm have Sony XZ1C and used this project for my phone, all works perfect except one thing. If i'm choose LTE network my sim card detected is too long after phone reboot, but after ~1 minute it's worked, if i'm choose 3g network, my sim card detected right after reboot without any delay. Can someone tell me what need to change or help me with this small problem?
[Treble-Enabled Device Development A/AB ROMS] reynard1:
phh can you add this to rom?

https://github.com/microg/android_p...mits/a4ff77e83a662ef2288092dcebf2d7ef52179963
[Treble-Enabled Device Development A/AB ROMS] oF2pks:
Give a try to microG all-in-one Treble GSi (v121): https://xdaforums.com/project-trebl...arm64aosp-9-0-0r21-microg-ufofficial-t3878115
[Treble-Enabled Device Development A/AB ROMS] iHusky:
It will work on Sony Xperia XA 2 (H3113) with Gapps and Magisk?
[Treble-Enabled Device Development A/AB ROMS] iamthatakhil:
I don't know if this is linked, but I've freshly unlocked bootloader and installed TWRP and Custom ROM phh 9.0 AOSP v121 on my Note 8 yesterday. Even my phone says the security patch is August 1st.
[Treble-Enabled Device Development A/AB ROMS] CrioNat:
Anyone try this rom on Honor 8?
[Treble-Enabled Device Development A/AB ROMS] Magendanz:
Has anyone figured a way to fix offline charging on Samsung devices?

It shows the initial charging splash when the cable is connected, but then hangs. I thought this was just due to the fact that our GSI didn't include system/bin/lpm, but restoring that file didn't help. Are there additional dependencies? I'd settle for normal boot, but the usual trick of replacing lpm with a shell script also didn't work for me.
[Treble-Enabled Device Development A/AB ROMS] 0815900:
Hi, on Cubot X19 No gsi Rom ist booting...

I tried different gsi Roms and different instructions for flashing the system.img

Bootloader ist unlocked and twrp ist installed, also orange state disabler and magisk is installed, but i have an bootloop in Startup. Only the stock Rom ist booting
[Treble-Enabled Device Development A/AB ROMS] bdrew:
Wtf am i doing wrong??

So i've tried to install this on my Motorola e5 plus (hannah) over and over and over... I cannot get it to work.... I've tried flashing Arm_A arm64_a arm64_ab none of them work... I've tried with fastboot or from twrp..... it just never boots keeps boot looping.... What in the F*** am i doing wrong??
[Treble-Enabled Device Development A/AB ROMS] codergenius:
Device Alldocube M5XS [Helios X27 tablet, 3GB RAM, 32 BG ROM]

flashed and booted AOSP 9.0 v119 with following bugs.

1) battery is not charging in fully booted state OR fully off state, but only in TWRP

2) cannot enable/ approve USB debugging (adb devices always gives unauthorized, despite deleting keys from .android directory in the computer)
[Treble-Enabled Device Development A/AB ROMS] Nordicus:
1. Stop swearing.

2. Read OP carefully
[Treble-Enabled Device Development A/AB ROMS] secretwolf98:
There is newer builds:

v121: https://github.com/phhusson/treble_experimentations/releases/tag/v121

v120: https://github.com/phhusson/treble_experimentations/releases/tag/v120
[Treble-Enabled Device Development A/AB ROMS] codergenius:
tried v121, but no success.
[Treble-Enabled Device Development A/AB ROMS] shinezyy:
Thank you a lot for your nice work!

The problem I encountered is that when trying to add a fingerprint, my in-display fingerprint sensor is mistaken for a back/rear fingerprint sensor. (It asked me to find my fingerprint sensor from the back....)

The vendor overlay file I made according to this thread is also attached. (If there is some mistakes about it, please correct me)

Log that might be related: (Full logs are also attached)

I SystemServer: StartFingerprintSensor
I SystemServiceManager: Starting com.android.server.fingerprint.FingerprintService
D SystemServerInitThreadPool: Started executing FingerprintService.onStart
V FingerprintService: mDaemon was null, reconnect to fingerprint

The rom I'm using: AOSP 9.0 v119 aosp-9.0-arm64-ab-gapps-su.img

Device: Lenovo Z6 (L78121) with Snapdragon 730, and in-display fingerprint sensor from Goodix.

Vendor version: From the offical zui 11.1.262 rom

Logs are attached, including the log during boot and the log when I try to add a fingerprint.
[Treble-Enabled Device Development A/AB ROMS] buzz-27:
Hello,

This rom work perfectly on my "Archos Hello 7", just the alarm notification is very high. When is the wakeup time my ears bleed and that with mini level in configuration parameter !

unfortunately the number of step in configuration for alarm is half to media or call ? is it a potential factor of my issue.

I tried to change the configuration with Viper and build.prob but without success.

If you can help me to configure the alarm volume level, it will be perfect for my mornings wakeup !

thanks.
[Treble-Enabled Device Development A/AB ROMS] phhusson:
I recommend you to try Lineage 16 ( https://sourceforge.net/projects/andyyan-gsi/files/ )

I'm guessing one of the many additional settings in Lineage can be used for that.

Please report back whether this suits you
[Treble-Enabled Device Development A/AB ROMS] buzz-27:
Ok, I try and come back ! thanks for this fast reply.

Well, the Lineage 16 "treble_arm64_avN.img.xz" version work but same issue, for alarm the first step have mini level.volume 28% no less :confused: !!

Is it possible to param by buildProp ?

Currently I have recorder some wake-up sounds with very low level.
[Treble-Enabled Device Development A/AB ROMS] boringpie:
Tested on Elephone Soldier

I tested on Elephone Soldier. There is no speaker sound. Everything else is working fine.
[Treble-Enabled Device Development A/AB ROMS] phhusson:
See https://github.com/phhusson/treble_experimentations/issues/874, and especially https://github.com/phhusson/treble_experimentations/issues/874#issuecomment-555729754
[Treble-Enabled Device Development A/AB ROMS] Magendanz:
[MENTION=1915408]phhusson[/MENTION], is there a recommended approach for GSIs to handle offline charging?

On Samsung devices, connecting to power after shutdown boots with ro.bootmode=charger, which in init.${ro.hardware}.rc starts a class called "sec-charge" that in turn starts the lpm service in init.rc. The problem is that /system/bin/lpm and its animation resources live in the system partition. There's actually a ton of hardware-specific setup done in the OEM version of the init.rc that's not included in the GSI init.rc, with the ultimate outcome being that the device hangs.

Does AOSP have an equivalent of lpm that just displays the battery charge level and shuts back down when done? Or can I make it do a normal boot without bootloader modifications?

I've tried the various methods of simply rebooting from charge mode, but those haven't worked for me. The closest I've gotten is calling trigger late-init, which looks like a normal boot but has the touchscreen disabled.
[Treble-Enabled Device Development A/AB ROMS] phhusson:
Try adding to /system/etc/init/no-charge.rc:

on charger
trigger late-init

That should start Android instead of being stuck in a broken charge mode i think
[Treble-Enabled Device Development A/AB ROMS] alusher:
I have a black shark 1. I haven't been able to get any updates since Dec. 5, 2018 something to do with a modified system. The reason it's modified is that I tried to install twrp. My question is will I be able to try this rom with my security patch being Dec5 2018. I'd rather ask this then to asked about bringing my paperwieght back from the dead thanks.. my phone is 64 a a/b and will work with treble ROMs.
[Treble-Enabled Device Development A/AB ROMS] Magendanz:
That did the same thing as calling trigger late-init from init.${ro.hardware}.rc. It launches normally, but the touch screen is disabled (and potentially much more).
[Treble-Enabled Device Development A/AB ROMS] killerscope2:
hey i found a bug on wifi my internet goes up to 40-50MBbs and then goes down to 10 and sometimes even more down. also overnight something with the wifi went wrong and got a bugreport where can i send it?
[Treble-Enabled Device Development A/AB ROMS] dotKin:
Log in or register on Github and open a issue here describing what's the issue and attaching logs https://github.com/phhusson/treble_experimentations/issues
[Treble-Enabled Device Development A/AB ROMS] Khotyz:
not working in J610G with project treble, twrp and OEM unlock, I just wanted a gsi that would work on it and not stay on the infinite logo screen :ccc
[Treble-Enabled Device Development A/AB ROMS] Khotyz:
infinite restarts on j610g :c
[Treble-Enabled Device Development A/AB ROMS] phhusson:
Well then perhaps we could reboot?

Something like on charger\nexec u:r:su:s0 -- /system/bin/reboot
[Treble-Enabled Device Development A/AB ROMS] Magendanz:
There are some efforts documented out there to reboot, but they mostly go like this:

on property:ro.bootmode=charger
class_start sec-charger

service autoreboot /system/bin/reboot
class sec-charger
critical

or

on property:ro.bootmode=charger
start autoreboot

#autoreboot service which command reboot
service autoreboot /su/bin/su /system/bin/reboot -c reboot now
user root
oneshot

Neither of these worked for me, but this device isn't rooted. What's that "nexec u:r:su:s0" command do? (I can't seem to find a man page for it.)
[Treble-Enabled Device Development A/AB ROMS] phhusson:
Right so, issue is that SELinux policy probably doesn't allow init to execute /system/bin/reboot (at least that's what I assume).

So i use the "su" SELinux context which is allowed to do anything on userdebug builds, to bypass this.
[Treble-Enabled Device Development A/AB ROMS] Magendanz:
Unfortunately, this isn't working either and it's back to hanging. I'm vacationing "down under" for the next 3 weeks, but will try to troubleshoot further when I return. I haven't been setting SELinux contexts on these .rc files when I replace them (only setting chmod 755). Do you think that might be the problem?

P.S. What threw me from your last suggestion was the "nexec" command, which I hadn't seen before. Turns out that I picked up an "n" from the previous newline "\n". (Doh!)
[Treble-Enabled Device Development A/AB ROMS] boomo15:
Did post in wrong tread,sorry.

Installed v123, all working smooth and fast, except one issue - I can send SMS but can't receive from any number. Nokia 7.2, original vendor, rooted, twrp, Magisk canary. Returning back on stock all working. Tried switching SIM card to Moto G6 with Omni treble pie - all working too. Thank you.
[Treble-Enabled Device Development A/AB ROMS] :
How can I remove this ugly Google search box from home screen? I wonder why this is included in the first place.
[Treble-Enabled Device Development A/AB ROMS] boomo15:
Replace launcher. It what I did.
[Treble-Enabled Device Development A/AB ROMS] Rox598:
Nvm
[Treble-Enabled Device Development A/AB ROMS] luvilela:
Hey, can I use in Samsung J8 (Samsung Galaxy SM-J810M)?
[Treble-Enabled Device Development A/AB ROMS] Ww222:
Hotspot doesn't work at all on mate 8 in last build.
[Treble-Enabled Device Development A/AB ROMS] moctir:
Not sure if you're still interested in bug reports, but battery usage has no data on the Cubot King Kong Mini. Let me know if you need logs or something.

EDIT: Apologies, just seen this post:

Will attempt this and report back.
[Treble-Enabled Device Development A/AB ROMS] sparks2020br:
10.0 v209 working like a charm on xt-1922-5 :)

thank you!
[Treble-Enabled Device Development A/AB ROMS] :
On Redmi Note 5 Pro, the system doesn't recognize physical SD cards in exFAT format as portable storage.
[Treble-Enabled Device Development A/AB ROMS] phhusson:
Thanks for the report.

Did you do a factory reset in the meantime, or you hit this issue with a simple upgrade?
[Treble-Enabled Device Development A/AB ROMS] moshe_lm:
on the wrong thread.ignore.
[Treble-Enabled Device Development A/AB ROMS] KineSight:
Has anyone here tried this GSI on any of the Samsung Galaxy A Series (A10, A20, A30, A50 etc.)?
[Treble-Enabled Device Development A/AB ROMS] th3legend:
Well I couldn't get it working on the aospv10 for safety net so I am trying 9 instead ..it works but still failing basic integrity with no securize option that I can find on the latest...I'm on a20
[Treble-Enabled Device Development A/AB ROMS] jwarrior319:
I find it odd the securize option is missing. I just noticed i dont have it although last time i installed this exact version using the exact same file i downloaded, it was there. ?
[Treble-Enabled Device Development A/AB ROMS] th3legend:
V10 has it but hangs when you select it....v9 doesn't have the options latest versions used for both as of today's date
[Treble-Enabled Device Development A/AB ROMS] kylek389:
Hello, the AOSP 9.0 v123 that I installed was a clean install (the usual stock EMUI8 restore via dload, factory data reset/wipe + cache wipe, and then fastboot flash system with AOSP 9.0 v123).
[Treble-Enabled Device Development A/AB ROMS] JakeZain:
Hey while downloading from GitHub the download always crashes after 10 mins are there ant mirrors available ?
[Treble-Enabled Device Development A/AB ROMS] 123_win:
Syncing r53-r47 failed => solved

Using latest script (build.sh) from github.

Try to compile latest AOSP 9.0 and did get the following errors.

While sync:

============

[...]

warning: redirecting to https://gitlab.com/aosp-security/platform_test_vti_test_serving.git/

fatal: Couldn't find remote ref refs/heads/android-9.0.0_r53-r47

warning: redirecting to https://gitlab.com/aosp-security/platform_test_vti_test_serving.git/

fatal: Couldn't find remote ref refs/heads/android-9.0.0_r53-r47

error: Cannot fetch platform_test_vti_test_serving from https://gitlab.com/aosp-security/platform_test_vti_test_serving

[...]

warning: redirecting to https://gitlab.com/aosp-security/platform_external_x264.git/

fatal: Couldn't find remote ref refs/heads/android-9.0.0_r53-r47

warning: redirecting to https://gitlab.com/aosp-security/platform_external_x264.git/

fatal: Couldn't find remote ref refs/heads/android-9.0.0_r53-r47

error: Cannot fetch platform_external_x264 from https://gitlab.com/aosp-security/platform_external_x264

[...]

While checkout the script aborted:

===================================

platform_external_webview_support_interfacChecking out projects: 53% (361/681) platform_external_wycheprooferror: Cannot checkout platform_external_x264: ManifestInvalidRevisionError: revision refs/heads/android-9.0.0_r53-r47 in platform_external_x264 not found

error: in `sync -c -j 1 --force-sync`: revision refs/heads/android-9.0.0_r53-r47 in platform_external_x264 not found

So i deleted from manifest.xml:

===============================

line 377 <project path="external/x264" name="platform_external_x264" groups="pdk"/>

line 663 <project path="test/vti/test_serving" name="platform_test_vti_test_serving" groups="vts,pdk"/>

Also deleted the corresponding files from project-dir and .repo-dir. After that checkout was successful.

My question: are these projects missing or is the manifest not correct?

P. S. Compiling in progress.

Edit 2:

===============================

Installed missing tools (not listed in wiki):

git lfs

xmlstarlet

Edit 3:

===============================

Compiling failed with missing vti test_serving.

Manually cloned:

git clone http://git.videolan.org/git/x264.git (copy folder to ./external/)

git clone https://android.googlesource.com/platform/test/vti/test_serving (copy folder to ./test/vti/)

Edit 4:

===============================

Used disk space is w/o ccache: ~192GB

After these steps, compiling was successful.

Thanks for your work, neeeded this bluetooth fix :).
[Treble-Enabled Device Development A/AB ROMS] Sindrom:
Hi. I have problem with mobile data in this gsi on Galaxy A8+ I don't know what to do. Can anyone help?
[Treble-Enabled Device Development A/AB ROMS] veekay:
Is there a way to enable the auto wake/sleep feature when using a magnetic case?
[Treble-Enabled Device Development A/AB ROMS] phhusson:
I'd say this should be pretty easy.

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

- device name/model name

- the result of:

+ launch adb shell getevent

+ open/close the magnetic case

+ copy the content of the screen with the getevent command
[Treble-Enabled Device Development A/AB ROMS] veekay:
Submitted. See if it gets any traction. Still have an open issue from October.
[Treble-Enabled Device Development A/AB ROMS] Okiera29:
Any idea why I can't get this to boot? I am on a Huawei Mate SE BND-L34 running stock Oreo. I was on build 8.0.0.330 and running an OpenKirin ROM just fine. I upgraded to the latest firmware 8.0.0.361 as I wanted face unlock and a few other things fixed(bluetooth issue) Since then, I can not get any Treble ROM to boot. I have tried all the OpenKirin Omni versions. I have tried this ROM and LOS. I do a factory reset through the stock recovery. I then flash the new system img. Then I boot into the stock recovery and factory reset again(just like to start new ROMs in a clean state) When I boot I am stuck on the "Your device has been unlocked and can't be trusted" splash screen. I would love to get rid of all the Huawei bloat and get back to Pie as well. Any help or suggestions would be greatly appreciated. Oh yeah, one more quick thing. Device is A only and I am downloading arm64-aonly-gapps-su.img for the ROM
[Treble-Enabled Device Development A/AB ROMS] Halwer:
Dear phhusson!

Fist of all, thank you for your hard and amazing work! Without it I couldn't use my chinese phone, the way I wanted. I just wanted to ask, if you finished developing PIE releases or can we expect more coming soon?

Thank you again!
[Treble-Enabled Device Development A/AB ROMS] Star Dust:
Is their a fix for In call sound for Samsung j4core? Everything is working except the in call sound. I can't hear the person on the other end of the call and they can't hear me too.
[Treble-Enabled Device Development A/AB ROMS] :
Hi , I have the Samsung Galaxy A10 (A105F/DS U3). My device is treble supported , A/B rom supported , architecture - x64 supported chipset. But , my device do not support seamless updates. Please tell if i can flash this gsi image to my device. Waiting for your reply. Thanks in advance.
[Treble-Enabled Device Development A/AB ROMS] [Acme]:
Flashed successfully!

But... I have a message,

Android System

There is an internal problem with your device.

Contact your manufacturer for details.

And... small icons, small fonts. I suppose this could be solved via configuration

---------- Post added at 01:18 PM ---------- Previous post was at 01:12 PM ----------

BT crash
[Treble-Enabled Device Development A/AB ROMS] jwarrior319:
Yes you can
[Treble-Enabled Device Development A/AB ROMS] alvinprimo:
Hi, im installed this rom and my wifi and hotspot can't turn on. Also the stock camera but its on the OP. My device is lenovo s5. Installed over the oreo stock. Any trick to make my wifi hotspot works? Everything else seem fine until now..thank you dev for this nice Rom
[Treble-Enabled Device Development A/AB ROMS] Mass13:
Same here, Huawei Mate 10 Lite, I was on v119, tried v123,

did not boot,

AOSP 10 no go,

tried to flash back to 119, no go

I'm on OmniROM Pie Alpha 6.2 right now.
[Treble-Enabled Device Development A/AB ROMS] Okiera29:
I have pretty much given up on my Huawei devices. As good as my Mate 9 was, it died a horrible death and can't get an unlock code for a new one. I have gone to the dark side and have a Oneplus 6T on the way
[Treble-Enabled Device Development A/AB ROMS] alvinprimo:
Anyway to fix offline charging guys, Lenovo s5?
[Treble-Enabled Device Development A/AB ROMS] Rush:
Wrong thread, any device specific questions should be asked on your device forums
[Treble-Enabled Device Development A/AB ROMS] alvinprimo:
I thought offline charging is a bug on all GSI rom, and im on phh aosp 9 rom. I name my device because no dedicated forum for my device here in xda. So maybe someone own Lenovo s5 can help me..