yashsingh1/xdaforums huggingface dataset:
[Treble-Enabled Device Development A/AB ROMS] AT-12:
Yeah the one i tried was an unofficial build from turboluke. Both v3.2 and v3.3. But since this problem was also persistent in Andy Yan and eremiteins LOS builds, i reverted back to my previous rom. Will try the official builds soon. Thanks
[Treble-Enabled Device Development A/AB ROMS] Slok 00:
hello i am trying to get this working on htc u11+ but i am getting bootloop at first logo... i flashed it via fastboot -u flash system quack.img ... any idea why is this happening? i am coming from htc stock pie rom with unlocked bootloader

EDIT: SOLVED
[Treble-Enabled Device Development A/AB ROMS] icodix:
yes, my device is compatible, but I always bootlooped.

---------- Post added at 03:11 AM ---------- Previous post was at 03:11 AM ----------

how? can you explain? thanks
[Treble-Enabled Device Development A/AB ROMS] Slok 00:
https://xdaforums.com/showpost.php?p=82527271&postcount=101
[Treble-Enabled Device Development A/AB ROMS] icodix:
ill try it later. Thank bro!
[Treble-Enabled Device Development A/AB ROMS] Rush:
Your device is pretty new, this is a problem for many other devices as well, but with it being a newer device, expect some kind of overlay specifically for 120hz devices to work on the S20Ultra. Or just, try yourself by forcing the frame rate (don't ask me where XD)
[Treble-Enabled Device Development A/AB ROMS] Fatact:
Hello, thanks to [MENTION=1915408]phhusson[/MENTION] and the whole community for bringing the GSI ROMs.

I need help for an issue with the network, I can't receive and make phone calls but I can still send and receive SMS and use 4G.

In Google Dialer> Settings> Calling accounts> Bouyge telecom (my operator)> Additional Settings, "Network or SIM card error" appears ... When I try a call, the correspondent's phone rings but my phone displays "call ended" but when someone calls me, i get absolutely nothing...

Screenshots are there: https://imgur.com/a/M02qLUF

---------- Post added at 06:58 PM ---------- Previous post was at 06:55 PM ----------

I have a Honor 9 lite
[Treble-Enabled Device Development A/AB ROMS] AT-12:
Dt2w on aod not working [J600F]

Unable to wake device by double tapping on the AOD. This feature used to work on android 9 gsi's but doesnt work on any of the Q gsi's that I've tried so far. Is there a fix to this?
[Treble-Enabled Device Development A/AB ROMS] eremitein:
in the 10 behavior changed - you need swipe on screen
[Treble-Enabled Device Development A/AB ROMS] Royna:
Mtp is not working
[Treble-Enabled Device Development A/AB ROMS] Miustone:
[MENTION=1915408]phhusson[/MENTION]

I filled an Issue on GitHub but don't got a Response there. Is there any Chance to add SONY Overlay for the XZ3, Xperia 1 & 5 since they all have official Android 10!? What we lacking of:

-VoLTE

-Wifi Calling

-HD Calls (Related to the first two i guess)

-Always on Display / Assistant Ambient Mode

-Camera Lenses are switching between front and back while there are 3 on the Back (Tele, Normal, Wide)

-Camera Button isn't mapped

My Xperia 5 runs Your GSIs without any hicks, SElinux enforcing and without disabled AVB or disabled Encryption on Stock Android 10 Base. It even uses the "right" fingerprint ids as Device Informations (But with Test Keys and Userdebug so no Safetynet passing). So i guess it wouldn't be to unrealistic? SONY is also great in sharing Sources and i would also mind helping out with Overlays if needed. Looking forward to get Support from You!

Edit: Found this https://github.com/phhusson/treble_experimentations/wiki/How-to-create-an-overlay?

I'll be back!
[Treble-Enabled Device Development A/AB ROMS] Miustone:
Had a lot of values folders in res and no xml folder. Removed the public.xml from within the main value folder and did the other Edits based on the XZ3. https://github.com/phhusson/vendor_hardware_overlay/pull/214

Xperia 5 done. Xperia 1 will follow once i got the Framework from someone. :angel:
[Treble-Enabled Device Development A/AB ROMS] phhusson:
Please open an issue at https://github.com/phhusson/treble_experimentations/issues/

this will make it easier for me to track this.

Attach the result of `adb shell dumpsys SurfaceFlinger with the issue.

Looks like you don't even know why you want an overlay...

What geve you the impression that you need an overlay?

I can't see your issue in https://github.com/phhusson/treble_experimentations/issues?q=is:issue+xperia ?

Not in overlay

Not in overlay

1. Not in overlay

2. How do you check?

3. Do you have HD calls on 3G?

Oh well this one is indeed in overlay.

What's that?

Not in overlay

Not in overlay

Please just open an issue for every issue you listed, at https://github.com/phhusson/treble_experimentations/issues/
[Treble-Enabled Device Development A/AB ROMS] Miustone:
Sounds like we need some Vendor Patches instead. Ambient Mode is part of NGA and unlocked on most modern Devices. It uses Ambient Display to show Google Assistant, Photos, News, Music and so on. Possible that it needs the /permissions (there is one from Google called NGA.xml). Would be nice to get Ambient Display/AoD to work with the pushed Overlay. Will be the same on the Xperia 1

Oh and no. HD Calls are just working over 4G/5G and Wifi (:

We also have a lot of stuff in /product but You disabled the usage of it right!? Is there any way to use parts of it anyways? Like ims and such?
[Treble-Enabled Device Development A/AB ROMS] phhusson:
What? No. all the features you listed except ambient assistant thingy can be fixed without changing vendor.

Ok, so you're actually trying to add a new feature to your device, that's out of the scope of a GSI.

Ok, then yeah of course you can't have HD calls without VoLTE if it requires VoLTE...
[Treble-Enabled Device Development A/AB ROMS] Miustone:
<!--
These are configurations that should exist on devices that support Next Generation Assistant
-->
<config>
<!--
This feature is meant to be the feature identifying devices that support NGA
-->
<feature name="com.google.android.feature.NEXT_GENERATION_ASSISTANT"/>
</config>

nga.xml (Located at /product/etc/sysconfig)

If our Devices would use their own /product would it be enabled on My Device. Double Touch to wake does also not work btw. I can open up single issues for the Problems if You want to! Have much respect for Your work but i'm looking at it from another angle You know. There seems to be a lot of Potential in this in views of coming Android Versions and the Problems we have with TWRP. So i just started my interest for this and want to contribute if i can. Just have still to learn some things :cowboy:
[Treble-Enabled Device Development A/AB ROMS] phhusson:
AFAIK that's not enough, but anyway, again that's ouf of scope of my GSI.

No, GSIs ignore device's /product, and have their own /system/product.

/

If you want those issues fixed, yes open those issue entries.
[Treble-Enabled Device Development A/AB ROMS] speedyjay:
Done buddy! I appreciate your help.
[Treble-Enabled Device Development A/AB ROMS] orbital_71:
Understand that u write phh superuser for treble rom. Is there a way to unroot treble??
[Treble-Enabled Device Development A/AB ROMS] Rush:
Just flash magisk
[Treble-Enabled Device Development A/AB ROMS] orbital_71:
Tried for havoc gsi there still root in it
[Treble-Enabled Device Development A/AB ROMS] phhusson:
Click securize in treble settings.
[Treble-Enabled Device Development A/AB ROMS] orbital_71:
I click mine securize in havoc gsi nothing come out from it.
[Treble-Enabled Device Development A/AB ROMS] Fatact:
I had this issue. Uninstall Magisk and flash phh superuser zip file and install the APK

https://xdaforums.com/project-trebl...le-root-phhs-superuser-phhusson-t3811563/amp/
[Treble-Enabled Device Development A/AB ROMS] krus5:
cubot A5

hi need some help I decided to flash this rom on my cubot a5 I download treble info and it says : Your device supports the legacy version of project treble using vndk version 27.0, my phone i arm32 and also it says it does not support system-as-root use an A-only operating system, where can i download version 27 please?
[Treble-Enabled Device Development A/AB ROMS] devrieshh:
There is almost no sound on my Leagoo xrover,i cant hear it ring when calling, alarm also almost not to hear.

When i play music with earphone it is ok,but with speaker no sound,nothing

could that be fixed?

Also the new google search field doesnt respond,cant type in it.

thanks for some advice
[Treble-Enabled Device Development A/AB ROMS] phhusson:
This is a pretty common issue, I'm expecting the fix to be easy.

Please create a new issue at https://github.com/phhusson/treble_experimentations/issues for this including a link to your stock rom.
[Treble-Enabled Device Development A/AB ROMS] :
Orbot ( +orwall? )

I want to thank you ph for your effort and this gsi, providing us a stock android for any device and giving us the opportunity to get rid off most off google's trashes. I am encountering two issues. The first is that i cant make orbot or any other vpn to startup automatically with the system, even if i put always on vpn and check on settings of each vpn to start at boot. And second, i cant make orbot work along with orwall, it seems that orwall just blocks every connection, even if i set it in every single app that it appears in its menu, still doesnt give me any internet access. My phone is RedMi 8a, does anyone else encountering issues like these two? Thanks in advance.
[Treble-Enabled Device Development A/AB ROMS] scandiun:
I guess the Samsung Galaxy Tab 3 10.1 GT-P5210 is not supported...
[Treble-Enabled Device Development A/AB ROMS] simonk206:
Hey [MENTION=1915408]phhusson[/MENTION] do you think its possible to fix auto brightness on Samsung Galaxy Note10+ N975F (Exynos)? It's the only thing that don't work for me on GSI. You need something? Thanks in advance
[Treble-Enabled Device Development A/AB ROMS] phhusson:
It's possible, and it's even pretty easy, though I don't have the motivation to do it.

Come to https://t.me/phhtreble I'll try to guide you on how to do it. And maybe later you'll be able to do it for other devices as well :)
[Treble-Enabled Device Development A/AB ROMS] victorcabral:
[MENTION=1915408]phhusson[/MENTION] , Is there a way to install Magisk for realme 5? The GSI is compatible with the device and it's working but it seems that after flashing Magisk, it stucks to Realme logo (not the Android boot). I don't want to use superuser.
[Treble-Enabled Device Development A/AB ROMS] xarvox:
Redmi 7A, no wifi/mobile data

Hello and thank you for your sharing this project in the first place!

However, im having some issues with my phone on your rom, there´s no wifi nor mobile data; no internet connection at all..

But i do have bluetooth and cell reception, so the RIL seems to be working to some extent..

The odd thing is that there was no initial setup ether, no full-screen app asking for wifi password or google account..
[Treble-Enabled Device Development A/AB ROMS] orbital_71:
[MENTION=1915408]phhusson[/MENTION] was it a must for gsi to have system as root to boot up??
[Treble-Enabled Device Development A/AB ROMS] phhusson:
No, that's what a-only variant is for.
[Treble-Enabled Device Development A/AB ROMS] cHawk:
[MENTION=1915408]phhusson[/MENTION] I tried using Magisk props hide to bypass SafetyNet and Cts profile but got a bootloop after a reboot. I've used this method on previous Phh based treble ROMs and I've never had a bootloop issue.

I've encountered this issue on both Descendent OS and Havoc OS rom based on the latest build.
[Treble-Enabled Device Development A/AB ROMS] orbital_71:
If is a Arm64 AB device without magisk and system as root the phone will still boot up as well?
[Treble-Enabled Device Development A/AB ROMS] lee.wp14:
Hi, sorry for bumping this post as this is the only thing that I could find on internet regarding the wallpaper problem.

This problem also exists when I'm adapting my device to aosp/caf based android 10 roms such as aospa and posp. However things work fine when it comes to lineageos.

Is there any information regarding this error? Or anyone has ever looked into this issue? Strange enough, the wallpaper in lockscreen works when applied separately.

I have reverted a commit in frameworks/base and external/skia but it didn't help. I couldn't identify any more difference in sources against LineageOS's so far, apart from this commit: TextureView rebind GL texture, if AHB content has changed.

Edit: SOLVED. here is a fix, mostly applicable to aosp/caf based roms.

https://github.com/hikuii-archive/p...mmit/b225804e0ccaa268ce315f05cf4e2a862f0cbbeb
[Treble-Enabled Device Development A/AB ROMS] Reznor7:
Hope you get a reply. I'm facing the exact same issue.
[Treble-Enabled Device Development A/AB ROMS] GroovyG:
Hi guys, using a mediatek P70 device and can't get VoLTE and VoWIFI to run with everything I've found so far, install ims-q.apk and the xml file, move the apk to /system/app and reboot multiple times. Everything else including 4G works perfectly. Did anyone with this chipset get VoLTE running on their device and if so, what did you do?
[Treble-Enabled Device Development A/AB ROMS] HueyT:
GSI can't do VOLTe. 4G is best you can hope for.
[Treble-Enabled Device Development A/AB ROMS] Rush:
But I'm using Volte Right Now.

:| What?
[Treble-Enabled Device Development A/AB ROMS] icebergREAL:
Any particular reason to this? Does VOLTE work, in non-GSI ROMs (on device specific system)?

LTE is 4G, there should be a quick fix to activate voice over it..
[Treble-Enabled Device Development A/AB ROMS] VZTech:
[MENTION=1915408]phhusson[/MENTION] any reason the newest builds have my devices screen timeout stuck at 5 seconds? I change it, but it always timesout. Any ideas?
[Treble-Enabled Device Development A/AB ROMS] Hanthonious:
Finally I can boot a ROM with gapps with v217 and without custom recovery, so much apreciated
[Treble-Enabled Device Development A/AB ROMS] rajaumarfarooq:
[MENTION=1915408]phhusson[/MENTION] any chance the brightness bug of being too bright is fixed in this release of v217
[Treble-Enabled Device Development A/AB ROMS] phhusson:
I have no idea what you're talking about.
[Treble-Enabled Device Development A/AB ROMS] rajaumarfarooq:
since v215 the minimum brightness remains too bright I am talking about that. it was working fine till v214 but on v215 the minimum brightness became too bright
[Treble-Enabled Device Development A/AB ROMS] ps000000:
I wish to ask. [MENTION=1915408]phhusson[/MENTION]

How to flash gsi in curtana (Redmi Note 9S)?

The fastboot & LRTWRP did not saw "System" partition in this device.:confused:
[Treble-Enabled Device Development A/AB ROMS] phhusson:
You need to use stock recovery's fastboot. Flash back stock recovery.

To trigger stock recovery's fastboot you can:

- From Android, do adb reboot fastboot (NOT adb reboot bootloader)

- From recovery, select "Go to fastboot mode" (NOT reboot to bootloader)

- From bootloader, do `fastboot reboot fastboot` (no this isn't a joke)

Please note that you'll need a recent fastboot targetted for Android 10.

Of course you also need to flash vbmeta, this one can be done from bootloader.
[Treble-Enabled Device Development A/AB ROMS] VZTech:
[MENTION=1915408]phhusson[/MENTION] are these built from googles gsi's, then you add features?
[Treble-Enabled Device Development A/AB ROMS] phhusson:
I'm not sure if this is the question, but this isn't a repack of Google's GSI. This is built from AOSP source code.
[Treble-Enabled Device Development A/AB ROMS] VZTech:
Yes, that was my question. Thanks. Reason i asked is googles gsi work very well on my Red magic 5g, but are missing alot of features. Yours has some issues with my device like brightness times out after 5 secs, and pic message mms reboots the phone.

EDIT, v2.17 build brightness is fixed.
[Treble-Enabled Device Development A/AB ROMS] Max128:
Hello , i have the HTC u12+ a device with A/B slot.. I always installed my things on slot a. I have tried for the first time the treble rom aosp Phh-based roms.. I had installed it the 11 may.. working pretty fine except for a few bugs.. No problem with the charge at all. The 19 may i wanted to install the recovery permanent way for the first time so.. i flash twrp with recovery ramdisk on it and after i flash touchscreen_hexpatcher.zip after that for keeping the stock kernel here the description of the patch ( Flashing touchscreen_hexpatcher.zip will make touch work when using stock kernel but render all recovery related commands unusable. )

After that.. the recovery was working.. but a few hours later when i wanted to charge the device.. i have a new and weirld bug, the charge problem. So When i put the phone in charge , this happen every few seconds ---> slow charging ---> charging ----> fast charging ---> slow charging --- > etc.... no more stable charge.. before that i connected the charger and 2-3 seconds after that is stay at quick charge like stock rom.. I have trying so many things after that.. reinstall the rom many times, format wipe , custom kernel, apply the RUU again for restoring completely at stock.When i install again a gsi rom i having the same problem of charge. If i power off the phone with gsi installed and when i charge it is look fine. When i restore at stock rom ( Android Pie rom ruu from HTC) the charge is fine only gsi rom is missing up the charge. Someone tell me the stock rom and aosp rom is not charging a phone in the same way is why.. The story of recovery, I was told that it was not probably related but for me it is too big for a coincidence.

Since that i have put many hours on this.. I am really at short ideas for gsi rom.. I am really tired so i have restored the stock rom and i will keep it for now.. So now i am writing here for maybe to getting some help and getting a fix for this.. I am sure that i am not the only one getting some problem with the charge on a gsi rom.. probably not for the same reason, however. May not be reported either .. I have found on xda some thread with some patchs ( thermal files) for fixing the charge on aosp rom.. But is only some particularly phone so.. I have found some people having problem with the charge on Android 10 through. I have made a little video of the problem before i was go to stock yesterday. Yes i have trying other cable usb and wall outlet. HERE THE VIDEO
[Treble-Enabled Device Development A/AB ROMS] sarajevski qdroid:
Same on mi Oukitel C11 Pro
[Treble-Enabled Device Development A/AB ROMS] KACE321:
Hi, I appreciate all your hard work on creating a more compatible GSI for android 10.

But I don't understand why despite what google has done, android GSI still has hardware faults/bugs on many treble-supported phones?

Is the \vendor partition not truly a separation of the Android framework from the drivers?
[Treble-Enabled Device Development A/AB ROMS] tchmit:
Hi, Everything works perfectly, in Blackview BV5800pro, except for deep sleep, I have a 5600mA battery and it lasts 5 hours, all four cores work at maximum most of the time, this happens to me in AOSP 10 and Lineage 17.1,

In AOSP 9 and Lineage 16, deep sleep works perfectly and the battery lasts 4 days
[Treble-Enabled Device Development A/AB ROMS] I1V1A1N:
To update vendor.

https://android.googlesource.com/platform/development/+/master/vndk/tools/definition-tool/
[Treble-Enabled Device Development A/AB ROMS] sarajevski qdroid:
Do you know will there be update with that vendor update because i don’t think i can run those codes. I’m not developer. I know only to flash with TWRP and Fastboot.

* I also tried flashing patches.zip on twrp but it gave invalid zip error
[Treble-Enabled Device Development A/AB ROMS] I1V1A1N:
More may be written about it here.This should be done in Linux.
[Treble-Enabled Device Development A/AB ROMS] phhusson:
Usual recommendation is to run `top` on the device to see what eats the cpu.

It's impossible to make a perfect driver/OS separation. Look at Windows, drivers still randomly break, and they've worked on this compatibility for decades now.

Android is using technologies that didn't exist back then, so we got something that worked pretty fast, but yeah it won't ever be perfect.

Also, Microsoft does a lot of testing on OEM devices to ensure Windows doesn't break for those OEM devices, while Google does no such thing (yet?), and I believe that without testing, there is no way it works.

Anyway, that's with a ****load of testing that I manage to do my GSI.
[Treble-Enabled Device Development A/AB ROMS] franco619:
for some reason sometimes a black screen appears with white stripes and I have to restart. My device is a motorola moto e6 plus
[Treble-Enabled Device Development A/AB ROMS] LeonardoGC:
Hi icebergREAL,

I have the same problem: reboot happens on the sleeping state, usually on the early morning hours.

I am using AOSP 10.0 v216 (system-quack-arm64-ab-gapps.img) with a Samsung Galaxy A20 (SM-A205G).

I generated two logcat files in order to identify the problem:

logcat.txt with the following ADB command:

adb logcat -d > logcat.txt

events.txt with the following ADB command:

adb logcat -d -b events > events.txt

Questions:

Did you create an issue for this problem (reboots in the sleeping state)? (Github issues) If the answer is No I will a create an issue.

What results did you get from your tests?

What was the result with other GSIs?

How can I improve my logcat skills too?

What should I search in the logcat files generated?

Thanks in advance.

Regards
[Treble-Enabled Device Development A/AB ROMS] LeonardoGC:
Hi phhusson,

From your previous answer I understand that in order to update an AOSP 10.0 installation one only needs to flash the system image. Question: In this scenario (update AOSP installation), is it necessary, before flashing the image, to wipe the system image in the recovery (TWRP)? I suspect that it's not necessary but I am not sure.

Thanks in advance.

Regards
[Treble-Enabled Device Development A/AB ROMS] TomRon:
boot loop Blackview BV9800 (Treble GSI supported)

Hello,

unfortunately I ran always into bootloops.

Device:

Blackview BV9800 (Mediatek MT6771V/CT)

ARM64

A-Only

Treble supported

Additional Info:

Stock ROM available (Android 9) Kernel-Version: 4.4.146

bootloader unlocked (device in orange state)

1. Variant: Things done to the Device without TWRP:

Stock ROM reflashed (SP Flashtool)

tried to flash system-quack-arm64-aonly-go.img (AOSP 10.0 v217) via SP flashtool --> flash passed but after reboot I ran into a boot loop

after flashing only the Stock system.img to the system partition phone boots up normally

2. Variant: Things done to the Device with TWRP:

Stock ROM reflashed (SP Flashtool)

Boot image pached with MagiskManager v7.5.1.apk and flashed with SP Flashtool

TWRP flashed with SP Flashtool

--> phone still booting into Stock OS

wiped Dalvik, System and Cache via TWRP

tried to install system-quack-arm64-aonly-go.img (AOSP 10.0 v217) via TWRP --> failed

E: Cannot flash images to file System

tried to flash system-quack-arm64-aonly-go.img via SP flashtoll --> flash passed but after reboot I ran into a boot loop

after flashing only the Stock system.img to the system partition phone boots up normally

I also tried the same procedure with Lineage 17.1 with same results...

Does anyone sees the issue?
[Treble-Enabled Device Development A/AB ROMS] Nordicus:
- boot in TWRP

- flashing system.img file

- wipe cache/dalvik

- reboot

Profit! :cool:
[Treble-Enabled Device Development A/AB ROMS] phhusson:
No need to wipe system.

1. Use fastboot, not twrp or SP flash tool

2. Flash vbmeta.

Don't wipe cache/dalvik, it's useless when using my releases.
[Treble-Enabled Device Development A/AB ROMS] tchmit:
HI, I already identified the problem, this is when I install a gapps package higher than nano gapps, yesterday I installed only the playstore package and downloaded the other google applications from the playstore, and I have no problem, the battery estimate gives me between 4 and 5 days, and go into deep sleep correctly, now everything works perfectly, the system has no failure, everything works perfectly