Related
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.
When I checked the Exposed framework for my LG V20 h918 8.0.0 ARM 64 on the download page there was 6 different options to chosuse from and the don't say witch one is what so far as I taped the right android os then I tap the ARM 64 then it took me to a download page that has 6 options that arn't marked fo witch is what for what. So witch one is the right one for me?
It's easiest to install the Xposed Framework from within the Magisk Manager. Just search for it under Downloads like you would for any other Magisk module. It's a universal installer that will automatically pick the right one for the phone. More info here:
https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268
Background
It has been a long time since the Qualcomm first launched the IMS support in its AMSS(Adavanced Mobile Subscriber Software) subsytem since CDMA platforms,which is the major function part of VoLTE implementation on MSM platforms,but even years later,almost no one talks about this topic on internet,someone noticed about the Samsung IMS configuration,but it's higher layer and not applicable to original MSM platform phones.
Why no one talked about manual VoLTE configuration in the past
There are many reasons that caused such situation,first,the Qualcomm have NDA on its platform internal scheme,many engineers hesitate to share even some simple magic value about some NV items,which results complete blackbox to the APSS Android environment developers.Second,when there is limited number of available VoLTE phones,the manual configuration methods are hide by the selfish drive-test related device sellers,and they even try to block some useful info on some websites by abuse in order to hide the top business secret.I tried to talk about such topic in past days,but all got blocked in the end.Third,the phone vendors want you just to buy new phones to support the VoLTE,and they just choose to not support the sold devices,in some time,even add barricade,this is something that are not noticed by many customers
How it worked
Most of the Qualcomm IMS feature are implement in the AMSS subsystem,which means the configuration is saved in modem's memory,in this case,the EFS on QC phones,which means you will not got the VoLTE work through some Android side prop modification,like the most talked Magisk VoEnabler.Although these props in android environment are the key switch to launch the IMS function routine,but it will not work when you just opened the switch.They are just some RILJ/RIL control flags that decide which phone to be used(the imsphone or gsmphone in RILJ code).And such prop flags may vary from vendor to vendor,it might need extra prop to be set to make sure the IMS routine are properly called.In English,the Android side is just a client of the IMS-client inside modem AMSS subsystem,all of the actual IMS procedures are all completed in the modem environment.
How is it configured
There are many tools to configure such thing right now,I guess even some private ones,but the major way to configure the IMS configuration is through QXDM,it will have a plenty of NV items and EFS configuration in IMS section,the Qualcomm have internal guide since MSM8960,which talked about how to manually set those values to make the IMS VoLTE work.however I haven't see anyone even talked about it,may due too the reasons I talked above.Obviously,such manual configuration way is user un-friendly,the QC have to find some way else.This had introduced the MBN MCFG when Chinese rolling out the VoLTE,and such methods were invented by the OPPO I guess(patents about it).MBN format had been used by QC for years,but the mcfg mbn is different at least in some way,so no current available tools to parse it on other platform except the AMSS itself.So The MCFG MBN contains IMS related configuration stuff,but how to find what it actual contains?This problem remains unsolve until I found the ORCT by linneman in 2018,a simple and buggy toolkit to parse at least some recent MSM8996 platform MBNs ,and finnally got the proper contents in sw_mcfg.mbn file,Then it's the time to manually add those NV and items file into EFS through QPST,after all that the VoLTE finally worked.
Misconception about MCFG MBN
I guess people noticed something about MBN when some guy tried to use VoLTE on Pixel 2,then they made the Magisk VoEnabler,they thought they had loaded the proper sw_mcfg.mbn by replaceing the MBNs inside vendor partition,but none of them realized that they actually falled back to the generic 3GPP configuration of MSM platform,and after MSM8996,that configuration defaultly enabled the IMS feature to work on some 3GPP lab setting networks,interestingly very coincident work on live network
Further work
Android PDC
In fact,there is an app called MBN test which is considered as bloatware for many users,none of them realized it's the important tool kit like PDC used to choose the MBN for carriers,but on phone it self,it works through the RIL_PDC related command and have the same feature like Windows PDC,but this app got misconfigured when outside the factory,and its configuration methods are highly secreted by the vendors.no one willing to answer this question.
Android IMS NV configuration
After Android Lolipop,Google had introduced the carrierconfig framework,which provided some internal methods like nvReaditem,which can actually be used to configure the IMS parameters in modem side,but it's really weired that no one had realised about this usage on whole internet.I think it will be a more generic and one-click way to DIY VoLTE even on some other platform through those API,but no one ever talked about it
Add the ORCT mirror
GitHub - vtsingaras/orct: Open Radio Calibration Toolkit, an enhanced Open Source Implementation to replace Qualcomm's QRCT
Open Radio Calibration Toolkit, an enhanced Open Source Implementation to replace Qualcomm's QRCT - GitHub - vtsingaras/orct: Open Radio Calibration Toolkit, an enhanced Open Source Implementat...
github.com
Hey I'm wondering if you know how to change the identification domain. My carrier, Bell mobility, uses "ims.bell.ca" instead of the standard "ims.mnc610.mcc302.3gppnetwork.org".
My OnePlus 8 phone uses [email protected] as it's identification and the IMS core answer with 403 Forbidden.
A pixel 5 request [email protected] and it's working.
What do I need to change in the MBN to make it use "ims.bell.ca"?
Any news about this topic?
Based on other guides I am trying to load MBN files from other smartphones rom having the same soc (Snapdragon 845), but the new MBN file is not loaded and I see no error.
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.
Hi, while I am facing this issue, thanks to @BillGoss for highlighting the changes required for people who root/magisk installed.
OxygenOs 12 Beta
OxygenOs 12 CBT for kb2001 - working on all variants (you install at your own risk) https://mega.nz/file/CVsgyaAB#zrRWx1vIKUc6pMmNesu8ywpaUSAJWJecDcROvwOGOug
forum.xda-developers.com
So I compared the file with the original @kdrag0n Universal SafetyNet Fix, and the files required to change is:
credit to @BillGoss & @kdrag0n
1st --
system.prop [ORIGINAL from kdrag0n]
# Basic MagiskHide properties
# RootBeer, Microsoft
ro.build.tags=release-keys
# Samsung
ro.boot.warranty_bit=0
ro.vendor.boot.warranty_bit=0
ro.vendor.warranty_bit=0
ro.warranty_bit=0
# SafetyNet
ro.boot.verifiedbootstate=green
ro.boot.veritymode=enforcing
ro.boot.vbmeta.device_state=locked
vendor.boot.vbmeta.device_state=locked
# Other
ro.build.type=user
ro.debuggable=0
ro.secure=1
Click to expand...
Click to collapse
system.prop [MODIFIED]
# Basic MagiskHide properties
# RootBeer, Microsoft
ro.build.tags=release-keys
# Samsung
ro.boot.warranty_bit=0
ro.vendor.boot.warranty_bit=0
ro.vendor.warranty_bit=0
ro.warranty_bit=0
# OnePlus
ro.is_ever_orange=0
# SafetyNet
ro.boot.verifiedbootstate=green
ro.boot.veritymode=enforcing
vendor.boot.vbmeta.device_state=locked
# Other
ro.build.type=user
ro.debuggable=0
ro.secure=1
Click to expand...
Click to collapse
2nd --
service.sh [ORIGINAL from kdrag0n]
# Late props which must be set after boot_completed
{
until [[ "$(getprop sys.boot_completed)" == "1" ]]; do
sleep 1
done
# avoid breaking Realme fingerprint scanners
resetprop ro.boot.flash.locked 1
# avoid breaking OnePlus display modes/fingerprint scanners
resetprop vendor.boot.verifiedbootstate green
}&
Click to expand...
Click to collapse
service.sh [MODIFIED]
# Late props which must be set after boot_completed
{
until [[ "$(getprop sys.boot_completed)" == "1" ]]; do
sleep 1
done
# avoid breaking Realme fingerprint scanners
resetprop ro.boot.flash.locked 1
# avoid breaking Oppo fingerprint scanners
resetprop ro.boot.vbmeta.device_state locked
# avoid breaking OnePlus display modes/fingerprint scanners
resetprop vendor.boot.verifiedbootstate green
}&
Click to expand...
Click to collapse
File Replaced from his last latest release 2.2.1(Zygisk):
1. https://raw.githubusercontent.com/kdrag0n/safetynet-fix/master/magisk/service.sh
2. https://raw.githubusercontent.com/kdrag0n/safetynet-fix/master/magisk/post-fs-data.sh
3. https://raw.githubusercontent.com/kdrag0n/safetynet-fix/master/magisk/system.prop
As I don't know how to build from GitHub, I manually replaced the files shown above. All files are copied from @kdrag0n GitHub Repo [Zygisk version]
Thanks, It work
I just upgrade to android 12 today and fingerprints sensor didn't work
Got an error in the installation.
Device is system-as-root
Unable to extract zip file!
Installation failed
bojiokia said:
Hi, while I am facing this issue, thanks to @BillGoss for highlighting the changes required for people who root/magisk installed.
OxygenOs 12 Beta
OxygenOs 12 CBT for kb2001 - working on all variants (you install at your own risk) https://mega.nz/file/CVsgyaAB#zrRWx1vIKUc6pMmNesu8ywpaUSAJWJecDcROvwOGOug
forum.xda-developers.com
So I compared the file with the original @kdrag0n Universal SafetyNet Fix, and the files required to change is:
credit to @BillGoss & @kdrag0n
1st --
2nd --
File Replaced from his last latest release 2.2.1(Zygisk):
1. https://raw.githubusercontent.com/kdrag0n/safetynet-fix/master/magisk/service.sh
2. https://raw.githubusercontent.com/kdrag0n/safetynet-fix/master/magisk/post-fs-data.sh
3. https://raw.githubusercontent.com/kdrag0n/safetynet-fix/master/magisk/system.prop
As I don't know how to build from GitHub, I manually replaced the files shown above. All files are copied from @kdrag0n GitHub Repo [Zygisk version]
Click to expand...
Click to collapse
How come your zip is 223kb when the one I modified is one only 92kb? See https://forum.xda-developers.com/t/oxygenos-12-beta.4383689/post-86562887
This one's updated with the files from @kdrag0n's GitHub that were updated on the 10th and 12th of March 2022.
Hello, the attached file 'safetynet-fix-v2.2.1.1_Realme_FingerprintFix.zip' does not fix the fingerprint reader for me.
But the other file 'safetynet-fix-v2.2.1-ob1.zip' form the other thread works for me.
My phone version is KB2005_11_C.11, Magisk 24.3 .
I've taken a look into the source code, looks like the issue is now fixed in the commit 55f892fb8855a7867a186970e0bfc31e665ab183. However, @kdrag0n hasn't provided a new release with that commit on Github.
I've cloned the repository (https://github.com/kdrag0n/safetynet-fix.git) and compiled the module myself. I can confirm the module I just compiled fixes the fingerprint issue.
Here's the module I compiled, based on commit 57b726c260bb40b838c5d942965282a5a482bdbe
Hello, thanks for your new patch.
I confirm that the fingerprint reader works with it.
Alas, there is a new issue: Niantic games (e.g. Pokemon Go, Pikmon Bloom ....) wont run now. It looks like there is user authentication issue.
So I'm reverting to 'safetynet-fix-v2.2.1-ob1.zip' for now, where I have both finferprint reader and Niantic games working.
Does anyone have an update solution for the fingerprint problem?
The SaftyNetFix v2.3.1 from kdrag0n does not work for me, the SaftyNet is fine but my fingerprint sensor does not work.
Device: Oneplus 8T EU version OOS12 C.20
Ramme said:
Does anyone have an update solution for the fingerprint problem?
The SaftyNetFix v2.3.1 from kdrag0n does not work for me, the SaftyNet is fine but my fingerprint sensor does not work.
Device: Oneplus 8T EU version OOS12 C.20
Click to expand...
Click to collapse
Did you try previous safetynet-fix-v2.2.1-ob1.zip version?
Yes I have tried all versions from the XDA forum, also from other threads.
I have found the problem. I used Magisk Hide and the SaftyNet script in combination.
Without Magik hide my fingerprint sensor works.
But my CTS profile fails without Magisk Hide.
It is due to the version OOS C.20 "C.21".
Everyone in the OOS forum is reporting a Saftynet problem.
I hope there is a solution from Oneplus as soon as possible.
Ramme said:
Yes I have tried all versions from the XDA forum, also from other threads.
I have found the problem. I used Magisk Hide and the SaftyNet script in combination.
Without Magik hide my fingerprint sensor works.
But my CTS profile fails without Magisk Hide.
It is due to the version OOS C.20 "C.21".
Everyone in the OOS forum is reporting a Saftynet problem.
I hope there is a solution from Oneplus as soon as possible.
Click to expand...
Click to collapse
Hi,
Can you please share the patched boot.img for C.21 IN version, if you have it.
Or tell me the way to patch a boot image.
I am trying with magisk to patch the boot image, but when I do "fastboot boot boot.img" with the patched image, it doesn't work. Magisk doesn't shot Direct install. Basically I am not able to root my C.21 IN version.
Any help would be appreciated.