Related
Note : This guide is exclusively for Mi Max 2. Do not try on other devices otherwise you may brick your device.
If you are a MIUI user then you must be familiar with Google Assistant bug on Nougat roms. Previously i was thinking that this issue is in google app itself. But later on i came to know that all miui devices running on nougat has this issue. Google assistant detects your voice and gives the results without any problem but doesn't speak the result. I did lots of hit and trail but they didn't work. Just yesterday i came to know that the issue is with OGG Audio Codec. So the fix was to disable the ogg codec. And this can be done by editing your build.prop. This require root access. So we will have to deal with the following code
Code:
mm.enable.qcom_parser=1048575
change it to
Code:
mm.enable.qcom_parser=1032191
save your file and reboot your device. Google Assistant should work falwlessly.
Magisk moduel also available. Download from attatchment.
Hit Thanks if it helps you.
Sir in my device it is not working..??
Plzzz i need help
Introduction
Few weeks ago, I got a Pixel 1 as my backup phone, when I try to connect it to the Microsoft Wireless Display Adapter, it couldn't find the Adapter.
I haven't used Android phones for a long time. In my mind, Android natively supports Miracast. After some searching, I was frightened to find that Google has removed Miracast from Android.
I was really disappointed because I often cast my Windows devices easily by using Miracast. My Projector has only two HDMI ports, one for HDMI cable, and one for Wireless Display Adapter. I can't add a Chromecast unless a HDMI switch is used.
One possible solution is to add a line "persist.debug.wfd.enable=1" in "build.prop" to enable WiFi-Display, but many people say that it doesn't work since Android N, the phone can discover WiFi-Displays but unable to cast.
Since Android framework is open source, I did some searching and found that some WiFi-Display related code still exists. Android 9 still keeps the WifiDisplayAdapter in DisplayManagerService, but removed WifiDisplay from MediaPlayerService, that's why we can discover WiFi-Displays but can't cast.
I recovered some code from AOSP history commits, fixed the build errors, and debugged on my Pixel, finally the Miracast can work on my Pixel.
If you also want Miracast to work on your Google phones, you can follow my steps, but first make sure your ROM is open source so that you can change and rebuild it.
If you have a Pixel 1 running the same version of system, you can simply replace some files in your system with the files I built.
If you have other Google phones or running different versions, you can apply my patch to AOSP, and build it by yourself. I have built the latest version for all Google Pixel phones, but I haven't tested except Pixel 1.
If your ROM is not open source, I will no longer be able to help, since MediaPlayerService may have been changed by your ROM, you may can't replace it with the AOSP version.
Prerequisites
Pixel running Android 9.0.0 build number PQ1A.181205.002.A1 or PQ1A.190105.004.
Bootloader unlocked.
adb and fastboot tools and drivers are working for your device.
Note & Disclaimer
These steps will change files in your system, your Pixel should run the exact same version of system. Pushing files to different versions of system may cause unknown problems.
Please check carefully before running each command, a mistaken operation may result in unable to boot up, or destroy your data, or even damage your phone.
If you are not sure about what these steps are doing, but still want to go ahead, please backup your phone firstly, you may not be able to recover your phone to its original state.
I have only tested on Pixel 1 with build number PQ1A.181205.002.A1 and PQ1A.190105.004, for other phones or versions, you should build and test on your own.
Basic Steps
Flash the same version of factory image for your phone.
Download the prebuilt files from https://github.com/sbjbs/android-wfd-patch
Add this line into "build.prop", without it, we will not be able to enable WiFi-Display:
Code:
persist.debug.wfd.enable=1
Replace some files in system:
Code:
system/lib/libaudioflinger.so
system/lib64/libaudioflinger.so
system/lib/libserviceutility.so
system/lib64/libserviceutility.so
system/lib/libmedia.so
system/lib64/libmedia.so
system/lib/libwilhelm.so
system/lib64/libwilhelm.so
system/lib/libandroid_runtime.so
system/lib64/libandroid_runtime.so
system/lib/libstagefright.so
system/lib64/libstagefright.so
system/lib/libstagefright_wfd.so
system/lib64/libstagefright_wfd.so
system/lib/libmediaplayerservice.so
If you have magisk installed, you can refer to Phoenix Wright's post:
Phoenix Wright said:
using "setprop" to set that property once is enough, no need to touch build.prop; given it's a "persist" property it'll be permanent.
using magisk to overlay them on /system
Click to expand...
Click to collapse
Some extra steps that you may need
Remove dm-verity metadata of system.img
The dm-verity can prevent us from changing the system, and what's more it has a forward-error-correction(FEC) feature, which can detect and correct some corrupted data.
I spend a lot of time on attempting to change the build.prop but fail again and again, it just always correct the file, and I can't enable wifi-display.
I don't know how to disable it. Since the error-correcting info should be stored in the dm-verity metadata, I just removed the dm-verity metadata from the stock system.img, and flash the system.img.
I will list the steps to remove dm-verity metadata, but if you can disable dm-verity entirely, that should work too.
For phones that have a vbmeta partition (like Pixel 2), seems you can flash an special vbmeta.img to disable AVB. You can build the empty vbmeta image by this command, but I don't have a device to test if it works:
Code:
avbtool make_vbmeta_image --flag 2 --padding_size 4096 --output vbmeta.img
For Pixel 1, we need to remove dm-verity metadata that attached to system.img, first convert the sparse system.img to an ext4 image:
Code:
simg2img system.img system.ext4.img
read the block count to calculate the system size:
Code:
od -j 1028 -An -N4 -tu system.ext4.img
for Pixel 1, it should be 516099. You also can read it by a Hex Editor, e.g., WinHEX in Windows, read 4 bytes starting from 1028 bytes, as a little-endian hex value.
so the real system partition size is 516099 * 4096 = 2113941504 bytes.
we need to set the data to zero after that position. It's important to do this, since we need to overwrite the metadata in that area, rather than just truncate the size of system.img.
next get the ext4 image size, for Pixel PQ1A.181205.002.A1, it should be 2147483648.
so we need to write 2147483648 - 2113941504 = 33542144 bytes：
Code:
dd if=/dev/zero of=system.ext4.img seek=2113941504 count=33542144 oflag=seek_bytes iflag=count_bytes
we also can use some other tools to do this, e.g., WinHEX in Windows. Open the file in in-place mode, and jump to 2113941504, and select it as the begin, and jump to the end, and select as the end, and fill the selection with all zero.
after that, flash the changed system.ext4.img to Pixel:
Code:
fastboot flash system system.ext4.img
Test that you can boot up normally. If not, check what's wrong and fix it.
Temporary boot up by TWRP image
We don't have to install TWRP, but just use it to temporary boot up, so that we can mount the system partition for writing. If you have TWRP installed, you can just boot to TWRP.
Download TWRP image for pixel, just need the twrp.img, we won't install the zip file.
boot your device to bootloader:
Code:
adb reboot bootloader
and boot by the twrp.img
Code:
fastboot boot twrp.img
after TWRP booted up, just leave it there, no need to unlock or input password, we will change the system by adb.
Mount system partition for writing.
In the current version of TWRP for Pixel (twrp-3.2.3-1-sailfish.img), its fstab has an entry for system partition, we can directly mount it.
Code:
adb shell mount /system
run mount to check if successfully mounted:
Code:
adb shell mount
you should see an entry like this:
Code:
/dev/block/sda34 on /system type ext4 (rw,seclabel,relatime)
If not, you should stop now, and check the above steps.
after mount, we can use adb to push files into system.
Hey guy,
You helped me a lot to understand why it was not working with Pie. I tried several custom ROMs + the official Pie and it was not working.
There is Wireless display option in quick settings but it' doesn't find my Microsoft Wireless Display Adaptor also.
I so downgrade to Oreo. With Oreo it works without any issue. (there is an option "allow Wireless display" to tick and then your miracast dongle will appear).
You did a great job to make it working on Pie. Congratulations. I will anyway stay on Oreo. I think google will change that (many people already complained i guess).
Jean Michel
jean_michmich said:
Hey guy,
You helped me a lot to understand why it was not working with Pie. I tried several custom ROMs + the official Pie and it was not working.
There is Wireless display option in quick settings but it' doesn't find my Microsoft Wireless Display Adaptor also.
I so downgrade to Oreo. With Oreo it works without any issue. (there is an option "allow Wireless display" to tick and then your miracast dongle will appear).
You did a great job to make it working on Pie. Congratulations. I will anyway stay on Oreo. I think google will change that (many people already complained i guess).
Jean Michel
Click to expand...
Click to collapse
Thanks for your reply!
I have tested on Pie on my Pixel, I often play online games while cast is on, and didn't meet any problems last week.
I also hope that Google will support Miracast again in the future, but it seems unlikely in the near future.
Google has abandoned it since Android 6 (source: Wikipedia), and now they're deleting unused source code related to wifi-display.
I'm more worried about that there will be more build errors and potential issues when we try to enable it for future Android versions.
sbjbs said:
Thanks for your reply!
I have tested on Pie on my Pixel, I often play online games while cast is on, and didn't meet any problems last week.
I also hope that Google will support Miracast again in the future, but it seems unlikely in the near future.
Google has abandoned it since Android 6 (source: Wikipedia), and now they're deleting unused source code related to wifi-display.
I'm more worried about that there will be more build errors and potential issues when we try to enable it for future Android versions.
Click to expand...
Click to collapse
OK it's getting more clear. You are right. Wikipedia says : "but support was dropped with Android 6.0 Marshmallow in 2015 in favor of Google's own proprietary Google Cast protocol.[15] Some manufacturers of Android devices step in and support Miracast through their software"
I'm not an "official android ROM" user.
I always use Pixel Dust custom ROM. For this custom ROM, Miracast was supported for Oreo but not for Pie (not yet).
jean_michmich said:
OK it's getting more clear. You are right. Wikipedia says : "but support was dropped with Android 6.0 Marshmallow in 2015 in favor of Google's own proprietary Google Cast protocol.[15] Some manufacturers of Android devices step in and support Miracast through their software"
I'm not an "official android ROM" user.
I always use Pixel Dust custom ROM. For this custom ROM, Miracast was supported for Oreo but not for Pie (not yet).
Click to expand...
Click to collapse
I used to be a ‘latest official ROM’ user
For custom ROMs, since they may have changed the framework, we can't replace files with AOSP version, but as long as they're open source, we can try to contribute to it.
Adding Miracast support in Android is not difficult, and many manufactures have their own support.
I hope your custom ROM will support Miracast for Pie in the near future.
Tested on Pixel 2 XL and working (for what it's worth, using "setprop" to set that property once is enough, no need to touch build.prop; given it's a "persist" property it'll be permanent). I built the .so files on my local aosp tree and I'm using magisk to overlay them on /system.
Hi @sbjbs
If I understand you right then you have patched the AOSP codebase. Would you mind sharing the repositories/commits on your GitHub? That would be highly appreciated. :good:
Regards
spezi
Sent from my Pixel 3 using XDA Labs
spezi77 said:
Hi @sbjbs
If I understand you right then you have patched the AOSP codebase. Would you mind sharing the repositories/commits on your GitHub? That would be highly appreciated. :good:
Regards
spezi
Sent from my Pixel 3 using XDA Labs
Click to expand...
Click to collapse
There's a link in the OP: https://github.com/sbjbs/android-wfd-patch/tree/master/patches/android-9.0.0
Phoenix Wright said:
Tested on Pixel 2 XL and working (for what it's worth, using "setprop" to set that property once is enough, no need to touch build.prop; given it's a "persist" property it'll be permanent). I built the .so files on my local aosp tree and I'm using magisk to overlay them on /system.
Click to expand...
Click to collapse
Great to hear that!
You method is simpler and more elegant, that's awesome!
Phoenix Wright said:
Tested on Pixel 2 XL and working (for what it's worth, using "setprop" to set that property once is enough, no need to touch build.prop; given it's a "persist" property it'll be permanent). I built the .so files on my local aosp tree and I'm using magisk to overlay them on /system.
Click to expand...
Click to collapse
Can you elaborate how you did use "magisk to overlay them on /system"?
I pushed them using adb as mentioned on github but it is stuck at Google splash screen. I've taimen BTW and am on Pixeldust ROM. It booted while writing this post but the screen was not responding to touch.
Nitin
nitin.chobhe said:
Can you elaborate how you did use "magisk to overlay them on /system"?
I pushed them using adb as mentioned on github but it is stuck at Google splash screen. I've taimen BTW and am on Pixeldust ROM. It booted while writing this post but the screen was not responding to touch.
Nitin
Click to expand...
Click to collapse
I made a module with the .so files I compiled: https://workupload.com/file/pd4EUBdw
Note that I can't vouch for this to work on your ROM, it works on taimen on stock 9.0 with January security patches though.
nitin.chobhe said:
Can you elaborate how you did use "magisk to overlay them on /system"?
I pushed them using adb as mentioned on github but it is stuck at Google splash screen. I've taimen BTW and am on Pixeldust ROM. It booted while writing this post but the screen was not responding to touch.
Nitin
Click to expand...
Click to collapse
Did you build the so files for your ROM from source? the patch has changed the interface of IMediaPlayerService, if anything else in your ROM is using IMediaPlayerService.h, you'd better rebuild and replace them.
that's why I uploaded the libwilhelm.so and libandroid_runtime.so, even though I didn't change the source code of them.
Phoenix Wright said:
I made a module with the .so files I compiled: https://workupload.com/file/pd4EUBdw
Note that I can't vouch for this to work on your ROM, it works on taimen on stock 9.0 with January security patches though.
Click to expand...
Click to collapse
Thanks!
sbjbs said:
Did you build the so files for your ROM from source? the patch has changed the interface of IMediaPlayerService, if anything else in your ROM is using IMediaPlayerService.h, you'd better rebuild and replace them.
that's why I uploaded the libwilhelm.so and libandroid_runtime.so, even though I didn't change the source code of them.
Click to expand...
Click to collapse
I tried building with my ROM but I got build errors related to OMX.h, I need to find a solution for them. Thanks anyways!
Nitin
Someone tries on Pixel 3? Thanks
It works perfectly ! I used the prebuilt files on the march build.
Do you know if we can force the 16/9 ratio ?
Thanks
edit : I will try with second screens !
this works a treat on my Pixel 3 XL (Stock Pie) just overlayed the files from Phoenix Wright using magisk and it works now....sweet thanks, now just need to figure out how to fool sky sports app into letting me cast.....
marshyrob said:
this works a treat on my Pixel 3 XL (Stock Pie) just overlayed the files from Phoenix Wright using magisk and it works now....sweet thanks, now just need to figure out how to fool sky sports app into letting me cast.....
Click to expand...
Click to collapse
Can you explain more how did you do?
Did you just flash the zip from Phoenix Wright in Magisk?
EMJI79 said:
Can you explain more how did you do?
Did you just flash the zip from Phoenix Wright in Magisk?
Click to expand...
Click to collapse
Yes just copied the .zip file from Phoenix Wright's post to my device then used the module install option in Magisk like if you are installing a module found in Magisk (use the plus sign to add your own .zip file instead and browse to the file you just saved) then reboot. Then i went to the cast option in settings - connected devices - connection preferences, there i could tick in the top right corner under the 3 dots "enable wireless display" and it showed my Panasonic TV, chose connected and boom it connected. Needed to enable the mirroring option on my Panasonic but this is a TV setting nothing to do with the phone, you might need to do a similar step based on your TV as they need to be able to see each other.
marshyrob said:
Yes just copied the .zip file from Phoenix Wright's post to my device then used the module install option in Magisk like if you are installing a module found in Magisk (use the plus sign to add your own .zip file instead and browse to the file you just saved) then reboot. Then i went to the cast option in settings - connected devices - connection preferences, there i could tick in the top right corner under the 3 dots "enable wireless display" and it showed my Panasonic TV, chose connected and boom it connected. Needed to enable the mirroring option on my Panasonic but this is a TV setting nothing to do with the phone, you might need to do a similar step based on your TV as they need to be able to see each other.
Click to expand...
Click to collapse
It did work today with my Sony television.
Thanks!
OMG!!! You made my week. Few hiccups tho....
Can anyone else confirm that Hulu and HBO go and Amazon prime . YouTube works.
Hulu and amazon I can log on but when it plays all you get is audio. Haven't tried Netflix I don't sub them.
HBO go as soon as I try to play a video it says this video cannot be played. If I disable the mirror it plays perfectly. Same thing with Hulu and prime. Disable the mirror an it works perfectly on my phone.
This tutorial was made by Craftingmod
Thanks so much for helping us.
Original Post: HERE
--------------------------
Note:tested only on GSI ROMs 9.0
1. Bluetooth audio connection fix
Backup the file /vendor/overlay/BluetoothResCommon.apk
Simply remove /vendor/overlay/BluetoothResCommon.apk via root explorer
2. aptX HD
Install "Bluetooth stack audio bitrate changer for SBC + aptX & aptX-HD enabler" from Download of Magisk Manager or Download Here (APTX for Android Oreo & Pie NOT WORK)
3. build.prop
Open /vendor/build.prop and find "persist.vendor.bt.a2dp_offload_cap=sbc-aac" and replace "sbc-aac" to "sbc-aac-aptx-aptXHD" (Add -aptx-aptXHD)
Note: if you don't find the add "persist.vendor.bt.a2dp_offload_cap=sbc-aac-aptx-aptXHD"
4. Restart device and test
Note: if it doesn't work undo everything you did thanks for trying
Hello my magisk cannot seem to find the module you were referring to. Do you have another link where i can download the module?
Hi There, and many thanks for you guides https://forum.xda-developers.com/member.php?u=9792389
This guide made bluetooth audio and connectio work, but bluetooth calling is not working. Can call but no sound is transmitted, so i cant use it. Any suggestions as how to proceed?
thorvall said:
Hi There, and many thanks for you guides https://forum.xda-developers.com/member.php?u=9792389
This guide made bluetooth audio and connectio work, but bluetooth calling is not working. Can call but no sound is transmitted, so i cant use it. Any suggestions as how to proceed?
Click to expand...
Click to collapse
try this , hopefully it will do the trick:
https://forum.xda-developers.com/showpost.php?p=79191978&postcount=5https://forum.xda-developers.com/showpost.php?p=79191978&postcount=5
I worked.
Fillint said:
try this , hopefully it will do the trick:
https://forum.xda-developers.com/showpost.php?p=79191978&postcount=5https://forum.xda-developers.com/showpost.php?p=79191978&postcount=5
Click to expand...
Click to collapse
Thanks :good: . I actually did look at the thread before, but had the impression that the GSI Treble roms were of the ASOP variant, contrary to the note: 'NOTE: This works only on CAF based custom roms. It doesn't work on AOSP.'
Am I wrong, or is it the note that does not apply in this case?
it looks like not both ways aren't working for 9.0 Havoc.
we need better solutions.
I tried these solutions on the Lenovo Z5 pro GT, but the Phone won't recognise any bluetooth IEM's. The sound keeps playing over the speaker. Does anyone have a solution?
When I change vendor to r/w it goes back to file system read only and I can't save the build.prop file afterwards
If someone was able to make it work can you please show me the build.prop permissions!!
this ROM is awesome. but there's a problem. my BT headphone no sound.
in developer options, "disable bluetooth A2DP hardware" can't be turned off. any solution?
And for xiaomi devices?
What is the apk that I have to delete if my device had miui?
in all the GSI images i installed audio BT is not working.
And BluetoothResCommon.apk is not in that path, why ?
build.prop is there but there is no "persist.vendor.bt.a2dp_offload_cap=sbc-aac-aptx-aptXHD" entry
Any help to fix bluetooth for this case ? I can pair, to headphones connect, for a moment seems to work, but finally audio get played in the phone itself.
kidronvalley said:
in all the GSI images i installed audio BT is not working.
And BluetoothResCommon.apk is not in that path, why ?
build.prop is there but there is no "persist.vendor.bt.a2dp_offload_cap=sbc-aac-aptx-aptXHD" entry
Any help to fix bluetooth for this case ? I can pair, to headphones connect, for a moment seems to work, but finally audio get played in the phone itself.
Click to expand...
Click to collapse
Overcame the lack of sound in BT headphones on android 10 by replacing system / lib / libbluetooth.so and system / lib64 / libbluetooth.so with stock firmware
AllexBast said:
Overcame the lack of sound in BT headphones on android 10 by replacing system / lib / libbluetooth.so and system / lib64 / libbluetooth.so with stock firmware
Click to expand...
Click to collapse
im gonna try this too because my Maxpad i10 plus as this issue
blaze2051 said:
im gonna try this too because my Maxpad i10 plus as this issue
Click to expand...
Click to collapse
Teclast M40 How to unlock bootloader?
I have found a method of Teclast P20HD to unlock bootloader which can be found in "https://forum.xda-developers.com/android/help/teclast-p20hd-android-10-tablet-4g-t4141997" and "https://forum.hovatek.com/thread-32287.html", but I'm not sure if...
forum.xda-developers.com
@AllexBast
by any chance have you experianced slow command response with ADB? I just install win10 1803 pro and its so so slow to even run adb devices command. does it make a difference if my device is running GSI Phh A11?
Did the trick for me! Thank you
SrCDA said:
This tutorial was made by Craftingmod
Thanks so much for helping us.
Original Post: HERE
--------------------------
Note:tested only on GSI ROMs 9.0
1. Bluetooth audio connection fix
Backup the file /vendor/overlay/BluetoothResCommon.apk
Simply remove /vendor/overlay/BluetoothResCommon.apk via root explorer
2. aptX HD
Install "Bluetooth stack audio bitrate changer for SBC + aptX & aptX-HD enabler" from Download of Magisk Manager or Download Here (APTX for Android Oreo & Pie NOT WORK)
3. build.prop
Open /vendor/build.prop and find "persist.vendor.bt.a2dp_offload_cap=sbc-aac" and replace "sbc-aac" to "sbc-aac-aptx-aptXHD" (Add -aptx-aptXHD)
Note: if you don't find the add "persist.vendor.bt.a2dp_offload_cap=sbc-aac-aptx-aptXHD"
4. Restart device and test
Note: if it doesn't work undo everything you did thanks for trying
Click to expand...
Click to collapse
Thanks, but editing /vendor/build.prop reaquires writing onto /vendor, so what are the apps to offer rw for /vendor?
hd_scania said:
Thanks, but editing /vendor/build.prop reaquires writing onto /vendor, so what are the apps to offer rw for /vendor?
Click to expand...
Click to collapse
It can be done with root or in TWRP.
But now most phones have aptx-aptXHD support in original firmware, so there's a high possibility you don't need this step. By the way, it is not worth it to fix A2DP though, cause for now it's almost not possible (at lease I didn't solution) to fix bluetooth in call and A2DP offload at the same time. For me bluetooth in call is more important, and there's actually no side effect to turn off A2DP offload as far as I understand.
Anyways, to make bluetooth in call and Aptx (of course others like LDAC) both work, you'll need to:
1. remove /vendor/overlay/BluetoothResCommon.apk (if presented) (if presented and deleted, do a factory reset)
2. remove /vendor/etc/a2dp_audio_policy_configuration.xml
3. Enable "Force-disable A2DP offload" in phh settings
4. Enable "use alternate audio policy" in phh settings if your volume adjustment have any problems (if you got multi ones in different feature category, try different combination until it behave normally)(may require reboot)
5. flash Magisk module "aptx-HD-magisk-10_arm.arm64.zip" to fix aptx support
Now both sbc-aac-aptx-aptXHD-LDAC and bluetooth in call should work. Tested on 2 Qualcomm setups recently with phh android 12 based rom.
Hope this could help you and others having same issues.
XT19443 said:
And for xiaomi devices?
What is the apk that I have to delete if my device had miui?
Click to expand...
Click to collapse
Tho Xiaomi's MIUI really modified the whole aosp crazyly,but the device itself is still treble-compactible
the file is called MIUIbluetoothres.apk(probably,on miui 12.5's vendor)
BUT you dont need to del it.
To Fix: TURN ON "force disable a2dp offload" in phh treble settings.
that's it.(worked on redmi 10a.(MTK))
(ps: actually aptx is a qcom thing so it probably wont work on mtk devices.)
This is a simple guide
with links to download the files that you all need to fix the mi note 3 libraries to make it work with the gcam version that you will try
Yes the front camera WORKS GREAT
Thanks to Engineer_Mode
The fix is MiNote3-Camera2API-fix v23 by Engineer_Mode
with or without ARCORE option (there are 2 separate files) You must flash it from TWRP!!
MiNote3-Camera2API-fix v23 without ARCORE
MiNote3-Camera2API-fix v23 with ARCORE
And the gcam versions that i am using are
MGC_7.3.020_Parrot043-v2 by Parrot043
the config file is attached below (MiNote3_Parrot043_7.3.020_V1.xml)
PocoSv10.6.2b.apk"]PocoSv10.6.2b.apk by san1ty
Please post the best gcam version that you tried and works better...
Please read the above by GreatApo
# MiNote3-Camera2API-fix
This is an TWRP flashable zip for Xiaomi Mi Note 3 intended to fix the Camera 2 API on MIUI10 8.1 and MIUI10/11 9.0.
## Disclaimer
Use at your own risk. I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
## Features
MIUI10 Android 8.1 version
- Enables Camera2API in build.prop
- OIS/Front camera fixes (changes the appropriate lib files, credits at the bottom)
MIUI10/11 Android 9.0 version
(Combined by Engineer_Mode as Magisk module)
- Enables Camera2API in build.prop
- Enables EIS (Electronic image Stabilization) in build.prop
- Front Camera Fix
- TelePhoto Camera Packages List (Permissive Mode Needed)
- 1080p 120 fps Slow Motion in GCam
- Sound Stereo Record; HEVC Fix
- Additional Features Activated in Device Features
## Instalation
0. Back up these files (or do a full backup):
(On Android 8.1)
- /system/etc/permissions/android.hardware.camera.full.xml
- /system/etc/permissions/android.hardware.camera.raw.xml
- /system/vendor/lib/libmmcamera_jason_s5k3p8sp_sunny.so
- /system/vendor/lib/hw/camera.sdm660.so
- /system/build.prop
(On Android 9.0)
- /system/etc/device_features/jason.xml
- /system/vendor/etc/mixer_paths.xml
- /system/vendor/etc/media_profiles.xml
- /system/vendor/etc/media_profiles_vendor.xml
- /system/vendor/etc/camera/jason_imx386_ofilm_chromatix.xml
- /system/vendor/etc/camera/jason_imx386_semco_chromatix.xml
- /system/vendor/etc/camera/jason_s5k3m3_ofilm_chromatix.xml
- /system/vendor/etc/camera/jason_s5k3m3_semco_chromatix.xml
- /system/vendor/etc/camera/jason_s5k3p8sp_sunny_chromatix.xml
- /system/vendor/etc/camera/s5k3m3sm_chromatix.xml
- /system/vendor/etc/camera/s5k3p8sp_chromatix.xml
- /system/vendor/etc/permissions/android.hardware.camera.ar.xml
- /system/vendor/etc/permissions/android.hardware.camera.full.xml
- /system/vendor/etc/permissions/android.hardware.camera.raw.xml
- /system/vendor/lib/libmmcamera_jason_s5k3p8sp_sunny.so
- /system/build.prop
1. Flash your new rom or update
2. Boot to your system
3. Reboot into recovery
4. Flash this zip form TWRP
## Revert
If something doesn't work, restore your backuped files (do not forget to also add permissions) or dirty flash (flash over) your new rom/update from TWRP again.
## Custom build.prop options
If you want to add some more options in your buid.prop, you can add them in file "/tmp/update-build.prop", and they will be included in your buid.prop after flashing it.
## Credits
Camera fix: I was informed about this fix from [this XDA topic](https://forum.xda-developers.com/mi-note-3/how-to/google-camera-how-to-mi-note-3-t3757049). All thanks go to: WebDingo, Savitar and also dianluitao, EnesSastim, dimi89
Latest versions for MIUI 10/11 are provided as magisk modules by [Engineer_Mode](http://4pda.ru/forum/index.php?showtopic=878111&st=3460#entry83639600)
Buid.prop edit code: To edit the build.prop, the code from [this XDA post](https://forum.xda-developers.com/showpost.php?p=19093919&postcount=20) by unCoRrUpTeD was used.
## I want more
A complete work/gather up about the GCam fixes for Mi Note 3 has been done by Engineer_Mode and you can learn more on [this 4PDA post](http://4pda.ru/forum/index.php?showtopic=878111&st=3460#entry83639600) (use Chrome's translate)
It doesn't work and returns my hardware support level to Legacy. I had to setprop persist.camera.HAL3.enabled 1 again to use my gcam, and this 7.3.020 version doesn't work either.
It works but i have whatsapp front camera lagging issue. Now found v25 and will try it.
WARNING! I AM NOT RESPONSIBLE FOR ANYTHING DONE TO YOUR DEVICE. TRY AT YOUR OWN RISK!
Sup y’all!?! Just wanted to share these modifications. These are a collection of android mods that I have been using. Some are original and some are not. The attached ax562.zip contains files which need to be put in the corresponding directories with the corresponding permissions(Not recovery flashable!). I have also included FDEA.I magisk .zip module. This module is an Artificial Intelligence app. This is the first majisk module iteration of the .apk. Links to original works of some of these mods are listed below. Big shout out to followmsi, Feravolt, [email protected], the TWRP team and the LOS team!
PS. If anyone wants to help create a flashable .zip that would be great!
ALL THESE STEPS ASSUME YOUR ARE ON LINEAGE OS 18.1 AND USING MAGISK (They might work on other systems but I have not tested).
*
*
*
Steps:
1. Download and extract ax562.zip anywhere.
2. Copy /data and /system files to their proper locations and change permissions of all files to 755.
3. Copy contents of “build.prop” and put them at the end of /system/build.prop and save (might have to mount /system as rw).
4. In TWRP recovery, mount /vendor and replace /vendor/etc/mixer_paths_0.xml (I amplified the speaker output to 33, if too loud, adjust accordingly) with the mixer_paths_0.xml file provided.
5. Google “Chrome” users, in TWRP recovery, mount /vendor and rename /vendor/lib/libnvomx.so to “libnvomx.so.BAK”(This uses Google codecs instead of Nvidia codecs).
6. FDE.AI – I provided the majisk module in the ax562.zip for majisk users. Go into magisk and add the module manually. If you want to use only the .apk or want to dl the module directly, it’s available on Feravolt’s github page in releases (link below). I recommend "Performance mode", setting "Build Prop Tweaks: Nico's gpu tweaks" and finally executing "/aggressiveai on" in the "Elizabeth" AI Chat section. Lastly, I also recommend turning off "Battery Optimization" for the FDE.AI apk.
7. You can also update accordingly without needing to install a new "updated magisk module". The newest version is 12.6 which was released 10/26/21. I've tested this new version and it gives even more of a performance improvement. I did notice for about the first day of gaming it needs to machine learn but after it settles in, GREAT. There is a renamed function though, /aggressiveai does not exist anymore. Use "/advancedai on" to turn on this function. I also keep "Force Dozed Mode" active in the settings screen.
Release 12.6 · feravolt/FDE.AI-docs
Update changelog.md
github.com
8. Enjoy!
https://github.com/feravolt/FDE.AI-docs
https://forum.xda-developers.com/t/...-flashable-increase-your-performance.1353903/
If anyone has any questions, wants to add a script, or has found an error/improvement I'm all ears!
I will try this when the July 2021 build comes out!
EnginEAR said:
I will try this when the July 2021 build comes out!
Click to expand...
Click to collapse
Word.
Updated instructions. Enjoy!
Seems to be working well! It's always hard to say how much of a perceived improvement is the latest ROM improvements vs the tweaks but it very much feels snappier and more able to switch from app to app without long pauses.
I see the app could just run on the device without the content in the zip you provided, may I ask what's the differences about using the files provided? Sorry if it's a silly question, I'm too noob to understand the instructions :'(
thetample said:
I see the app could just run on the device without the content in the zip you provided, may I ask what's the differences about using the files provided? Sorry if it's a silly question, I'm too noob to understand the instructions :'(
Click to expand...
Click to collapse
2. Some of my custom scripts plus other scripts to improve performance.
3. More custom build.prop commands to improve performance
4. Improve the sound by amplifying the output through the mixer_paths0.xml modification.
5. Using googles codes vs the nvidia codecs which are not supported for watching vids in chrome.
6. Installing FDEai.apk as root app through magisk module installation. This ensures that the app does what it's supposed to do like initialize on startup with root privileges etc. Hope that helps.
Just updated the OG post to be able to update the FDAI.apk. Sorry for the lag but I didn't know the apk would install properly as long as the FDAI magisk module was installed first. Enjoy!
How much does it improve by using these "TWEAKS" ? what about battery consumption? is it any higher?
I'm tempted to try it.
Fonsocruise said:
How much does it improve by using these "TWEAKS" ? what about battery consumption? is it any higher?
I'm tempted to try it.
Click to expand...
Click to collapse
Honestly, I would say it's about 10-30% performance increase (most noticeable while gaming). The battery consumption is very efficient.
Any updates to this? With the more recent FDE updates advanced AI can only be enabled while using auto. Do your performance scripts still work on the most recent LOS? Ive been having heating issues trying to watch livestreams and I'm trying to figure it out
101010101001 said:
Any updates to this? With the more recent FDE updates advanced AI can only be enabled while using auto. Do your performance scripts still work on the most recent LOS? Ive been having heating issues trying to watch livestreams and I'm trying to figure it out
Click to expand...
Click to collapse
These mods were all tested on LOS 18.1 and do work. I am not on LOS 19 so I have not tested them on 19. I know FDEAI was updated recently and you could use the most updated APK found on his github above. I'm waiting for camera support to jump on LOS 19.