[AOSP 10.0] [2019-12-06] Quack Phh-Treble

Search This thread

phhusson

Recognized Developer
Jul 23, 2009
2,481
4,782
Paris
Hi 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.
 
Last edited:

mtnez.david

Senior Member
Jun 10, 2015
99
24
53
I want to test it on op7 as soon as possible

Sent from my GM1903 using Tapatalk

---------- Post added at 08:54 PM ---------- Previous post was at 08:53 PM ----------

Thank you very much

Sent from my GM1903 using Tapatalk
 

Ham1do

Senior Member
Aug 24, 2013
445
469
Excellent work :good:
Works well on Huawei P10 lite ( emui 8 ) except:
- Fast battery drain & battery usage isn't aviable
- Unknown model/build number
- There is an internal problem .. ( message ) on boot
- Camera fixed using a patch ( libcamxxx )
 
Last edited:
  • Like
Reactions: Chisetdel31260

mathy007

Senior Member
Dec 29, 2012
806
234
warri
Well phh keep up the good worwork, you're doing something different and we appreciate your time and effort in helping other devices with little or no custom ROMs support enjoy the latest version of AOSP
 
  • Like
Reactions: iwannarock

MIcHiJK

Senior Member
Feb 13, 2016
444
97
Ive tested v. AOSP 10.0 on the p8lite2017 (PRA-LX1)
Everything seems to work fine, so you will be able to use it daily even now. Everything is fixed but for NFC you need to flash a fix and for GPS: it is partly working and instable. I don't know if there are any improvements in the Versions after v206 since they don't boot.

Every version since v206 will bootloop. You can try to dirty flash it over an booting android 10 ROM but this will cause system problems.

Thanks for everything!


NfC Fix:
https://forum.xda-developers.com/p1...al-fixes-hi6250-devices-t3936745/post81021365


Thanks for all developments!
Last Edit: 13th January 2020
 
Last edited:

william_1434

Member
Apr 29, 2012
32
3
I'm on mi 9 lite (mi cc9) most things work but lockscreen cant be set other then swipe.

2g4zqQW
 

Attachments

  • Screenshot_20191028-121512.png
    Screenshot_20191028-121512.png
    90.9 KB · Views: 9,422

jngiag

Senior Member
Jul 19, 2009
264
142
Mi 5s Plus

Working - google play service, call, sms, mtp, camera, wifi, mobile data, magisk (phh modified version only), IR blaster, music & video

Not working - bluetooth, gps, some softwares installed through magisk failed to get storage permission (the same software in apk version has no problem).

:good:
 

MotoX4

Senior Member
May 19, 2018
218
293
Easthampton
Consumer name: Moto X4
Developer name: payton
Model: XT1900-1
Boot type: AB
Arm type: Arm64
Consumer type: Google Fi
Cellular provider: Google Fi
Location: USA

SD card used? No. - Internal storage only (32 GB)

Before install? Full wipe + full firmware flash = clean device

File: system-quack-arm64-ab-gapps.img

Status: Bootable but not yet useable.

Hardware:
  1. The thumbprint device is not working. This means you cannot swipe for navigation or unlock your phone using a thumbprint.
  2. No sound on calls. -- But can make calls
  3. Reboot device is always greeted with "SIM card added" notice telling me to reboot the device. -- I can ignore this and make phone calls.

ROM Software:

  1. Andriod Webview cannot be installed (error received when updating bundled Chrome)
  2. Developer options: OEM unlock is greyed out -- The phone is unlocked.
  3. The navigation menu when enabled does not display.
  4. Google which is bundled with Gapps cannot update.
 

AJ

Senior Member
Aug 8, 2012
343
67
google pixel can't pass safetynet ?

thus google apps don't work

anyone can ??
 

justcallmeTHEKID

Senior Member
May 10, 2012
62
14
Elyria
I cant get it to boot on my moto g7 power, treble and a/b enabled. flash twrp , install image to system but it just reboots as if there is no OS, system is mounted when flashed.
 
Clean flash arm64 a only vanilla on my s9+ with magisk v20 and a custom kernel, but won't boot. I have a logcat if you want that? Not sure why it won't boot. Seems it can't find ANYTHING that is supposed to be in the treble manifest.xml for the device
I have successfully installed v201 on my s9+ using csj1 vendor and using latest ww(yarpins) kernel for oneui although this release isnt stable enough for our device as of many UI glitches and many random reboots
 

phhusson

Recognized Developer
Jul 23, 2009
2,481
4,782
Paris
  • Like
Reactions: czmasterlp

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    能在ZTE 8012N上刷新? 安卓10 MT6853
  • 196
    Hi 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.
    11
    do you plan on doing it?
    Yes, though I've been planning it for more than a year.
    7
    Just flashed v211. What is this green dot on the lockscreen for? If I push it the screen dims and the green dot becomes brighter.
    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
    Well not working on V40 with LOS 17 android 10 base... haven't tried with Stock LG Pie base tho....
    Use stock vendor. It is very likely lineage breaks Treble compatibility.

    works fine on sony xperia 10 dual sim + android 10 software binaries
    Thanks for the report.
    Could you update https://github.com/phhusson/treble_experimentations/wiki/ and create a page for your device mentioning your tests?

    - adaptive brightness doesnt work, i can change brightness....but the automatic change isnt there....someone get what i mean?
    - battery stats....there is no app data....only the graph
    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.

    ps i would love to continue seeing AOSP+su-nogapps :fingers-crossed:
    I definitely don't plan on obsoleting it. Though i'm interested, may I ask why you're using this one?

    ps.: changelog said october security update? in options still september written?
    Yup my bad, that's indeed still september.
    Hopefully next should be proper november.

    Its working perfectly. but it would be awesome if the fix was built in
    Well the zip itself is closed-source, I can't integrate it without its sources