Database Develop

Android P Treble GSI

Has anybody tried the Android P DP4 GSI on the Xiaomi Mi 8/ Mi 8 SE?
Couldn't get the treble P GSI to boot on my Mi 8 SE but I managed to get the Oreo GSI running (doesn't have notch support though).

PravAndroidGeek said:
Has anybody tried the Android P DP4 GSI on the Xiaomi Mi 8/ Mi 8 SE?
Couldn't get the treble P GSI to boot on my Mi 8 SE but I managed to get the Oreo GSI running (doesn't have notch support though).
Click to expand...
Click to collapse
Which GSI booted on your SE?
Other Mi8 SE users reported that every GSI they flashes resulted in a bootloop.
Can you also mention the last MIUI version you had when you flashed a GSI?
As for P, you tried the semi-GSI, right?
Some people said that they had to fix things themselves for the image to boot but did you try flashing Magisk or setting Selinux to permissive? There should be a "permissiver" zip on the P gsi thread if I'm not mistaken.
dm-verity and selinux could cause a bootloop.

The Marionette said:
Which GSI booted on your SE?
Other Mi8 SE users reported that every GSI they flashes resulted in a bootloop.
Can you also mention the last MIUI version you had when you flashed a GSI?
As for P, you tried the semi-GSI, right?
Some people said that they had to fix things themselves for the image to boot but did you try flashing Magisk or setting Selinux to permissive? There should be a "permissiver" zip on the P gsi thread if I'm not mistaken.
dm-verity and selinux could cause a bootloop.
Click to expand...
Click to collapse
Got my Mi8 SE running MIUI 9 Chinese.
Unlocked the bootloader and flashed the latest Xiaomi.EU MIUI 10 ROM as a base and then tried both: GSI for phh-Treble AOSP and Resurrection Remix phh-Treble. Both worked surprisingly well, the notch being detected was the main issue. I followed this guide on xda.
Yes it was the P semi-GSI that resulted in a bootloop. Might try the permissiver zip.

PravAndroidGeek said:
Got my Mi8 SE running MIUI 9 Chinese.
Unlocked the bootloader and flashed the latest Xiaomi.EU MIUI 10 ROM as a base and then tried both: GSI for phh-Treble AOSP and Resurrection Remix phh-Treble. Both worked surprisingly well, the notch being detected was the main issue. I followed this guide on xda.
Yes it was the P semi-GSI that resulted in a bootloop. Might try the permissiver zip.
Click to expand...
Click to collapse
Tell us how it works out [emoji846]
Skickat från min MI 8 via Tapatalk

PravAndroidGeek said:
Got my Mi8 SE running MIUI 9 Chinese.
Unlocked the bootloader and flashed the latest Xiaomi.EU MIUI 10 ROM as a base and then tried both: GSI for phh-Treble AOSP and Resurrection Remix phh-Treble. Both worked surprisingly well, the notch being detected was the main issue. I followed this guide on xda.
Yes it was the P semi-GSI that resulted in a bootloop. Might try the permissiver zip.
Click to expand...
Click to collapse
Been wanting to get the 8 se, but I've been waiting to hear if phh-treble and other GSIs work before buying. other than notch problems are there any other major issues? Once P is released and phh-treble is updated to android 9 the notch won't be a problem anymore due to AOSP notch support.

Running lineage GSI on SE too without issues (except some full screen apps which do not support notch). The minimum brightness is a bit high.

Ydraulikos said:
Running lineage GSI on SE too without issues (except some full screen apps which do not support notch). The minimum brightness is a bit high.
Click to expand...
Click to collapse
Can you point me to a guide to run Lineage os or RR on out SE?
I am familiar in flashing custom for many years but i am new to treble and just heard about it.

Unlock your bootloader, flash a TWRP and format your data partition. Then flash and try to boot the latest xiaomi.eu rom. If you succeed, format /data /system /cache and flash /system with an arm64 GSI for A only devices such as https://github.com/phhusson/treble_...d/lineage-v21/system-arm64-aonly-gapps-su.img

Ydraulikos said:
Unlock your bootloader, flash a TWRP and format your data partition. Then flash and try to boot the latest xiaomi.eu rom. If you succeed, format /data /system /cache and flash /system with an arm64 GSI for A only devices such as https://github.com/phhusson/treble_...d/lineage-v21/system-arm64-aonly-gapps-su.img
Click to expand...
Click to collapse
ok, i am running xiaomi.eu rom so thats allready done.
The img i download is allready the lineage os, what i see
And is there a completely different forum/site where just. only trebel based custom roms are stored and discussed.
Is it gapps included, because normally it has to be flashed separtly.
Can you just format and go back to any miui rom, and when wanted to trebel based, just flash img file in /system again
Sorry for all the questions

marcel112 said:
ok, i am running xiaomi.eu rom so thats allready done.
The img i download is allready the lineage os, what i see
And is there a completely different forum/site where just. only trebel based custom roms are stored and discussed.
Is it gapps included, because normally it has to be flashed separtly.
Can you just format and go back to any miui rom, and when wanted to trebel based, just flash img file in /system again
Sorry for all the questions
Click to expand...
Click to collapse
Gapps are included in the above link. You don't need to flash anything else. And yes you can always flash the stock rom. Just remember to erase /data when you change between MIUI & AOSP based ROMs.

Ydraulikos said:
Gapps are included in the above link. You don't need to flash anything else. And yes you can always flash the stock rom. Just remember to erase /data when you change between MIUI & AOSP based ROMs.
Click to expand...
Click to collapse
ok, so its like normal business.
Normally when i switch between custom i allways full wipe
/dalvik
/data
/cache
/system
As long as format data was once, i dont have problem..
Can you provide links for more like RR for SE?
I didnt knew there was development at all for SE on custom roms
EDIT: https://forum.xda-developers.com/pr...opment/resurrection-remix-phh-treble-t3767688
this one is for RR, and if i am correct you linked me to the first in the V5 section, so the xiaomi mi 8 se is a ARM64 A-only device?
But what is the difference between gapps and vanilla

marcel112 said:
ok, so its like normal business.
Normally when i switch between custom i allways full wipe
/dalvik
/data
/cache
/system
As long as format data was once, i dont have problem..
Can you provide links for more like RR for SE?
I didnt knew there was development at all for SE on custom roms
EDIT: https://forum.xda-developers.com/pr...opment/resurrection-remix-phh-treble-t3767688
this one is for RR, and if i am correct you linked me to the first in the V5 section, so the xiaomi mi 8 se is a ARM64 A-only device?
But what is the difference between gapps and vanilla
Click to expand...
Click to collapse
Gapps include google services, vanilla does not.
Mi 8/SE are ARM64 A-only devices. You can try flashing any treble based rom with a high chance to operate normally. With a decent treble implementation, there is no need for custom rom development. The device specific blobs are moved to a separate partition and are provided by vendor.

Ydraulikos said:
Running lineage GSI on SE too without issues (except some full screen apps which do not support notch). The minimum brightness is a bit high.
Click to expand...
Click to collapse
Does the system detect the notch on lineage?

Ydraulikos said:
Gapps include google services, vanilla does not.
Mi 8/SE are ARM64 A-only devices. You can try flashing any treble based rom with a high chance to operate normally. With a decent treble implementation, there is no need for custom rom development. The device specific blobs are moved to a separate partition and are provided by vendor.
Click to expand...
Click to collapse
i did full wipe,
after that i tried to install image, but as what do i need to flash this?
system image
boot
recovery
vendor image
firmware
persist
splash
logo
etc etc?
i choose system image, but after flash ( was quick ) i get no OS?
edit: so i can flash anyone off this page, as long as i use arm64 Aonly for my Mi 8 SE?
edit 2: got it..
install is real fast, and phone is very quick
after trying treble...
i tried to go back to miui backup..
It boots fine, but i cant get past pin code?
I know 100% its the right code, does it have to do with trying treble?

PravAndroidGeek said:
Has anybody tried the Android P DP4 GSI on the Xiaomi Mi 8/ Mi 8 SE?
Couldn't get the treble P GSI to boot on my Mi 8 SE but I managed to get the Oreo GSI running (doesn't have notch support though).
Click to expand...
Click to collapse
MI8 is also same.
P GSI (can't boot)
RR oreo rom (all working)
- last MIUI verion : XIAOMI.EU 8.7.19 version.

jectsin said:
MI8 is also same.
P GSI (can't boot)
RR oreo rom (all working)
- last MIUI verion : XIAOMI.EU 8.7.19 version.
Click to expand...
Click to collapse
Everything works on RR? How is the camera?

_katho_ said:
Everything works on RR? How is the camera?
Click to expand...
Click to collapse
work. but bad quality

jectsin said:
work. but bad quality
Click to expand...
Click to collapse
yes and notch is not detected for me

marcel112 said:
yes and notch is not detected for me
Click to expand...
Click to collapse
Notches are "expected" on AOSP only with P and newer Android versions.
It probably can be modded but since P is around the corner, it might not be worth it.

The Marionette said:
Notches are "expected" on AOSP only with P and newer Android versions.
It probably can be modded but since P is around the corner, it might not be worth it.
Click to expand...
Click to collapse
i know this is not miui forum, but i made twrp backup..
Why cant i unlock after restoring after flashing Treble based roms ?
I tried yesterday 3 trebles and full wiped, and restored nandroid of miui 10.
All looks good, but after boot up, i cant get past pincode( i know its right code 110% )

ROG II is apparently fully Project Treble complaint. Has anyone flashed AOSP roms?

I saw a blogspam here - https://www.getdroidtips.com/download-and-install-aosp-android-10-gsi-for-asus-rog-phone-2/ that reminded me our device is Project Treble compliant so it should be able to use Generic System Images. Has anyone gotten one to work properly?
Prior (somewhat heated) discussion here about a particular GSI image - https://forum.xda-developers.com/rog-phone-2/help/brave-to-try-project-treble-upgrade-to-t3993641
Screenshot from Treble Info app by Hackintosh Five

People tried (including me), there is already a thread here: https://forum.xda-developers.com/rog-phone-2/how-to/guide-install-gsi-image-google-apps-t3998133
Also Android 11 GSI thread here: https://forum.xda-developers.com/rog-phone-2/how-to/android-11-developer-preview-t4053895
Here is my report of some bugs I found yesterday on HavocOS (A10) GSI: https://forum.xda-developers.com/showpost.php?p=81841237&postcount=195
Do not expect any device specific features like back led, higher refresh rates or air trigger support.
Both recoveries available for our device fail to install gapps (error 255 - Insufficient Space Available in System Partition) without modifying the installer.sh script. So either that or find a GSI image with gapps included.

Maczuga said:
... find a GSI image with gapps included.
Click to expand...
Click to collapse
Is there one you recommend? Does any stuff break other than 120hz refresh? Does VoLTE or VoWIFI work?

skrowl said:
Is there one you recommend?
Click to expand...
Click to collapse
If you are ready to face some bugs: https://forum.xda-developers.com/pr...iscussion/gsi-expressluke-built-gsis-t4003457
There is a gapps version of havoc os 3.2 which I tested yesterday.
However I was way more satisfied with RR based on Pie, but that required modifying the gapps installer.sh file to force AB structure, gapps were discovering device as some other partition type.
EvolutionX 4 didn't boot for me. Same with crDroid from some other source.
Dunno about any volte / vowifi and such staff. It's not really a thing in my country. The most annoying thing were all the color modifications being broken - so I could not adjust screen contract, enable reading mode, set grayscale from digital wellbeing. Also you are forced to use side USB port for any actions other than charging. Bottom one only worked for charging, and I didn't even test the charging speed.
All those bugs I have experienced occurred both on Android 9 and 10

GSI flashing on k20 pro

Can someone give me a process on how can i boot gsi images on my k20 pro.
Any gsi images..

Do you already know?

Dimasik137 said:
Do you already know?
Click to expand...
Click to collapse
nope i tried some gsi with fcrypt disabler but they didn't boot so just left trying.

Ezio553 said:
nope i tried some gsi with fcrypt disabler but they didn't boot so just left trying.
Click to expand...
Click to collapse
Same thing, i tried to install Flyme

Dimasik137 said:
Same thing, i tried to install Flyme
Click to expand...
Click to collapse
Yeah now i don't know but there should be some modifications needed to boot gsi on this phone or maybe an older vendor might be required i am not sure but i have never tried booting gsi with miui vendors only v12 vendors and oss vendor probably will never boot any gsi directly

you need android 11 vendor from MIUI 12.5. Android 10 vendor are borked that you can't use it for booting GSI ROMs. Just download MIUI 12.5 recovery ROM and delete everything except vendor.

Kursem said:
you need android 11 vendor from MIUI 12.5. Android 10 vendor are borked that you can't use it for booting GSI ROMs. Just download MIUI 12.5 recovery ROM and delete everything except vendor.
Click to expand...
Click to collapse
Ok so that means i can even use eu roms vendor to boot gsis .

Ezio553 said:
Ok so that means i can even use eu roms vendor to boot gsis .
Click to expand...
Click to collapse
yep, as long as it's based on Android 11

Kursem said:
yep, as long as it's based on Android 11
Click to expand...
Click to collapse
Ok i will test out this.

[Magisk Module] Enable RAW capture for GCam

This Module enables RAW Capture on the Galaxy A30, and changes the camera Hardware Level from Limited to Full.
RAW Capture is required for most GCams to work.
For information about GCam, go to this thread. It's for the A20, but contains useful information.
Click to expand...
Click to collapse
How does it work?
It works by replacing the library located at /vendor/lib/libexynoscamera3.so with an edited one. For reverse engineering enthusiasts, here is the patch applied to the library.
Prerequisites
- Magisk v20.4 or newer
- Android 11 vendor and kernel (Not compatible with versions of the Eureka Kernel older than 9.0)
Installation
Install as a normal Magisk Module, through Magisk Manager or TWRP.
Troubleshooting
Camera doesn't work, shows Black Screen
Make sure you are using a compatible Android 11 kernel and vendor.
If this issue is happening after updating your firmware, please let me know.
Telegram
GitHub
Download

Does this work with aosp based roms? Or is it just one UI?

Borkode said:
Does this work with aosp based roms? Or is it just one UI?
Click to expand...
Click to collapse
Yes, it works with AOSP.

What kernel you recommend to use in gsi ROM with this module?

SirKosichka said:
What kernel you recommend to use in gsi ROM with this module?
Click to expand...
Click to collapse
I don't know much about kernels for the A30. In my A20 with an Android 12 GSI i use stock kernel with some small modifications (dmverity disabled, MTP fixed for AOSP, etc.)

TBM 13 said:
I don't know much about kernels for the A30. In my A20 with an Android 12 GSI i use stock kernel with some small modifications (dmverity disabled, MTP fixed for AOSP, etc.)
Click to expand...
Click to collapse
bro, you can enable 60fps FHD record for our devices?

Wow, that seems like an promising approach ! Keep up the good work.
Any chance the patcher can be extended to Galaxy S10/20/21 ? or is that a completely different topic ?

flunkyball said:
Wow, that seems like an promising approach ! Keep up the good work.
Any chance the patcher can be extended to Galaxy S10/20/21 ? or is that a completely different topic ?
Click to expand...
Click to collapse
Probably, I would have to check their libexynoscamera3.so library.

flunkyball said:
Wow, that seems like an promising approach ! Keep up the good work.
Any chance the patcher can be extended to Galaxy S10/20/21 ? or is that a completely different topic ?
Click to expand...
Click to collapse
I just checked the library of the Galaxy S10 and yes, it should be possible. However, doesn't it already support RAW?

TBM 13 said:
However, doesn't it already support RAW?
Click to expand...
Click to collapse
On the stock rom it probably does.
For the S10/20 on LOS only standard and wide lens are accessable whereas the telephoto is not.
On the S10 for LOS 17.1 I therefore had a patched "libexynoscamera3.so" as well granting access to telephoto lens via gcam.
However for LOS 18.1/19.0 or even for my new phone the S20 I was not able to find any patched libs anymore since nobody took the effort of reverse engineering it as you did.
Would you be willing to make the necessary adaption for your patcher to successfully enable raw on all lenses for LOS 18.1/19 on the S10/20 ?

flunkyball said:
On the stock rom it probably does.
For the S10/20 on LOS only standard and wide lens are accessable whereas the telephoto is not.
On the S10 for LOS 17.1 I therefore had a patched "libexynoscamera3.so" as well granting access to telephoto lens via gcam.
However for LOS 18.1/19.0 or even for my new phone the S20 I was not able to find any patched libs anymore since nobody took the effort of reverse engineering it as you did.
Would you be willing to make the necessary adaption for your patcher to successfully enable raw on all lenses for LOS 18.1/19 on the S10/20 ?
Click to expand...
Click to collapse
Sure. Do you have Telegram?

Bro, you can make this mod for Android 10 vendor?

SirKosichka said:
Bro, you can make this mod for Android 10 vendor?
Click to expand...
Click to collapse
Technically, yes. However, in the A20 enabling RAW in the Android 10 library makes the camera freeze after some seconds in apps like GCam.
If you are willing to test, i can do it, maybe the A30 doesn't have the same issue.

Bro will this mod work for Galaxy A30 (Android 11) ??
Edit: I'm sorry....for a moment I thought this mod for A20.....Sorry again.

Hridoyz said:
this mod work for Galaxy A30 (Android 11) ??
Click to expand...
Click to collapse
Yes, only on gsi or Oneui3.1 ROMs.You need ROM with 11 vendor

Version 2.1 of the module released, the biggest change is that there is no longer a need to change the Black Level in GCam settings, so GCams (or other camera apps) that don't have this option should now take photos without pink tint.
Full changes can be found here.

not work in A305f

Ali1412 said:
not work in A305f
Click to expand...
Click to collapse
That's not really helpful. What is happening to make you say it doesn't work, black screen? What ROM are you using? What kernel? What vendor, the one that comes with the ROM, stock Android 11 vendor or a custom one? What camera apps did you try?

TBM 13 said:
That's not really helpful. What is happening to make you say it doesn't work, black screen? What ROM are you using? What kernel? What vendor, the one that comes with the ROM, stock Android 11 vendor or a custom one? What camera apps did you try?
Click to expand...
Click to collapse
use stock rom and stock vendor and stock kernel android11 (ONE UI 3.1) and have black screen

Ali1412 said:
use stock rom and stock vendor and stock kernel android11 (ONE UI 3.1) and have black screen
Click to expand...
Click to collapse
on Snake OS 5 gcam support included

Question vendor_hardware_overlay

Does anyone have the vendor hardware overlay for the POCO M3 Pro / Redmi Note 10 5G? It says here you can create your own with linux, but I don't have access to a linux machine myself.

camellian it's fully supported by phhusson gsi. i think vendor overlay is not necessary. but if you want to try the only way is linux. you can install in dual boot on you pc. it's easy

wetito said:
camellian it's fully supported by phhusson gsi. i think vendor overlay is not necessary. but if you want to try the only way is linux. you can install in dual boot on you pc. it's easy
Click to expand...
Click to collapse
That wouldn't solve the problems with the screen brightness, then? If that's the case, it sucks because it's the only thing that doesn't work properly with the rom

has somebody check whether miui 13's vendor fixes the brightness issue?

sucius said:
That wouldn't solve the problems with the screen brightness, then? If that's the case, it sucks because it's the only thing that doesn't work properly with the rom
Click to expand...
Click to collapse
there's a fix to solve this. or wait future updates. or install a11 based gsi

wetito said:
there's a fix to solve this. or wait future updates. or install a11 based gsi
Click to expand...
Click to collapse
I'm currently using the fix but in low light conditions the screen will still go blank sometimes. I'll wait for future updates, then

wetito said:
camellian it's fully supported by phhusson gsi. i think vendor overlay is not necessary. but if you want to try the only way is linux. you can install in dual boot on you pc. it's easy
Click to expand...
Click to collapse
this phone not supported but note 10s
look this: https://github.com/phhusson/vendor_...pie/Xiaomi/RedmiNote10S/res/values/config.xml
The developer will get phuked because they add values for note 10 5g.

wetito said:
camellian it's fully supported by phhusson gsi. i think vendor overlay is not necessary. but if you want to try the only way is linux. you can install in dual boot on you pc. it's easy
Click to expand...
Click to collapse
Brightness bug

wetito said:
there's a fix to solve this. or wait future updates. or install a11 based gsi
Click to expand...
Click to collapse
A11 is bugged too

wetito said:
there's a fix to solve this. or wait future updates. or install a11 based gsi
Click to expand...
Click to collapse
How to fix

https://github.com/iamverycute/brightness_fix
could you add on on your guide for flashing gsi

Does "wake screen for notifications" work for any of you? I'm assuming this is related to brightness bug. The brightness_fix app doesn't seem to fix this at all.