Treble ROM Oreo and Pie references...

Search This thread

xgneilx

Senior Member
May 25, 2012
262
126
Common bugs:

1. Flickering screen during brightness adjustment.
2. No auto brightness.
3. BT media playback only or incall only but not both.
4. No battery usage statistics (can't see apps but can see hardware %)
5. Probably stuttering sound when choosing ringtones.
6. no MTP

Comparison:

1. Both Havoc and PD appears to be more fluid than Oreo.
2. Xposed supports Oreo only.
3. Havoc has more customization than Pixel Dust. Two particular customization that I am missing are (1) scrambling of numbers during PIN entry after a boot up, and (2) brightness adjustment by swiping in status bar.
4. Pixel Dust is currently more updated than Havoc.
5. Fluid Navigation app is working properly with Pixel Dust unlike on Havoc that only side swipes were working not the bottom swipes.
6. PD has better night mode color temp than Havoc.
7. PD's auto brightness adjustment seems to be faster and more appropriate than the fix for Havoc 10/21.
8. Pie's DND feature is more customizable than Oreo.

AICP-M Oreo Treble

HAVOC Pie 10/21

Workaround:
1. Execute command in Terminal with SU permission: setprop persist.sys.qcom-brightness 4095
2 and 3. Copy the contents of the Vendor-2018-11-05.zip file to your vendor partition and set permissions to 644 on all files.
This fixes the following...
  • BT audio in-calls
  • BT audio in-calls using messenger, viber, etc...
  • BT media playback
4. You have to be running on a more updated Xiaomi EU rom before going to GSI. Per my experience battery stats are working on both 8.10.25EU and 10.0.3.0EU ROMS, and at least nano gapps, but wasn't working on 8.8.9EU.
5. Delete the folders /Vendor/lib/Soundfx and /Vendor/lib64/Soundfx
6. If you really need MTP, proceed here... thanks to SUPERUSER for the find...

Pixel Dust Pie 11/14 Gapps Included so no need to install separately, just make sure to factory reset after flashing system image.

Workaround:
1. Execute command in Terminal with SU permission: setprop persist.sys.qcom-brightness 4095
2. Fixed already if you came from EU 8.11.15.
3. Copy the contents of the vendor_for_PD_2018-11-14_release.zip file to your vendor partition and set permissions to 644 on all files.
This fixes the following...
  • BT audio in-calls
  • BT audio in-calls using messenger, viber, etc...
  • BT media playback
4. Fixed already if you came from EU 8.11.15
5. Fixed already.
6. If you really need MTP, proceed here... thanks to SUPERUSER for the find...

Best GCAM w/ Night Sight

Safely freezable apps in Havoc
See attached images...

Flashing tips...

You want to try Treble but you are currently in Global Stable? Proceed here...
Moving between ROM guides? Proceed here...
Running on GSI but want to update base Xiaomi EU ROM?
Code:
1. Backup Data, System (including image), and Vendor (including image) in TWRP.
2. Wipe Cache, Dalvik, Data, and System.
3. Reboot to recovery
4. Install latest Xiaomi EU ROM (make sure to mount all partitions)
5. Reboot to recovery
6. Restore Data, and System from backup
7. Reboot to recovery
8. Install gapps
9. Install magisk
10. Clear Cache and Dalvik
11. Reboot to System

Note: If the latest update doesn't have the Vendor fixes, you need to apply the same fixes as indicated here in the OP.

Based on my experience FAQs.
1. Can I format or wipe system partition in TWRP?
YES. I have done that several times and I am still enjoying my phone. Just make sure that you flash a rom after wiping otherwise you'll just have a paper weight.

2. Do I need to move to MIUI stable ROMs before flashing Treble roms?
NO. I went straight from Xiaomi EU 8.8.9

3. Is it more complicated to flash custom ROMs in Mi Max 3 compared to older Mi Max?
YES, in a way, because here we need to consider ARB. But generally NO, if you haven't triggered your ARB yet.

4. Do I need to go back to MIUI before jumping to different GSI?

NO, per my experience. I clean flashed 9.0 directly from 8.1 GSI.

5. Can I use the official TWRP for GSIs/Treble ROMS?
YES.

6. I'm on Havoc, how can I upgrade to the latest GSI?
-boot to recovery
-wipe system, cache, and dalvik
-install the latest gsi img file to system
-reboot to recovery
-install gapps
-wipe cache and dalvik
-reboot

7. Can I downgrade from latest GSI to an older one?
YES. Just follow the instructions in #6.

8. Can I move from weekly EU rom to stable EU rom?
YES. I installed 10.0.3.0 eu from 8.10.25 eu

9. Can I install GSI on top of MIUI Global 10.0.1.0?
YES. However I was only able to do it once, and cannot do it again. Can't really help with the procedure.


If I have helped you through this, don't forget to click the THANKS button.
 

Attachments

  • Vendor-2018-11-05.zip
    18.9 KB · Views: 412
  • _20181105_082820.jpg
    _20181105_082820.jpg
    168.8 KB · Views: 2,980
  • _20181105_082803.jpg
    _20181105_082803.jpg
    163.7 KB · Views: 2,948
  • _20181105_082753.JPG
    _20181105_082753.JPG
    238 KB · Views: 2,902
  • _20181105_082740.JPG
    _20181105_082740.JPG
    244.7 KB · Views: 2,371
  • _20181105_082729.JPG
    _20181105_082729.JPG
    237.1 KB · Views: 2,296
  • vendor-etc-2018-11-09.zip
    18.2 KB · Views: 270
  • vendor_for_PD_2018-11-14_release.zip
    6.5 KB · Views: 285
Last edited:

xgneilx

Senior Member
May 25, 2012
262
126
Re: #3
If bt incall if more important to you than bt media playback, i think i accidentallly stumbled upon an unexpected workaround... Install Xiaomi Mi A1 Camera module in Magisk and you'll be able to use your bt for calling. You don't even need to use the camera, but it works.
 

MrColdbird

Senior Member
Nov 25, 2011
1,178
2,195
www.black-seraph.com
So... After doing all those fixes of yours Bluetooth is now fully working? Both A2DP and HFP?

Either way: keep it up. Can't wait to have a fully working GSI treble vendor.
 

famaTV

Senior Member
Aug 22, 2012
88
18
Hello friends,

Many thanks for all the community teamwork! :)

I can confirm, after following the guide, that my BT in Call and Media is working perfectly, no flickering with brightness and auto-brightness and adjustment is working great (just make sure you use the latest apk file in post #51 in that thread).

I also would like to share that I left the phone in Airplane mode for 16 hours with ZERO drop in battery!

For GCam, where did you download that, please (4. Gcam seems to work better as I haven't experienced any hiccups i.e. sudden crashing.)?

Also, for the below point, can you explain what you are talking about as I couldn't follow:

3. Whitelisting in Doze mode runs effectively. i.e. Titanium backup scheduled tasks, sms backup schedules, etc...

Thank you again for sharing your success!
 

opasha

Senior Member
Jul 2, 2009
2,293
616
Hello friends,

Many thanks for all the community teamwork! :)

I can confirm, after following the guide, that my BT in Call and Media is working perfectly, no flickering with brightness and auto-brightness and adjustment is working great (just make sure you use the latest apk file in post #51 in that thread).

I also would like to share that I left the phone in Airplane mode for 16 hours with ZERO drop in battery!

For GCam, where did you download that, please (4. Gcam seems to work better as I haven't experienced any hiccups i.e. sudden crashing.)?

Also, for the below point, can you explain what you are talking about as I couldn't follow:

3. Whitelisting in Doze mode runs effectively. i.e. Titanium backup scheduled tasks, sms backup schedules, etc...

Thank you again for sharing your success!
From this thread - latest link at the top: https://www.celsoazevedo.com/files/android/google-camera/dev-tolyan009/#apk469

Doze is deep sleep. So, it shuts off things including apps when screen is off to preserve battery life unless you make app exceptions (whitelist). He makes scheduled backups in those apps, so whitelisting prevents them from being interrupted/closed in Doze.
 
Last edited:
  • Like
Reactions: xgneilx

famaTV

Senior Member
Aug 22, 2012
88
18
From this thread - latest link at the top: https://www.celsoazevedo.com/files/android/google-camera/dev-tolyan009/#apk469

Doze is deep sleep. So, it shuts off things including apps when screen is off to preserve battery life unless you make app exceptions (whitelist). He makes scheduled backups in those apps, so whitelisting prevents them from being interrupted/closed in Doze.

Thanks for your swift reply and help. I have installed Doze and will try it for a couple of days and watch for a noticeable difference.

For the GCam, I installed that one in the link you provided me, but it doesn't say it's for MAX3 ... I followed all recommended settings, but still the back camera doesn't work (shows pure black screen). Should I use MAX2 (I have seen it in the list) or am I missing something here?
 

opasha

Senior Member
Jul 2, 2009
2,293
616
Thanks for your swift reply and help. I have installed Doze and will try it for a couple of days and watch for a noticeable difference.

For the GCam, I installed that one in the link you provided me, but it doesn't say it's for MAX3 ... I followed all recommended settings, but still the back camera doesn't work (shows pure black screen). Should I use MAX2 (I have seen it in the list) or am I missing something here?
You're very welcome. Do you have camera2_api_enabler installed from magisk? You need that.
 

famaTV

Senior Member
Aug 22, 2012
88
18
Hello,I couldn't see it in Magisk but Googled and downloaded it from this link

https://forum.xda-developers.com/apps/magisk/module-camera2api-enabler-t3656651

I downloaded and installed the second attached file.

Installed and checked with Camera API probe and got the below, however, now it crashes when I change to front camera and still the front doesn't work.

Code:
Model:Phh-Treble with GApps
Manufacturer:unknown
Build:8.1.0
SDK:27
------------------------------------------
Camera ID: 0
Lens facing: Back
SupportLevel:Level_3
SupportLevel HR:Level_3
Manual exposure:1
Auto exposure:1
Auto exposure, always flash:1
Auto exposure, auto flash:1
Auto exposure, auto flash, red eye reduction:1
AE Lock:1
Manual focus:1
Auto focus:1
Auto focus macro:1
Auto focus continuous picture:1
Auto focus continuous video:1
Auto focus EDOF:0
White balance off:1
Automatic white balance:1
WB: cloudy day:1
WB: day:1
WB: fluorescent:1
WB: incandescent:1
WB: shade:1
WB: twilight:1
WB: warm fluorescent:1
AWB Lock:1
RawCapture:1
BurstCapture:1
------------------------------------------
Camera ID: 1
Lens facing: Front
SupportLevel:Level_3
SupportLevel HR:Level_3
Manual exposure:1
Auto exposure:1
Auto exposure, always flash:1
Auto exposure, auto flash:1
Auto exposure, auto flash, red eye reduction:1
AE Lock:1
Manual focus:1
Auto focus:0
Auto focus macro:0
Auto focus continuous picture:0
Auto focus continuous video:0
Auto focus EDOF:0
White balance off:1
Automatic white balance:1
WB: cloudy day:1
WB: day:1
WB: fluorescent:1
WB: incandescent:1
WB: shade:1
WB: twilight:1
WB: warm fluorescent:1
AWB Lock:1
RawCapture:1
BurstCapture:1
------------------------------------------
Camera ID: 2
Lens facing: Back
SupportLevel:Level_3
SupportLevel HR:Level_3
Manual exposure:1
Auto exposure:1
Auto exposure, always flash:0
Auto exposure, auto flash:0
Auto exposure, auto flash, red eye reduction:0
AE Lock:1
Manual focus:1
Auto focus:0
Auto focus macro:0
Auto focus continuous picture:0
Auto focus continuous video:0
Auto focus EDOF:0
White balance off:1
Automatic white balance:1
WB: cloudy day:1
WB: day:1
WB: fluorescent:1
WB: incandescent:1
WB: shade:1
WB: twilight:1
WB: warm fluorescent:1
AWB Lock:1
RawCapture:1
BurstCapture:1
------------------------------------------
Camera ID: 3
Lens facing: Back
SupportLevel:Level_3
SupportLevel HR:Level_3
Manual exposure:1
Auto exposure:1
Auto exposure, always flash:1
Auto exposure, auto flash:1
Auto exposure, auto flash, red eye reduction:1
AE Lock:1
Manual focus:1
Auto focus:1
Auto focus macro:1
Auto focus continuous picture:1
Auto focus continuous video:1
Auto focus EDOF:0
White balance off:1
Automatic white balance:1
WB: cloudy day:1
WB: day:1
WB: fluorescent:1
WB: incandescent:1
WB: shade:1
WB: twilight:1
WB: warm fluorescent:1
AWB Lock:1
RawCapture:1
BurstCapture:1

Sent from my Phh-Treble with GApps using Tapatalk
 
Last edited:

jaflendrino

Member
Oct 9, 2006
30
3
so, no issues, all is working now ?
bluetooth is full, music and calls? auto brightness?
how can i do it?
Only double touch to wake screen dont work, isnt it?,
 

xgneilx

Senior Member
May 25, 2012
262
126
Hello friends,

Many thanks for all the community teamwork! :)

I can confirm, after following the guide, that my BT in Call and Media is working perfectly, no flickering with brightness and auto-brightness and adjustment is working great (just make sure you use the latest apk file in post #51 in that thread).

I also would like to share that I left the phone in Airplane mode for 16 hours with ZERO drop in battery!

For GCam, where did you download that, please (4. Gcam seems to work better as I haven't experienced any hiccups i.e. sudden crashing.)?

Also, for the below point, can you explain what you are talking about as I couldn't follow:

3. Whitelisting in Doze mode runs effectively. i.e. Titanium backup scheduled tasks, sms backup schedules, etc...

Thank you again for sharing your success!

For gcam.
https://forum.xda-developers.com/showpost.php?p=77361996&postcount=14

For doze: as opasha said. In MIUI even if I whitelisted TB, etc... It's not running during doze mode.
Btw, you don't need to install doze. It's built-in feature since Android L but started working efficiently in Android M.

Not my work, but I've attached here the camera2api magisk module
 

Attachments

  • Camera2_API_Enabler-v1.0.0.zip
    10.2 KB · Views: 32
Last edited:

jngiag

Senior Member
Jul 19, 2009
249
134
Using the latest Vanilla noSu AICP mordiford , and open gapps pico.

Bugs:
1. Flickering screen during brightness adjustment.
2. No auto brightness.
3. BT incall not working.
4. No battery usage statistics (can't see apps but can see hardware %)

Workaround:
1. Run this in terminal with SU privilege...
setprop persist.sys.qcom-brightness 4095

2. Just copy the framework apk file as instructed in this thread.
https://forum.xda-developers.com/pr.../overlay-enable-night-light-adaptive-t3741965

3.1. You will find a file in this thread named "Audio xml.zip" https://github.com/phhusson/treble_experimentations/issues/48. Copy all its contents to /Vendor/etc folder. Make sure to backup all the files that it will replace so that you can revert to original as needed without flashing vendor from MIUI.
3.2. Overwrite the included "audio_policy_configuration.xml" file in (3.1) with the one that I have made based on Mi Max 3 vendor as attached here, otherwise, you will be able to fix the BT incall but you won't be able to hear alarm and phone rings when not connected to BT.

4. Will probably look into this the next time I have free time.


Observation:
Cons:
1. Idle time with same apps and settings (no data and wifi) for 6-8hrs
1.a EU Rom = 0% battery drop
1.b AICP treble = 2% battery drop (probably because of #3 in Pros)
2. I am missing the better MIUI built-in camera. The Camera that came with AICP or even Open Camera is not as good as the built-in camera of MIUI for this phone.

Pros:
1. Battery usage when either wifi or data is on, almost the same with MIUI. I don't notice significant drop of battery per my usual usage.
2. Not MIUI.
3. Whitelisting in Doze mode runs effectively. i.e. Titanium backup scheduled tasks, sms backup schedules, etc...
4. Gcam seems to work better as I haven't experienced any hiccups i.e. sudden crashing.

Everything else seems to be working as expected.

If I have helped you through this, don't forget to click the THANKS button.


Based on my experience FAQs.
1. Can I format or wipe system partition in TWRP?
YES. I have done that several times and I am still enjoying my phone. Just make sure that you flash a rom after wiping otherwise you'll just have a paper weight.
2. Do I need to move to MIUI stable ROMs before flashing Treble roms?
NO. I went straight from Xiaomi EU 8.8.9
3. Is it more complicated to flash custom ROMs in Mi Max 3 compared to older Mi Max?
YES, in a way, because here we need to consider ARB. But generally NO, if you haven't triggered your ARB yet.

Steps (1) & (3) fixed the problem of brightness flickering during brightness adjustment and BT media and call using Havoc-OS 2.0 (Android 9.0) GSI (2018-10-18). I didn't try step (2). Nice work! :good:
 
I read the whole Thread but I have a few questions:

1. Is this Havoc a whole custom rom without MIUI? Since I used lineageos on my max2 I search for a nonmiui Rom for my max3.

2. Is there somewhere a whole installation tutorial? But I am on 8.10.18 miglobe rom (same as xiaomi.eu weekly). I think there is ARB. I don't want to brick the max3 :) or is it impossible because of ARB?


For the camera I tested a few cams. The best I found is:

https://www.celsoazevedo.com/files/android/google-camera/f/GoogleCamera_6.1.009.215420794-beta2.apk

Except slowmo all is working even the HDR+enhanced mode works. All other apks I tested crash with hdr+enhanced.
Slow motion I don't find a apk which don't crash. But I used slowmo never.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 32
    Common bugs:

    1. Flickering screen during brightness adjustment.
    2. No auto brightness.
    3. BT media playback only or incall only but not both.
    4. No battery usage statistics (can't see apps but can see hardware %)
    5. Probably stuttering sound when choosing ringtones.
    6. no MTP

    Comparison:

    1. Both Havoc and PD appears to be more fluid than Oreo.
    2. Xposed supports Oreo only.
    3. Havoc has more customization than Pixel Dust. Two particular customization that I am missing are (1) scrambling of numbers during PIN entry after a boot up, and (2) brightness adjustment by swiping in status bar.
    4. Pixel Dust is currently more updated than Havoc.
    5. Fluid Navigation app is working properly with Pixel Dust unlike on Havoc that only side swipes were working not the bottom swipes.
    6. PD has better night mode color temp than Havoc.
    7. PD's auto brightness adjustment seems to be faster and more appropriate than the fix for Havoc 10/21.
    8. Pie's DND feature is more customizable than Oreo.

    AICP-M Oreo Treble

    HAVOC Pie 10/21

    Workaround:
    1. Execute command in Terminal with SU permission: setprop persist.sys.qcom-brightness 4095
    2 and 3. Copy the contents of the Vendor-2018-11-05.zip file to your vendor partition and set permissions to 644 on all files.
    This fixes the following...
    • BT audio in-calls
    • BT audio in-calls using messenger, viber, etc...
    • BT media playback
    4. You have to be running on a more updated Xiaomi EU rom before going to GSI. Per my experience battery stats are working on both 8.10.25EU and 10.0.3.0EU ROMS, and at least nano gapps, but wasn't working on 8.8.9EU.
    5. Delete the folders /Vendor/lib/Soundfx and /Vendor/lib64/Soundfx
    6. If you really need MTP, proceed here... thanks to SUPERUSER for the find...

    Pixel Dust Pie 11/14 Gapps Included so no need to install separately, just make sure to factory reset after flashing system image.

    Workaround:
    1. Execute command in Terminal with SU permission: setprop persist.sys.qcom-brightness 4095
    2. Fixed already if you came from EU 8.11.15.
    3. Copy the contents of the vendor_for_PD_2018-11-14_release.zip file to your vendor partition and set permissions to 644 on all files.
    This fixes the following...
    • BT audio in-calls
    • BT audio in-calls using messenger, viber, etc...
    • BT media playback
    4. Fixed already if you came from EU 8.11.15
    5. Fixed already.
    6. If you really need MTP, proceed here... thanks to SUPERUSER for the find...

    Best GCAM w/ Night Sight

    Safely freezable apps in Havoc
    See attached images...

    Flashing tips...

    You want to try Treble but you are currently in Global Stable? Proceed here...
    Moving between ROM guides? Proceed here...
    Running on GSI but want to update base Xiaomi EU ROM?
    Code:
    1. Backup Data, System (including image), and Vendor (including image) in TWRP.
    2. Wipe Cache, Dalvik, Data, and System.
    3. Reboot to recovery
    4. Install latest Xiaomi EU ROM (make sure to mount all partitions)
    5. Reboot to recovery
    6. Restore Data, and System from backup
    7. Reboot to recovery
    8. Install gapps
    9. Install magisk
    10. Clear Cache and Dalvik
    11. Reboot to System
    
    Note: If the latest update doesn't have the Vendor fixes, you need to apply the same fixes as indicated here in the OP.

    Based on my experience FAQs.
    1. Can I format or wipe system partition in TWRP?
    YES. I have done that several times and I am still enjoying my phone. Just make sure that you flash a rom after wiping otherwise you'll just have a paper weight.

    2. Do I need to move to MIUI stable ROMs before flashing Treble roms?
    NO. I went straight from Xiaomi EU 8.8.9

    3. Is it more complicated to flash custom ROMs in Mi Max 3 compared to older Mi Max?
    YES, in a way, because here we need to consider ARB. But generally NO, if you haven't triggered your ARB yet.

    4. Do I need to go back to MIUI before jumping to different GSI?

    NO, per my experience. I clean flashed 9.0 directly from 8.1 GSI.

    5. Can I use the official TWRP for GSIs/Treble ROMS?
    YES.

    6. I'm on Havoc, how can I upgrade to the latest GSI?
    -boot to recovery
    -wipe system, cache, and dalvik
    -install the latest gsi img file to system
    -reboot to recovery
    -install gapps
    -wipe cache and dalvik
    -reboot

    7. Can I downgrade from latest GSI to an older one?
    YES. Just follow the instructions in #6.

    8. Can I move from weekly EU rom to stable EU rom?
    YES. I installed 10.0.3.0 eu from 8.10.25 eu

    9. Can I install GSI on top of MIUI Global 10.0.1.0?
    YES. However I was only able to do it once, and cannot do it again. Can't really help with the procedure.


    If I have helped you through this, don't forget to click the THANKS button.
    4
    Just a little update on the common issues of Havoc (2018.10.27 & Eu rom 8.10.25).

    1) Brightness adjustment flickering issue fixed
    2) BT Audio fixed (both media & call)
    3) Audio connecting to ear piece working
    4) Viper4Android works
    5) Camera works
    6) Auto Brightness - Didn't try
    7) Stereo speaker - Tested according to https://www.youtube.com/watch?v=hTvJoYnpeRQ . There are sounds left & right channel from top & bottom speakers.
    4
    Yup. After doing 3.1 and 3.2 i have media and calls routed to bt if connected to bt.
    You're awesome. Thanks for all the testing. Looks like treble is getting closer. You should message these fixes to the aicp team.
    3
    Re: #3
    If bt incall if more important to you than bt media playback, i think i accidentallly stumbled upon an unexpected workaround... Install Xiaomi Mi A1 Camera module in Magisk and you'll be able to use your bt for calling. You don't even need to use the camera, but it works.
    3
    Is it /system/app/ims/* and /system/app/imssettings/* that is needed to be copied over?
    Where should you place the folder in the vendor? In /vendor/app?
    Those are among the files that need copying over... But also their depending .so files.

    In addition to that the init scripts need to be slightly modified to ensure the services are getting started as well (and probably a few other small things).

    As I said. I didn't have the time to look into this further yet. This is my only phone and at the end of the day I always have to return to MIUI to ensure it works fine for the next day of work.

    EDIT: Decided to collect all vendor patches we've gathered so far, as well as treblizing patch #1 so that the manual adb approach is no longer required.
    To prepare your Max 3 for GSI usage, coming from any cleanly installed MIUI ROM (Xiaomi.eu in my case), follow the following steps:
    1. Extract the attached zip and copy the vendor folder contents into your /vendor partition (root & remount,rw or compatible recovery required!)
    2. Execute the command inside the install-overlay.sh script to give the framework overlay APK it's proper access permission flags
    After doing said changes you should have working bluetooth, flicker-free as well as automatic brightness controls.
    Still missing / on the to-fix list are:
    • VoLTE support (missing IMS services in /vendor)
    • MTP file transfer (only on Pie? seems to work in AICP Oreo?)