Database Info

Xperia L Microphone Issue

A few days ago I discovered that people I talk to over the phone can't hear me, whether they call me or I call them, while I can hear them perfectly.
My voice if very muffled, impossible to comprehend, sometime it cuts out completely and there's also a persistent "static" noise in the background, kind of like wind blowing. I can usually make myself heard only if I raise my voice by a lot, close to yelling actually.
I tested the microphone via the service menu AND the Xperia Diagnostics app and I'm even more puzzled. Initially I'd say that about 70-80% of the time I had to raise my voice a lot so that the recorder can pick up anything and the results I got were essentially what the people I talked to reported. I looked up the issue on various forums, fiddled with the settings, disabled xLoud, noise suppression, took the SIM out and put it back in, did a repair via the PC Companion AND a factory reset later on and nothing seems to consistently work. Sometimes they can hear me, sometimes they can't. Testing results are also much better now and I'm able to clearly hear my voice most of the time, but when actually calling someone, even when they say they hear me clearly they can still hear that annoying static. I now have noise suppression turned off, since that seems to help.
To my knowledge, this started to happen after the 4.2.2 update, a very buggy update. I also had a problem with headphones (two pairs in otherwise working order) not being recognised, even though both were initially working well with the phone. Eventually I had to repair the phone twice for that (the first time it didn't fix anything) just to get the phones working again. It's after that that I noticed this mic problem.
I also found this thread and I wonder if that lil' piece of rubber can be the problem. Apparently those are Ions, but I'm thinking maybe there's enough internal commonality between that and the XL that I could actually have the same problem.
Other than that, what would you advise? Try to go back to 4.1.2?
Service is my last option due to time and distance concerns. Thanks!
Model: C2105
Android: 4.2.2
Build no.: 15.3.A.0.26

potato muncher said:
A few days ago I discovered that people I talk to over the phone can't hear me, whether they call me or I call them, while I can hear them perfectly.
My voice if very muffled, impossible to comprehend, sometime it cuts out completely and there's also a persistent "static" noise in the background, kind of like wind blowing. I can usually make myself heard only if I raise my voice by a lot, close to yelling actually.
I tested the microphone via the service menu AND the Xperia Diagnostics app and I'm even more puzzled. Initially I'd say that about 70-80% of the time I had to raise my voice a lot so that the recorder can pick up anything and the results I got were essentially what the people I talked to reported. I looked up the issue on various forums, fiddled with the settings, disabled xLoud, noise suppression, took the SIM out and put it back in, did a repair via the PC Companion AND a factory reset later on and nothing seems to consistently work. Sometimes they can hear me, sometimes they can't. Testing results are also much better now and I'm able to clearly hear my voice most of the time, but when actually calling someone, even when they say they hear me clearly they can still hear that annoying static. I now have noise suppression turned off, since that seems to help.
To my knowledge, this started to happen after the 4.2.2 update, a very buggy update. I also had a problem with headphones (two pairs in otherwise working order) not being recognised, even though both were initially working well with the phone. Eventually I had to repair the phone twice for that (the first time it didn't fix anything) just to get the phones working again. It's after that that I noticed this mic problem.
I also found this thread and I wonder if that lil' piece of rubber can be the problem. Apparently those are Ions, but I'm thinking maybe there's enough internal commonality between that and the XL that I could actually have the same problem.
Other than that, what would you advise? Try to go back to 4.1.2?
Service is my last option due to time and distance concerns. Thanks!
Model: C2105
Android: 4.2.2
Build no.: 15.3.A.0.26
Click to expand...
Click to collapse
Well since you said that this started happening after you've updated to 4.2.2 you have 2 options
1. Reflash the 4.2.2 update
2. Downgrade to 4.1.2
I hope that helps
Sent from my C2104 using xda app-developers app

Unfortunately, I can't be sure if it's due to 4.2.2 or just a coincidence, since it didn't start immediately after the update. Like I said, that thread about the Ion mic problem got me thinking that maybe this is what happened, in which case it's only a coincidence that I also updated to 4.2.2 a couple of days prior.
"Reflash the 4.2.2 update" - is this different from repairing it via the PC Companion? Like I said, I already did that and a factory reset later on and it didn't help with this.
In any case, thanks for your help! :good:

potato muncher said:
A few days ago I discovered that people I talk to over the phone can't hear me, whether they call me or I call them, while I can hear them perfectly.
My voice if very muffled, impossible to comprehend, sometime it cuts out completely and there's also a persistent "static" noise in the background, kind of like wind blowing. I can usually make myself heard only if I raise my voice by a lot, close to yelling actually.
I tested the microphone via the service menu AND the Xperia Diagnostics app and I'm even more puzzled. Initially I'd say that about 70-80% of the time I had to raise my voice a lot so that the recorder can pick up anything and the results I got were essentially what the people I talked to reported. I looked up the issue on various forums, fiddled with the settings, disabled xLoud, noise suppression, took the SIM out and put it back in, did a repair via the PC Companion AND a factory reset later on and nothing seems to consistently work. Sometimes they can hear me, sometimes they can't. Testing results are also much better now and I'm able to clearly hear my voice most of the time, but when actually calling someone, even when they say they hear me clearly they can still hear that annoying static. I now have noise suppression turned off, since that seems to help.
To my knowledge, this started to happen after the 4.2.2 update, a very buggy update. I also had a problem with headphones (two pairs in otherwise working order) not being recognised, even though both were initially working well with the phone. Eventually I had to repair the phone twice for that (the first time it didn't fix anything) just to get the phones working again. It's after that that I noticed this mic problem.
I also found this thread and I wonder if that lil' piece of rubber can be the problem. Apparently those are Ions, but I'm thinking maybe there's enough internal commonality between that and the XL that I could actually have the same problem.
Other than that, what would you advise? Try to go back to 4.1.2?
Service is my last option due to time and distance concerns. Thanks!
Model: C2105
Android: 4.2.2
Build no.: 15.3.A.0.26
Click to expand...
Click to collapse
The ultimate method for fix this problem is send it to sony service center,,i suggest so,,i think it the best choices

potato muncher said:
"Reflash the 4.2.2 update" - is this different from repairing it via the PC Companion? Like I said, I already did that and a factory reset later on and it didn't help with this.
In any case, thanks for your help! :good:
Click to expand...
Click to collapse
You can either use as you said repairing via PCC or just flash FTF.

Gear s2 ringing with note 7

Got my note 7 yesterday (love it!) My watch is set to vibrate for everything (no sound) as this is working fine for notifications but when I get a call the phone and the watch ring. I even tried setting the phone to vibrate too and it still rings (same ringtone as the phone). Is anyone else having this issue?

I am having the same issue. Since i never have my phone set to ring (Always rely on my S2 classic for alerts) I just set my Note 7 ringtone to "Silent" no it seems to "Work" ok.
Not the ideal solution, but a "fix" for now...

Thank you.... I'm glad it's not just me. I called Samsung today about it and they were clueless...

I've sent a message to Samsung. Hopefully this gets patched. I'm pretty sure turning off bluetooth audio will stop the issue. Anyone tried it? In bluetooth settings.
Sent from my SM-N930V using Tapatalk

I will try that but, then we can't use it to answer calls. It is definitely a bt issue....i tested it by turning off bt and calling the watch's phone number and it vibrated as it's supposed to. Hopefully enough people contact samsung so that they can get working on a fix for this.

Watch ring ? Or vibrates ?
Wysłane z iPad za pomocą Tapatalk

Me too
Yes I'm having the same issue too. It's really annoying. It's just with the Note7 since it didn't happen with my S7E. Sucks since I can't wear it at work now since I have my phone on vibrate I don't need my watch ringing.

me23brown said:
Yes I'm having the same issue too. It's really annoying. It's just with the Note7 since it didn't happen with my S7E. Sucks since I can't wear it at work now since I have my phone on vibrate I don't need my watch ringing.
Click to expand...
Click to collapse
As a "quick fix" change the phone ring tone to "silent" that works for me.

Thanks but when I tried that neither the watch or the phone would vibrate so I wouldn't know if I was getting a call or notification.

I called samsung about this, has anyone else? I think the the more people that report it the better chance we have of getting a fix for it quicker.

I was able to get it to work but both the ringer AND media in the phone need to be on vibrate. Basically what I did was open the sound setting on my phone and was messing with the settings while calling my phone from another phone until I found the right mixture. This is what worked for me. Now my phone and watch vibrate. I would suggest doing what I did until you find the right mixture.
If I take it off vibrate on my phone they both ring. Hope this helps.

I've got a ticket opened with Samsung. My first inquiry got redirected. Hope this one sticks.
Sent from my SM-N930V using Tapatalk

Happening with me as well, did an online chat with samsung support to report it and gave them a link to this topic.

Has anyone heard anymore about this? I've periodically checked for an update/fix but haven't seen anything.

Same issue
I've had this problem too. been having the issue Since day one with the note 7. I've called Samsung at least 3 times about it. They were clueless. The first 2 times they kept telling be to call my carrier. I know it's not a carrier issue. For god sakes you're the maker of the watch! Brought it to the Samsung kiosk... Also clueles only answers i can seem to get are factory reset it, which didn't work. Come on Samsung! I'm going to try some of the options you guys gave.

Was having the same issue after I got my new phone setup with my gear... tried mutiple things, ended up doing a factory reset on my watch, reconnected to my n7 and my previous settings were restored to my watch via gear manager...and I was back in business.. no more ringing from the watch...

I've reset watch 3 times.....but I'll try 1 more

bump

Mine is doing it also. I have factory reset wach times

4th factory reset didn't fix it

Problem with pixel phone app??

Just wondering if anyone knows if there's been an update to the phone app that's causing issues? Over the last 4 days mine has gotten funky. It's sometimes hanging and I have to hold power till it reboots. Sometimes they can't hear me and I can hear them. Sometimes neither of us can hear each other. Sometimes it takes ages to connect, if at all. And sometimes it works fine. Just wondering if anyone else has noticed anything. It's come out of the blue for me.

goughymachine said:
Just wondering if anyone knows if there's been an update to the phone app that's causing issues? Over the last 4 days mine has gotten funky. It's sometimes hanging and I have to hold power till it reboots. Sometimes they can't hear me and I can hear them. Sometimes neither of us can hear each other. Sometimes it takes ages to connect, if at all. And sometimes it works fine. Just wondering if anyone else has noticed anything. It's come out of the blue for me.
Click to expand...
Click to collapse
I'm having the same issue. In fact I had a long call yesterday where suddenly neither of us could hear each other. I tried calling voicemail but could only hear it with speakerphone on. Seems to have started after the March security update was installed. Its basically making my phone unusable (I have to restart it multiple times a day).

Pixel 2 phone calls default to Loudspeaker

I'm having this issue, it defaults to loudspeaker 70% of the time, incoming and outgoing calls.
I need to tap the loudspeaker icon twice to disable it.
Factory reset done, clear Phone app cache done, reinstall updates on phone app done.
still no fix.
anyone having this issue as well?

squareballz said:
I'm having this issue, it defaults to loudspeaker 70% of the time, incoming and outgoing calls.
I need to tap the loudspeaker icon twice to disable it.
Factory reset done, clear Phone app cache done, reinstall updates on phone app done.
still no fix.
anyone having this issue as well?
Click to expand...
Click to collapse
Yes and it is quite irritating.

Hi, I have exactly the same problem.

Do you have a case on the phone? Perhaps it's detecting that you are in dock mode? Just throwing some things out there since it does not seem to be widespread.

squareballz said:
I'm having this issue, it defaults to loudspeaker 70% of the time, incoming and outgoing calls.
I need to tap the loudspeaker icon twice to disable it.
Factory reset done, clear Phone app cache done, reinstall updates on phone app done.
still no fix.
anyone having this issue as well?
Click to expand...
Click to collapse
I thought I was going crazy when I picked up a call it was super loud prior to putting it to my ear lol I have no case nor screen protector so this is a legit bug.
Interesting....just applied March update. I'll see if this remedies it.

bakemcbride21 said:
I thought I was going crazy when I picked up a call it was super loud prior to putting it to my ear lol I have no case nor screen protector so this is a legit bug.
Interesting....just applied March update. I'll see if this remedies it.
Click to expand...
Click to collapse
March update did not fix it. It's getting really annoying

Time for an RMA. This can't be software related since very few are seeing it. Could be hardware so a different unit is in order. Good luck.
Sent from my Pixel 2 using XDA-Developers Legacy app

I'll bet this is happening to more people than we think. Very rarely do I chime in, I'm usually a lurker. But I figure I better say something because this problem has already happened to me twice today. It is really really frustrating. Especially for a device as expensive as this one.

bobby janow said:
Time for an RMA. This can't be software related since very few are seeing it. Could be hardware so a different unit is in order. Good luck.
Sent from my Pixel 2 using XDA-Developers Legacy app
Click to expand...
Click to collapse
RMA time??? Not on Verizon lol I don't use my phone to talk enough to justify getting an unlockable phone on RMA.
I'll deal with the occasional speakerphone pickup for the $50 I paid for the phone (well work paid) and having it unlocked/rooted etc

jascolli said:
I'll bet this is happening to more people than we think. Very rarely do I chime in, I'm usually a lurker. But I figure I better say something because this problem has already happened to me twice today. It is really really frustrating. Especially for a device as expensive as this one.
Click to expand...
Click to collapse
I'll bet it's not. The device has been out 6 months and I see 4 users with the problem out of thousands out there. If you don't want to RMA then there is no reason to complain especially if you paid 50 bucks. That's why they do RMA for instances like this. Manufacturing flaws happen, deal with it or replace the device
'nuff said.
Sent from my Pixel 2 using XDA-Developers Legacy app

Guys, I think I found out what's causing this to happen.
The 3.5 audio adapter.
I did not plug in the adapter for 2 days, and the phone did not default to loudspeaker during phone calls.
But last night I plugged in and listen to music, after unplugging, the phone all go into loudspeaker again when phone calls are made/received. Restart the phone and now it never happened.
Gonna monitor few more days and update here.

OK, it is confirmed after using the audio adapter, the phone will definitely switched to loudspeaker mode during phone calls on default , it happens randomly and i would say 70 percent of the time.
its been the 5th day i did not plug in the audio adapter , all my phone calls are not defaulted to loudspeaker, and worked flawlessly.
Google team if you're seeing this, please make a fix to it!

I've had this issue a few times and I've never used the audio adapter. I did send Google feedback about it through the settings menu a couple of months ago, but I've never heard back from them. It's been a while since I've experienced this issue and for sure it's annoying when it happens. I thought it happened because of a previous phone call loudspeaker state. If you had the loudspeaker on on a previous call then the next call would also have the loudspeaker on when it shouldn't.

miamistevie said:
I've had this issue a few times and I've never used the audio adapter. I did send Google feedback about it through the settings menu a couple of months ago, but I've never heard back from them. It's been a while since I've experienced this issue and for sure it's annoying when it happens. I thought it happened because of a previous phone call loudspeaker state. If you had the loudspeaker on on a previous call then the next call would also have the loudspeaker on when it shouldn't.
Click to expand...
Click to collapse
I still use the loudspeaker during phone calls, but at the next call, the phone does not default to loudspeaker.

I have been having two problems with my Pixel 2:
1) i cannot use a headset all the time for phone calls. I have to reboot the phone first then it's ok. I don't use the phone enough to have determined what has been done beforehand to cause this.
2) Sometimes the phone defaults to speaker phone for a phone call. Rebooting fixed it. I did use the headset the other day and then the past 2 calls were on speaker phone and tapping the speaker button did not change the setting.

I think this call quality issue is actually a SIM issue

Hi there,
I'm one of the many that's been hit by the call quality issues of the Pixel 3. I use a Pixel 3 white with Tele2 in the Netherlands and I cannot make or receive calls when the problem hits. I also have the problem where I'll cut out every 20 seconds or so any people will tell me they can't hear me.
Restarting it fixes it temporarily and then it just goes on again. It's ridiculous. I'm on my second phone already.
I've found that when this happens, when I go to settings in the Phone app, go to calls and then call forwarding or additional settings, nothing loads. It may even say SIM read error. When I restart the phone, and I can make phone calls properly again, these settings load again. Seeing as these settings are loaded from my SIM settings, I have a feeling something with the phone reading the SIM isn't quite right.

Got T-Mobile NL and especially at home, most times, people can't hear me properly.

call quality
I'm on verizon, and when I call into work conferences from home, I get complaints that I sound like I'm underwater. I've tried disabling advanced calling and that doesn't change anything (was a recommendation in a Google forum). I haven't experienced dropped calls yet, but I don't make a ton of phone calls, so that doesn't mean much.

There are tons of threads like this talking about sound issues when calling. For me the only problem I have is when someone calls me they cant hear me on speaker phone until I turn that off and talk on the regular mic. I dont know why Google hasnt addressed it yet? Leads me to believe that it may not be a software issue that it is more like a hardware problem so they will just keep swapping them out until you are good or they are done swapping and your screwed.

Super-Veloce said:
Got T-Mobile NL and especially at home, most times, people can't hear me properly.
Click to expand...
Click to collapse
Same here, if a call goes through. Usually it won't even connect

Archangel said:
There are tons of threads like this talking about sound issues when calling. For me the only problem I have is when someone calls me they cant hear me on speaker phone until I turn that off and talk on the regular mic. I dont know why Google hasnt addressed it yet? Leads me to believe that it may not be a software issue that it is more like a hardware problem so they will just keep swapping them out until you are good or they are done swapping and your screwed.
Click to expand...
Click to collapse
It's so strange, it seems like a software issue. I got one replacement and it does it as well. But a restart fixes it and doing some of the cache clearing fixed it for me for 3 days. Now it's back again.

It would be nice if it were a software issue but it doesnt even seem to be on Googles radar to fix? If they just swap out enough phones for the next few months until the next phone is announced by Google, everyone will want the Pixel 4 and forget about these issues.
Legendhidde said:
It's so strange, it seems like a software issue. I got one replacement and it does it as well. But a restart fixes it and doing some of the cache clearing fixed it for me for 3 days. Now it's back again.
Click to expand...
Click to collapse

P3 white / SIM O2 Germany. I have No problems.

The SIM card is not the problem. When I had my Pixel 3XL and my wife had a Pixel 3, we replaced both our SIM cards. This failed to resolve the issue with both phones. Go read the official product forums. Too many people have ruled that out.
After 3 months without the ability to make phone calls, the only troubleshooting step that worked was to returned the phones and get another model (Oneplus 6t). Calls have been crystal clear using the same SIM cards in all the same environments.
This is either a software issue, or a component issue. I suspect its a component issue. I would put money that there is a bad transmitter or chip-set in the phone. As someone who works with electronics on a daily basis, the intermittent nature of the problem follows the type of symptoms I see when a circuit is slowly building stray capacitance and has no way to bleed out extra potential. Similar to static electricity. This would explain why it goes away for most people for a brief period when they power cycle their phone. It would also explain why not everyone experiences it.
Google may be able to band-aid the hardware defect with software by actually cutting out HD quality on calls and fudging it, and most people won't be able to tell the difference. They might have the ability to power cycle and fulling resent a single component after each phone call. They did the same type of thing when the bottom speaker on the 3XL was buzzing at certain frequencies. They simply programmed the software to prevent the bottom speaker from playing sounds from within those frequencies. Most people aren't going to notice that one of the two speakers is slightly muted.

The only way to remedy this is to have 4g enabled at all times. Calls should then be using volte or HD voice and the issue goes away.
I anable 4g even when wifi is on and calls on both my Pixel 3 (Sold) and Mate 20 Pro are clear and rock stable if not a tiny bit tinny or raspy at the high end due to HD voice.
This is on EE Uk , but I would imagine is similar on cariers from other countries.
On a side note, with O2 I do not have this issue at all so maybe it's something to do with the frequencies or bands the mobile operator is using.

It is definitely not related to the SIM. I have replaced my regular SIM with eSIM on T-Mobile CZ and I still have this issue. I have even transferred my number from Vodafone CZ due to my contract expiring, and its still there.

Hoping after Android Q , this issue will shine [emoji848][emoji848][emoji848]
Sent from my Pixel 3 using Tapatalk

I have this issue too, updated to the Android Q beta in hopes this would stop it from happening - but it is still happening.
I can hear everyone perfectly well but they say I am breaking up or sometimes I hear terrible interference and the call is dropped. Tried all the troubleshooting steps.
One thing is I noticed if I am using hands free (car's bluetooth or the pixel headphones) the issue never occurs (so far). I am thinking the antenna might be interfered with while it's in my hand. Can everyone try using hands free solutions while not holding the phone and see if it persists?
Thanks

Factory reset and removal of certain third party apps seems to have fixed the problem for me

Div250 said:
Factory reset and removal of certain third party apps seems to have fixed the problem for me
Click to expand...
Click to collapse
and now we need to know which are those "some 3d party apps"
please, thank you

Remove recently downloaded apps one by one , restart phone normally, then make a call to see if removing that particular app solved the problem. If not, continue until you do find that app. In my case, I had my suspicions on the two that I removed and that was it.

check SIM for scratches
My SIM card is scratched. Could the phone be damaging the SIM upon insertion?
I saw on another forum that their call quality issues go away when they use the headphones that come with the phone. So that would not be consistent with a SIM issue... hmm.