[AOSP 8.1] [2019-03-06] Phh-Treble

Search This thread

CosmicDan

Senior Member
Jun 19, 2009
5,862
7,697
34
Sydney
Xiaomi Poco F1
Thanks a lot CosmicDan. I know that method, and, for now, I am not blocked on Gapps. But, IIRC, there are quota on the amount of device 'registration's (I have 2 now). For other custom firmware (GZOSP) it looks like it helped to simply edit the build.prop fingerprint in /system to get 'Certified'. Actually, GZOSP was 'Certified' and stock was not :cowboy:. However, for Treble AOSP, I could not get this to work. Maybe one needs to hack other .prop files (like in /vendor) or maybe I miss something? Also, for my Treble AOSP tissot, the GSF Device-ID registration succeeded, but, the Play Store nevertheless still says 'uncertified'. As said, it is (as is the safetynet cts) a minor issue because, apparently, I can use Gapps just fine.

I guess changing the fingerprint will fix it, we're talking about it internally (there's a few props) but I don't actually know if it causes any problems if it shows as Uncertified.
 
  • Like
Reactions: Dior DNA

hussain525

Member
Dec 23, 2013
44
3
Mumbai
aosp onlya su +gapps boots and gets stuck on One Sec screen (the first screen that appears after loading) and nothing happens please help

Hello,

I faced the same problem last night but got it fixed. What I did was just do a clean install of the AOSP system image (Wipe Data, Cache, Dalvik/ART Cache, System partition and Internal storage) and VOILA everything was A-Okay!! :D:D
 

phhusson

Recognized Developer
Jul 23, 2009
2,448
4,694
Paris
Thanks a lot CosmicDan. I know that method, and, for now, I am not blocked on Gapps. But, IIRC, there are quota on the amount of device 'registration's (I have 2 now).
Nope, google has said that they won't limit the number of registrations
(Though I expect that they'll watch for people with > 100 registrations to ensure that's not an OEM cheating)
 

CosmicDan

Senior Member
Jun 19, 2009
5,862
7,697
34
Sydney
Xiaomi Poco F1
Nope, google has said that they won't limit the number of registrations
(Though I expect that they'll watch for people with > 100 registrations to ensure that's not an OEM cheating)

Though I was told it's not a unique ID sadly, it's regenerated on a fresh boot? I was hoping it'd be based on a device IMEI or serial hash or something so you only need to do it once...
 

Dior DNA

Senior Member
Aug 17, 2015
1,455
637
Though I was told it's not a unique ID sadly, it's regenerated on a fresh boot? I was hoping it'd be based on a device IMEI or serial hash or something so you only need to do it once...

I don't know at all but one could try to check: what if ID may be unique by firmware.
 
Last edited:

Tmyol

Member
Jun 7, 2018
7
0
There are five problem in latest rom that I found:
1.Caller ringer output is accompanied by "Drips"
2.Bluetooth often shows that it has stopped running when it is off.
3.Battery usage is not specifically displayed.
4.The dark wallpaper drop-down menu under Android 8.1 does not switch to dark.
5.Charging without sound.
I hope you can Solve these problem in next Update,
i am using honor 7x in this room,i really like it.:fingers-crossed::fingers-crossed::fingers-crossed:
 
Last edited:

imHadees

Senior Member
Jun 22, 2014
711
287
There are five problem in latest rom that I found:
1.Caller ringer output is accompanied by "Drips"
2.Bluetooth often shows that it has stopped running when it is off.
3.Battery usage is not specifically displayed.
4.The dark wallpaper drop-down menu under Android 8.1 does not switch to dark.
5.Charging without sound.
I hope you can Solve these problem in next Update,
i am using honor 7x in this room,i really like it.:fingers-crossed::fingers-crossed::fingers-crossed:
This should fix some of your problems: https://forum.xda-developers.com/ho...erlay-dil3mm4-s-overlays-bond-series-t3815504
Most of the problems aren't because of the ROM, but because of the way manufacturers implemented Treble for their devices.
 

xpsviewer

Member
Oct 3, 2017
17
8
changsha
SD Card problems on redmi 4x [santoni]

I found this treble image is almost perfect for me but I found a glitch which matters.
The version I use is system-arm64-aonly-vanilla-nosu updated in 2018-7-3

Sometimes after boot from shutdown or every time boot from recovery the system will not recognize the SD card. It says 'SD card format not support' and then I can not format or do anything because the phone will crash and loop in Android logo. But after forced reboot It maybe works normally or still crash. I tried to format the card to ext4 but problem still just with a lower probability.
The original lineage os provided by remi4x's treble's author doesn't have such problem.
I don't know if my device's only problem or a generic one.
And I don't know what logs I can provide to help.
The stock los just from https://forum.xda-developers.com/xiaomi-redmi-4x/development/treble-lineageos-15-1-beta-t3790991

Thanks for the dev's hard work and I hope any can help with this problem.

add a bug:
When enable power save, the image with launcher3 will have a launcher crash. other launchers don't have such prob.
 
Last edited:

bieltv3

Senior Member
Jun 12, 2012
1,299
9,879
Barcelona
For God's Sake!

I do not have the words to express my feelings on this. I am bieltv.3 and I was a young developer for CyanogenMod (KitKat version). Once we started developing custom ROMs, every device had their different drivers, their different camera sensors, different display configurations, closed common .so libraries... All the makefiles were full of if-else depending on each device you were building the ROM for.

I was fighting to bring Ice Cream Sandwich, the first Android OS made for armv7 devices to old armv6 ones... Years of work to make every driver to work... I do remember how we manage to write the whole .c camera library for a SAMSUNG device.

Seen the major improvement on development, as well as the chance for a united project for AOSP for most major devices running oreo makes me cry of joyness. Congratulations to the man in charge @phhusson and GOOGLE for being so smart on this...

I stopped developing ROMs when Cyanogen broke, but I think it may be time to contribute to this major project. It has given me the day! Will be buying soon an S9 and getting on to it asap.
 

St.Noigel

Senior Member
Mar 7, 2013
1,044
320
Ivano-Frankivsk
I have a Moto G6+ which has no real dev support! It probably never will because Moto/Lenovo chose not to release it in the US. Thanks to Gsi I can flash custom roms and thanks to Phh almost everything works. Fingerprint scanner does not work but Phh is working on it which makes since to do since other devices will surely use the same hardware for the fingerprint scanner at some point. At that point Bluetooth is the only thing partially broken that I have noticed. I can hear certain things through Bluetooth but not music. There are probably other things broken but in my 10 years of android modding that's pretty much always been the case. Hasn't stopped many people from enjoying roms to daily driver status. So if my somewhat obscure device can be mostly supported through the Gsi concept when no one wants to dev for the specific device, tell me how Gsi is a bad thing?

Sent from my moto g(6) plus using Tapatalk

I have the same issues on my Sharp Aquos S2 (SD630 too) on AOSP, RR, AICP, Havoc... (
Do you have sollution already?
 

Rainick

Member
Jul 28, 2018
5
0
hi phhusson,thank you for you great work,this is really amazing.
but when i used it on huawei honor 8,i found the camera and flash light are not available,it said "can not contact camera."
i tested camera on LINEAGE and it worked pretty well, so i don't think it's hardware problem.
i hope you will fix this problem and i will keep focusing on this program.

add:i download system.img for A-only ARM64 devices with GApps and SU
 
Last edited:

Wirtos

Member
Dec 13, 2016
25
13
Just a few bugs on Redmi Note 4: time resetting to 00:30 after every reboot and apps not installing via Google play Market.
Sometimes, when i trying to install some apps, it's just showing "waiting for download" sign forever. Reboot fixes download bug, but it's randomly appearing after some time.
 

CosmicDan

Senior Member
Jun 19, 2009
5,862
7,697
34
Sydney
Xiaomi Poco F1
i flashed liniageOS and extracted the camera into apk,it can work on lineageOS,but still crashed on this AOSP.
i think it may be camera drive's problem

It's a Vendor problem.

Reach out to your device development forum for developers to make a GSI Patch.

It's unreasonable to wait for Phh to try and fix every ODM's crappy Treble implementation, especially if he doesn't even have the device.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 437
    WARNING: You'll most probably loose ALL your data, and might break your phone. Please use with extreme caution!

    The goal of this ROM is to provide full Treble-compatible hardware support, and nothing else.
    This means that hardware which DON'T have Treble API won't be supported, like Essential's external camera.
    No feature will be added. This will ease forward porting to new Android versions, which is the very goal of Project Treble :)

    My hope is that other ROM developers will use this ROM as a basis to construct more advanced ROM.

    For a list of supported devices, consult and fill https://github.com/phhusson/treble_experimentations/wiki

    How to flash:
    Follow instructions available at https://www.xda-developers.com/flash-generic-system-image-project-treble-device/

    Changelog
    v29 (2019-03-06):
    - March security patch
    - Fix MT6739 incoming SMS and mobile data

    v27 (2019-01-08):
    - January security patch
    - arm32_binder64 variant
    - Minor stuff

    v25 (2018-09-07)
    - September security patch
    - [Mi 6X/Mi Pad 4] Fix backlight
    - [Mi Mix 2S] Disable fingerprint button behaviour
    - [Galaxy S9/Note 9]
    - Fix (some) MTK incoming call
    - Fix a2dp on some devices
    - Fix boot on some devices

    v23 (2018-08-07):
    - August security patch
    - Fixes tethering on some Qualcomm devices (Thanks @notsyncing)
    - Enable Ambient Display for everyone
    - Add an off-computer flasher (first step towards OTA)
    - Fixes MTP
    - Fixes fingerprint on Moto devices
    - Change Huawei quick charge based on device (Thanks @Dil3mm4 )
    - Fixes camera on Moto devices
    - Fix notches height for some devices (Thanks @tadiT7)

    v22 (2018-07-03):
    - July security patches
    - Fixes Samsung Galaxy S9 fingerprint enrollment
    - Fix in-call audio for Pixel 2
    - Disable night mode on some MTK for which it is very slow
    - Fix wifi tethering on some configurations

    v21 (2018-06-27):
    - [OnePlus 6] Fix booting on A slot
    - [OnePlus 6] Fix userdata filesystem size
    - [OnePlus 6] Include a framework-res overlay (fixes auto backlight, improve battery-life, ...)
    - Fix status bar height for notches on various devices (Thanks @tadiT7)
    - [Samsung Galaxy S9 Qualcomm] Fix backlight
    - Fix webview in Android Go variant
    - Fix audio jack for some devices
    - Fix H264 encoding on Huawei (Thanks @OldDroid)
    - Fix backlight on some SDM845 devices (Xiaomi Mi Mix 2S, Xiaomi Mi8)

    v20 (2018-06-07):
    - June Android security patch level
    - New experimental FLOSS variant (check sources for list of apps)
    - [OnePlus6] Fixes backlight
    - [OnePlus6] Partial support for DnD slider
    - Fixes bug on some A/B devices where device would stop booting after several success

    v19 (2018-06-03):
    - Huawei fast charge (Thanks @flex1911 and @OldDroid)
    - Fix MTK TrustKernel TEE (those devices will need to factory reset!)
    - Support 32bits Android 8.0 devices
    - Rewrite Security Patch Level for Android 8.1 devices, and A/B devices as well. Should fix boot for some devices.
    - Enable GPU profiling on Huawei devices to fix UI glitches
    - Fixed Modded Google Camera installation
    - Use round icons
    - Enable doze
    - New Android Go variant
    - On Huawei devices add "Swipe fingerprint for notifications" option
    - Releases are now compressed with xz. Uncompress before flashing.

    v18 (2018-05-14):
    - Update to Android Security Patch level 2018-05-01
    - Disable HW keystore on mediatek devices using trustedkernel, until it is fixed
    - Re-enable Huawei navigation keys (Thanks @LuK1337 and OpenKirin team)
    - Fixes android build version/security patch level (might lead to stuck on bootanimation some devices)
    - Enable NightMode for everyone
    - Enable automatic backlight with Huawei Mate 9 settings on Huawei devices
    - Remove unnecessary warning on boot (if you still get it, it means it is useful, to tell me!)
    - Include android.system.net.netd, fixes data connection for several Qualcomm devices

    v17: (2018-04-24)
    - Fixes multimedia from SDCard
    - Fixes in-call audio for Qualcomm devices
    - Fixes in-call earpiece/speaker for Foxconn/Qualcomm devices (Razer Phone, Sharp Aquos S2, ...)
    - Fixes signal level for Huawei devices (Thanks to OpenKirin team)
    - Fixes boot on some A-only devices (HTC U11+, Xperia XZ1 at least)
    - Report vendor's security patch level instead of framework security patch level
    - Fix fsck for f2fs (Thanks @flex1911 and @LuK1337)

    v16: (2018-04-05)
    - Fixes MTP access to sdcard
    - v15 was missing graphical glitches fix. Applied it again.
    - Resize /system to maximum size on first boot

    v15: (2018-04-03)
    - Update to 2018-04-01 security patches
    - Fixes FAT sdcards
    - Fixes some USB-C headphones on some devices
    - Fix Essential PH-1 boot

    v14: (2018-03-26)
    - Fixes Galaxy S9(+) backlight control

    v13: (2018-03-23)
    - Disable Android's fake touches, which made unlocking hard
    - Fixes Galaxy S9 boot and WiFi
    - Make system.img back to 1.5GB
    - Disable again adb auth, to help debugging

    v12: (2018-03-05)
    - Updated to security patch 2018-03-01
    - Various stability, behind-the scene, changes
    - Fixes camera on MTK devices
    - Support ARM32 devices
    - Supports HW button backlight

    v11: (2018-02-20):
    - Fixes bluetooth on Kirin 970 devices (Thanks @LuK1337)
    - Fixes sdcard on Huawei devices
    - Includes nfc-nci.conf, should fix NFC on some devices
    - Show real Android version (Thanks @LuK1337)
    - Enable ADB authentification

    v10: (2018-02-18)
    - Android 8.1 !
    - Includes versioned vndk, so devices running both 8.1 and 8.0 should work

    v9: (2018/01/15)
    - Include the compositing fixes for Kirin 970
    - Crude support for Huawei fingerprint gestures (click = home, left = back, right = voice assistant, up = quick settings, down = notifications, long press = recent apps)

    v8: (2018/01/14)
    - Huawei compositing fixes (fixes various graphical glitches)
    - Various su SELinux fixes

    v7: (2017/12/30)
    - Fixes various regressions (APNs, A/B, vanilla, fingerprint ...)
    - Fixes dev/input requirement (not useful to any real-life product yet, afaik)
    - Fixes some not-installable applications from Play Store
    - Fixed substratum in phh's superuser

    v6: (2017/12/19)
    - Major code clean-up. Please report regressions
    - Fixes random reboot on Huawei devices
    - Optionally includes SU (you need to install phh's SuperUser from F-Droid/Play Store)

    v5: (2017/12/14)
    - Fixes FDE decryption (SystemUI was crashing in loop)
    - Use a real list of APNs
    - Include Chrome and Gboard (fixes IME crash when trying to input a symbol)
    - Fixes SEPolicy for Hardware Overlay Picker (should fix crash of Hardware Overlay Picker on startup)

    v4: (2017/12/10)
    - Fixes sdcard in MTP
    - Fixes Dual-SIM
    - Includes hardware-specific overlays:
    - Enable 4G selection in networks
    - Bigger status bar on Essential PH-1
    - Enable navigation bar on HTC U11+

    v3: (2017/12/04)
    - Fixes sdcard in MTP build fail, so will be fixed in next release
    - New variant including gapps

    v2: (2017/11/26)
    - Fix wifi tethering
    - Fix F2FS userdata
    - Fix sdcard
    - Fix fingerprint (Huawei)

    Download:
    https://github.com/phhusson/treble_experimentations/releases/download/v29

    Want to chat about this project? Go to Freenode IRC, #phh-treble.
    IRC: irc://irc.freenode.net/#phh-treble
    WebIRC: http://webchat.freenode.net/?channels=#phh-treble&uio=d4
    Matrix: #freenode_#phh-treble:matrix.org

    Other chatrooms:
    Telegram https://t.me/phhtreble

    Thanks @MishaalRahman and @Exelios for the huge kickstart help

    Thanks to all my donators:
    - @Exelios

    - @fargonaz
    - @VictorM86
    - @howdid
    - @heatfire
    - @ohwarumbloss
    - @RexGoogolplex
    - @abhas.abhia
    - @Emoclaw
    - @Sebianoti
    - @DocRambone
    - @egandt
    - @Blackbird1997
    - @Burakki
    - @josdehaes
    - @TheUndertaker21

    Thanks to the following companies:
    - Huawei, for a Huawei View 10
    - Blackview, for a Blackview A20

    PS: Yes the name sucks, but I'm clueless about a name
    114
    How to know if your phone is supported:

    - Does your OEM provides a stock Oreo ROM?
    No ===> Your phone is not supported
    - Run Treble Check on stock Oreo ROM. Does it say Treble is supported?
    No ===> Your phone is not supported

    If all answers are yes, then your phone MIGHT be supported.
    Test it, and report the result!
    76
    Build script available at https://github.com/phhusson/treble_experimentations/blob/master/build.sh

    Current status:

    Over-all:

    Xperia XZ1:
    - Broken camera (because of Sony's DRM)

    Huawei Mate 9 Pro and Honor 9:
    - Fingerprint sensor should have "home" behaviour
    - software keys should be disabled

    Known end-user problems (WON'T BE FIXED in this ROM):
    - No exfat
    70
    Known mess:
    - A-only should use https://android-review.googlesource.com/q/hashtag:"non-ab-boot-gsi"+(status:open OR status:merged) instead of dm-verity hacks
    - the dm-verity work-around is also needed on A/B, so other patches are missing, for some other reason
    - On A/B devices, this system.img effectively transforms the device into a userdebug build. This means adb root works!
    adb root should work on A-only later too, though it requires that the OEM includes https://android-review.googlesource.com/q/topic:move-adbd-to-system+(status:open+OR+status:merged)
    This can probably be worked-around by moving adbd inside a /system/etc/init/xxx.rc
    - ADB auth is totally disabled at the moment on A/B, this is bad, but useful for debugging.
    - Huawei (for instance Mate 9) doesn't declare android.hardware.fingerprint. This ROM does it for them, but this need to be better implemented
    - SuperSU and Magisk screws with SELinux policy. DO NOT USE SuperSU OR Magisk WITH THIS ROM
    31
    There, I released my first Android 8.1 version.
    Overall, I consider it less stable than 8.0, but I think it should be usable.

    For the known limitations:
    - On MTK, camera doesn't work
    - On Huawei, I could get Huawei stock app to run

    And Download manager is still broken, so you still have to kill play store every time you want to download an app...

    Dirty flash should work, but I barely tested it.

    It took me a lot of effort, so please enjoy :)
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone