[SOLVED]Severe Call Distortion Following Upgrade - HTC One SV

I just upgraded to 4.2.2 and Touch 5 by bootflashing system.img and boot.img (see this thread). Normal sound (such as youtube) works fine, but in-call audio is horribly distorted, coming across as a harsh, angry shrieking buzz. This problem only began following the flash/update. Anyone else dealt with this or have any ideas what the problem could be?
EDIT: it's not only regular calls. Calls over Talkatone (google voice) experience the same distortion. The distortion is present on both the front speaker (the 'normal' speaker for calls) and the rear speaker (used for speakerphone and for other sounds, like youtube, which sound normal). Thought that detail might be relevant. Talkatone was using wifi, so same connection as youtube (network data was disabled)

zomgitsanoob said:
I just upgraded to 4.2.2 and Touch 5 by bootflashing system.img and boot.img (see this thread). Normal sound (such as youtube) works fine, but in-call audio is horribly distorted, coming across as a harsh, angry shrieking buzz. This problem only began following the flash/update. Anyone else dealt with this or have any ideas what the problem could be?
EDIT: it's not only regular calls. Calls over Talkatone (google voice) experience the same distortion. The distortion is present on both the front speaker (the 'normal' speaker for calls) and the rear speaker (used for speakerphone and for other sounds, like youtube, which sound normal). Thought that detail might be relevant. Talkatone was using wifi, so same connection as youtube (network data was disabled)
Click to expand...
Click to collapse
You have to grab the firmware.zip from inside of the ota zip for 4.2.2 cricket.
Place the firmware where your proper adb/fastboot files are at, then boot in to fastboot on your device.
Code:
fastboot erase cache
Code:
fastboot oem rebootRUU
Code:
fastboot flash zip firmware.zip
Sent from my K2_CL using Tapatalk
---------- Post added at 01:00 AM ---------- Previous post was at 12:55 AM ----------
The new update comes with new firmware but since you only bumped up your boot.img and system.img you left behind the firmware lol. Do that, and all will be well again.
Sent from my K2_CL using Tapatalk

I dont want to open new thread so I will ask here. I noticed that people i talk over my one sv are complaining about call quality/loudnes...if i move phone (lower part where mic is) from my face then they say: why dont i hear you...? I think problem is in mic that captures poorly or in that other mic for noise suppresion... Belive that is the thing with a lot of htc phones (htc sensation also)... Where could be the problem? How to increase mic volume or turn off noise suppresion...

mlesic said:
I dont want to open new thread so I will ask here. I noticed that people i talk over my one sv are complaining about call quality/loudnes...if i move phone (lower part where mic is) from my face then they say: why dont i hear you...? I think problem is in mic that captures poorly or in that other mic for noise suppresion... Belive that is the thing with a lot of htc phones (htc sensation also)... Where could be the problem? How to increase mic volume or turn off noise suppresion...
Click to expand...
Click to collapse
I personally don't have such problem. The most time the others can hear me good and can hear them good.

Most of times for me is ok also, but one person told me (with xperia z) that poor sound quality is just when speaking with me and person with htc sensation. If i lean my phone against my face is ok. But manipulation gets it worse so other side dramaticaly gets worse... Dont know...

Code:
sending 'zip' (34555 KB)... OKAY
writing 'zip'... INFOzip header checking...
INFOshift signature_size for header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOstart image[hboot] unzipping for pre-update check...
INFOstart image[hboot] flushing...
INFO[RUU]WP,hboot,0
INFO[RUU]WP,hboot,99
INFO[RUU]WP,hboot,100
INFO...... Successful
INFOstart image[sbl2] unzipping for pre-update...
INFOstart image[sbl2] flushing...
INFO[RUU]WP,sbl2,0
INFO[RUU]WP,sbl2,100
INFO...... Successful
INFOstart image[sbl3] unzipping for pre-update...
INFOstart image[sbl3] flushing...
INFO[RUU]WP,sbl3,0
INFO[RUU]WP,sbl3,100
INFO...... Successful
INFOstart image[rpm] unzipping for pre-update...
INFOstart image[rpm] flushing...
INFO[RUU]WP,rpm,0
INFO[RUU]WP,rpm,100
INFO...... Successful
INFOstart image[tz] unzipping for pre-update...
INFOstart image[tz] flushing...
INFO[RUU]WP,tz,0
INFO[RUU]WP,tz,100
INFO...... Successful
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
The distortion has lessened (I can make out words), but still sounds like distorted robots :/
Is that last line the problem?

@zomgitsanoob
Do it again. Whenever it say 'please flush image again immediately' that literally means to flash it again lol.
It happens sometimes.
Sent from my K2_CL using Tapatalk

Related

Hearing myself on the speaker on NATF

I'm running NATF 4.6 with a .19 radio and after flashing everything yesterday, i've noticed that when I make a call and speak into the microphone, i can hear myself on the ear speaker. if i turn up the volume it gets louder until the volume is maxed then secondary to the duplex, i no longer hear myself. if i lower the volume down the lowest, i can still faintly hear myself. this is driving me crazy as when the volume is up to second bar or more, my voice is significant on the ear speaker. this never happened on the stock ROM so I'm guessing its a ROM issue for which there is something I have to tweak somewhere. Anyone have any input?? Does it have something to do with the ICR and if so, how do i disable it??
bad radio flash, re flashed and all is good... done and done.
i'd close this thread if i could....

Speaker problem with rom [ROM][CM10][Kang][Pyramid][RC][4.1.2][27 Oct]

First of all exucuse my poor english. Secondly yes I'm new and I hate myself as the introduction said.
I have flashed [ROM][CM10][Kang][Pyramid][RC][4.1.2][27 Oct] rom. During calls there is a problem with speaker (loud speaker). After pushing the speaker button there is only silence. When you want to turn it off, for about 2 second you can hear caller. I wonder if its a bug or problem with my configuration?
Please respond.
For previous builds it was reported that toggling volume manually to loudest and then back to normal level could help initialize volume (once after reboot).
As far as I understood the CM source commits, this is a known issue and might be dealt with eventually.

Echo problem on caller's phone.

The Problem
Caller hears his voice, echo effect.
Check with GSM provider and the problem is from my phone they also reset my line.
Did not believe my provider and check with a SIM of another provider but the same problem.
Walk around my town the same problem if i make a call or someone calls me he hears his voice.
Do hard reset :crying: but the same problem.
On Settings -> Sound and Notification -> Sound Enchancement ->all to off, or no result if on or off .
and at More -> Mobile networks -> Enchanced 4G LTE Mode on or off has no result the problem is the same,
also same problem if i use 3G or 4G network for my connection at the GSM provider.
If i use a pair of headphones the problem is much more better, caller does not hear his voice, almost nothing of echo.
Using loudspeaker of the phone is like using headphones the same results, caller does not hear his voice, almost nothing of echo.
Found that when i push the headphones out in order to continue speaking with phone's mic, echo starts to be enormous to the caller, especially if speaker power is to max.
Echo decreases when i push my speakers power to min, but still exist a liitle only echo to caller's phone.
The problem full fixed only if i turn off-mute my mic when the caller is speaking but i can not mute and unmute mic when i want to talk!
Can someone help... any solution?
No any idea?
First, you didn't say what device you have or what android version/ROM you are using, that information would be useful in providing answers.
It seems to me that your mic is picking up the sound that your speaker is emitting and then feeding back to their phone. If you are on stock, try turning the in call volume down so that your speaker isn't so loud.
If you are rooted and using a custom ROM, you can edit your sound file in a text editor to change the max in-call speaker volume.
The point is, try to keep the sound coming from your speaker low enough so that your mic doesn't "hear" it.
Aside from that, check out the link below
https://www.androidpit.com/forum/611785/echo-on-phone-calls
The link below explains, another possible cause
https://www.techwalla.com/articles/how-to-cancel-the-echo-on-a-cell-phone
You can try this thread also, it discusses the issue and some workaround solutions.
https://forum.xda-developers.com/showthread.php?t=2756122
amnis said:
No any idea?
Click to expand...
Click to collapse
ive always noticed this issue when using speakerphone
the noise from the loud speaker is so loud that the mic picks it up and reverberates the sound causing a echo
have had it happen on many devices
Droidriven said:
First, you didn't say what device you have or what android version/ROM you are using, that information would be useful in providing answers.
It seems to me that your mic is picking up the sound that your speaker is emitting and then feeding back to their phone. If you are on stock, try turning the in call volume down so that your speaker isn't so loud.
If you are rooted and using a custom ROM, you can edit your sound file in a text editor to change the max in-call speaker volume.
The point is, try to keep the sound coming from your speaker low enough so that your mic doesn't "hear" it.
Aside from that, check out the link below
https://www.androidpit.com/forum/611785/echo-on-phone-calls
The link below explains, another possible cause
https://www.techwalla.com/articles/how-to-cancel-the-echo-on-a-cell-phone
You can try this thread also, it discusses the issue and some workaround solutions.
https://forum.xda-developers.com/showthread.php?t=2756122
Click to expand...
Click to collapse
I Think that i should low the mic's sensitivity because if i low the speaker volume i can not hear the caller in a noisy place.
If i scratch with my nail the back metal case of the phone the caller hears a very loud noise.
Do you know how the above can be done, how can lower the mic's sensitivity?
Device is a Vernee Apollo light not rooted with Android 6.
Thank U
amnis said:
I Think that i should low the mic's sensitivity because if i low the speaker volume i can not hear the caller in a noisy place.
If i scratch with my nail the back metal case of the phone the caller hears a very loud noise.
Do you know how the above can be done, how can lower the mic's sensitivity?
Device is a Vernee Apollo light not rooted with Android 6.
Thank U
Click to expand...
Click to collapse
That can probably be edited in your sound file like the speaker volume can be edited.
Sent from my SM-S903VL using Tapatalk
it's understandable, but the strong echo of the fire phone arises from behind the bottom speaker near the microphone, the lower speaker during the conversation should be off by 0, but the program fire os, then it does not turn it off, I think, that this is some kind of error in the software. from the echo can be removed by disconnecting the wire from the bottom speaker next to the microphone, and through the stereo headphones will be. I'm very sorry for the translation from Russian into English. this is Google translator.
flesh54 said:
it's understandable, but the strong echo of the fire phone arises from behind the bottom speaker near the microphone, the lower speaker during the conversation should be off by 0, but the program fire os, then it does not turn it off, I think, that this is some kind of error in the software. from the echo can be removed by disconnecting the wire from the bottom speaker next to the microphone, and through the stereo headphones will be. I'm very sorry for the translation from Russian into English. this is Google translator.
Click to expand...
Click to collapse
то ,что эхо возникает из за отражённых сигналов в эфире это понятно , но сильное эхо fire phone возникает из за нижнего динамика около микрофона , нижний динамик при разговоре должен отключаться на 0, но программа fire os ,почему то его не отключает , я думаю , что это какая то ошибка в программном обеспечении . от эхо можно избавится отключением провода от нижнего динамика рядом с микрофоном, а через наушники стерео будет.

Building Custom Rom HELP NEEDEED Final annoyances

hi, ive been putting together my own custom ROM for S905X based boxes and have almost finished, just a few things that are bugging ne and need some help getting the last of these bugs (annoyances) ironed out
Rom Link
https://apkpure.com/amazon-prime-video/com.amazon.avod.thirdpartyclient/download?from=details
So already fixed a bunch of issues including power standby issues, Wifi & Bluetooth drivers, Modified system apps to replace icons ect...
Things that need fixed
1. Issue when there is delay between the video starting and the audio starts, same with any sound there is a delay (happens with any sound if its been quiet for 5-10seconds (The issue wasn't there on the factory ROM so ive ruled out hardware)
2 Bluetooth audio volume is too loud (it sounds distorted and i have to reduce the (Android) Volume to 50-70% to remove the distortion) i have looked at various files in system/ect (audio policy volumes.xml ect...) any ideas what could cause this
I have attached some files from my ROM that might be useful

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.. ;-)

Categories

Resources