Related
Description
Fixes in call low volume mic issues for various Android devices.
Can also fix "Ok Google" detection.
Tested on OnePlus One running both Android 6, 7 & 8 Roms
Note: Originally designed for the OnePlus One but will work for some others. Your mileage will vary.
How it works
Uses the tool "resetprop" to modify the default values found in build.prop to:
Code:
ro.qc.sdk.audio.fluencetype=none
persist.audio.fluence.voicerec=true
persist.audio.fluence.speaker=false
use.voice.path.for.pcm.voip=true
Requirements
Magisk v16.0 or higher
Links
Magisk
Support
Github
Donate
Changelog
v3.2.4
Bump to 3.2.4
v3.2.3
Updated template to v1500
v3.2.2
Updated template to v1400
v3.2.1
Fixed Template & cache bug
v3.1.1
Fixed Magisk Manager download bug. Should be good to download through the manager now.
v3.1
Updated template to v4
Updated to Magisk v13.1
v3
Changed to now use PROPFILE
Updated to Magisk v12.0
v2
Name changed from OnePlus One (bacon) Mic Fix
Updated template to v3
v1
Initial Release
.
Perfect I just use this and modify the build prompt. What exactly is the issue from? Is one mic dead and needs replacing thus using this work around or is it something separate to that?
This is a module for magisk. You need to flash that first before flashing this. If you found this thread somehow but don't know what magisk is, I suggest you read up on magisk first. This module modifies the build.prop so you don't need to, and persists through updates.
I'm not sure what the cause is, but it's the same or similar fix that many OPO owners have used.
I love you, really. This finally fixed my microphone issue on my Nexus 6P!
Will this also work on the oneplus 3 and oneplus 3t? I seem to have this mic issue on both 3 and 3t. Thanks.
Poli169 said:
Will this also work on the oneplus 3 and oneplus 3t? I seem to have this mic issue on both 3 and 3t. Thanks.
Click to expand...
Click to collapse
It's untested but has been reported to work on other phones. There's no harm in trying, if you have issues just remove the module. Let me know if it works.
How does this work? After installing this module I checked the build.prop and it's still the same as before but somehow my mic is now working properly.
alif1994 said:
How does this work? After installing this module I checked the build.prop and it's still the same as before but somehow my mic is now working properly.
Click to expand...
Click to collapse
It doesn't change the build.prop file, only what value is loaded for the props at system startup. More info here: https://forum.xda-developers.com/apps/magisk/magisk-details-dummies-to-developers-t3473486
Didgeridoohan said:
It doesn't change the build.prop file, only what value is loaded for the props at system startup. More info here: https://forum.xda-developers.com/apps/magisk/magisk-details-dummies-to-developers-t3473486
Click to expand...
Click to collapse
Oh that is interesting. So I won't have to modify build.prop everytime I update. Thanks for the explanation.
alif1994 said:
Oh that is interesting. So I won't have to modify build.prop everytime I update. Thanks for the explanation.
Click to expand...
Click to collapse
No worries. That's one of the beautiful selling points of Magisk... If you've clean flashed an update, all you have to do is flash the Magisk zip and your modules and voila! All your mods (build.prop, replacing system sounds, debloating apps, moving apps to system, etc) are already done as soon as you boot up! If you do a dirty update all you probably have to do is flash Magisk again since your modules will still be in /data.
Updated for magisk 11.6
Changed name to Android Mic Fix
Which mic issue does this fix? I have phone/audio issues not sure if its connected.
Can't play audio sometimes as phone audio profile is active, would this fix that?
Sent from my Moto G4 Play using XDA Labs
moshiach101 said:
Which mic issue does this fix? I have phone/audio issues not sure if its connected.
Can't play audio sometimes as phone audio profile is active, would this fix that?
Click to expand...
Click to collapse
This only fixes mic issues, sorry
Hi @Nomelas , I have a OPO.
I've installed the module with Magisk and then I took a look at my build.prop. Nothing seems changed, is it normal?
giocchi27 said:
Hi @Nomelas , I have a OPO.
I've installed the module with Magisk and then I took a look at my build.prop. Nothing seems changed, is it normal?
Click to expand...
Click to collapse
Run getprop command in terminal. Your actual build.prop isn't updated because of the nature of Magisk.
Nomelas said:
Run getprop command in terminal. Your actual build.prop isn't updated because of the nature of Magisk.
Click to expand...
Click to collapse
Ok, with getprop I can see them.
Sorry, it's my first time with Magisk.
Hi, so far I only found "it fixes mic issues". Maybe I'm being selectively blind, but could someone please state which mic issues this fixes?
I'm on HTC one M7 using the last lineage os before it was discontinued for M7, and I do suffer low mic output in calls, and the phone occasionally reboots if I switch speakerphone on during a call (weirdly only when maps is running navigation), but does this have anything to do with those "mic issues"?
Thanks, and please forgive my blindness if it's obvious!
damac said:
Hi, so far I only found "it fixes mic issues". Maybe I'm being selectively blind, but could someone please state which mic issues this fixes?
I'm on HTC one M7 using the last lineage os before it was discontinued for M7, and I do suffer low mic output in calls, and the phone occasionally reboots if I switch speakerphone on during a call (weirdly only when maps is running navigation), but does this have anything to do with those "mic issues"?
Thanks, and please forgive my blindness if it's obvious!
Click to expand...
Click to collapse
yeah, test it out yourself. It fixes the low volume of your mic in calls.
Nomelas said:
yeah, test it out yourself. It fixes the low volume of your mic in calls.
Click to expand...
Click to collapse
I tested, but get instant reboot on initiating a call. Switching the module off in magisk made the phone behave normal again. Anything I can do to help track down the cause?
damac said:
I tested, but get instant reboot on initiating a call. Switching the module off in magisk made the phone behave normal again. Anything I can do to help track down the cause?
Click to expand...
Click to collapse
Unfortunately it's only been tested on a few devices. What device are you using?
EDIT: Nevermind, I see in your previous post: HTC one M7 using the last lineage os.
Ah so, I'm not sure what your issue is. It looks to be that because you would get reboots when switching to speakerphone in calls, this fix will only amplify that effect. Unfortunately I don't think I can be of any help to you. I'm sorry :/
I would suggest checking out the HTM M7 sub-forum for support in this case.
https://2.bp.blogspot.com/-
[B][U][SIZE="4"][PLAIN]XDA:DevDB Information[/PLAIN][/SIZE][/U][/B]
[SIZE=3][B]Resurrection Remix For The Huawei P9 Lite, ROM for the Huawei P9 Lite[/B][/SIZE]
[B][U]Contributors[/U][/B]
[URL="https://forum.xda-developers.com/member.php?u=4400604"]Meticulus[/URL]
[B]Source Code:[/B] [URL="https://github.com/Meticulus/android_kernel_huawei_hi6250_4.1"]https://github.com/Meticulus/android_kernel_huawei_hi6250_4.1[/URL]
[B]ROM OS Version:[/B] 7.x Nougat
[B]ROM Kernel:[/B] Linux 4.x
[B]Based On:[/B] AOSP, LineageOS
[B][U]Version Information[/U][/B]
[B]Status:[/B] Testing
[B]Created[/B] 2017-12-05
[B]Last Updated[/B] 2018-01-18
Unblock me on Gmail xd nice job and apreciet or return
Hi, this is I flashed 5 days ago, all is working great, I am facing only 1 problem, Viper is going off after screen off. How can I prevent this? Have any solution?
Thanks for your hard work.
Anonda said:
Hi, this is I flashed 5 days ago, all is working great, I am facing only 1 problem, Viper is going off after screen off. How can I prevent this? Have any solution?
Thanks for your hard work.
Click to expand...
Click to collapse
Try to disable battery optimization for the app...
Anonda said:
Hi, this is I flashed 5 days ago, all is working great, I am facing only 1 problem, Viper is going off after screen off. How can I prevent this? Have any solution?
Thanks for your hard work.
Click to expand...
Click to collapse
In stock emui 5.0, i installed Viper through magisk and no problem whatsoever, of Viper being disabled, after screen off.
Nomatrix said:
In stock emui 5.0, i installed Viper through magisk and no problem whatsoever, of Viper being disabled, after screen off.
Click to expand...
Click to collapse
disable battery optimization for the app.. tw1st3d83 was replayed this in thread
go in settings>battery>more settings>optimize battery(somethink like that, i use different language not eng in rom)>show all apps>music> dont optimize
same to viper
my bad.... thouth that you use RR
for stock emui5 go in settings>battery and there will be option to close apps when screen is off. Go in and uncheck viper and now app will not close after you lock phone
V4A not working.
@Meticulus will probably fix call issues soon since muting calls are impossible.
How to fix usual bugs?
Can't see phone dialer when calling someone?
Go to settings -> Default Apps -> Phone -> Set Phone app as default.
Fingerprint force close? Can't add a new FP?
Go to settings -> Privacy -> Lock screen method -> Select PIN or Password.
(It's because you can't use a gesture lock screen for fingerprint)
Google Pixel launcher doesn't show notifications for new messages/ missed calls/ etc.
Well that's because Pixel devices don't support badge icon counter. You may find something in play store or use Nova Launcher instead or something.
Viper4Android doesn't work?
Flash Magisk 14 from Extras in Meticulus TWRP.
How to pass Safetynet check?
Download and flash this> https://forum.xda-developers.com/showpost.php?p=73432221&postcount=1075
Coolyou said:
@Meticulus will probably fix call issues soon since muting calls are impossible.
How to fix usual bugs?
Fingerprint force close? Can't add a new FP?
Go to settings -> Privacy -> Lock screen method -> Select PIN or Password.
(It's because you can't use a gesture lock screen for fingerprint)
Google Pixel launcher doesn't show notifications for new messages/ missed calls/ etc.
Well that's because Pixel devices don't support badge icon counter. You may find something in play store or use Nova Launcher instead or something.
Viper4Android doesn't work?
Flash Magisk 14 from Extras in Meticulus TWRP.
How to pass Safetynet check?
Download and flash this> https://forum.xda-developers.com/showpost.php?p=73432221&postcount=1075
Click to expand...
Click to collapse
Tried V4A fix and doesn't work, it installs drivers, but if i go to driver status it says:"Enabled:No", how can i fix this?
RawKnighy said:
Tried V4A fix and doesn't work, it installs drivers, but if i go to driver status it says:"Enabled:No", how can i fix this?
Click to expand...
Click to collapse
First install init.d light from F-Droid. Then use Magisk modul.
ScanX said:
First install init.d light from F-Droid. Then use Magisk modul.
Click to expand...
Click to collapse
Now it says:"Enabled:yes, Processing:No" so still nothing.
Oh... forgot Busybox. For me its working. Hope that helps you too!
ScanX said:
Oh... forgot Busybox. For me its working. Hope that helps you too!
Click to expand...
Click to collapse
Already installed
Another great work <3
The issue with the signal being lost seems to be fixed in the latest build
Sent from my HUAWEI P9 lite using Tapatalk
SoT is great. Everything worked mostly smooth. But one thing, i can't connect with my MiBand 2 on BT. He don't find it.
Coolyou said:
@Meticulus will probably fix call issues soon since muting calls are impossible.
How to fix usual bugs?
Can't see phone dialer when calling someone?
Go to settings -> Default Apps -> Phone -> Set Phone app as default.
Fingerprint force close? Can't add a new FP?
Go to settings -> Privacy -> Lock screen method -> Select PIN or Password.
(It's because you can't use a gesture lock screen for fingerprint)
Google Pixel launcher doesn't show notifications for new messages/ missed calls/ etc.
Well that's because Pixel devices don't support badge icon counter. You may find something in play store or use Nova Launcher instead or something.
Viper4Android doesn't work?
Flash Magisk 14 from Extras in Meticulus TWRP.
How to pass Safetynet check?
Download and flash this> https://forum.xda-developers.com/showpost.php?p=73432221&postcount=1075
Click to expand...
Click to collapse
I just flashed this great ROM following the instructions and I'm facing this phone bug
I'm not sure about the first point: The standard phone app is set but I cant't see the phone dialer when calling someone nor hear him. Is there a workaround?
THX in advance.
Finally my solution was to enable 3G for phone calls. Everything is fine now.
Hello all. This rom is very good and I'm using it for a while now, the only problem is that it seems I can't go past 4h of sot. Does anyone know why that's happening?
maartenw8 said:
Hello all. This rom is very good and I'm using it for a while now, the only problem is that it seems I can't go past 4h of sot. Does anyone know why that's happening?
Click to expand...
Click to collapse
You need to change your habits... Uninstall apps that you do not use, uninstall any magisk or xposed modules that do not use etc...
Im getting around 6h of sot after changing my habits and uninstalling unnecessary apps and sh*t
Rom is really amazing!
Hey all, no idea where else to post this, i rooted my phone and everything is fine (except for lucky patcher not working at all), im using magisk hide for certain apps and games like pokemon go, super mario run and mario kart tour, all 3 of these games crash/close/will not work, with a rooted phone thats NOT using magisk hide. All 3 of these games work fine its just pokemon masters not working.....Its it an incompatibility issue? Magisk hide is clearly working as intended.
Using EU version of the phone on android 9 with MIUI Global 10.3.3 stable.
JasonBjorn said:
Hey all, no idea where else to post this, i rooted my phone and everything is fine (except for lucky patcher not working at all), im using magisk hide for certain apps and games like pokemon go, super mario run and mario kart tour, all 3 of these games crash/close/will not work, with a rooted phone thats NOT using magisk hide. All 3 of these games work fine its just pokemon masters not working.....Its it an incompatibility issue? Magisk hide is clearly working as intended.
Using EU version of the phone on android 9 with MIUI Global 10.3.3 stable.
Click to expand...
Click to collapse
Never played pokeman, so can't give definite answers.
Have you hidden Magisk itself? Are you on the latest Magisk 20.1?
If both of these are true, then someone with experience of getting pokeman working on this phone will need to step in.
Robbo.5000 said:
Never played pokeman, so can't give definite answers.
Have you hidden Magisk itself? Are you on the latest Magisk 20.1?
If both of these are true, then someone with experience of getting pokeman working on this phone will need to step in.
Click to expand...
Click to collapse
hidden magisk and am on the latest build yes.
Delete or rename your TWRP folder and it will work.
lordgumo said:
Delete or rename your TWRP folder and it will work.
Click to expand...
Click to collapse
That did indeed work lmao thank you. Just changed it to Twerp.
I have two Xiaomi phones, one Redmi Note 8 and one Redmi Note 10, both with unlocked bootloaders. I made a fresh factory reset on them and installed the latest version of Magisk.
My problem is that SN basicintegrity fails on both of them (and ctsProfile as well of course). But I want to take care of basicintegrity first.
What I have done already is to enable MagiskHide and also Hide Magisk app with a custom name.
For MagiskHide, I selected all modules under "Google Play services" and "Google Play Services for AR". Not sure if I should select anything else. I also tested hiding with a root checker app and it looks that hiding works.
I have no Magisk modules installed. Using stock ROM on both phones.
Is there anything else I should to to pass basicintegrity SN?
API error?
If so, just wait for some days new version will solve this problem.
Pixel 3 XL on android 11 with magisk 22. Safetynet passed up until a few days ago. Not now tho. I wonder what changed?
Guys just put some more effort into searching, there is one big Magisk support thread and lot of discussion about this issue
Update to latest Canary
https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-debug.apk
Lord Sithek said:
Guys just put some more effort into searching, there is one big Magisk support thread and lot of discussion about this issue
Click to expand...
Click to collapse
It's difficult to find info in one big thread, not sure why that's how most discussion happens. Separate threads make more sense.
hkjo said:
It's difficult to find info in one big thread, not sure why that's how most discussion happens. Separate threads make more sense.
Click to expand...
Click to collapse
Multiplying posts doesn't make sense in my opinion. Several different threads were created for the same issue. It's not really that difficult to check few last pages of the main support thread since the issue is relatively new
Yeah, multiple threads on the same topic aren't good.
But one big thread that mixes different discussions beats the whole idea. Threads were invented for a reason. To concentrate discussion on a specific topic or sub-topic, and to have a sensible title. To save you from scanning posts in a megathread to find out if they're about your topic or not. Also, not all discussion is necessarily recent.
I had the exact same issue yesterday.
A quick search of the support thread took me to
The solution
wfred said:
I had the exact same issue yesterday.
A quick search of the support thread took me to
The solution
Click to expand...
Click to collapse
Hello,
Please, if you could—I hope you could—post the link to the solution you found. The masked link isn't working.
Thanks!
Cyb3rFr4nk said:
Hello,
Please, if you could—I hope you could—post the link to the solution you found. The masked link isn't working.
Thanks!
Click to expand...
Click to collapse
The linked solution is:
Update Magisk (to build 22103 or later).
This thread is about the Magisk apps SafetyNet checker extension needing an update due to an API error. SafetyNet wasn't actually failing...
If you need a few tips on how to get SafetyNet passing, there are some collected here:
https://www.didgeridoohan.com/magisk/MagiskHide#hn_SafetyNet
Cyb3rFr4nk said:
Hello,
Please, if you could—I hope you could—post the link to the solution you found. The masked link isn't working.
Thanks!
Click to expand...
Click to collapse
Here you go, don't know why it was messed up
Magisk General Support / Discussion
This is the place for general support and discussion regarding "Public Releases", which includes both stable and beta releases. All information, including troubleshoot guides and notes, are in the Announcement Thread
forum.xda-developers.com
Basically it was moving to the canary
Didgeridoohan said:
The linked solution is:
Update Magisk (to build 22103 or later).
This thread is about the Magisk apps SafetyNet checker extension needing an update due to an API error. SafetyNet wasn't actually failing...
If you need a few tips on how to get SafetyNet passing, there are some collected here:
https://www.didgeridoohan.com/magisk/MagiskHide#hn_SafetyNet
Click to expand...
Click to collapse
Thank you!
I had visited the link to your site, through Google search, while searching for a fix. I also went to magisk general discussion thread, and started reading from April 23rd backwards, in a bid to locate/trace "the solution." While doing that, I came across "the solution," but didn't really try that as I'm on a later stable build (23000) than that canary build.
Background: I started facing this issue, yesterday, after I installed 23.0, from 20.4—which I had been on for a long time and didn't really want to upgrade from to avoid something like this, but after updating my Redmi Note 7 to MIUI 12.5 (Q) (I'm on xiaomi.eu stable), I started having restarts. So, I made the jump.
The restarts stopped after uninstalling that build, so I decided to upgrade to the latest stable. Did that, only to find that SafetyNet no longer passes. Basic integrity fails, and that was before installing EdXposed, which usually causes this. When I first noticed it, I checked my Play Store for device certification status, and it came out positive. That changed after a couple of reboots—I don't know which one in particular, as there were quite some during that time.
I've tried everything—except uninstalling and re-installing magisk—without success: different versions of Universal SafetyNet Fix, MagiskHide Props, enabling and disabling MH.
I have decided to put up with it. Since only a couple of my apps are affected (no GPay in my country), I am trying to make do without them until I get my new phone. Don't wish to do something that would require a factory reset/data wipe, as this is currently my DD, and I'd hate to get stranded.
Thanks all the same.
wfred said:
Here you go, don't know why it was messed up
Magisk General Support / Discussion
This is the place for general support and discussion regarding "Public Releases", which includes both stable and beta releases. All information, including troubleshoot guides and notes, are in the Announcement Thread
forum.xda-developers.com
Basically it was moving to the canary
Click to expand...
Click to collapse
Cyb3rFr4nk said:
Thank you!
I had visited the link to your site, through Google search, while searching for a fix. I also went to magisk general discussion thread, and started reading from April 23rd backwards, in a bid to locate/trace "the solution." While doing that, I came across "the solution," but didn't really try that as I'm on a later stable build (23000) than that canary build.
Background: I started facing this issue, yesterday, after I installed 23.0, from 20.4—which I had been on for a long time and didn't really want to upgrade from to avoid something like this, but after updating my Redmi Note 7 to MIUI 12.5 (Q) (I'm on xiaomi.eu stable), I started having restarts. So, I made the jump.
The restarts stopped after uninstalling that build, so I decided to upgrade to the latest stable. Did that, only to find that SafetyNet no longer passes. Basic integrity fails, and that was before installing EdXposed, which usually causes this. When I first noticed it, I checked my Play Store for device certification status, and it came out positive. That changed after a couple of reboots—I don't know which one in particular, as there were quite some during that time.
I've tried everything—except uninstalling and re-installing magisk—without success: different versions of Universal SafetyNet Fix, MagiskHide Props, enabling and disabling MH.
I have decided to put up with it. Since only a couple of my apps are affected (no GPay in my country), I am trying to make do without them until I get my new phone. Don't wish to do something that would require a factory reset/data wipe, as this is currently my DD, and I'd hate to get stranded.
Thanks all the same.
Click to expand...
Click to collapse
Since version 8.3.0 additional measures to detect root have been added, do not update as MagiskHide won't be able to prevent detection. Until a solution is found I would recommend staying on the previous version for as long as possible.
Finding out what exactly is causing the root detection is beyond my technical abilities but I would provide as much information needed to those willing to help.
---
Update: December 14th 2021 - Method no longer sufficient
---
The solution found by @pxrave appears to be working:
pxrave said:
Hey fellas I got it working and others apps detect magisk before.
Update to latest v23
Install modules riru and riru unshare
Remove data from tan app
Go to magisk hide and tick all process to hide included the isolated
Start the tan app and do the activation again.
Problem you need wait 2 days to activate because comdirect use new activation process for photo tan app.
Working fine all version 8.3
Click to expand...
Click to collapse
Link to the Riru Unshare module:
GitHub - vvb2060/riru-unshare
Contribute to vvb2060/riru-unshare development by creating an account on GitHub.
github.com
also stcpay yesterday is updated to 1.6 and started to detect my magisk canary (22105)
I can confirm what swour says.
on Android 9 and 11, my magisk root is recognized, magiskhide is active and the phototan app is added.
Yes this is a serious problem. I used xposed magisk and x privacy... Latest comdirect tan app detect all...
+1
+1 big issue for me
Only solution I found (for now): Go back to version 8.2.1 using a backup or any mirror, e.g. https://downloadapk.net/comdirect-photoTAN-App.html
Unfortunately you need to register again then
I have already applied the update. The easiest method is to wait few days for a magisk fix, right? I would can wait few days, no problem. I have an absolutly clean Android 8.1 build on the phone for banking. It's crazy that the bank is make it so difficult for us to use a save own build.
allrightlite said:
The easiest method is to wait few days for a magisk fix, right? I would can wait few days, no problem.
Click to expand...
Click to collapse
Perhaps that is too optimistic. I doubt that one app is of great interest
Asellus said:
one app is of great interest
Click to expand...
Click to collapse
Until the new root detection is also available for other apps, it will be fixed quickly.
Conan179 said:
Until the new root detection is also available for other apps, it will be fixed quickly.
Click to expand...
Click to collapse
Thanks, then I will easly wait. No need to reactivate hopefully.
Conan179 said:
Until the new root detection is also available for other apps, it will be fixed quickly.
Click to expand...
Click to collapse
Yes, of course, if other app developers find a similar way. So, congrats to the developers of the phototan app to find it.
Asellus said:
Yes, of course, if other app developers find a similar way. So, congrats to the developers of the phototan app to find it.
Click to expand...
Click to collapse
I don't think so, there is at least one other app that shows the same behavior.
new root dedction
i updated stc pay yesterday to 1.6 and it found my magisk canary (22105) the think i notes is the (isolated) is added to the app !!!
forum.xda-developers.com
I also noticed the (isolated) thing with me.
I tried with v23 this morning, w/o success :-(
Same here, got v23 and working safetynet-fix, no success. Downgraded photoTAN to v8.2.1 .
+1
I'm not surprised, there is nothing in the changelog that this has been fixed.
Downgrading to 8.2.0 or 8.2.1 doesn't work for me. Did you do something else than uninstalling 8.3.0 and installing 8.2.1?
muschi.muscholini said:
Downgrading to 8.2.0 or 8.2.1 doesn't work for me. Did you do something else than uninstalling 8.3.0 and installing 8.2.1?
Click to expand...
Click to collapse
I have a ZTE Blade L130 with the old photo tan app, that is my rescue. But you can't activate the old one. But it's keep working.
muschi.muscholini said:
Downgrading to 8.2.0 or 8.2.1 doesn't work for me. Did you do something else than uninstalling 8.3.0 and installing 8.2.1?
Click to expand...
Click to collapse
I had to unhide the app in magisk hide and hide it again, after that it worked.