Share this Story

All the way back during week one of our time with the Galaxy Nexus. emails started trickling in from users who were dealing with a microphone muting issue while on calls. We have yet to run into the issue ourselves, but it’s clear if you browse any tech forum on the internet that this is a problem for a number of owners. Verizon appears hesitant to admit that it’s a serious problem, so we thought we would run a poll to see how many of you are being affected by it. No better way to let them know that with some numbers, right?

What exactly is happening? While taking incoming calls or making outgoing calls, the microphone on the device will cut out so that the person on the other end of the line can no longer hear a thing which obviously leads to them hanging up. Toggling mute on or off, switching to speakerphone, swapping devices, activating new SIM cards, etc. are not helping the situation. It’s pretty obvious that this is a software bug that simply needs to be addressed in the next update. The problem is, that this started happening to users back in December and we are now almost a week into February without a fix.

We still have no word on when the big Android 4.0.3 (or is it 4.0.4 now?) update will be out.

Maybe this poll should be about the Verizon Galaxy Nexus. Those are the ones that seem to have the most issues from the Google forum (mine included)

http://www.facebook.com/people/Eon-Says/100002112069791 Eon Says

Just received my 2nd handset with this issue. Really thinking about giving up on the Nexus. I’ts just not worth the issues.

Modnoc121

I am having the same issue here any soulutions?

Wakajawaka

I have had two Nexi and both have cut out during calls. They both did it constantly. Non rooted 4.0.2. Nothing helps. Wiped the phone, no apps, turning on and off and changing various states. Still cuts out the mic. Very frustrating. It has gotten so bad, my friends, colleagues and customers know it is my phone and that I am waiting for a magical software fix which never comes. The most frustrating phone experience I have ever had. Giving up

nailbomb3

Kellex, you should bring this back to the front again. Here we are, its almost the end of March and still no fix.

This is a REAL issue and NO its not me covering the damn mic with my finger. It happens with:

1. all ROMS
2. all radios
3. all the Kernels I’ve tried
4. with bluetooth the speakerphone AND the Mic!

John Baptiste-Quero from Google tacitly admitted to me that its an issue with one of Sammys propietary closed source binaries. That would explain why 4.0.3 ROMS have the issue, because while userland is on 4.0.3 those proprietary binaries are OLD as there no newer factory image other than 4.0.2.

Someone needs to get a STRAIGHT answer about whether this is getting addressed in the 4.0.5 OTA.

Danzzwiebel

Second phone in a week – same issue. Grrrr!

Jeremy

Mine does this almost every single conversation. A huge disappointment, and frankly, embarassing. Talking to folks and having the mic cut out is so awkward!

If you are not one of the ones having this problem, I bet those of us that do have the problem can give a list of cities that you are NOT in. This is a regional issue; and NOT related to the region of the phone where I place my damn finger.

Anonymous

I got this phone the first day it came out. I started having this issue since day 1 where the other person I was talking with could not hear me, but I could still hear them just fine. I don’t use a Bluetooth device or a wired headset, just talking into the phone. A week later, I took the phone back and had it replaced with a new one. I thought this had fixed the problem but after a couple of weeks the problem returned. What is driving most of us crazy who are experiencing this issue is that Verizon tells everyone they have not heard of this problem before. You can tell by all the comments on various websites that thousands of people are calling in to complain about this issue, and many of them have traded their phone and sim cards in two or three times to see if that would fix the problem to no avail. But Verizon will act like you are the first person to call in to report this problem! I think it is great that most people who own this phone are not experiencing any issues, but if this poll is a reflection of what is going on nationwide, this is big problem and Verizon/Google/Samsung need to acknowledge it and get it fixed!

Lakerzz

The only problem/ bug I have with mine, is when you are doing something on the phone, and at the same time I receive a phone call, the slider to answer a call “freezes”. I then have to lock the phone, and unlock to “unfreeze” the answer slider!!

Anonymous

Wasnt aware there was an issue.. aside from abnormally low speakerphone no issues

I had problems with this with my first & second Nexus. I swapped my first one out for a different reason, but it continued to happen with my second one. On one forum, I read that someone had luck swapping their Sim card. Since my second one was using my first one’s Sim, I decided to give it a try. That apparently worked because I have not experienced the problem since.

Anonymous

So all of you who laughed at RAZR buyers because we didnt want v.0 of an OS, please refer to this article and comments. Thank you.

That being said, I do hope it gets resolved quickly. I feel for ya…

Anonymous

To those that suggest that we’re holding it wrong or somehow covering the mic hole.Those are questions I would ask a 5 year old. I’ve got 2 phones and both have this problem. My wife had 2 from BB and just ordered her 4th one from verizon, i’m ordering my 3rd one on monday. Phones have been in various stages of locked stock and unlocked rooted, no difference. Another result of this problem is that the dial pad wont transmit, meaning you can’t access voice mail because password isnt recognized. Where is verizons responsibility to give us working phones that we already bought and not pawn off refurb RAZR or Resounds to us that we didn’t want in the first place.

SKAV3NG3R

i have had this issue. I did how ever have a reboot issue…kind of like a boot loop. I took it in and they gave me a new phone on the spot. The only issue i have had is a buggy keyboard. Now to keep this in perspective, this is a new OS. With new a new OS there will be probs. Im okay with how things are thus far. Again, i would still tell anyo.e on verizon to pull the trigger and get this phone. All in all its a very good phone. I think people that come to this pg to help pick a phone see all the probs posted & think its not that good of a phone, it is. Just wanted to chime in.

Later

Kellyarens40

OK so here is the short version….Buy the Nexus on the day it drops and little by little I start having issues while making and receiving calls. The person on the other end can only hear a clicking noise, but I can hear them perfectly. This happens immediately, a few minutes in or maybe 30 minutes in. I call Verizon and new Sim Card…no fix, call Verizon and new phone…no fix, Call Verizon and new RAZR….problem solved.

Deiler

I love this phone, but the microphone cutting out is getting unbearable. It only happened periodically in the beginning, but now it is happening several times a day. It sucks that I can’t use my phone as a phone.

GOOGLE, Please fix this for us!!!!

Sts86gt

yes, I’m going back to my OG Droid. (just kidding).

Anonymous

I have issues with the headphones and mic that came with my Galaxy Nexus. People have a hard time hearing me using that little thing.

eze4

It’s called a bluetooth

Evan

I know what the problem is…it was manufactured by Samsung. I had a charge and swore I’d never buy from that company again. The pure Google is like lipstick on a pig.

Zeeds6

I had to go back to my iphone until they fix this problem. Almost every call it would do it. So annoying.

So glad this is getting more attention. Thank you Droid-Life!! Here is a Google issue thread that some of us have been talking about this problem for a while. http://code.google.com/p/android/issues/detail?id=24019
We have determined a few things: It is a one way audio issue and not a mic issue. This happens on headsets, bluetooth, etc… This seems to be a regional issue. Some users have reported moving or traveling and not having the issue anymore. This is not just a Verizon issue, GSM users and international users have had this problem as well. This issue happens regardless of ROM, Radio, Bootloader, etc. There is plenty more information in the thread above. Google/Samsung please fix this soon!!

Deiler

Thank you for cross-referencing this. Everyone, if you are experiencing this issue, PLEASE go and “star” the issue at the provided link. Hopefully that will get Google’s attention.
Thank you

Anonymous

Before you do that, make sure you are not covering the mic with your finger!

If after that it still isn’t working then by all means…

Anonymous

Not covering the mike with my finger…. as I stated this is a one way audio problem happening when talking on Bluetooth or wired headsets as well. Clearly not a finger issue. As seen in the poll almost a third of Nexus users are also experiencing this. We are all hoping for a fix soon. This phone is amazing but the one way audio.cut outs get beyond frustrating.

Anonymous

Not saying that the finger is the only cause. My voice recognition wasn’t working and my mic would cut out during calls. It turned out my finger was covering the mic (it is very easy to do). I’m just saying that this is probably happening to a few people as well and it would be good to check.

Anonymous

Agreed you may be experiencing this actually but that 1/3 on google forums is prolly half that due to trolls and another half of the alreadu half from ppl covering the mic… i cover the mic on my iphone4 almost every call cas the phone is so damn small but i have to admit its user error

Can we please stop bickering out the finger possibility and other assorted nonsense? This is clearly a bonafide issue that many gnex users are having. It seems to be regional and is extremely frustrating. Let’s focus on raising awareness to get a fix for those affected.

For those not affected – congratulations and enjoy all the benefits of this amazing device. Please help fellow gnex users by not ckuttering this with nonsense that may get in the way readers gathering info.

I’m off my soap box now.

Azndan4

I’m running AOKP (Android 4.0.3) and I have no mic problems. Is it only happening to people on the stock firmware?

Kris

Stock firmware is not stock as there was an update 4.0.2 right after activation. I am running Stock from the box (no custom roms) and I am having this problem

Anonymous

I am having this problem on AOKP. I have had it ony every ROM I have tried as well as different Radios.

jimbob

Truth be told, I’ve only talked on it about 5 minutes. The other person said I sounded great, like I was there and it wasn’t even a phone call. I’d say it’s doing okay so far.

I plug mine into a fm transmitter and it does cut out every once in a while. It acts like the output jack was unplugged. I found this also happens when listening to music with the headphones that came with the phone. My BIGGEST problem with the Gnex is that the ringer and notification volume are tied together. I don’t care if i get an email in the middle of the night, but i do want the phone to ring if someone calls. Having to change the notification default every night and every morning is getting tiresome and it makes it difficult to set up different ringtones for different things.

http://quiklives.tumblr.com quiklives

That’s an ICS thing, not phone specific. I can’t imagine why they thought it was a good idea. Latest version of AOKP has them unlinked.

Someones

never had it happen, but ive had a rom on my nexus forever

Ok

No, you’re most likely placing your finger over the little microphone dot which will completely mute the phone.

Mike Petty

I can still hear side-tone, aka my voice looped back into the speaker. It’s definitely picking me up. Not to mention, I’ve had phone calls cut out right in the middle of my daughter screaming at the top of her lungs, with absolutely zero audio on the other side. It’s not muffled, it’s totally 100% gone.

Matt

If you haven’t been fighting this problem for 2 months, you probably don’t want to speculate, because, you’re wrong.

I think this is a figment of folks imaginations…just like I am imagining my poor signal strength. I have, and still do, wanted to love this phone from day one. But now with Google pulling it off of “official support” and the fact that I can’t use it to its fullest capabilities because of a weaker than normal.signal, I have been really disappointed in the gnex. If this is what it means to own a Nexus, I could have lived without it. Wish I had known it two months ago when I used my last upgrade.

Anonymous

google is still supporting the phone, did you actually read the articles and clarifications from google, geesh

Anonymous

Yeah, I did read quite a bit. I’m still somewhat disappointed though because it sounds like the update will have to run through verizon. That stinks. If verizon messes with the updates, there goes the pure Google device. I hate that there is even a possibility of it. So while gnex is still supported it is not “officially supported”. At least that is what I have read.

angermeans

You might want to read a little more. All updates come “through Verizon” as they are checked to make sure there are no problems. The updates will come from Google and then checked and pushed. Nothing has changed in that matter. What happened yesterday was Google updating their developer page in AOSP to avoid confusion. Anyone can still build AOSP, but the data and phone calls will not work unless the missing signed apks from Verizon are there. Because of this Google took in off the dev page and that is it. Unless you plan to develop I doubt that you will ever notice a difference. I wonder if you even knew what a Nexus device was all about to begin with (I didnt until I really started to do some research. All this means is that the wonderful devs at XDA and RootzWiki will have to add the signed apk (I dont know too much how this works, but it might not even be different then what they have been doing all along) all CDMA devices have this issue that is why you cant just throw in a 4G SIM and off you go as you do with GSM phones. Believe me man I spent hours yesterday reading and I think if it bothers you this much then you should take a minute and read (starting with the posts on this site from yesterday and Android Central has a great one that Jerry wrote up and also it looks like he spent a lot of time answering people that posted their concerns) people need to let it go and/or go educate yourself before making an assumption as it really isnt anything to really worry about.

Anonymous

Hope you are right. That would be nice.

http://quiklives.tumblr.com quiklives

No. Verizon (or Sprint, or whatever CDMA carrier) has to provide Google with the CDMA things that require different keys. Then Google takes those and puts them in with its otherwise open source build and pushes it out. This is all just technicality. The reason it was pulled from their official stuff is because technically, it’s no longer open source once those other closed source bits go in there from VZW or Sprint or whoever. Updates are still coming to us straight from Google.

And anyway, “what it means to own a Nexus” is ****ing fantastic dev support, more than anything else. Slap a ROM and a kernel on there, and stop worrying and enjoy your phone.

Anonymous

good advice! I may just go with that and try a new rom tonight! Thanks!

Joshwaaaaa

Is it really the speaker? I’ve activated the keypad when it happened and hit the numbers and they don’t work either. Do they require a mic?

Joshwaaaaa

Yes, this has happened to me. Once it happened 3 times in an hour prompting me to call VZW support. Got transferred to some upper tier tech support who wanted me to do a bunch of crap I’ve already done then he puts me on hold and when he comes back he says it’s a known issue and that a fix is scheduled for this month. Who knows if he really knew anything. Love the phone otherwise.

Anonymous

Basically, I will be on a call, the person on the receiving end will all of a sudden not hear me. I can hear them fine. It happens frequently enough to be very inconvenient.

Mr. Vick

DUDE! this hits it on the head! I want to love my GNex but I can guarantee this mic issue to happen EVERY SINGLE call I make! Inconvenience is an understatement. I have tried diff combinations from stock, custom kernels, and ROMs but still have the issue. It has been described to me as a low popping sound when I try and speak or a flat out mute. I’ve tried going in store and get hit with the same “It’s a known issue” speech and basically wait for the update. I really am surprised Google nor VZW hasn’t addressed this issue. I am tempted to just switch back to the DX until something is done.

Matt

Funny, after 4 calls to 4 different techs, every single one denies that it is a known issue.

SD_Scott

This has only happened to me twice, but the call was dropped and then I couldn’t dial out and nobody could call me until I rebooted the phone. Running stock.

Anonymous

My RAZR works great, just in case you were wondering.

Anonymous

lol… thanks

Anonymous

I dunno if you have seen a GNex camera shot, but how does the Razr camera optics compare to the GNex? There’s a lot to be left desired of Moto’s cameras, and we all know from reviews that Samsung’s optics on the GNex is “subpar”. What do you think?

An unbiased opinion would be great. Still wondering if I should go and jump on the COSTCO Nexus deal, or wait a little longer til Mobile World Congress.

Thanks!

Anonymous

I am extremely pleased with the camera on the RAZR. It is not a point and shoot replacement, but it is quick, has good focus and great color. Also has the panoramic mode that works great. Like the Droid Life review says, this is the best camera on any Moto device ever.

Anonymous

Trying to compensate for that locked bootloader and year old OS?

My gnex works flawless and i couldnt imagine being off ICS after running it for 3 days.. it would be like going back to XP from 7…. android 2.0-2.3 are all the same +/- some new options … 4.0 is a brand new unbelievably polished OS that i cant wait to hit all android devices.. its stunning even for noobs.. matias was an amazing hire

Pcraig87

No problems here running AOKP milestone 3. No mic issue, no random reboots. All in all I am pretty happy with this phone. One thing to fix is the volume of the speaker. Volume+ is working ok but an OTA fix would be nice.

Anonymous

Never had random reboots on stock.. volume is my only gripe… as for the only addituons that would make stock ics better? A customizable button on the lock screen and power control toggles in the noti pull down… i know ill rom soon dont worry.. stock ics is incredible

Anonymous

This happens to me all the time, always have a fear it will cut off during important calls. Running stock, rooted and unlocked.

Anonymous

It is not the mic. It is something with either the codec or transmission it seems. I have been told of it happening on calls I have made and I also had my friend with a Verizon Gnex cut out on me. It just goes silent and then you only hear very short blips of audio that sound nearly like clicks but you can tell it is small chunks of the actual audio.

It happened on mine completely stock and my friend’s phone completely stock. It has also happened on mine with different ROMs and the 4.0.3 basebands. So something needs to change.

http://profile.yahoo.com/VWUEDDOTB2H5OSXWYMFNS56KC4 Joey

That’s where I’m at. I’ve tried, during calls, to use the buttons to see if they’ve made noises and they don’t get a reaction out of the other person I’m talking to. I don’t think it’s a mic issue either.

Anonymous

The next time your mic cuts out check where your fingers are at. I’ve found that the mic is positioned in such a way that my pinky (the finger I use to brace the bottom of the phone) almost always covers the mic completely…especially when holding the phone with my left hand (which is what is most comfortable for me).

Deiler

No, that is not the case. There is a real problem.

Kellyarens40

I am sorry, but that comment is almost insulting….You need to read some of the forums….this happens even when you are using blue tooth.

http://profile.yahoo.com/VWUEDDOTB2H5OSXWYMFNS56KC4 Joey

Or maybe you can answer why people don’t hear you pressing numbers either, smart guy.

About Droid Life

We consider ourselves to have the greatest Android community in the world, here at Droid Life. We talk general news, feature apps, review phones, and even teach you how to hack a little. But most importantly, there is no place on the internet that has the reader participation that we do and consider ourselves to be completely community driven. If you were looking for the best place to learn about Android and talk with like-minded folks about all things tech, then Droid Life is for you.