Has anyone else experienced an issue with the mac randomizer turning on after every restart even though the option is, objectively, turned OFF in Developer Options?
[AOSP 10.0] [2019-12-06] Quack Phh-Treble
- Thread starter phhusson
- Start date
I am using [AOSP 11] Quack Phh-Treble. Vanilla version works fine but gapps version is booting but not even the status bar or the navigation bar is loading. Initial google account setup freezes.
So I wanted to flash gapps after installing the vanilla version but after booting the complaint is: "Google services cannot run on this device. This device is not play protected."
Any fix to this? I want to flash the vanilla ROM and then flash gapps.
Ive flashed quack a/b img version on my lenovo z5 . All is working good except Bluetooth calls and some blank glitches (spaces) than appears in apps like youtube and messenger when i scroll. Ive tried to play a little bit with webwiewer's options in the dev menu but i cant fix it.
Can anybody help?
Can anybody help?
bluetooth - try to search in the web/phh chat/xda, there is specific solution for Lenovo z5 (need enable in Phh settings > Misc > Force disable A2DP or remove some apk from /vendor)
glitches - need update Adreno GPU driver, also you can find in the web and XDA have thread for drivers too
Hi, man) Glad to see that someone find it) I already did TWRP, kernel and vendor for GSI ROMs. Welcome)
When the system reboots, the device logo appears and then flashes and boots into download mode.
(SM-A605F)
(SM-A605F)
Last edited:
FYI
I installed AOSP 12.1 v414 on an Samsung Galaxy Tab A 10.1 (2019)
stock FW was/is: either T510XXU5CUL1 or T510XXU5CVB1
following this instruction:
github.com
so far so good
thanks @phhusson
I installed AOSP 12.1 v414 on an Samsung Galaxy Tab A 10.1 (2019)
stock FW was/is: either T510XXU5CUL1 or T510XXU5CVB1
following this instruction:
Samsung Galaxy Tab A 10.1 (2019)
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
so far so good
thanks @phhusson
Branch Grid
Branch Grid
which would explain why they won't boot
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
196Hi all,
Here is the thread about Phh-Treble for Android 10.0, codename Quack.
The goal of Phh-Treble for Android 10.0 is the same as for Android 8.0, 8.1, and 9.0: Bring latest AOSP to the maximum number of devices running Google-certified Treble[1], with full hardware support.
You can download latest release at https://github.com/phhusson/treble_experimentations/releases
Which variant do I pick
To know which variant to download, use https://play.google.com/store/apps/details?id=tk.hack5.treblecheck . Don't use other Treble Check apps, they'll give erronous informations.
And then, you're free to choose between vanilla and gapps variant.
What works?
On some devices, everything. They are still not the majority though.
What you can expect on the majority of devices?
It should boot successfully on pretty much all devices with Google-certified Treble. [1]
Most features should work on the majority of devices out-of-the-box: RIL, WiFi, brightness control, buttons, gestures, ...
However, many devices still have issues with hardware video decoding and camera.
Is device XXX supported?
If it's a Google-certified Treble, yes it is. Unlike Google's GSI, Treble devices supported, there is no exception.
There might be bugs of course, but if you help me, I'll fix them!
Which vendor to use?
1. Always use your actual device's vendor
2. Always use OEM unmodified vendor, not some custom vendor
3. This includes boot.img. boot.img and vendor MUST BE the same version.
4. If you're on an Android 8.0 vendor, you'll need to stick to vendors with Security Patch Level before April 2019 (that's a bug of my GSI)
Enjoy!
[1] How do I know my device is Google-certified Treble?
Well it's easy, if your device has first been released with Oreo or more recent, and it has google apps, it has a Google-certified Treble.
Please note that this means only the vendor provided by the OEM is certified, not the one from device-specific ROM.117
Right, that's a fail from me, that will be fixed in next release.
That's intended for devices with optical under-display fingerprint.
I'm respinning a v212 to fix that.7
Use stock vendor. It is very likely lineage breaks Treble compatibility.
Thanks for the report.
Could you update https://github.com/phhusson/treble_experimentations/wiki/ and create a page for your device mentioning your tests?
Those are fairly easy to fix, you just need an overlay, based on infos from stock rom.
There is a guide there https://github.com/phhusson/treble_experimentations/wiki/How-to-create-an-overlay? or a quite automatic script there: https://github.com/phhusson/treble_experimentations/blob/master/overlay/generate.sh though I recommend you join @PHHtreble telegram group so I can help you create it.
I definitely don't plan on obsoleting it. Though i'm interested, may I ask why you're using this one?
Yup my bad, that's indeed still september.
Hopefully next should be proper november.
Well the zip itself is closed-source, I can't integrate it without its sources
