Related
Hi,
A couple of days ago I lost completely my mic during calls. (Other persons can not here me but i can. Even when i speak through speakers they can not here me)
Even the sound with my video's is gone.
But the strange thing is that when i tap my phone when my voice recorder app is on, it will detect the tapping but it will not record anything.
Can anybody help in this matter?
I use a ZP999 rooted, custom rom
update : the voice recorder did record something afterall.
When i put my headset in i can hear it clear.
I did pull out my headset and i now can hear the voice recording through my speakers which before didn't work.
I had some hope now the mic of my phone dialer should work but it didn't.
Can there be something wrong with my headset-input-jack which controls also the mic of my dialer???
Is it possible that my phone "thinks" there is still a headset inside so my mic won't work?
I remember i used some softtouch-pen which had on the other end a "jack"-like the usual headsets. But i remember it didn't fit the wright way.
It could possibely caused the harm.
Any way to override or fix this problem ???
Any help would be welcome.
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.
As the title says only the bottom firing speaker is working when on speakerphone. The top earpiece works as a speaker with Spotify and YouTube with no problem. However whenever using speaker phone it is only from the bottom speaker.
I have tried a different dialer app, and the beta google dialer with no luck. Wanted to see if anyone else noticed the same issue and if it might be a firmware issue.
ki4mor said:
As the title says only the bottom firing speaker is working when on speakerphone. The top earpiece works as a speaker with Spotify and YouTube with no problem. However whenever using speaker phone it is only from the bottom speaker.
I have tried a different dialer app, and the beta google dialer with no luck. Wanted to see if anyone else noticed the same issue and if it might be a firmware issue.
Click to expand...
Click to collapse
Doubt it. Likely by design to protect hearing when folks absent mindedly put handset to ear with speakerphone engaged. Done that a few times on my Moto devices; not a fun experience.
I'm having a weird problem with the mic on my HTC U11. The past week sometimes when I received a call, other people couldn't listen to me, eventually it's happening on every call.
I also noticed that the voice recording app, and other 3rd party video apps are not recording sound, "Manual Camera DSLR" app does some kind of a loud "click" sound when the record starts and then stops the audio, but if I use the Hi-Res or 3D function on the native camera app the sound is recorded and also if I put the call on speaker the sound is back. I tried to clean the phone but didn't help and did a doing a call to another phone and everything I could hear was total silence like if it was muted, not distorted sound like if the mic was dirty or something blocking it, until I put the call on speaker the sound was "not muted"
Any idea on how could I attempt to fix it?
Thanks.
Hope this 6 easy ways help you fix the issue with HTC:
1. Restart your phone
2. Check if the phone cover covers the microphone
3. Check connected devices
4. Clean the microphone
5. Remove third-party apps
6. Software update
jack lamters said:
Hope this 6 easy ways help you fix the issue with HTC:
1. Restart your phone
2. Check if the phone cover covers the microphone
3. Check connected devices
4. Clean the microphone
5. Remove third-party apps
6. Software update
Click to expand...
Click to collapse
Restarted, didn't work.
No cover on phone, also sound doesn't sound covered, just 0 sound, not even white noise or interference.
Not connected
Seems clean
Didn't work
No updates
Have been doing more checks... native camera app is also failing, does the same "click" sound and then stops recording audio. Moments ago mic wasn't working on voice recorder, then I plugged the charger and mic started to work.
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.. ;-)