[Xiaomi Mi Max 3 Guides, News, & Discussion] SUPERUSER:
I get error 6 on havoc, maybe there is a typo somewhere?

Edited the file manually, works good

---------------------------------------------------------

I kind of got bluetooth working by your post on havoc V2.0 10/27

First only bluetooth calling worked but with a little fiddling I got both media and calling to work.

Only Volte is still not working.

HavocOS V2.0 27/10/2018 (flashed over Xiaomi.eu pie and pie fw-non-arb)

I am using:

Havoc-OS-v2.0-20181027-GSI-ARM64-Aonly-Official.img

open_gapps-arm64-9.0-pico-20181216.zip

Flashed over:

xiaomi.eu_multi_MIMAX3_8.12.13_v10-9.zip

fw-non-arb_nitrogen_miui_MIMAX3_8.12.13_4c12517959_9.0.zip

To combat permission errors for some reason I now have both on miui and treble roms I now do all operations via the TWRP file manager.

I've tried root explorer, solid explorer and x-plore,

Its like there is an issue with unmounting the partition after making any modification to any file.

First time moving or copying or editing permissions goes fine. But second time all errors begin.

Could not delete folder, could not create folder, could not set permissions, cannot rename file, cannot rename folder etc etc.

I've yet to try this via the terminal which is too much work via the touch screen and I don't like doing it via adb and terminal..I'm lazy.

mount -o remount,rw /data or replace data with the partition you want to remount usually solves it.

First, MTP is working out of the box both on

Havoc-OS-v2.0-20181027-GSI-ARM64-Aonly-Official.img

Pixel_dust_system-arm64-aonly.img

You no longer need to flash POST-sGSI_3_v0.5.zip if you come from a pie based xiaomi.eu before flashing a treble pie rom.

I choose to use Havoc due to Pixel dust has the annoying prompt everytime you reboot:

"Your vendor image does not match the system. Please flash the PQ1A.181105.017.A1 vendor image for your device"

More info in post #131 and #132

https://xdaforums.com/project-trebl...evelopment/9-0-pixel-dust-pie-t3862484/page14

On AICP-Mordiford I could not call and have mobile data activated, as expected if you don't have Volte enabled.

But this should work only that you should get 3G or HSPA+ speeds, its slow but still possible to surf while calling.

This works fine in Havoc and Pixel dust.

You just have to wait for 30 seconds after the call is connected and the 3G icon will soon appear in the notification bar.

And there is no series of random reboots;

(one when someone calls me + screen of death so I cannot answer the call forcing me to hard reset the power and two after I hang up) on Havoc or pixel dust.

This was the worst part with Aicp-Mordiford that made me go back to miui.

That and not having mobile data while calling, plus loosing photos taken with GCam_Pixel3Mod during the day that was gone after the reboots.

Rom installation (follow steps to avoid internal storage being total 32GB instead of 128GB)

recovery
[LIST]
[*]Wipe
Dalvik / ART Cache
Substratum Overlays
Cache
Data
Internal Storage
System
Vendor
[*]Reboot to recovery
[*]Flash xiaomi.eu_multi_MIMAX3_8.12.13_v10-9.zip
[*]Flash fw-non-arb_nitrogen_miui_MIMAX3_8.12.13_4c12517959_9.0.zip
[*]Reboot (Its important to let the xiaomi.eu rom boot one time, read comment below)
[/LIST]
recovery
[LIST]
[*]Wipe
Swipe to Factory reset
[*]Flash Havoc-OS-v2.0-20181027-GSI-ARM64-Aonly-Official.img
[*]Flash Opengapps Pico
[*]Reboot
[/LIST]
recovery
[LIST]
[*]Flash Magisk
[*]Reboot
[/LIST]

Experienced a Slight issue....internal storage is only 32GB.

Did some more clean flashes tests and the key is to flash xiaomi.eu and let the miui rom boot at least one time.

Then reboot to twrp and swipe to factory reset and then flash the treble system.img

Flashing the xiaomi.eu first and not letting the phone boot the miui rom makes the internal storage to 32GB after flashing the treble system.img.

I learned something new..that's not a bad thing after all even that I now have to configure the phone again..

Bluetooth audio fix

To get call working from bluetooth headset it worked as you mentioned to use the vendor zip from MrColdbird.

The other zip files in OP post does not work at all.

But media through bluetooth did not work..first try I made it was the opposite that media worked but call didn't..

I did several tests and clean flashes and added and removed one file at a time last night and this whole morning and figured out which files are needed.

And which are not needed so you don't have to copy all files from MrColdbird vendor zip.

Files:

/etc/audio_policy_configuration.xml	< fix call audio to bluetooth headset

/etc/audio/a2dp_audio_policy_configuration.xml	< fix media audio to bluetooth headset

If audio still don't work after applying files, remove audio_policy_configuration.xml in vendor/etc/audio/.

The first file, audio_policy_configuration.xml fixes the call so that the stream goes to the headset.

Otherwise it goes trough the phone call speaker.

First time I made a call after copying the file it went trough the phone speaker on max volume.

I tapped on the speaker icon and set it to speaker and back to bluetooth and then the sound went through to the bluetooth headset.

The second file, a2dp_audio_policy_configuration.xml fixes so that the media audio stream goes to the headset.

Otherwise it will go trough the speaker.

And in the Settings app>Sound>Play media to> will be stuck at "This device", selecting the headset does nothing without copying the file to vendor.

I removed a2dp_audio_policy_configuration.xml to confirm this, and copied it back and playing music through the bluetooth headset worked again.

recovery
[LIST]
[*]Mount Vendor
[*]Advanced
[*] File manager
[*] Copy audio_policy_configuration.xml /vendor/etc
[*] Go to /vendor/etc/audio_policy_configuration.xml
[*] Set permission
[*] Erase all 0000 and write 644 and confirm (do not write 0644 because the phone will not boot, twrp will add the 0 automatically when typing 644 and confirming)
[*] Copy a2dp_audio_policy_configuration.xml /vendor/etc/audio
[*] Go to /vendor/etc/audio/a2dp_audio_policy_configuration.xml
[*] Set permission
[*] Erase all 0000 and write 644 and confirm (do not write 0644 because the phone will not boot, twrp will add the 0 automatically when typing 644 and confirming)
[*]Reboot
[/LIST]

Viper4Android by ahrion magisk module works good out of the box.

It even recognizes the connected device when opening the app and switches to Bluetooth Device tab.

On AICP-Mordiford Oreo this was kind of randomly selecting the Phone Speaker, or the Headset whichever was used last.

And I had to pull and reinsert the cable a few times until it knew where to send the media stream.

Screen flicker and CAM2API fix

The flashable zip file from killwilli gave me error 6 in twrp from this post:

https://xdaforums.com/showpost.php?p=78405982&postcount=304

So I opened the build.prop in /vendor/build.prop and edited it myself and I included it in the zip file.

recovery
[LIST]
[*]Mount Vendor
[*]Advanced
[*] File manager
[*] Copy build.prop /vendor
[*] Go to /vendor/build.prop
[*] Set permission
[*] Erase all 0000 and write 644 and confirm (do not write 0644 because the phone will not boot, twrp will add the 0 automatically when typing 644 and confirming)
[*]Reboot
[/LIST]

Screen black bars bug on low dpi setting

There is no longer any black bar that overlays the navigation bar and notification bar when selecting a smaller dpi than 334 or 324, can't remember which one.

This happened when coming from a xiaomi.eu oreo based rom and flashing a pie based treble rom and setting the dpi lower than this value.

Now I set my Settings>Display>Smallest width to 597 dp, which is the smallest value before tablet mode is activated.

And I set Font size to 80%. There is no longer any issue with black bars on either side of the screen appearing.

Wifi hotspot

At point 4 on the GSI FAQ it says:

https://xdaforums.com/showpost.php?p=77908682&postcount=2

the only bug in this GSI is that you cant set up a password for the wifi hotspot. i am not resposible for this bug its a GSI PHH related bug if you want it fix dont ask me ask [MENTION=1915408]phhusson[/MENTION] he is responsible for it

For me wifi hotspot works fine if I keep it on 2.4GHz, and I tried changing the default password to my own, if I change the band to 5GHz it won't start.

But on 2.4GHz the wifi hotspot works fine, I connected my pc to the hotspot with my password I reached google.com with no issues.

Still testing camera

I am still conducting tests with GCam_Pixel3Mod_1.1_build.6.1.013 to see if I am able to keep the photos I take.

https://xdaforums.com/showpost.php?p=78092554&postcount=104

As I mentioned in the beginning the photos I took on AICP-Mordiford were gone after the series of reboots that happened.

All but one image was gone one day. I still do not trust that camera app to know what is causing the images to vanish.

And I do not know if this could still happen if I stay on Xiaomi.eu.

The dilemma is that the photos taken with this app are extraordinary better both way lower image noise, greater sharpness and color compared to aosp camera or open camera.

Not sure how I am going to test this.

Perhaps I will try taking photos once a day of a computer screen with numbers, 1, 2, 3, 4, 5, 6, 7, 8, 9 etc to easier discover a missing image.

Edit: feb 1 2019

Photos disappearing is no longer an issue on havoc or xiaomi.eu pie based.

I call this being isolated to AICP-Mordiford.