Child Item

Site Totals

61498 Questions Answered 271 Categories

Microphone issues

Hey all,

I purchased a Galaxy Nexus right after it came out and noticed that, intermittently, the microphone would just die out during the phone call. The reception was fine, the call didn't drop, and I could hear the other person very clearly; they just couldn't hear me. I checked to make sure I wasn't accidentally muting the phone (I wasn't), and I tried switching to speaker phone to see if it would solve the issue (it wouldn't). When I would call the person back, the mic function was fully restored, and when I asked them to describe the issue, they said that I sounded fine, then I'd drop out and they'd hear the shred of one more syllable and then nothing until the call terminated. I returned the phone for another phone, and I'm having the same problem. I love the phone, love 4G, but I need it to work, first and foremost, reliably as a phone. I did some research and other people seem to be having similar issues. See, e.g.,

http://www.galaxynexusforum.com/forum/galaxy-nexus-general-discussion/1112-mic-issue.html

http://www.droidforums.net/forum/droid-general-discussions/13988-mic-doesnt-work-sometimes.html

Can anyone provide information on whether this is a known issue? A software issue that can (and will) be fixed in an update? Or is it a hardware issue? Should I return the phone? Heck, if nothing else, misery loves company. Anyone else noticing this? Thanks!

Dan

Comments

gabe23

You're definitely not alone. Here's a current thread on XDA discussing the problem:

http://forum.xda-developers.com/showthread.php?t=1403051

Apparently the Charge had a similar problem that was fixed with a software update. It would be nice to get some confirmation from Samsung/Verizon/Google that they are working on this.

securitynick

Just want to chime in that I'm having the same issue. I have swapped out my Nexus, but not for this reason, although it did happen on that one as well. Just that on that one, it only happened once and then another issue came up. But it happened to me 3 times in one day, once today. Getting annoying.

epitaph

Thanks for the additional info. I agree that a confirmation coupled with an assurance that they were aware of and working on the problem would be helpful in making a decision on whether to keep the phone. I guess it's not a big deal until the 15th, but at that point, I'm going to have to decide whether to go back to my old phone or roll the dice with this one. Thanks again.

shealyse

I'm on my second phone with the same issue. I would encourage everyone who is experiencing this issue to call VZW Support and report the one-way audio problem. I know that there are a number of people calling this problem a "dropped call" which can be misleading to the support group. I spent a great deal of time on the phone with them yesterday and the tech created a post on their internal forums and called it a "one-way audio issue".

I have until the 15th to return the unit. If this issue cannot be identified in a short duration, I am going to return the phone. I am sure that I will get some grief with the restocking fee, but I will definitely NOT pay any restocking fee for returning something that does not function properly.

andycho

I made a youtube video of what my Galaxy Nexus is doing...and Verizon is not replacing with brand new phone.

http://youtu.be/Gp1YdIRPcN4

shealyse

Returned my unit for a full refund and switched back to my Thunderbolt. Worst phone I ever carried!

scorch968

That looks like the LTE login issue described in Anandtech's article. I think they baseband just needs some cleaner code. It looks like the LTE radio is attempting to make connection, fails, and for some reason is not retrying. You will get the same result enabling and disabling airplane mode. It's intermittent however. I noticed this issue more with 4.0.1, make sure you are running the latest ROM version 4.0.2 .

gabe23

Scorch, I disabled LTE on my phone and continued to have the problem. I also have a friend who lives in an area with no 4G coverage so he's never used LTE but continues to have the microphone problem. The issue is resolved by hanging up and calling back - no need to go to airplane mode.

Everyone please make sure that Google is aware of this problem also: http://code.google.com/p/android/issues/detail?id=24019

hockey930

My buddy and I are both having this one way calling issue.

If either of us are on our phones for generally over 8 minutes the other party can not hear either of us anymore.

We are both in Charlotte NC.

Making the same phone calls over and over again is getting very aggravating.

My phone is totally stock and this has been happening since day 1. I gave it a few times thinking my new phone can't possibly be messing up, but I was wrong.

milehighg8

I have had this issue since day 1 (about a month now), and looks like I am going to have to return this phone due to the out-bound audio cutting out issue. I've read all the posts in the other forums discussing this problem, and it seems that Verizon, Samsung, and Google are not willing to admit there is an issue. I love this phone, and really don't want to return it, but what choice do I have? Is there someplace other than these forums where we can complain and be heard?

gman265

I am having the same issue. I purchased the phone in December and only now am beginning to experience this mic drop out issue. Very frustrating.

triadguy

UPDATE!!!! Just got off the phone with Verizon Customer Service after they sent me a replacement phone and it has the same problem. Samsung issued an internal document to Verizon on Jan 21st. "One way Call Quality Issue" Verizon sent them some phones to test and they found the that the DTMF tones were overlapping during calls. A software fix is in the works for a February release.

andycho

Yeah but they sent you a replacement phone which is a recondition phone...I had mine replaced with new one..in the store. Check to see if there are any more problems with your replacement phone..Verizon likes to replace $300 phone with reconditioned(used) phones ...which people returned it because of similar problems.

gman265

I have noticed that this only happens when bluetooth is turned on. Regardless of whether it is connected or not.

gman265

The DTMF tones thing sounds a bit fishy. What does that have to do with a call that has already been established and on going for several minutes?

triadguy

No, they sent me a brand new phone!

triadguy

I have never turned bluetooth on and had the problem. I switched my DTMF tones to "long" and it hasn't repeated the problem.

securitynick

That is probably a coincidence. The dtmf tones have to do with dialing a number. They are the sound the numbers make. So when you press "5", it knows you are pressing "5" from the sound & not because you pressed it. The reason for long or short is that sometimes short is too short of a duration of the tone for the telephone switch to recognize it. So adjusting to long gives a longer play of the tone to fix that problem. Cell phones obviously don't have a dial tone, but the call ultimately routes though the land line system to connect the call, plus when you are in an auto attendant to, "press 1 for...", that's why you need dtmf tones to begin with. I really don't think this has anything to do with it, if it did, people would probably be complaining about calls not connecting to the right numbers. Unfortunately someone probably thought this would be a good technical term to throw out there & hopefully believe it. No offense to you. Mine got resolved by swapping out my sim card. Don't know if that was a fluke, but heard that on some other forums & tried it out & haven't experienced it since.

zachf

I had the SAME problem since I got mine (running 4.1) until I just updated it today to 4.2.2 and now my mic works and people can hear me. The stranger thing is that I asked Verizon a couple months ago if they could fix it and they referred me to Samsung for warranty issues. Well, after sending in the phone (after hunting down a replacement on craigslist), Samsung deemed it as BER which I found meant beyond economical repair. I got the nexus back in the mail yesterday with this letter/explanation and figured i'd surrender. Verizon said it would be a hardware issue, not software. Samsung said it was a hardware and my hardware was corrupt.

Funny thing is it now works after 6months of not working after a SOFTWARE update... Just figured I'd let people know and hope it worked for you. Also, I have about twenty videos of people from the Samsung repair warehouse on my phone. So much for factory resetting the device before I sent it to them only to get it back with 30 minutes of video.

Child Item