Database Info

[Solution] Nexus 5 Low or No Mic/Noisy Mic after disabling EndFire

Hey guys,
So this is my first post after visiting XDA for quite some time, so you'll have to forgive my lack of finesse in my formatting. Anyway, I've had the common issue with the microphone in my Nexus 5 where the noise canceling was going overboard or the microphone wasn't picking up my voice well enough even being like 2 cm away. I found previous solutions that end up disabling EndFire in the build.prop. This has worked as a workaround, and a very noisy one as it picks up a ton of environment sound and I would get my own echo with absolute annoying clarity (which is what I'd rather the person on the other end hear). I've had this issue across a great number of roms so I know that those who experience this issue with their microphones won't get a solution by just changing and it goes to show how the software is in fact screwing up somewhere.
So I've done some experimenting from what I can pick up from the great community here and actually sorta stumbled on a two-part solution to this issue. This solution has me so stoked because I had a clean sound for the first time in a long while. So without further ado here's what you do.
First Step:
If you haven't already got a build.prop editor download one (there's tons of free one's out there.) Then find the setting for persist.audio.dualmic.config and set the value to broadside. This is a term I picked out of the mixer_paths.xml file which actually is included in part two of this solution (false will not work, I tried). I don't know what broadside is admittedly but my guess is that it's a dual-mic config as well but isn't used, or maybe it is. Anyway, please also check other audio settings to make sure they match what's in the screenshot as I do know the disabling endfire solution messes with those sometimes. Once you've finished that you can choose to reboot or not you will have to at the end either way.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Second Step:
Alrighty you are doing great thus far. The last step in this can look overwhelming as we are going into the xml file known at mixer_paths.xml. This will look rather daunting for those who are new and maybe never seen a xml file. I know I hadn't until working on this. So to view and edit you can use the file explorer/editor of your choice. I recommend ES explorer as most people do. So you'll navigate to /system/etc/mixer_paths.xml .
Note: Be sure you have root explorer enables if you are using ES Explorer, otherwise you'll get an error when trying to save. That can be found in Menu(Sidebar-thingy)-->Tools-->Root Explorer on the most recent version.
Once you have it opened you may need to scroll all the way down to the bottom of the file as for some reason the file doesn't entirely load the text unless you do. Once the text is loaded go ahead and hit edit.
Now find the line that is called path name="handset-mic">. It will be in about the center of the page if you loaded the whole thing. The whole section looks like this. Pictures are below to see the changes as well.
<path name="handset-mic">
<path name="adc1" />
<ctl name="ADC1 Volume" value="16" />
<ctl name="DEC6 Volume" value="86" />
</path>
You'll be making three changes so it looks like this
<path name="handset-mic">
<path name="adc3" />
<ctl name="ADC3 Volume" value="16" />
<ctl name="DEC4 Volume" value="86" />
</path>
Hit the back button up top and tell it to save.
Then just reboot your phone.
Click to expand...
Click to collapse
Before
After
Admittedly I don't know what changing those things does other than the fact that my microphone woes only happened on calls. I do know whenever I'd send a voice clip through fb and whatnot generally it went through just fine. So my hypothesis is that this forces the phone to uses those "channels" persay as I did pull those three changes from a different part in this xml. I also found the broadside term in this file just below endfire. Maybe it's an unused config, I dunno but it works, so best of luck to you who still need a clean voice calling solution.
Please help this solution get out there as I've yet to see anyone working on the mixer_paths.xml in this fashion (If I'm wrong about that my apologies). I've seen a large number of people trying to adjust the number values but to little success. I hope that this gets out there and proves to be a big solution for the community. Share if this helped!
Be awesome out there,
daScholar

Loud echo
Thank you so much for this! It works, people can hear me now. Trouble is, there's a loud echo on the other end. Meaning that the other person hears their voice really loud making it quite annoying for them.
Any thoughts on this??
Thank you!

chicocardo said:
Thank you so much for this! It works, people can hear me now. Trouble is, there's a loud echo on the other end. Meaning that the other person hears their voice really loud making it quite annoying for them.
Any thoughts on this??
Thank you!
Click to expand...
Click to collapse
I'll look into this for sure. Thanks for the response. I tested this with myself on skype so not exactly the best experiment I'll definitely see if I can replicate this and tweak it so that doesn't happen. I've not heard of the receiving phone getting an echo from itself because of the senders phone settings, but I'm definitely no expert. Thanks for the feedback, will get back to ya soon.

If it helps, the same echo is achieved by making these build.prop edits which I use to combat my ultra-low mic volume on lollipop
persist.audio.fluence.voicecall=false
persist.audio.fluence.voicecomm=false
persist.audio.fluence.voicerec=false

Thanks, but echo continues. Echo is on other end, not my end.

chicocardo said:
Thanks, but echo continues. Echo is on other end, not my end.
Click to expand...
Click to collapse
You've not been given a solution so why wouldn't echo continue?
I'm confused

rootSU said:
You've not been given a solution so why wouldn't echo continue?
I'm confused
Click to expand...
Click to collapse
I thought you posted solution for the echo. I managed to sort out muffled mic with the solution on the initial thread, but with that came the echo from the other end. I thought you posted the solution for it.
Thanks

chicocardo said:
I thought you posted solution for the echo. I managed to sort out muffled mic with the solution on the initial thread, but with that came the echo from the other end. I thought you posted the solution for it.
Thanks
Click to expand...
Click to collapse
No. I was telling the OP that the build.prop edits that I use to combat low mic volume produce the same echo as his solution.

chicocardo said:
I thought you posted solution for the echo. I managed to sort out muffled mic with the solution on the initial thread, but with that came the echo from the other end. I thought you posted the solution for it.
Thanks
Click to expand...
Click to collapse
K So I've been trying to replicate it on my phone and can't seem too. Everyone I called said that things were just normal. Have you tried resolving the mic issue before by boosting the mic or speaker volume? Because maybe that's a factor and needs to be reset/disabled. I'm using a fresh rom install so nothing else audio wise has been touched. One thing I'd try is if you have MultiRom then just install another rom so you have a fresh install to try this fix on.
Another option is to go back to that mixer_paths.xml file and lower the values of either the "handset-mic" or one of the speaker values. I found the solution above with a lot of trial and error seeing what's happening. If nothing changes undo what you did and try another spot. (Make Sure to reset your phone everytime)
Is it everyone you are calling says that?

Just a quick note to the OP: the microphone device "broadside" has been deprecated in the audio HAL as of Android 5.0
I have spent way more time with audio on the Nexus 5 than I probably should have, but believe me, there is no real solution to this problem that can come from this community. At the telephony level, audio is adjusted via proprietary vendor blobs. Also, telephony audio never reaches user space.
Having said that, I did manage to find a workaround that disables array processing while retaining echo and noise control. It involves a custom kernel, Tasker, shell scripts, and a whole lot of TLC. Certainly not recommended for the casual user...

chdloc said:
Just a quick note to the OP: the microphone device "broadside" has been deprecated in the audio HAL as of Android 5.0
I have spent way more time with audio on the Nexus 5 than I probably should have, but believe me, there is no real solution to this problem that can come from this community. At the telephony level, audio is adjusted via proprietary vendor blobs. Also, telephony audio never reaches user space.
Having said that, I did manage to find a workaround that disables array processing while retaining echo and noise control. It involves a custom kernel, Tasker, shell scripts, and a whole lot of TLC. Certainly not recommended for the casual user...
Click to expand...
Click to collapse
I'd be interested... I'm familiar with all those things. Please let me know

rootSU said:
I'd be interested... I'm familiar with all those things. Please let me know
Click to expand...
Click to collapse
Please send me a PM as I do not intend to release my workaround publicly.
It would cause a major support headache...

Thanks for the info I am still on kitkat so that's a good thing to note for sure.
Sent from my Nexus 5 using XDA Free mobile app

chdloc said:
Please send me a PM as I do not intend to release my workaround publicly.
It would cause a major support headache...
Click to expand...
Click to collapse
I can only send pms to people on my friends list. I'll send a request shortly, please accept it.

daScholar said:
<path name="handset-mic">
<path name="adc1" />
<ctl name="ADC1 Volume" value="16" />
<ctl name="DEC6 Volume" value="86" />
</path>
You'll be making three changes so it looks like this
<path name="handset-mic">
<path name="adc3" />
<ctl name="ADC3 Volume" value="16" />
<ctl name="DEC4 Volume" value="86" />
</path>
Click to expand...
Click to collapse
Be careful. What you have done here is change the microphone from the main one (close to the USB port)
to the auxiliary one (close to the headphone port) for the "handset-mic" device. Echo is almost inevitable due
to the close proximity between the microphone and earpiece. As you can see in the mixer file, speakerphone
mode deliberately switches from the main microphone to the auxiliary one for (likely) this very reason.
Also, I suspect that the "handset-mic" device is not even used during cellular telephony when beamforming (any dmic device) is enabled.
I cannot currently verify this suspicion as I have disabled beamforming altogether in my setup. But you can easily check by looking at the output of
Code:
logcat | grep audio_hw_primary
while making a cellular call.
Edit: Just checked, and no, by default the "handset-mic" device is not used while making cellular calls.
Note that dual-microphone processing is enabled only when making cellular calls. Skype, Hangouts, Viber, other VoIP apps, and other random voice recording apps (including Google Now) *will* use the "handset-mic" device and possibly choke when presented with your mixer_paths.xml edit.
Edit: Come to think of it, you guys having issues with low TX levels, try to lower your earpiece (loudspeaker playback) level as much as practical. Depending on what the dual-microphone algorithm (endfire) actually does, it is possible that TX levels are reduced due to the occurrence of double-talk in the presence of very high coupling between the earpiece loudspeaker and the auxiliary microphone. If my theory is correct, then your TX level may be modulated as a function of how loud the far-end is (regardless of whether it's speech or some other background signal).

chdloc said:
Be careful. What you have done here is change the microphone from the main one (close to the USB port)
to the auxiliary one (close to the headphone port) for the "handset-mic" device. Echo is almost inevitable due
to the close proximity between the microphone and earpiece. As you can see in the mixer file, speakerphone
mode deliberately switches from the main microphone to the auxiliary one for (likely) this very reason.
Also, I suspect that the "handset-mic" device is not even used during cellular telephony when beamforming (any dmic device) is enabled.
I cannot currently verify this suspicion as I have disabled beamforming altogether in my setup. But you can easily check by looking at the output of
Code:
logcat | grep audio_hw_primary
while making a cellular call.
Edit: Just checked, and no, by default the "handset-mic" device is not used while making cellular calls.
Note that dual-microphone processing is enabled only when making cellular calls. Skype, Hangouts, Viber, other VoIP apps, and other random voice recording apps (including Google Now) *will* use the "handset-mic" device and possibly choke when presented with your mixer_paths.xml edit.
Edit: Come to think of it, you guys having issues with low TX levels, try to lower your earpiece (loudspeaker playback) level as much as practical. Depending on what the dual-microphone algorithm (endfire) actually does, it is possible that TX levels are reduced due to the occurrence of double-talk in the presence of very high coupling between the earpiece loudspeaker and the auxiliary microphone. If my theory is correct, then your TX level may be modulated as a function of how loud the far-end is (regardless of whether it's speech or some other background signal).
Click to expand...
Click to collapse
Thanks for that info. The strange thing is now I've reverted the mixer file back to the original and I'm not getting all the background noise that I was before... Not quite sure why it's working now. I've still got broadside in my build.prop in place of endfire. Strange thing was is that the first time I had only made that change to the build.prop I still got tons of environment noise. I've only used this on Kitkat and looks like this won't work on lollipop. You we right about the other apps being choked out as I hadn't even thought to look into that, rarely using them. Thanks so much for all the input, being somewhat of a noob to this, all of the info you guys are giving is a treasure trove for me. Thanks.
Edit: Forgot to mention something specifically about that handset-mic device put back to default is causing an echo where I hear myself did you have any suggestions pertaining to that?
Edit: so I changed the ADC3 parts back to ACD1 and left the DEC4 change as is I'm now getting both VoIP and Calls clearly dunno how that's related to the echo though as you said there wasn't anything in the log pertaining to the handset-mic

daScholar said:
K So I've been trying to replicate it on my phone and can't seem too. Everyone I called said that things were just normal. Have you tried resolving the mic issue before by boosting the mic or speaker volume? Because maybe that's a factor and needs to be reset/disabled. I'm using a fresh rom install so nothing else audio wise has been touched. One thing I'd try is if you have MultiRom then just install another rom so you have a fresh install to try this fix on.
Another option is to go back to that mixer_paths.xml file and lower the values of either the "handset-mic" or one of the speaker values. I found the solution above with a lot of trial and error seeing what's happening. If nothing changes undo what you did and try another spot. (Make Sure to reset your phone everytime)
Is it everyone you are calling says that?
Click to expand...
Click to collapse
Thanks for giving it a try. Yeah, everyone is complaining about that issue. I find it wierd that you don´t have that, other users are complaining about the same echo,
Which ROM do you have? I have Cataclyst.
Thanks

daScholar said:
Not quite sure why it's working now. I've still got broadside in my build.prop in place of endfire. Strange thing was is that the first time I had only made that change to the build.prop I still got tons of environment noise.
Click to expand...
Click to collapse
What you are seeing may be related to what I have observed in my own testing several months ago. Broadside seems to be working, but I noticed it being a lot more finicky than endfire in that it would attenuate the TX much more frequently than endfire would. Plus, the first call after a reboot was always bad (echo and noise). Toggling speakerphone fixed that for the remainder of the system uptime. Not sure what is up with that, but I think it is related to calibration. As I said before, the broadside setup has been removed from the audio HAL as of Android 5.0
Edit: Forgot to mention something specifically about that handset-mic device put back to default is causing an echo where I hear myself did you have any suggestions pertaining to that?
Click to expand...
Click to collapse
Do you hear yourself with a delay or does it sound pretty instantaneous?
If it is instantaneous, then what you are hearing is called sidetone. Every handset feeds a low-level copy of the microphone signal back to the loudspeaker in order to make up for the sound blocked by the device being pressed to your ear. The idea is to make a telephone conversation sound more like a natural face-to-face conversation where you can hear yourself clearly without any obstructions that cover your ear. Pretty clever if you ask me.
In your case the sidetone may be too loud.
If you hear yourself with a delay, then the sound is being reflected by either the far-end (acoustic echo) or by the network itself (network echo).
Do you hear yourself when you revert to stock settings throughout your system?
Edit: so I changed the ADC3 parts back to ACD1 and left the DEC4 change as is I'm now getting both VoIP and Calls clearly dunno how that's related to the echo though as you said there wasn't anything in the log pertaining to the handset-mic
Click to expand...
Click to collapse
So how does your mixer_paths.xml file look like? From what you are writing it is not quite clear what you did.

So I've installed the stock 4.4.2 and changed just the build.prop to broadside and it seems to be working thanks for the advice. No changes now to the mixer file.
Sent from my Nexus 5 using XDA Free mobile app

Fixed my phone
I followed both steps, and made tests after each of them.
Step 1 - Fixes the microphone problem, but there are still fade-outs in the voice and possible echoes in noisy conditions.
Step 2 - Resolved the echoes and provides crystal clear clarity.

[MOD][ROOT][G930F]Speaker volume boost

Hello
I give you speaker volume boost for the Galaxy S7, Exynos variants. check under system/etc and mixer_paths.xml with a root explorer.
these are the stock values, I think 30-31 is good, but you can try higher values and see what you think.
<ctl name="DSP5L Input 1 Volume" value="26" />
<ctl name="DSP5L Input 2 Volume" value="26" />

I think I found the values, if anyone else could try and verify it would be good, but I noticed louder sound
<ctl name="DSP5L Input 1 Volume" value="26" />
<ctl name="DSP5L Input 2 Volume" value="26" />
thats the stock values, you could try 30-31.
Tapatalked from GALAXY S7

For a headphone volume hack (not speaker) see here: http://forum.xda-developers.com/galaxy-s7/themes/galaxy-s7-s7-edge-easy-headphone-volume-t3337937

33 its good

thanks
hey thank you for the for that. only im not up to the levels of you guys. I'm just a low level scrub. but i do appreciate it. thanks for the time. dont get that a lot or see it that much now days. well on here " XDA" i do. love this place. thanks to you and everyoneelsehere!

Rooting my Galaxy s7
Hello,
I do not know the first thing about rooting my phone. Can you please explain step by step?

dcova15 said:
Hello,
I do not know the first thing about rooting my phone. Can you please explain step by step?
Click to expand...
Click to collapse
Here's the STEP BY STEP instructions, this is, if you have an Exynos version of the S7 (930F for example)...
http://forum.xda-developers.com/galaxy-s7/development/recovery-official-twrp-herolte-t3333770
Regards,
Chale

wow
Great mod thanks

This thread seems a bit old, but after I thought that flashing the zubi mod with flashfire didn't really yield a lot of difference (at least not noticeable for me), I tried this one. To verify, I actually set the values to 15 and the sound of the speaker was clearly less loud. As 30 didn't yet cut it, I'll try the 33.
What I found though, just as a side note: if you scroll down after changing numbers according to this thread, if you mute incall for the same values (guess this would be speaker phone), and unmute later, the values go back to 26. So I will change this to the same numbers as I'll use for the regular speaker.

Mikegrmn said:
This thread seems a bit old, but after I thought that flashing the zubi mod with flashfire didn't really yield a lot of difference (at least not noticeable for me), I tried this one. To verify, I actually set the values to 15 and the sound of the speaker was clearly less loud. As 30 didn't yet cut it, I'll try the 33.
What I found though, just as a side note: if you scroll down after changing numbers according to this thread, if you mute incall for the same values (guess this would be speaker phone), and unmute later, the values go back to 26. So I will change this to the same numbers as I'll use for the regular speaker.
Click to expand...
Click to collapse
If you don't see difference is because you don't flash the mod correctly, the version that you flash is not for your model or Flashfire is not compatible with this mod
The difference is brutal

zubi182 said:
If you don't see difference is because you don't flash the mod correctly, the version that you flash is not for your model or Flashfire is not compatible with this mod
The difference is brutal
Click to expand...
Click to collapse
Well, I downloaded the proper version and after some initial screen outputs telling me that not all permissions could be set properly, I found the flashfire setting where it said that everything got through properly. Maybe it didn't, but it still said it did. And after having successfully flashed xposed with flashfire, it should also work with the sound mod. Whatever.

Can i use do this with just root without custom recovery?

Wow! Nice trick.
I'm using Lineage OS 17.1 and my s7 is much louder now.
//Push
Found this thread, everyone have to see this too. If not posted already somewhere else on here..

PrevosHD said:
Wow! Nice trick.
I'm using Lineage OS 17.1 and my s7 is much louder now.
//Push
Found this thread, everyone have to see this too. If not posted already somewhere else on here..
Click to expand...
Click to collapse
Alternatively, you could do it systemlessly by using JamesDSP Magisk module's output gain feature.

Mic problem during video calls (G930F)
Hi, great tutorial/info.
I have a PixelExperience Plus custom ROM on my S7 G930F.
I am looking for the mic information as i believe that the mixer_paths file has either lowered the volume or changed which mic it is using as when i am on a video call i have to almost speak into the bottom of the phone, near the charge port. I know it is specific so i may just need to install the stock mixer_paths_0.xml file but i can't find it anywhere online. I dont suppose anyone on here has one saved that i could copy? Should have backed it up but i am a fool ;P
It is only a small problem but as i am not aways at home when my missus puts my son to bed i'd still like to be able to video call properly.
Thanks for your time.

[email protected] said:
Hello
I give you speaker volume boost for the Galaxy S7, Exynos variants. check under system/etc and mixer_paths.xml with a root explorer.
these are the stock values, I think 30-31 is good, but you can try higher values and see what you think.
<ctl name="DSP5L Input 1 Volume" value="26" />
<ctl name="DSP5L Input 2 Volume" value="26" />
Click to expand...
Click to collapse
This work also for me on my Galaxy S7, running Pixel Experience made by Expressluke with Android 13 running also Twrp 3.7 and Magisk 25.2.

Broken main mic, using a seconfary mic

So my main mic is broken, as a temp solution I tried changing it to the secondary mic. I followed these instructions.
"Open up mixer_paths.xml, go to the "main-mic" entry under "Analog input devices", and change the "DEC4 MUX" value from "ADC3" to "ADC5". Then, change all instances of "DEC4" to "DEC2" (there should be 3 of them you need to change). Now, scroll down a bit to "Recording paths" and locate the "handset-mic" entry. Change "ADC3 Volume" to "ADC5 Volume".
Save your changes and reboot. The microphone used for phone calls will now be the one located at the very top of the device, right above the front-facing camera. This is also the microphone that is used when speakerphone is enabled."
At first this worked, but now it only works in audio recording apps. No longer when I'm in a call, unless I get on loudspeaker.
I'm on CM 12.1, anyone have any ideas?

This same thing happened to my wife's phone 2 days now. I can barely hear her on a phone call unless she uses speaker phone. The microphone works using google or in Handsent when voice typing. Hope this isn't a hardware failure. I tried uninstalling any new apps.
Running stock software on her phone. Maybe she wore out the mic.

Hi,
Try this. I hope it works.
Regards

Echo problem when calling (for callers)

Hello,
I have an issue with my Mi MIX 2S. When somebody calls me, they complained because they have a big echo of themselves and its very annoying for both.
If i lower the volume, its better for them but I cant ear them through the speaker.
Some problem in speaker mode. No problem on heatset+mic.
I think when call start, speakers is too loud and both mic sensibility is to high. So if there is a voice cancaling option, it doesnt work correctly or mics are too sensitives.
I contact Xiaomi, no answer to the problem and they wont take the phone because its no longer under warranty.
I contact other users through Xiaomi Forum, some people is having this issue with Mi Mix 2S but also other Xiaomi phones. No real solution and people with this is geting bigger.
I bought the phone just before the official rom goes to MIUI 9 to MIUI 10 (november 2018). I thing, not sure, i didn't have the problem before MIUI 10.
Actual System info :
MIUI Global 10.2.2.0 Stable
What I have done with no solution :
Factory reset = did not solve the problem
Install new official ROM erasing all data. I tried V10.0.2.0.ODEMIFH, V10.0.6.0.PDGMIFH and V10.0.9.0.PDGMIFH = did not solve the problem
Root + TWRP + fallowing this tread [FIX] In call echo and noise from top mic pocophone + Magisk module = did not solve the problem
https://forum.xda-developers.com/poco-f1/themes/fix-noises-echoes-mic-t3886049
For this last one, wizard8400 modified the XLM \vendor\etc\mixer_paths_overlay_static.xml
I supposed that the POCO will have the same directory than MI MIX 2S but no. Or I dont know how.
In TRWP > Advanced > File Manager > Vendor
> lib64
>hw
> (list of .so files)​>compatibility_matrix.xml
>manifest.xlm
Or In TRWP > Advanced > File Manager > Data > Vendor
> Audio > acdbdata > delta > files no XLM
> other files > files no XLM or no files
Anyone have solved this issue or can help me ?
Or how to find, if it exist, a similar file as "mixer_paths_overlay_static.xml" to redefine mic and noise cancellation settings.
Thank you

Hi.
I experience the same problem,when its a good voice connection...i have to lower the volume.Sad situation.I think its a design flaw,speaker to close to mic,resonating materials,something like that.

I have pass the issue of injecting the XLM.
I'm trying different settings as mention by wizard8400 on this tread.
No success for now, I'm asking help in his tread also.
Anyway, if it can help some one to have access to VENDOR, is very simple in fact :
- Need to install TWRP
- In TWRP go to MOUNT, select VENDOR and go back to main screen
- Go to ADVANCED > FILE MANAGER
- VENDOR/ETC/ xlm files are availables

theozmoz said:
Hello,
I have an issue with my Mi MIX 2S. When somebody calls me, they complained because they have a big echo of themselves and its very annoying for both.
If i lower the volume, its better for them but I cant ear them through the speaker.
Some problem in speaker mode. No problem on heatset+mic.
I think when call start, speakers is too loud and both mic sensibility is to high. So if there is a voice cancaling option, it doesnt work correctly or mics are too sensitives.
I contact Xiaomi, no answer to the problem and they wont take the phone because its no longer under warranty.
I contact other users through Xiaomi Forum, some people is having this issue with Mi Mix 2S but also other Xiaomi phones. No real solution and people with this is geting bigger.
I bought the phone just before the official rom goes to MIUI 9 to MIUI 10 (november 2018). I thing, not sure, i didn't have the problem before MIUI 10.
Actual System info :
MIUI Global 10.2.2.0 Stable
What I have done with no solution :
Factory reset = did not solve the problem
Install new official ROM erasing all data. I tried V10.0.2.0.ODEMIFH, V10.0.6.0.PDGMIFH and V10.0.9.0.PDGMIFH = did not solve the problem
Root + TWRP + fallowing this tread [FIX] In call echo and noise from top mic pocophone + Magisk module = did not solve the problem
https://forum.xda-developers.com/poco-f1/themes/fix-noises-echoes-mic-t3886049
For this last one, wizard8400 modified the XLM \vendor\etc\mixer_paths_overlay_static.xml
I supposed that the POCO will have the same directory than MI MIX 2S but no. Or I dont know how.
In TRWP > Advanced > File Manager > Vendor
> lib64
>hw
> (list of .so files)​>compatibility_matrix.xml
>manifest.xlm
Or In TRWP > Advanced > File Manager > Data > Vendor
> Audio > acdbdata > delta > files no XLM
> other files > files no XLM or no files
Anyone have solved this issue or can help me ?
Or how to find, if it exist, a similar file as "mixer_paths_overlay_static.xml" to redefine mic and noise cancellation settings.
Thank you
Click to expand...
Click to collapse
Unfortunately this is a hardware issue but don't know yet is it main mic or noice cancelling mic problem.
My brother have same problem, i order new replacement microphone (5€) and waiting to replace for him, i will report if changing main microphone fix problem.
It can be also problem with ruber band around microphone if not fitting good sound from speaker can leak inside and create echo sound.

Yes please, report if it's a hardware solution.

Dadovvv said:
Unfortunately this is a hardware issue but don't know yet is it main mic or noice cancelling mic problem.
My brother have same problem, i order new replacement microphone (5€) and waiting to replace for him, i will report if changing main microphone fix problem.
It can be also problem with ruber band around microphone if not fitting good sound from speaker can leak inside and create echo sound.
Click to expand...
Click to collapse
Hi there!, bad news from me. I've ordered the same replacement part (and also the speaker which is over the mic part) and the echo didn't dissapear. I've not mounted the speaker part as you can see i my picture it doesn't comes witht the micro connector (red circle in the picture) which I suspect that deliveries the sound from the main mic to the earpiece, I'm asking for a refund of the part. I've tested the new parts calling my daughter and she told me that the echo has decreased but still there. My bet is that the problem is on the earpice. Why? 'cause if I use the headset or the external speaker the problem dissapears. I have to say that my phone has a very small crack at the lower left corner too.
Any idea?
Thanks in advance.

Hi, I'm almost sure that the problem comes, as another member said, from the top speaker (earpiece). I've tried to fix it cancelling the echo mic (using software) but when I try to edit the file I've saw that it's already with the suggested values <ctl name="DEC8 Volume" value="0" />
<ctl name="DEC7 Volume" value="92" />
Now the question is...how to disable the cancellation mic (hardware level)? It's so dangerous to desolder it since it's a and part and the risk of damaging the board is high....Any ideas?
Let's try to find a solution

solmer said:
Hi, I'm almost sure that the problem comes, as another member said, from the top speaker (earpiece). I've tried to fix it cancelling the echo mic (using software) but when I try to edit the file I've saw that it's already with the suggested values <ctl name="DEC8 Volume" value="0" />
<ctl name="DEC7 Volume" value="92" />
Now the question is...how to disable the cancellation mic (hardware level)? It's so dangerous to desolder it since it's a and part and the risk of damaging the board is high....Any ideas?
Let's try to find a solution
Click to expand...
Click to collapse
Thank you for your feedback Solmer.
I'm fallowing the other thread on the Poco where you posted.
The 10.3 is out but I'm unable to install due to the ROOT.
As I Said and as you tried, there is a code line that we are missing because I tried every value possible on the codes given on the poco thread.
As you Said, sound is capturer by the top mik from the top speaker that is not well encapsulated. We need to find thé code to disable thé top mik.

theozmoz said:
Thank you for your feedback Solmer.
I'm fallowing the other thread on the Poco where you posted.
The 10.3 is out but I'm unable to install due to the ROOT.
As I Said and as you tried, there is a code line that we are missing because I tried every value possible on the codes given on the poco thread.
As you Said, sound is capturer by the top mik from the top speaker that is not well encapsulated. We need to find thé code to disable thé top mik.
Click to expand...
Click to collapse
Hi Theozmoz ! yeas the 10.3 is out, I've tested today with no luck, I can confirm that 10.3 doesn't fix the echo bug. Same here...no luck with the code :crying:
I've tried even to put a small piece of gummy tape in front of the top mic with no luck neither....Sometimes the echo starts and it's the same along all the calling time...other times it goes down after a couple of minutes (but doesn't dissapears...). We need a solution :crying: I've bought mine 2 weeks ago and want to use it but first i need to fix the echo. Mine is 2nd hand but the problem is present inn new ones too

Could you please confirm this bug at https://c.mi.com/thread-1894332-1-0.html ?
Regards,

Fr3dY said:
Could you please confirm this bug at https://c.mi.com/thread-1894332-1-0.html ?
Regards,
Click to expand...
Click to collapse
Hi there!, sure right now...let's try to find a solution....Now I'm on Revolution OS v9.3.7 with a firmware who somebody posted ona a TElegram channel, the echo has become lower but not fixed 100%

Anybody solve this issue?

I had the same problem when i had Pixel Experience ROM installed. Everyone did say they can hear themselves and that the quality is very bad.
I flashed the latest MIUI Rom a few days ago and now I have normal quality again. How can this be? Did someone Experience (lol) this too? Want to go back to a custom rom but on custom roms I have this issue which I don't have on MIUI based ROM.

I can confirm on miui 10.3.2.0 editing \vendor\etc\mixer_paths_overlay_static.xml seem to solve echo caller problem
Thanx

hocuspocus69 said:
I can confirm on miui 10.3.2.0 editing \vendor\etc\mixer_paths_overlay_static.xml seem to solve echo caller problem
Thanx
Click to expand...
Click to collapse
Can you help please how to edit?

Kubis01 said:
Can you help please how to edit?
Click to expand...
Click to collapse
you need ROOT
with a file manager
go to \vendor\etc\mixer_paths_overlay_static.xml
then follow https://forum.xda-developers.com/poco-f1/themes/fix-noises-echoes-mic-t3886049
personally i'll use <ctl name="DEC8 Volume" value="40" /> to mantain a little noise cancelling
don't use magisk module i think it was made for pocophone
better to edit directly it
CHEERS

hocuspocus69 said:
you need ROOT
with a file manager
go to \vendor\etc\mixer_paths_overlay_static.xml
then follow https://forum.xda-developers.com/poco-f1/themes/fix-noises-echoes-mic-t3886049
personally i'll use <ctl name="DEC8 Volume" value="40" /> to mantain a little noise cancelling
don't use magisk module i think it was made for pocophone
better to edit directly it
CHEERS
Click to expand...
Click to collapse
do you know if it 's possible to do this on custom roms too?

I don't know sorry but i think it's not a dangerous item(bootloop or brick) as you edit it in right format...so try it but wait a couple of day of use before to toast at it

This device suffers from huge connectivity problems since january updates:
http://c.mi.com/thread-1896725-1-0.html
Some people reports echo, some can't hear caller etc. LTE disconnects and can't reconnect. Phone acts like it has damaged modem.
There were no problems in ROMs before january, I tested few ROMs, some claims that AOSP are better, others that they have much smaller range etc.
Hope that xiaomi will fix that.

Hello,
Repumping this thread. Did someone install the new MIUI 10.3.3.0 for Mi Mix 2s ?
Thx

Question Microphone issues poll. [ Please participate :) ]

Hi, I've noticed that when recording voice notes on instant messaging apps such as WhatsApp or Telegram, the microphone being used for that is the one on the top (near the selfie cameras) instead of the one on the bottom (next to the USB port) and it records in such a bad quality. This issue extends to all apps, including Google voice search and Google assistant.
I've used this app (https://play.google.com/store/apps/details?id=org.greh.mictest) to test the microphone and it only works with the bottom microphone only if you set it to MIC and Stereo, every other setting just uses the top microphone. Also, recording video with the stock camera (using audio zoom or not) records audio with just the top mic too.
If anyone could test their device (either on stock or custom ROM, it doesn't matter as they both use the same mixer path and audio platform info) and answer the poll either with a yes or a no I would be very grateful.
I've factory reset the phone, checked apps that may be conflicting, etc and it's driving me nuts. Motorola support is just suggesting me to replace the phone, but I'm pretty sure this is a software issue.
I'm on the latest stock update if that matters.
EDIT: After more testing on camcorder, stereo recording works fine, but when choosing mono recording, it records sound with the top mic. This done with OpenCamera. Choosing different input options from open camera shows that when you select "Default input" in mono mode, it defaults to the top mic instead of the bottom one.

I am on lineage os 18.1 currently and honestly had no answer for the poor audio quality of my VNs in IM apps... I even developed a practice of asking about my voice clarity during phone calls. Now I understand...
I am going to upgrade to 19.1. If I find a fix or workaround, I will report back here.

I was just doing a little research. Maybe someone can compile an apk or a flashable zip to iron out this bug if Motorola doesn't step on it...
It appears that the "android.permission.RECORD_AUDIO" for IM apps is linked to "MediaRecorder.AudioSource.CAMCORDER" when it should be linked to "MediaRecorder.AudioSource.MIC" or vice-versa.

KnightTheWayne said:
I was just doing a little research. Maybe someone can compile an apk or a flashable zip to iron out this bug if Motorola doesn't step on it...
It appears that the "android.permission.RECORD_AUDIO" for IM apps is linked to "MediaRecorder.AudioSource.CAMCORDER" when it should be linked to "MediaRecorder.AudioSource.MIC" or vice-versa.
Click to expand...
Click to collapse
Nice find, I was taking a look at the stock mixer_paths.xml and the build.prop file under system_ext and found two things, for mono recordings, the mixer_paths.xml redirects all voice recording requests to the "speaker mic" which is set to record from microphone 2 (the top microphone from my testing) and the build.prop file has noise cancelling disabled for speaker and voice recording, if noise cancelling was active, the phone would use the main mic and use the top one for noise cancelling.
I will report this again to Motorola (the first time they just told me to get the phone RMA'd lmao, now I have mor people to back up my claims).

KnightTheWayne said:
I was just doing a little research. Maybe someone can compile an apk or a flashable zip to iron out this bug if Motorola doesn't step on it...
It appears that the "android.permission.RECORD_AUDIO" for IM apps is linked to "MediaRecorder.AudioSource.CAMCORDER" when it should be linked to "MediaRecorder.AudioSource.MIC" or vice-versa.
Click to expand...
Click to collapse
Hey, here are the things I think should be changed for the issue to be resolved (either try one or the other, not the two at the same time so we can see which one of these fixes the issue, if they do at all):
1) In the file '/system_ext/etc/build.prop':
In lines 37 and 38 we can see that noise cancelling is disabled for voice recording and speaker mode, which means that instead of using the bottom mic and the top mic as the noise mic, it's just using one mic, and it's using the wrong one (the top one), this values should be set to true.
2) In the file '/vendor/etc/mixer_paths.xml':
At lines 2177 through 2187 we can see each mic, 'mic1', 'mic2' and 'mic3' being set to 'amic1', 'amic3' and 'amic4' respectively. 'mic1' is the bottom mic, 'mic2' is the top mic and 'mic3' is the audio zoom mic.
Then, at line 2234 we can see that 'speaker-mic' is being set to 'amic3' ('mic2' according to the previous setting) which makes no sense as 'amic3' is the top mic, this should be set to 'amic3'.
I can't try this because my phone is still locked, but if you're rooted you could try this and see if they do work.

blckbear said:
Hey, here are the things I think should be changed for the issue to be resolved (either try one or the other, not the two at the same time so we can see which one of these fixes the issue, if they do at all):
1) In the file '/system_ext/etc/build.prop':
In lines 37 and 38 we can see that noise cancelling is disabled for voice recording and speaker mode, which means that instead of using the bottom mic and the top mic as the noise mic, it's just using one mic, and it's using the wrong one (the top one), this values should be set to true.
2) In the file '/vendor/etc/mixer_paths.xml':
At lines 2177 through 2187 we can see each mic, 'mic1', 'mic2' and 'mic3' being set to 'amic1', 'amic3' and 'amic4' respectively. 'mic1' is the bottom mic, 'mic2' is the top mic and 'mic3' is the audio zoom mic.
Then, at line 2234 we can see that 'speaker-mic' is being set to 'amic3' ('mic2' according to the previous setting) which makes no sense as 'amic3' is the top mic, this should be set to 'amic3'.
I can't try this because my phone is still locked, but if you're rooted you could try this and see if they do work.
Click to expand...
Click to collapse
On any custom ROM I have noise cancelling issues: my caller always hears their own voice when I'm in speaker mode.
So I tried to apply the changes you mentioned on LineageOS 19.1:
1) Cannot be done because lines 37-38 are missing
2) I did it by setting amic1 and then amic4, with a restart each time. But it looks like I broke my phone by doing this, as now calling apps just crash or stop working properly. Do I have to do anything else besides just modifying and restarting the phone? Even after setting it back to amic3, calling apps still crashed.
Edit: I had to update LineageOS to finally fix the problems.
In any case, can you share your stock build.prop and mixer_paths?

Demax55 said:
On any custom ROM I have noise cancelling issues: my caller always hears their own voice when I'm in speaker mode.
So I tried to apply the changes you mentioned on LineageOS 19.1:
1) Cannot be done because lines 37-38 are missing
2) I did it by setting amic1 and then amic4, with a restart each time. But it looks like I broke my phone by doing this, as now calling apps just crash or stop working properly. Do I have to do anything else besides just modifying and restarting the phone? Even after setting it back to amic3, calling apps still crashed.
Edit: I had to update LineageOS to finally fix the problems.
In any case, can you share your stock build.prop and mixer_paths?
Click to expand...
Click to collapse
the mixer paths file is the same on stock and custom roms, the build prop is auto generated so they're different, it wouldn't be a good idea to use the stock build prop in lineage. It's a pitty that the changes made stuff worse. the only thing that comes to mind is to check under /vendor/etc and system/etc for the other build prop files and see which ones have the settings for noise cancelling. I'll extract them from lineage and see if there's anything I can suggest. Thanks for testing tho

Demax55 said:
On any custom ROM I have noise cancelling issues: my caller always hears their own voice when I'm in speaker mode.
So I tried to apply the changes you mentioned on LineageOS 19.1:
1) Cannot be done because lines 37-38 are missing
2) I did it by setting amic1 and then amic4, with a restart each time. But it looks like I broke my phone by doing this, as now calling apps just crash or stop working properly. Do I have to do anything else besides just modifying and restarting the phone? Even after setting it back to amic3, calling apps still crashed.
Edit: I had to update LineageOS to finally fix the problems.
In any case, can you share your stock build.prop and mixer_paths?
Click to expand...
Click to collapse
For the issue you say, you may be able to fix it by changing some stuff inside /vendor/build.prop
In line 134 change "persist.vendor.audio.voicecall.speaker.stereo" from true to false. If this doesn't fix your issue when calling using speaker mode then I'm out of ideas sadly.

blckbear said:
Hey, here are the things I think should be changed for the issue to be resolved (either try one or the other, not the two at the same time so we can see which one of these fixes the issue, if they do at all):
1) In the file '/system_ext/etc/build.prop':
In lines 37 and 38 we can see that noise cancelling is disabled for voice recording and speaker mode, which means that instead of using the bottom mic and the top mic as the noise mic, it's just using one mic, and it's using the wrong one (the top one), this values should be set to true.
2) In the file '/vendor/etc/mixer_paths.xml':
At lines 2177 through 2187 we can see each mic, 'mic1', 'mic2' and 'mic3' being set to 'amic1', 'amic3' and 'amic4' respectively. 'mic1' is the bottom mic, 'mic2' is the top mic and 'mic3' is the audio zoom mic.
Then, at line 2234 we can see that 'speaker-mic' is being set to 'amic3' ('mic2' according to the previous setting) which makes no sense as 'amic3' is the top mic, this should be set to 'amic3'.
I can't try this because my phone is still locked, but if you're rooted you could try this and see if they do work.
Click to expand...
Click to collapse
Hi @blckbear ;
Could you share the exact lines (the content) in /vendor/etc/mixer_paths.xml and /system_ext/etc/build.prop which should be tested? I am on LOS20 and could do the check for you by pulling/pushing the files and changing the lines you are talking about, though on LOS20 it is definitely not /system_ext/etc/build.prop ;-)

blckbear said:
For the issue you say, you may be able to fix it by changing some stuff inside /vendor/build.prop
In line 134 change "persist.vendor.audio.voicecall.speaker.stereo" from true to false. If this doesn't fix your issue when calling using speaker mode then I'm out of ideas sadly.
Click to expand...
Click to collapse
Thanks for the help, but unluckily changing line 134 from true to false did not fix the issue...

blckbear said:
Hey, here are the things I think should be changed for the issue to be resolved (either try one or the other, not the two at the same time so we can see which one of these fixes the issue, if they do at all):
1) In the file '/system_ext/etc/build.prop':
In lines 37 and 38 we can see that noise cancelling is disabled for voice recording and speaker mode, which means that instead of using the bottom mic and the top mic as the noise mic, it's just using one mic, and it's using the wrong one (the top one), this values should be set to true.
2) In the file '/vendor/etc/mixer_paths.xml':
At lines 2177 through 2187 we can see each mic, 'mic1', 'mic2' and 'mic3' being set to 'amic1', 'amic3' and 'amic4' respectively. 'mic1' is the bottom mic, 'mic2' is the top mic and 'mic3' is the audio zoom mic.
Then, at line 2234 we can see that 'speaker-mic' is being set to 'amic3' ('mic2' according to the previous setting) which makes no sense as 'amic3' is the top mic, this should be set to 'amic3'.
I can't try this because my phone is still locked, but if you're rooted you could try this and see if they do work.
Click to expand...
Click to collapse
Using LOS20 build and changed the lines as you mentioned:
In /system/build.prop:
Code:
persist.vendor.audio.voicecall.speaker.stereo=false
In /system/vendor/etc/mxer_paths.xml line 3018:
Code:
<path name="amic1" />
The complete part:
Code:
<path name="speaker-mic">
<path name="amic1" />
</path>
Testing the coming days, will let you know the results.

Moto-J said:
Using LOS20 build and changed the lines as you mentioned:
In /system/build.prop:
Code:
persist.vendor.audio.voicecall.speaker.stereo=false
In /system/vendor/etc/mxer_paths.xml line 3018:
Code:
<path name="amic1" />
The complete part:
Code:
<path name="speaker-mic">
<path name="amic1" />
</path>
Testing the coming days, will let you know the results.
Click to expand...
Click to collapse
Unfortunately people on the phone are complaining about echo every time when on loudspeaker.
So, back to default settings.. ;-)