Database Info

Fix for low microphone volume in kitkat

So guys after a lot of research and playing around I have discovered a fix for the low microphone volume that we have since the kitkat update. Apparently it has to do with the way the audio config was changed between JB and KK.
The offending file is mixer_paths_VY55.xml in the /system/etc/ directory.
I changed the lines
Code:
<ctl name="DEC1 Volume" value="84" />
<ctl name="DEC2 Volume" value="84" />
to
Code:
<ctl name="DEC1 Volume" value="99" />
<ctl name="DEC2 Volume" value="99" />
I think this variable might have something to do with audio decoding (pretty sure I'm wrong and subject to correction).
Anyway, I have edited all the mixer_paths files to include this change and put them in a zip.
INSTALLATION:
You will need to be rooted (http://forum.xda-developers.com/xperia-m2/general/guide-root-kitkat-d2303-d2302-unlocked-t2898954)
Install a root explorer app
Delete the four mixer_paths files in /system/etc/
And you will need to copy the files in the zip to this location
Set their permissions to rw-r--r--
Reboot your device and enjoy your boosted mic!
To other people out there with other phones trying to fix their low kitkat mic volumes, try looking for a value in mixer_paths.xml related to the microphone that has a value of 84, and change it to 99
PS: PLEASE AVOID using the built in sony notes app to record or playback audio, it is buggy, does not work properly, and to get your audio to work normally you need to close the app.

What about Lollipop?
Do you know if this fix works in Lollipop?
I've just bougth this cellphone and it came with lollipop already. What can I do to fix it? Thanks

Guys just tried on M2 Aqua Lollipop 5.1.1 18.6.A0.182
There are only 3 archives: mixer_paths, mixer_paths_VY55 e mixer_paths_VY58. Changed the numbers and now the volum is so much better
Very happy, thank you

works fine 10x

Any solution for Ice Cream Sandwich, i have same problem but these files are absent in my device

Excellent work ismithx - just cured my "mic-dead" Xperia M2 !! - Now working better than ever !!

that works well for Lollipop
Thanks a lot! :good:

Really need help - just tried to use this on my Sony M2 but quickly found that I can't make calls - as soon as the receiver picks up my phone restarts?! I tried to change the value back to 84 since low volume is better than no volume but it keeps saying "Failed saving mixer_paths_VY55.xml"!! I also tried to reset my phone but it's still there, no idea what to do please help!

Tested on msm8909 lollipop [WORKING]
tquin said:
Do you know if this fix works in Lollipop?
I've just bougth this cellphone and it came with lollipop already. What can I do to fix it? Thanks
Click to expand...
Click to collapse
I required this solution because the device I tested always has a low mic volume on Viber. It works fine with WhatsApp and normal calls though. And this device is having a qualcomm msm8909 chipset. it is not an Xperia M2.
In my case I had these 7 files inside /system/etc
mixer_paths.xml
mixer_paths_msm8909_pm8916.xml
mixer_paths_qrd_skuh.xml
mixer_paths_qrd_skui.xml
mixer_paths_skua.xml
mixer_paths_skuc.xml
mixer_paths_skue.xml
I tested one by one because there was not mixer_paths_VY55.xml in my device as ismithx said.
Finally I succeeded with mixer_paths_skue.xml

[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.

Thoughts - Force High Impedance Mode without external cables

It seems not everyone is aware of the "High Impedance" mode for the DAC.
It's the best mode and the audio quality seems to be the best.
You can only trigger it with connecting high impedance headphones,
Or, like many here do, hassle your way with cables to trick it into this mode
(For example - i use extension cable+audio technica anc33is = triggers "High Impedance" mode).
Personally i think it is absurd to go through all those tricks just to get good audio quality.
I guess it exist to prevent headphone damage / battery),
But really, i'd like to get the full power from the audio chip, because that's what i bought, without traveling with tons of cables.
Now for the actual stuff:
Any ideas how to remove the software limit and force it into "high impedance" always?
Perhaps some *.prop file, or..? How would you approach this.

In fact @HocqpepaTy has provided a method to triggers "High Impedance" mode without external cables in the DAC-Fix thread.
1. You need root on your phone
2. Using a root explorer, mount R/W and navigate to system/etc
3. Go to /system/etc/mixer-paths.xml (remember to backup it first)
4. Find this part of code, change the value of "headphones-hifi-dac" from "31" to "13" to make normal mode same as AUX mode, also, "0" for High Impedance Mode
Code:
<path name="headphones-hifi-dac">
<ctl name="Es9018 Master Volume" value="31" />
</path>
<path name="headphones-hifi-dac-advanced">
<ctl name="Es9018 Master Volume" value="0" />
</path>
<path name="headphones-hifi-dac-aux">
<ctl name="Es9018 Master Volume" value="13" />
</path>
5. Change permissions of mixer-paths.xml to 0644. (rw-r-r)
6. Reboot.
PS: After reboot, it will not change the text, still showing "normal audio device", but the changes in sound is noticeable.

ivangundampc said:
In fact @HocqpepaTy has provided a method to triggers "High Impedance" mode without external cables in the DAC-Fix thread.
1. You need root on your phone
2. Using a root explorer, mount R/W and navigate to system/etc
3. Go to /system/etc/mixer-paths.xml (remember to backup it first)
4. Find this part of code, change the value of "headphones-hifi-dac" from "31" to "13" to make normal mode same as AUX mode, also, "0" for High Impedance Mode
Code:
<path name="headphones-hifi-dac">
<ctl name="Es9018 Master Volume" value="31" />
</path>
<path name="headphones-hifi-dac-advanced">
<ctl name="Es9018 Master Volume" value="0" />
</path>
<path name="headphones-hifi-dac-aux">
<ctl name="Es9018 Master Volume" value="13" />
</path>
5. Change permissions of mixer-paths.xml to 0644. (rw-r-r)
6. Reboot.
PS: After reboot, it will not change the text, still showing "normal audio device", but the changes in sound is noticeable.
Click to expand...
Click to collapse
Thanks, I did this and sound got louder and clearer, I tested with Chopin piano sonata :good:

melorib said:
Thanks, I did this and sound got louder and clearer, I tested with Chopin piano sonata :good:
Click to expand...
Click to collapse
Found a way to change analog gain value without having to mess around with editing Mixer_paths.xml and what not.
Assuming you're rooted download ALSAMixer from Google Play install ALSA from in the app and make sure you select alsa_amixer controls as your Mode in settings in the ALSAMixer App.
After that search for Es9018 Master Volume and change the value to anything from 0 to 80. 0 being max volume like High Impedance mode is set to.
This isn't permanent and will reset on restart but it's nice to be able to change analog volume on the fly.

Thanks to ivangundampc for this trick.
Thanks also to KosanRio for the alsamixer tweak. I'm curious if the end result is the same (with a '0' value in alsamixer or in /system/etc/mixer-paths.xml)...

oleg77 said:
Thanks to ivangundampc for this trick.
Thanks also to KosanRio for the alsamixer tweak. I'm curious if the end result is the same (with a '0' value in alsamixer or in /system/etc/mixer-paths.xml)...
Click to expand...
Click to collapse
It is I believe, plugging in Aux/High-impedance headphones/normal headphones will all give you the exact same value in AlsaMixer as it does in Mixer_paths.xml

finally a superb sound out of the box
:good:
I'm relieved not to have to use an adapter cable with the V10 anymore !

Edit, nevermind.

melorib said:
Thanks, I did this and sound got louder and clearer, I tested with Chopin piano sonata :good:
Click to expand...
Click to collapse
I ran into this blog struggling with trying to get more gain out of my V10. I'm on MM and rooted. I currently do not hear the quick silence switching between HiFi ESS DAC and back to the SoC DAC. I previously had a V10 that was on LP and I could hear the serious difference. The only output I can get out of my phone is the SoC.
In regards to this mixer paths edit, does the lower number (in this case 13) change the audio gain to output more voltage? Also, you state "0" for high impedence mode. Am I supposed to change the 0 to 13 as well?
I really wish I could understand this more. I have V4A installed and running without issues - which I did in the past on LP. Now I'm just baffled I can't figure out what's going on.
Thanks in advance!

joesee said:
I ran into this blog struggling with trying to get more gain out of my V10. I'm on MM and rooted. I currently do not hear the quick silence switching between HiFi ESS DAC and back to the SoC DAC. I previously had a V10 that was on LP and I could hear the serious difference. The only output I can get out of my phone is the SoC.
In regards to this mixer paths edit, does the lower number (in this case 13) change the audio gain to output more voltage? Also, you state "0" for high impedence mode. Am I supposed to change the 0 to 13 as well?
I really wish I could understand this more. I have V4A installed and running without issues - which I did in the past on LP. Now I'm just baffled I can't figure out what's going on.
Thanks in advance!
Click to expand...
Click to collapse
Someone correct me if I'm wrong but I think 0 is for high gain mode. 13 is for Aux mode.
If you don't want to mess with xml you can download the alsa app and play with that a bit.
Head over to head-fi.org there are more forum posts on getting best sound out of the V10.
Sent from my LG-H901 using Tapatalk

gustav30 said:
Someone correct me if I'm wrong but I think 0 is for high gain mode. 13 is for Aux mode.
If you don't want to mess with xml you can download the alsa app and play with that a bit.
Head over to head-fi.org there are more forum posts on getting best sound out of the V10.
Sent from my LG-H901 using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply! I tried out the Alsa app, but when I select the controls (not scontrols) nothing appears in the list. Not sure what I'm doing wrong? I granted it root access. The error I get is: "error: only position independent executables (PIE) are supported."
I think there's something wrong with the ROM in general. This is complete stock with only root. Previously I could tell when the DAC was enabled by a short period of silence, and the volume would then be reduced. Also, when the volume was at 0 it was at the far left and would go all the way to the right as "max", and when it's on it would start at 0 at the far left, then only go to 75 (which is the DAC's max volume setting).
The confusion here is I can't get any difference in sound no matter what I do. Even if I trick the DAC into aux mode, nothing changes. Trying to adjust the balance in the HiFi settings page does nothing.
When I had LP installed, it worked PERFECT. I used the DAC only on flac files when I was home sitting in my chair, and would leave the DAC off for mp3's and Spotify while traveling because the volume would go higher to overcome the aircraft noise.

joesee said:
Thanks for the reply! I tried out the Alsa app, but when I select the controls (not scontrols) nothing appears in the list. Not sure what I'm doing wrong? I granted it root access. The error I get is: "error: only position independent executables (PIE) are supported."
I think there's something wrong with the ROM in general. This is complete stock with only root. Previously I could tell when the DAC was enabled by a short period of silence, and the volume would then be reduced. Also, when the volume was at 0 it was at the far left and would go all the way to the right as "max", and when it's on it would start at 0 at the far left, then only go to 75 (which is the DAC's max volume setting).
The confusion here is I can't get any difference in sound no matter what I do. Even if I trick the DAC into aux mode, nothing changes. Trying to adjust the balance in the HiFi settings page does nothing.
When I had LP installed, it worked PERFECT. I used the DAC only on flac files when I was home sitting in my chair, and would leave the DAC off for mp3's and Spotify while traveling because the volume would go higher to overcome the aircraft noise.
Click to expand...
Click to collapse
Yeah does seem rom related with the error from alsa and nothing happening. Like its not getting enabled. Since your rooted, can you make a twrp backup, then do a factory reset and see if that does anything.
You could also try flashing the two roms available for the device. I'm like you, stock rooted. But I'd probably make a backup and try Andy's rom just to see if it's software related.
Sent from my LG-H901 using Tapatalk

Thanks for all this. Worked like a charm. No more bs with extension wires. I swear it sounds even louder and cleaner with just the headphones plugged in without the extension cable.
Just curious. Has anyone tried any other value, like 12 or 14. Why 13?

Hi,
My V10 not recognized the high impedence ear Phone.
The only way is modify The values on System file?
Best regards

Microphone issues

I need some help with diagnosing this. Something is wrong with the microphone(s) on my device and I can't figure out what to try. I have searched and I have tried the trick with applying pressure on the flex-cable. It does not work.
This is what I see:
Regular phone call = the person on the other side hears nothing. Just silence.
Speakerphone = Everything is OK!
Headphones = Everything is OK!
This points me to a defective microphone at the bottom.
BUT:
Voice recording app (Easy Voice Recorder) = Just garbled noise / hissing. If I speak or snap my fingers, nothing is picked up.
Video recording through default camera app = The same as above, just noise/hissing. Nothing is picked up.
So, what microphone is used for what? What can I try to isolate the error?

Anyone?

I have exactly the identical problem. When I dial out I can hear the other person but they hear nothing. Like you the voice recorder works. And if speaker is on they can hear me. Like you, I researched the problem and applied the pressure trick but it did nothing. This is really weird. I didn't drop the phone or anything.
Sounds like a software problem to me.
I hope one of the experts helps us.

maybeme2 said:
I have exactly the identical problem. When I dial out I can hear the other person but they hear nothing. Like you the voice recorder works. And if speaker is on they can hear me. Like you, I researched the problem and applied the pressure trick but it did nothing. This is really weird. I didn't drop the phone or anything.
Sounds like a software problem to me.
I hope one of the experts helps us.
Click to expand...
Click to collapse
I have ordered a new mic/charger-flex and am going to replace it. I don't think that is the reason for this though...

That sucks. I found a thread which describes the same issue and in this case, the issue was hardware - a connector on the motherboard. Here's the thread link, hope it helps: http://forum.xda-developers.com/google-nexus-5/help/nexus-5-microphone-speakerphone-t3043151

jadajada said:
I have ordered a new mic/charger-flex and am going to replace it. I don't think that is the reason for this though...
Click to expand...
Click to collapse
What is a mic/charger-flex and where did you order it from? Is it the mike cable?
Please report back when you replace it so I know whether I need to do the same.
Thanks.

android_8 said:
That sucks. I found a thread which describes the same issue and in this case, the issue was hardware - a connector on the motherboard. Here's the thread link, hope it helps: http://forum.xda-developers.com/google-nexus-5/help/nexus-5-microphone-speakerphone-t3043151
Click to expand...
Click to collapse
I know about that problem, and I have tried that. It does not help on my phone.
maybeme2 said:
What is a mic/charger-flex and where did you order it from? Is it the mike cable?
Please report back when you replace it so I know whether I need to do the same.
Thanks.
Click to expand...
Click to collapse
It's this part.
It contains a new microphone, but since the phone behaves as it does, I don't really think it's a faulty microphone. But I'll update this post when the part arrives.

Thank you.
I don't think it is a hardware issue. Otherwise why would the *same* Mike work when we turn the speaker on or plug in earphones?
I think it is either software or some installed app conflicting in some way. But, what do I know?

Same issue
I do the same. it is not possible that so many instruments have the same problem and no solution to it. I tried everything possible. pressure on the flex cable connector does not help in this case. Various changes to the file buildprop not respond. I do not understand what the problem may be. u call this error manifests itself sporadically, but still persists. until this thing is super device ...

jadajada said:
I need some help with diagnosing this. Something is wrong with the microphone(s) on my device and I can't figure out what to try. I have searched and I have tried the trick with applying pressure on the flex-cable. It does not work.
This is what I see:
Regular phone call = the person on the other side hears nothing. Just silence.
Speakerphone = Everything is OK!
Headphones = Everything is OK!
This points me to a defective microphone at the bottom.
BUT:
Voice recording app (Easy Voice Recorder) = Just garbled noise / hissing. If I speak or snap my fingers, nothing is picked up.
Video recording through default camera app = The same as above, just noise/hissing. Nothing is picked up.
So, what microphone is used for what? What can I try to isolate the error?
Click to expand...
Click to collapse
Unless you or some root app you have installed messed with the audio mixer (file: /system/etc/mixer_paths.xml) or audio HAL (/system/lib/hw/audio.primary.msm8974.so) this is most likely a hardware problem. Which microphone is used depends on the application that requests it. There are two microphones on the Nexus 5, the main microphone is the one on the bottom and there is a second one near the headphone jack on the top.
In the handset telephony use-case, actually both microphones are being used. However, the main microphone picks up your voice while the other microphone is being used to cancel background noise only. When you switch to speakerphone, the "pickup" microphone switches to the one on top (for a good reason). The same happens when you plug in a pair of headphones without an inline microphone.
Most if not all other use-cases (apps) use the bottom microphone for audio recording.
A software problem can be ruled out by re-installing one of Google's stock builds.

Software test.
I did a partial software test. My phone is rooted so I made a nandroid backup of the present and then restored an earlier nandroid from 2 months ago before all these troubles started. After the restore, the problem was unchanged. Nobody can hear me when I call but they can hear me fine when I put the speaker mode on.
So, sadly, you are correct. Now we have to find out what needs to be replaced because the "phone" is useless this way. Other users have said replacing the microphone and cable did not help (hopefully jadajada's experience will be different).
Looking for mechanical causes, my bottom mike grill is quite dirty and may be blocked. Is there a safe way to clean it? Compressed air? Thin staple?

maybeme2 said:
Software test.
I did a partial software test. My phone is rooted so I made a nandroid backup of the present and then restored an earlier nandroid from 2 months ago before all these troubles started. After the restore, the problem was unchanged. Nobody can hear me when I call but they can hear me fine when I put the speaker mode on.
So, sadly, you are correct. Now we have to find out what needs to be replaced because the "phone" is useless this way. Other users have said replacing the microphone and cable did not help (hopefully jadajada's experience will be different).
Looking for mechanical causes, my bottom mike grill is quite dirty and may be blocked. Is there a safe way to clean it? Compressed air? Thin staple?
Click to expand...
Click to collapse
I also think that the problem is in the hardware, but I fear that somewhere on the main board, and it does not pay to fix it. Unfortunately. Almost I wonder if Google wants this old devices, so we had to buy a new series of Nexus. Joke . Otherwise, the phone I had disassembled and microphone has good coverage, therefore, was beautifully clean and free of dust and dirt.

In that case, what to replace the phone with? Another nexus 5 or a different phone? What are you going to do?

situsacek said:
I also think that the problem is in the hardware, but I fear that somewhere on the main board, and it does not pay to fix it.
Click to expand...
Click to collapse
Situsacek, you seem to know about these things. May I ask why you think the problem is on the main board? Is there a tool to test and find out other than replacing the microphone and flex cable to see if that fixes it or not?
How difficult is it to replace the microphone and flex cable? I am resigned to having to buy a new phone but am checking out my options.

maybeme2 said:
Situsacek, you seem to know about these things. May I ask why you think the problem is on the main board? Is there a tool to test and find out other than replacing the microphone and flex cable to see if that fixes it or not?
How difficult is it to replace the microphone and flex cable? I am resigned to having to buy a new phone but am checking out my options.
Click to expand...
Click to collapse
I have read a lot of discussion on this topic and this problem affects many devices. However, nobody knows the answer to this problem. No one knows the complete solution. For me, it manifests at 5/1 call, for a camera recording the whole time not sound correctly. Replace flex cable is not hard. Does not cost a lot of money on Ebay. But I do not think it will solve this thing, somebody already tried and always the same. I do not want to invest money, though it is not part of the solution. I am very disappointed by this, and I do not want the product from LG never more!
---------- Post added at 06:21 PM ---------- Previous post was at 05:32 PM ----------
situsacek said:
I have read a lot of discussion on this topic and this problem affects many devices. However, nobody knows the answer to this problem. No one knows the complete solution. For me, it manifests at 5/1 call, for a camera recording the whole time not sound correctly. Replace flex cable is not hard. Does not cost a lot of money on Ebay. But I do not think it will solve this thing, somebody already tried and always the same. I do not want to invest money, though it is not part of the solution. I am very disappointed by this, and I do not want the product from LG never more!
Click to expand...
Click to collapse
Here is a link to many topics. For me, nothing works out there.
https://m.reddit.com/r/Nexus5/comments/2ztw83/how_to_fix_microphone_issues/?sort=top
Sent from my ALE-L21 using XDA-Developers mobile app
---------- Post added at 07:18 PM ---------- Previous post was at 06:21 PM ----------
It was a kind signed the petition. Solves it for over two years. I recommend buying another mobile phone. There is no chance of redress. Thanks
https://www.change.org/p/google-fix-microphone-issues-on-nexus-5-phones#share
Sent from my ALE-L21 using XDA-Developers mobile app

For folks with (at least) a custom recovery (better: rooted), there is a way to make the camcorder and other audio recording devices use the auxiliary microphone (the one on top) instead of the main microphone (the one on the bottom). I'm not sure what can be done in the telephony (handset) use-case, though, without introducing a lot of noise, echo, and low speech levels for the far-end.
The "fix" involves modifying one file (/system/etc/mixer_paths.xml); PM me if you are interested in giving this approach a shot.

chdloc said:
For folks with (at least) a custom recovery (better: rooted), there is a way to make the camcorder and other audio recording devices use the auxiliary microphone (the one on top) instead of the main microphone (the one on the bottom). I'm not sure what can be done in the telephony (handset) use-case, though, without introducing a lot of noise, echo, and low speech levels for the far-end.
The "fix" involves modifying one file (/system/etc/mixer_paths.xml); PM me if you are interested in giving this approach a shot.
Click to expand...
Click to collapse
Hi, I also tried, but without any significant response. Could you give your instructions, so I can compare? Thank you
Sent from my ALE-L21 using XDA-Developers mobile app

situsacek said:
Hi, I also tried, but without any significant response. Could you give your instructions, so I can compare? Thank you
Sent from my ALE-L21 using XDA-Developers mobile app
Click to expand...
Click to collapse
OK, I'm assuming that the main microphone (bottom) is dead and that the auxiliary microphone (top, near headphone jack) is still operational.
To use the auxiliary microphone for both camcorder and (I'm guessing) most other audio recording apps, edit your /system/etc/mixer_paths.xml file (e.g. via a file explorer), search for the following entry:
Code:
<path name="handset-mic">
<path name="adc1" />
<ctl name="ADC1 Volume" value="16" />
<ctl name="DEC6 Volume" value="86" />
</path>
and replace with
Code:
<path name="handset-mic">
<path name="adc3" />
<ctl name="ADC3 Volume" value="16" />
<ctl name="DEC4 Volume" value="86" />
</path>
After saving the modified file (make backup of original file first!), make sure that the permissions are set to 644 (rw-r--r--), and reboot.
The next step is handset telephony. A very quick and likely very poorly performing solution would be to again simply use the top microphone. You will need the same modification as above. In addition, you need to disable dual-microphone support by editing your build.prop file:
After making a proper backup, replace
Code:
persist.audio.dualmic.config=endfire
with
Code:
persist.audio.dualmic.config=none
check the permissions (644), and reboot. Be advised that the microphone is now further away from your mouth so the TX level will be low. You could crank up the gain by increasing "ADC3 Volume" (permissible values are between 0 and 20) and/or "DEC4 Volume" (permissible values are between 0 and 124), followed by a reboot. Also keep in mind that echo cancellation and noise control will be turned off, so be prepared for a lot of complaints.

chdloc said:
OK, I'm assuming that the main microphone (bottom) is dead and that the auxiliary microphone (top, near headphone jack) is still operational.
To use the auxiliary microphone for both camcorder and (I'm guessing) most other audio recording apps, edit your /system/etc/mixer_paths.xml file (e.g. via a file explorer), search for the following entry:
Code:
<path name="handset-mic">
<path name="adc1" />
<ctl name="ADC1 Volume" value="16" />
<ctl name="DEC6 Volume" value="86" />
</path>
and replace with
Code:
<path name="handset-mic">
<path name="adc3" />
<ctl name="ADC3 Volume" value="16" />
<ctl name="DEC4 Volume" value="86" />
</path>
After saving the modified file (make backup of original file first!), make sure that the permissions are set to 644 (rw-r--r--), and reboot.
The next step is handset telephony. A very quick and likely very poorly performing solution would be to again simply use the top microphone. You will need the same modification as above. In addition, you need to disable dual-microphone support by editing your build.prop file:
After making a proper backup, replace
Code:
persist.audio.dualmic.config=endfire
with
Code:
persist.audio.dualmic.config=none
check the permissions (644), and reboot. Be advised that the microphone is now further away from your mouth so the TX level will be low. You could crank up the gain by increasing "ADC3 Volume" (permissible values are between 0 and 20) and/or "DEC4 Volume" (permissible values are between 0 and 124), followed by a reboot. Also keep in mind that echo cancellation and noise control will be turned off, so be prepared for a lot of complaints.
Click to expand...
Click to collapse
Hi, thanks for the nice described instructions. Yes it's the same procedure as I found and tried. Unfortunately, the other side is exposed to a strong echo. Pity that no fixed correction, not a precise explanation of why the problem arose at our facilities. Answer seemed to die along with the nexus 5

situsacek said:
Hi, thanks for the nice described instructions. Yes it's the same procedure as I found and tried. Unfortunately, the other side is exposed to a strong echo. Pity that no fixed correction, not a precise explanation of why the problem arose at our facilities. Answer seemed to die along with the nexus 5
Click to expand...
Click to collapse
Actually, I have dual-microphone processing disabled on my phone as well (but it is for a different reason) and I'm exclusively using the main microphone for the handset telephony use-case. I did succeed in enabling echo and noise control, but
I'm not sure whether it would work with the auxiliary microphone as well
the solution I came up with is, unfortunately, way too complicated and convoluted to share with the community (custom kernel, Tasker integration, and most importantly, individually adapted application of audio calibration data)
With the above modifications of mixer_paths.xml, using the auxiliary microphone for virtually any other purpose should work OK, though.

[GUIDE] How-to modify the ear speaker volume on Mi A1

This mini guide is for users who want to modify the ear/handset speaker volume for their Xiaomi Mi A1.
* You need to open one of the following files with root permissions:
(For STOCK) "root"\system_root\system\vendor\etc\mixer_paths_mtp_global.xml
(For CUSTOM) "root"\system\vendor\etc\mixer_paths_mtp.xml
* Find <path name="handset"> (Hint: It's near the bottom). Modify <ctl name="RX1 Digital Volume" value="88" /> for a value closer to 100 to increase the volume (92 works fine for me) or lower that number if the ear speaker is too loud for you.
* You can also modify the "Digital Gain" value within <path name="speaker"> if you want a louder bottom speaker. In my case the default is 56 and I increased it to 64.
* Save without changing the format (UTF-8 if the editor ask), and reboot.
Tested on two Xiaomi Mi A1 under STOCK 8.1 and Lineage OS 15.1, using Magisk Manager 16 (for root access), and Hootan Parsa's MIXplorer.
Best regards. [Sorry for my bad English]

Thank you
It works
Mine was set to 83 and I felt it too low and increased to 108. It's Really loud. Will scale it down

In bluetooth works?

seinas said:
In bluetooth works?
Click to expand...
Click to collapse
I don't see any numerical value to boost under <path name="headphones"> (nor Bluetooth headphones) for our device, but you can try to increase one at a time the following values under <mixer> near the beginning of the same file: BEWARE that this is a global change
Code:
<ctl name="RX1 Digital Volume" value="83" />
<ctl name="RX2 Digital Volume" value="83" />
<ctl name="RX2 Digital Volume" value="83" />

Hi
Moycano, how do I change root permissions?
I need to root my phone? I never did something like this. Does it erase my phone data?
How can I root my phone? Do you recommend on a good guide?
I really want to change my phone volume, it's very low.
Thanks,
Saar.

xgr3d said:
Moycano, how do I change root permissions?
I need to root my phone? I never did something like this. Does it erase my phone data?
How can I root my phone? Do you recommend on a good guide?
I really want to change my phone volume, it's very low.
Thanks,
Saar.
Click to expand...
Click to collapse
Please, don't be lazy and try to search if you have some question
https://forum.xda-developers.com/mi-a1/how-to/root-mi-a1-oreo-8-0-disabling-ota-magisk-t3728654

jack_21 said:
Please, don't be lazy and try to search if you have some question
https://forum.xda-developers.com/mi-a1/how-to/root-mi-a1-oreo-8-0-disabling-ota-magisk-t3728654
Click to expand...
Click to collapse
Thanks for the answer,
Does it put my phone in danger? Does it earse my phone data?
I just want my volume to be louder, there's no other way to fix this problem with no rooting?

xgr3d said:
Thanks for the answer. Does it put my phone in danger? Does it earse my phone data? I just want my volume to be louder, there's no other way to fix this problem with no rooting?
Click to expand...
Click to collapse
I don't think you can apply this fix without rooting, and rooting is probably the best thing you can do anyway; I can't stand a smartphone without ad-blocking, for starters.

i changed the value to 92 and rebooted and still no change in the call volume so i changed it to 99 and rebooted but still nothing and now it is 130 and nothing changed the volume is still very low
what should i do please help

it works !
it works perfect!
my value is 84, i change to 74 and the volume of the call is finally OK!!
THANK YOU VERY MUCH !!! YOU SAVE MY EAR..
:good::good::good::good::good:

I updated the post with proper instructions for Stock after I went back to it about a week ago. It was a little confusing since both files exist even after a full-format clean install but the system doesn't read the same file than LOS.

cool! can this also be done for the MIN volume? so basically how silent the first step after mute is?

Thanks ALot!
It worked as expected. it was frustrating attending calls with low earpiece volume had to keep earphones around.!!
Also
can we unroot and relock the boot-loader without affecting these changes? just like the case we do while installing google-cam and unrooting/re-locking doesn't affect camera2api or eis.

Hello, i would like to know if I apply this mod the phone will be able to receive OTA updates.
Thanks
Antonis

I can confirm OTA updates work just fine for LineageOS + MindTheGapps + SuAddon.
On the other hand, Stock + Magisk require to uninstall Magisk before OTA or it fails.

Followed the instructions, but now I have no audio at all.

Any chance to do this without root access?

Used this after my in ear volume was so soft after the July update. Turned the value up from 84 to 99 and it worked perfectly. Thank you so much this saved me a lot of money instead of getting a new phone!

Not able to save file after changing value.
Derestriction said:
Used this after my in ear volume was so soft after the July update. Turned the value up from 84 to 99 and it worked perfectly. Thank you so much this saved me a lot of money instead of getting a new phone!
Click to expand...
Click to collapse
Not able to save file after changing value. I am using miX to access file. Please let me know how to change value and fix the issue.

Really great!!! I was on 84 volume level now 100 is wow???