[AOSP 9.0] [2019-08-25] Phh-Treble

[lahaina]

Internal Storage and Notch problem

Hi! I tried this GSI ROM on Umidigi One and found some bugs.


First, the built-in storage of this mobile phone has about 32GB, but it was reduced to 4GB after installing this ROM.
So when I flashed to factory ROM, it returned to 32GB.


Second, the status bar ignored notch. This covering some content on the screen.
I saw about can support notch by applying overlay at vendor, is this correct?

I'm a beginner so I'm very confused.
How to fix these problems?? Please tell me the tutorial.

Sorry my bad English, I wrote from Japan using Google Translate...

 

[Dzol Cp]

Hi! I tried this GSI ROM on Umidigi One and found some bugs.


First, the built-in storage of this mobile phone has about 32GB, but it was reduced to 4GB after installing this ROM.
So when I flashed to factory ROM, it returned to 32GB.


Second, the status bar ignored notch. This covering some content on the screen.
I saw about can support notch by applying overlay at vendor, is this correct?

I'm a beginner so I'm very confused.
How to fix these problems?? Please tell me the tutorial.

Sorry my bad English, I wrote from Japan using Google Translate...

Hi dude, how you flash your ROM? Do you successfully boot this ROM on your phone? Are you using TWRP Recovery with PT support, if yes there shouldn't be any problem for your system partition. Just try some module from Magisk for your overlay, if you talking about vendor msg on startup, just ignore that.

I just using this latest buildon my Xiaomi Mi3, I really love it, so smooth, only the major bug for me is when call in/ call out , speaker and loudspeaker is not working as I get the msg that my device is not supported and phone call may not work properly. Network signal show only 3G connection, but after I test and setup my local APN service for 4G , the data connection was so faster, only show at signal is 3G.
That's it, overall, i really miss to use this ROM for my daily driver, battery management was so awesome.. Only the bug as I wrote before.

Thanks Dev @phhusson :highfive:

 

[kev1807]

I used system-arm64-aonly-gapps-su.img.xz

I'm running it on a M5 8.4 with no issues whatsoever, Netflix is fine, no media errors you describe. I'm on the 185 base, full wipe and flashed the system via recovery (didn't go the TWRP route, too many bricked devices on the unofficial build.). After flashing wiped cache and formatted data in recovery (don't recall the fastboot commands that did this).

The only issues I found. Keep an eye on the flashing process, I had errors from a specific cable on a usb2 port. Switched to s different cable and different vport on the PC and it was fine.

Once you are up and running, you will likely see font rendering blurryness, there is a setting in phh treble settings to fix this.

I installed magisk once everything was working, I disabled the built in su app, as it complained about bring out of date (don't remove it, just disable). There is a build.prop setting tweak to get Google assistant.

My device is now behaving perfectly and works and looks like a pixel tablet. Very pleased indeed.

Ich am in a Huawei Mediapark M5 Pro but switched Back Go 8.1 for now....
Can you Look vor Widevine Level, please?

 

[fargonaz]

Cool. You're right, no twrp, was advised it wasn't stable for m5? Just used adb/fastboot for all.

Can you give me a link for a good guide?

As soon as I booted in the pop up started so didn't bother setting anything up, I'll just wipe again.

Even with it back to factory spec Netflix now won't install. Says wrong version...

M5 8.4 doesn't support twrp though, followed OP to the letter, used adb/fastboot. I'll try fastboot -w.

The one in the M5 recovery thread works well enough, no, it's not 100%.
https://xdaforums.com/mediapad-m5/development/recovery-twrp-3-2-2-1-t3813825

It won't install gapps, so there's that.

 

[Smart Ru]

HTC U11 failed to boot after about half min,the AOSP logo appeared, and then the device screen turned into black,finally, it enter the bootloader mode
The log:https://drive.google.com/open?id=1fzOGhcXrLyDtQyT5QkrX1hI0IlLH-7WD

 

[DeeZZ_NuuZZ]

HTC U11 failed to boot after about half min,the AOSP logo appeared, and then the device screen turned into black,finally, it enter the bootloader mode
The log:https://drive.google.com/open?id=1fzOGhcXrLyDtQyT5QkrX1hI0IlLH-7WD

Wait you've flashed an aosp GSI on a non-gsi/non-treble phone? You're insane man ?
Get a RUU and don't try a GSI rom on a non-gsi/non-treble phone ....

Sent from my HTC U12+ using XDA Labs

 

[JBolho]

Hi dude, how you flash your ROM? Do you successfully boot this ROM on your phone? Are you using TWRP Recovery with PT support, if yes there shouldn't be any problem for your system partition. Just try some module from Magisk for your overlay, if you talking about vendor msg on startup, just ignore that.

I just using this latest buildon my Xiaomi Mi3, I really love it, so smooth, only the major bug for me is when call in/ call out , speaker and loudspeaker is not working as I get the msg that my device is not supported and phone call may not work properly. Network signal show only 3G connection, but after I test and setup my local APN service for 4G , the data connection was so faster, only show at signal is 3G.
That's it, overall, i really miss to use this ROM for my daily driver, battery management was so awesome.. Only the bug as I wrote before.

Thanks Dev @phhusson :highfive:

What are you saying regarding network bands? Mi3 is a 3G only device with a 21Mbps max download capability modem. It is not and never was 4G. And why use Treble when you have a full Pie rom for your device that is likely much more compatible? Heavy bugs are to be expected on a device that old (Snap800 was awesome but now it's just an outdated 32bit flagship), that is only Treble compatible thanks to a "hack". It may work, but the risks are much bigger than on a native Treble device with current hardware.

 

[swiftbones74]

Wait you've flashed an aosp GSI on a non-gsi/non-treble phone? You're insane man ?
Get a RUU and don't try a GSI rom on a non-gsi/non-treble phone ....

:good:

 

[NisseGurra]

How to solve the sleep of death?, My S9+ runs this GSI nicely but every time screen shuts of the phone locks up and need to be restarted to wake up the screen

 

[Dzol Cp]

What are you saying regarding network bands? Mi3 is a 3G only device with a 21Mbps max download capability modem. It is not and never was 4G. And why use Treble when you have a full Pie rom for your device that is likely much more compatible? Heavy bugs are to be expected on a device that old (Snap800 was awesome but now it's just an outdated 32bit flagship), that is only Treble compatible thanks to a "hack". It may work, but the risks are much bigger than on a native Treble device with current hardware.

Yeah bro you're exactly right, Mi3 is only 3G devices, which to H+ will appear, like I said, the connection is faster, only at signal shown 3G, I know what you mean, I have try Aosp Pie for my Mi3, pretty stable but battery is draining so fast as you even wonder I just back to addiction of flashing, as this time that GSI is all about.

H+ and 3G

 

[fattymcdirty]

Uh.. what's the changelog for 1.08 from yesterday?

 

[heisenberg17]

SOD Killer

How to solve the sleep of death?, My S9+ runs this GSI nicely but every time screen shuts of the phone locks up and need to be restarted to wake up the screen

There's an app at Play Store to fix that. It's called "SOD Killer (Sleep of Death)".

Also, may I ask: Is your S9+ Exynos or Snapdragon (G9650)?

 

[NisseGurra]

There's an app at Play Store to fix that. It's called "SOD Killer (Sleep of Death)".

Also, may I ask: Is your S9+ Exynos or Snapdragon (G9650)?

S9+ exynos, i found the cause: Magisk triggered the bug, no magisk and all fine.

 

[rooban90]

Fingerprint sensor is not working in Redmi 6 pro indian version with v108

Edit: reinstalled after 10.0.2.0 update. Fingerprint is working fine with v108 now.
Also v108 fixed screen blink issue and brightness slider issue.
Onl volte is not working

 

[darren1]

Uh.. what's the changelog for 1.08 from yesterday?

You can find it on Github here

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

 

[phhusson]

You can find it on Github here

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

I've also copy/pasted it to OP

 

[requiiiem]

I've also copy/pasted it to OP

Thanks! Moto E5 glitches are fixed? In op he says not yet.

Sent from my E5 Plus using XDA Labs

 

[eoghan2t7]

I've also copy/pasted it to OP

Have you been able to fix the slow FPS on the razer phone. When I installed this GSI it doesn't seem to have 120hz enabled by default like the Oreo flavour of gsi's? Other than that everything worked from what I can remember.

 

[phhusson]

Thanks! Moto E5 glitches are fixed? In op he says not yet.

Well, the glitch is fixed (that's the fix for snapdragon in the changelog), but current version no longer boots, so take your pick.
But you can just add debug.hwui.renderer=opengl in your /system/build.prop to fix it on old build.

Have you been able to fix the slow FPS on the razer phone. When I installed this GSI it doesn't seem to have 120hz enabled by default like the Oreo flavour of gsi's? Other than that everything worked from what I can remember.

I can say for sure that the FPS is higher on Razer Phone running my Pie GSI (I still have the wow feeling I pick it up), than on any other phone running my Pie GSI, so the 120Hz is enabled, that's without doubt.
Please note that there is an option (FPS Divisor) in phh-treble settings to reduce FPS (to lower power consumption). Double-check that you have this set to the lowest value.
Now, it is possible that the UI is globally slower on Pie than on Oreo, and since I'm merely comparing various devices running Pie, I wouldn't notice a regression.

 

[jc1986]

Mi Max 3 user here. Booted successfully and flashed magisk. Quick Charge only seems to work for a few seconds but if I use a regular charger it works. No matter which image I flash whether Vanilla only or with Gapps & SU. But its working fine with Havoc 2.0 and Pixel Dust. Does anyone have the sane issue as mine?