As of now I'm on my 4th Gnexus and once again I'm being plagued with the same issue I have since my first one back on launch day. Loss of voice during a call, high pitch noises, (think scratching on a chalk board) loss of sound on all key press as well as numbers when dialing.
I have called about this issue. First time around Verizon said take it back get a new one. So I did that and so on happened 2 more times same issue same results. Now on my 4th one its starting again. So verizon said it was Samsung and Samsung said Verizon.
So I was hoping for some input on what direction I should go now.
Sent from my Galaxy Nexus using XDA
After so many replacements, I can only imagine that this is happening because of your location?
Sent from my GT-P7510 using xda premium
My wife has the same phone and she has not had any of these issues. On the other had she doesn't use her phone as much as I do! I'm pretty much on mine all day and she maybe looks at it once a day.
Sent from my Galaxy Nexus using XDA
srh21 said:
My wife has the same phone and she has not had any of these issues. On the other had she doesn't use her phone as much as I do! I'm pretty much on mine all day and she maybe looks at it once a day.
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
This is an obvious case of user-error. The odds of getting a defunct phone that many times in a row is about like winning the lottery, literally.
srh21 said:
As of now I'm on my 4th Gnexus and once again I'm being plagued with the same issue I have since my first one back on launch day. Loss of voice during a call, high pitch noises, (think scratching on a chalk board) loss of sound on all key press as well as numbers when dialing.
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
when you said high pitch noises, do you mean that during a call you can hear a buzzing sort of noise when people speak? I get that on my nexus too, it's slightly irritating but I'll live with it, better than spending time to unroot it, go back to stock and then waste a whole week in the service centre.
akira02rex said:
This is an obvious case of user-error. The odds of getting a defunct phone that many times in a row is about like winning the lottery, literally.
Click to expand...
Click to collapse
It's obviously not user error.. If you read a bit you'd see there is a very lengthy thread about this very issue.. It's called microphone cutting out during call or something like that.. You can replace your phone as much as you want, it's not going to change it. the cause is unknown but I believe they have at least determined it not to be hardware..
Sent from my Galaxy Nexus using XDA App
Powell730 said:
It's obviously not user error.. If you read a bit you'd see there is a very lengthy thread about this very issue.. It's called microphone cutting out during call or something like that.. You can replace your phone as much as you want, it's not going to change it. the cause is unknown but I believe they have at least determined it not to be hardware..
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
That is correct. Audio outbound gets garbled and then lost completely. This is the worst bug of this phone. I can't count how many phone calls where I'd have to hang up and redial because the other person couldn't hear me anymore.
Sent from my Galaxy Nexus using Tapatalk
I'd blame the carrier, as i'm on Orange UK, and I use T-Mobile UK as well, and call quality both ends, is excellent
Your wife may not have the issue but are y'all talking on the same tower when the issue arises? I'm on Verizon as well and never had this problem. That said, I don't talk a lot, maybe 400 minutes a month - mostly to my boss that has an iPhone so half the time I can't hear crap anyway due to that fact.
I will say, as a recent T-Mobile transplant that has used Verizon off and on for several years with work phones, Verizon doesn't seem to have the same call quality in general terms. Maybe it's just my ear, but even back in the day I owned some Motorola claim shells that sounded pretty muddy.
Have you tried to replicate the problem on a completely stock phone with no 3rd party apps? I wonder if there's a conflict somewhere.
akira02rex said:
This is an obvious case of user-error. The odds of getting a defunct phone that many times in a row is about like winning the lottery, literally.
Click to expand...
Click to collapse
Not sure how it could be user error as well. This isn't my first phone.
srh21 said:
Not sure how it could be user error as well. This isn't my first phone.
Click to expand...
Click to collapse
KWKSLVR said:
Your wife may not have the issue but are y'all talking on the same tower when the issue arises? I'm on Verizon as well and never had this problem. That said, I don't talk a lot, maybe 400 minutes a month - mostly to my boss that has an iPhone so half the time I can't hear crap anyway due to that fact.
I will say, as a recent T-Mobile transplant that has used Verizon off and on for several years with work phones, Verizon doesn't seem to have the same call quality in general terms. Maybe it's just my ear, but even back in the day I owned some Motorola claim shells that sounded pretty muddy.
Have you tried to replicate the problem on a completely stock phone with no 3rd party apps? I wonder if there's a conflict somewhere.
Click to expand...
Click to collapse
I pretty much tried everything. New sim cards, using it with nothing installed (stock) I'm super bummed I been waiting on a nexus device to hit Verizon for a while now. I'm not sure how much longer I'm going to put up with this.
What about rolling back onto 3G? Are you on the fringe of LTE connectivity at all?
I know a lot of people talk about call quality. Frankly, I haven't experienced any issues and no one has told me that it sounds like crap (and believe me, I have friends that would mention it, we're a HARSH bunch). I don't doubt they exist, and you certainly don't sound like 3/4ths of XDA that are overly dramatic whiners. Out of curiosity, roughly how many minutes a month do you talk? Any chance that it's just an issue where, well you know, the more you do something the more opportunity to experience something that goes wrong? I used to talk a ton for work, like 3000+ minutes a month. I had a lot more dropped calls then than now, know what I mean?
You know what I'd do, which Verizon would HATE but, hey, you are the customer. I'd take you and your wife's phone into Verizon, and have them flip the numbers around. Keep EVERYTHING else about the phones the same. Her apps stay, your apps stay, just swap the numbers around and try her phone with your regular use for maybe 3 or 4 days. If you can replicate the problem while she doesn't experience the issue at all on your phone, then you can probably narrow it down to either the tower your on, or maybe the phone really is just buggy after you've been on it for a while.
Every so often I'll have a long conversation and a call gets dropped, but I've never not been able to hear someone or them not be able to hear me. Like, they're the typical issues that you could assign to either being a tower pass off problem or the nature of LTE long before the phone (on either my end or the other person's end). But, like I said, that's a rare occurrence for me.
What version of ICS are you running? I had this same problem, specifically and most frequently the one where the audio cuts out of a call, sometimes it'd do it and force me to re-call my girlfriend as many as 3 or 4 times in an hour.
What fixed it was flashing ICS 4.0.4 released from Google themselves (if I waited for Verizon to do it I'd probably be single by now). This fixed it for me immediately right out of the gate. I've had the other issues you spoke of every so often but the audio cut out was constant. This fixed everything. Been running for a while without problems (month or so maybe?).
Eh...you didn't flash it straight from Google. At best, you flashed it straight from the Verizon/Google ota server the test ota is on
I stand corrected, this is what I get when trying to post while on hold at work. Not straight from Google, leaked 4.0.4. Originally found it elsewhere linked to a google domain site, but it's best served up here.
http://forum.xda-developers.com/showthread.php?t=1481044
Give that a shot for now, fixed my woes anyway.
lblacklol said:
I stand corrected, this is what I get when trying to post while on hold at work. Not straight from Google, leaked 4.0.4. Originally found it elsewhere linked to a google domain site, but it's best served up here.
http://forum.xda-developers.com/showthread.php?t=1481044
Give that a shot for now, fixed my woes anyway.
Click to expand...
Click to collapse
From here?
http://android.clients.google.com/p....signed-mysid-IMM30B-from-ICL53F.659e0a8f.zip
try a different SIM/Network. you'd be suprised
IINexusII said:
try a different SIM/Network. you'd be suprised
Click to expand...
Click to collapse
What network do you suppose he would try?
Sounds like the phone is doing you a favor. If I had to talk to my girlfriend for an hour a day I'd want my phone to kill itself.
lblacklol said:
I stand corrected, this is what I get when trying to post while on hold at work. Not straight from Google, leaked 4.0.4. Originally found it elsewhere linked to a google domain site, but it's best served up here.
http://forum.xda-developers.com/showthread.php?t=1481044
Give that a shot for now, fixed my woes anyway.
Click to expand...
Click to collapse
Did not fix the microphone going out issue for me :-( I just flashed the 4.0.4 leak on Tuesday hoping it would alleviate this problem, but I had the mic go out about 15 mins into a call last night. Same story as with stock, had to hang up and re-dial to continue the conversation.
Related
Edit: please see this Google issue tracker post and star it to get Google's attention!
http://code.google.com/p/android/issues/detail?id=24019
I've had it happen 3 times now that I'll be on a call for a number of minutes and all of a sudden the person I'm talking to won't hear me any more. To be fair, I've been talking to the same person, and each time it's been an extended call (5+ minutes). It happened on Saturday, twice. Since then, I have wiped data/cache and flashed a custom rom. It happened again this evening, right around 10 minutes into the call.
The microphone doesn't come back. I tried turning on speaker phone and muting/unmuting my mic, but it won't bring the microphone back. Like I said, this is the same person I've spoken to each time, however, I've been speaking with them often (with their current phone) on my previous phone and never had this issue, so I'm not sure if it's their phone's problem. I spoke with someone else for 30+ minutes on Sunday and didn't have this happen.
To remedy the situation, I just hang up and call back and it works fine, until it happens again.
I'm confused. Is my phone problematic or is it a software bug or is it the other person's phone? Is anyone else experiencing this?
EDIT: Just thought I'd mention I'm on VZW LTE/CDMA.
Thought I was the only one with this problem. Had the exact same thing happen to me talking with my girlfriend the past two nights. Think I'm going to blow away everything and go back to stock 4.0.2. I think it's an app that's misbehaving.
Please report back with your findings.
I've had the same thing happen to me. It has happened the most often when talking to my gf who has an iphone 4 on ATT, but it also happened when I was trying to make dinner reservations at a restaurant that was using a landline.
I am running stock 4.0.2.
If anyone has any suggestions, I'm all ears.
This was a common problem on the Samsung Droid Charge, which uses the same questionable Via baseband modem for voice calls. The earlier Charge Froyo firmware had all kinds of voice issues: 1) outgoing voice drop. 2) systematic cut in/out. 3) garbled robot voice quality. 4) loud ear hurting static. Since the latest Charge firmware EP4 (gingerbread), all issues except occasional robot voice are fixed. The phone is now usable where it was laughable before. The loud static may have been linked to certain phones / hardware rather than firmware.
Hopefully Samsung can incorporate the Charge fixes into the Nexus.
Hopefully Samsung stops using 3rd rate Via chips.
Thanks for the input. Nice to have an idea of what's going on.
Sent from my Galaxy Nexus using Tapatalk
Hey I have this happen about once a day sometimes more and doesnt matter who im talking to it can happen to anyone at anytime. This is very annoying seems like the smarter and more advance these phones get the crappier the actual phone call part of it gets. I think they forget cell phones primarily are for phone calls
Ironically 2 of my calls today complained i was dropping out. But i had full signal. My phone is brand new so these are the only calls ive really made so far.
Reply I had the same thing happening to mine. I was actually on the phone with VZW Level 2 Tech support when the mic went dead. It happened twice while talking to the same agent. She said it sounded like a clicking noise on her end. She then told me to take the phone back to the store.
I went in and got it swapped for a new one and had to return that one the same day because the ear piece sounded blown. Now on my 3rd Galaxy Nexus. The mic issue hasn't happened yet but I just got this one yesterday.... I'll report back if it happens again.
Sent from my Galaxy Nexus using xda premium
I don't think this is a hardware problem. I've had this happen on all three GNs I've had. This last time I was talking on my jawbone headset. I tried switching to the phone mike and speaker phone it did not make a difference. I also tried muting and unmuting. How do we get Samsung to acknowledge this problem?
This happened to me a couple of times also, stock 4.0.2
I have the same problem on stock 4.0.2 and on RevolutionHD 2.1.2. I spent an hour or so with level 2 tech support. I was told that I was the only person to report this issue. They suggested that I change it out or switch to a different phone. My Son-in-Law has the Nexus as well and also has the same issue. I guess I have till 1/15/2012 to make up my mind.
I am having the exact same issues. I will say it lasts about 3-5mins in the call then no one can hear me, and I have to call the people back. I love my Nexus!! I am so glad that I am not the only one having this issue. Edit: I have gone on the VZW Tech Forums and informed them of my problem, and pointed to this thread. I am hoping I hear something from VZW. Maybe if we can get more people to post on the thread over there, VZW and Samsung will see there is a problem. Heres the link h t t p ://community.vzw.com/t5/4G-Discussion/No-One-Can-Hear-Me-After-3-5mins/td-p/762556 (sorry had to space the http part since I am new.
I've had this issue too. Sounds like a resonably easy thing to fix with software.
Sent from my Xoom using xda premium
Has anybody had this happen on 4.0.3? How about on the GSM GNex? Just trying to narrow it down.
Exact same problem here. I called Verizon and they sent out a new one. But after a few calls longer than 5 minutes the microphone went out and I had to call back. I reused the same SIM card. Could that be a potential solution?
Sent from my Galaxy Nexus using Tapatalk
I made tons of test calls today and not a single issue on my GSM version. I only experienced this cut out issue the first day so guess I'm good for now...
I've had this happen on me twice running a 4.03 Custom Rom. Happened about 15 minutes into each call
I believe it to be hardware.
Why do you think its hardware?
Sent from my Galaxy Nexus using Tapatalk
Anybody running into this? I bought a GNex about 2 weeks ago and when on a call I get a high pitch squeal randomly. Loud... like pull the handset from my head loud. The person on the other end doesn't hear it. I called VZW several times and they say they haven't heard of this. My wife got the same phone when I did and it happens to her, too. My twin got the phone about a week later and his is fine. I took the phone in to VZW earlier this week and they mailed me a replacement... it does it also. I changed the ROM to the Open Kang ROM to see if it might be a software thing... still doing it. Very frustrating. It happens when sitting in my office on 4G or 3G, when driving, etc... no real rhyme or reason that I've been able to figure out. The squeal happens every 3-15 minutes without any real pattern. I don't see any notifications or anything that are new after the squeal takes place.
If anybody else is experiencing this can you post? If you fixed please advise! Thanks!!!
aharper said:
Anybody running into this? I bought a GNex about 2 weeks ago and when on a call I get a high pitch squeal randomly. Loud... like pull the handset from my head loud. The person on the other end doesn't hear it. I called VZW several times and they say they haven't heard of this. My wife got the same phone when I did and it happens to her, too. My twin got the phone about a week later and his is fine. I took the phone in to VZW earlier this week and they mailed me a replacement... it does it also. I changed the ROM to the Open Kang ROM to see if it might be a software thing... still doing it. Very frustrating. It happens when sitting in my office on 4G or 3G, when driving, etc... no real rhyme or reason that I've been able to figure out. The squeal happens every 3-15 minutes without any real pattern. I don't see any notifications or anything that are new after the squeal takes place.
If anybody else is experiencing this can you post? If you fixed please advise! Thanks!!!
Click to expand...
Click to collapse
Yes, that happened to me when i was running stock at first too. Once i flashed AOKP 4.0.3 and franco's kernel, I haven't had that problem at all. It was REALLY annoying, sporadic, no rhyme or reason. It was also waaayyy louder than i thought the speaker could ever get ironicly enough. Also dont know if the new radios might have helped too, I flashed those separately because they aren't included on the 4.0.3 roms. Hope it helps =\
I called Verizon about this again today. I had enough trouble with one device that they sent me a second device. The second device does it too. Very frustrating. The device is also much slower than my old Incredible. I officially hate this device. Should be faster with a solid connection to 4G. I'm going to see what is necessary for VZW to somehow get me out of this device and into anything different. Hell, at this point I'm ok with an iPhone... anything but this.
I'm going to use this thread to track what I've been doing in the hopes that it can help others if they are dealing with VZW with this issue.
Dec/11 - bought the GNex new. Had the squealing problems and talked with the store I bought it from. They thought it was an app and suggested I make changes to my apps. I did that for a week or so and they finally exchanged the phone for new.
Jan/12 - new device arrives. Same trouble. I dropped the stock OS and went to the OKP OS. Same trouble. Figure I'll take notes for vzw and see if I can figure it out. What I found...
Seems to happen when talking with other mobile users, never to a land line. Later narrowed it down to only other vzw users, did not happen when talking to at&t users. Later narrowed it down that it only happens to other vzw users who are using the GNex device as well.
Called vzw last week after growing frustrated again. They had me do some troubleshooting on the device and re-provisioned my account. Same trouble. They sent me another new device. I put this device back to stock and relocked.
Feb/12 - 3rd device arrives. Stock OS, no apps installed. Had the same problem that same day. Called vzw the next morning and they had me put the device in safe mode so that they could determine if the problem was hardware or software. If you didn't know there was a safe mode now you know. Boot holding the down vol button until you're in the OS. Immediately had the same problem.
Called vzw back and demanded a different device. They told me they couldn't change the device because I was outside of 14 days. No kidding, I wouldn't be outside of 14 days if vzw hadn't been asking me to do all of this troubleshooting. I finally agree to pay full retail price if they credit my account for the past 3 months of troubleshooting. Nope. They make me upgrade eligible and I went a completely different direction to an iPhone hoping that this stupid squeal would be gone. I'll sell the GNex for close to retail on Craigslist at this point.
Mar/12 - iPhone is running for a day and I talk with my wife (GNex device). The squeal is there but MUCH SOFTER in volume. I will talk with my brother as I leave work tonight because I always have trouble with him on the phone. Hopefully this will help me know for sure.
What I think I'm finding is that it's not necessarily my GNex that had a problem... it's the reception from OTHER GNex users that is causing me the trouble. My wife has complained about the problem as well but at a much lesser frequency and only when on the phone with me. We don't talk on the phone that much. The curious piece is that my brother doesn't have the problem.
More to follow as I figure out for sure whether or not the iPhone has the same problem. If so then it's not my device, nevermind that I'm on my 4th device in 3 months. VZW has been entirely worthless through this process and has made me fight the entire way. Their customer service is horrible and the managers that I have been talking to should be fired. I can't believe they allow managers to talk with customers the way some of these guys do (especially this last Paul LaFranky dude (not sure about his last name)).
So I just came across this thread while doing my normal daily browsing here and find it interesting.
My nephew who has a SGSII here in east coast Canada on Bell txt'ed me earlier to ask if I ever get a "crazy squeal noise from your phone when you're trying to make/receive a call".
It's not all the time. He said it happened about 4 times in the past few months and it's only a land line. He doesn't make a lot of voice calls, mainly the 1 land line (work). When it happens, he hangs up and calls back and it's fine.
It may be completely unrelated to your issue. He's on stock gingerbread.
Anyway, thanks for posting the details and keeping record, i'll follow this for sure.
I have now had two calls today with the high pitch noise. At this point it is def not my device as I'm now on an iPhone. Good news is I can go back to the gnex. Bad news is that I'm all but certain that gnex devices are somehow SENDING these tones. With as unhelpful as vzw has been I'm beginning to think I may simply need to call those people less often... So annoying. I'll call vzw in the morning and see what they have to say. Ugh.
Mine does it too. It is my second one as my first stopped working on 3g so they replaced it. The first phone did it too. I just live with it.... I dont talk on phone much.
I get them as well with the GN, but I was also getting it with my thunderbolt from time to time.
My brother is upgrading to 4.0.4 today and will drop a new OS on his GNex. Once he does that I have asked him to call me to chat for a little bit. It would be great if that takes care of the problem! Fingers crossed. If that doesn't solve the problem I will call VZW with the additional info. If it does then I'll go back to the GNex and sell this new iPhone.
Update - called VZW to have my account updated with the latest notes. While on the phone the lady I spoke with acknowledged that there is a KNOWN ISSUE FOR THIS PROBLEM with Samsung devices. The devices that she said are affected are the Galaxy Nexus, the Charge and the Stratosphere. Samsung is supposedly working on an update that will address the problem. No ETA for that update.
I sure wish someone had told me about this sometime over the past 3 months of troubleshooting... it would have saved me the money for the iPhone as well as the hassle with vzw. Hopefully someone here will get some good out of this.
How odd. I have a VZW Nexus, but have not encountered this issue. I don't often make calls, but they sound fine when I do.
The problem is on the other end for the person you are talking to... they will hear a high pitch squeal from time to time. Mine would do it as often as every 10-15 seconds or so or could be as little as every half hour (or not at all depending on length of call).
I have talked with my brother a couple times today after he upgraded to 4.0.4 and haven't had the problem at all. I wonder if that update includes some work to fix this. ??
Hi everyone. I, as many others, have been having an issue with my microphone cutting out during a phone call. I have a roooted Verizon Galaxy Nexus running the 4.0.4 leak, but it appears that for everyone who is having this issue it doesn't matter which ROM you're running or even if you're rooted or not.
[EDIT]: It per one of the posters below, this is not so much a "microphone" issue as it is an "outbound audio" issue. Unfortunately I can't edit the subject name to refer to this, but for me personally when I've been doing google searches on this issue the first word that came to mind anyway was the word "microphone" or "mic" anyway.[/EDIT]
People have been trying different things like flashing different radios, muting and unmuting, turning off voice privacy, etc., but it seems that nothing helps. Not even several hardware replacements or sim card replacements.
However, I did notice a pattern from different forums, etc. It seems that some people either have the problem all the time, or not at all, and it seems that some people reported that traveling to different metro regions affected whether or not they had the issue.
So I was curious to see if the pattern has to do with geographical location as an issue with Verizon's network, vs. hardware/software issues.
This poll has 50 possible answers, 1 for each state. Please answer this poll ONLY if you ARE experiencing this issue, and please only vote for your state if you live in the state's capital. For example, I live in the Denver metro area, so I would vote for Colorado. However, if I lived in Fort Collins or Grand Junction, I would NOT vote at all.
If you have traveled and visited another state's capital and have had this issue there, you can go ahead and vote for it as well.
It will be interesting to see if we have a lot of hits in certain major metro areas and none in others.
[EDIT2] Also, if you don't have the problem at all, go ahead and post a comment with your location. In fact, it would be interesting to see if people don't have the problem but others in the same city do. [/EDIT2]
Thanks!
I thought I had this issue just turns out my pinkie was covering the microphone its king of poor positioning watch, the way u hold the phone after changing the way I hold it no one complains they can't hear me
Sent from my Galaxy Nexus using XDA
TLDR: I kept having people telling me that I sounded like a robot.
Sent from my Galaxy Nexus using XDA
I had this problem on back to back to back phone calls this morning. Horrible.
Sent from my Galaxy Nexus using Tapatalk
My wife and I are both having the issue in Richmond, VA but I could only vote once for myself. She has reverted to an old droid x as she cant rely on the phone anymore.
Might be a little late, but maybe we should collect ZIP codes instead? Then we could use this tool: http://batchgeo.com/
Try watching how u hold the phone I'm seriose since I changed the way I hold the phone this is a non issue your prolly plugging the microphone
Sent from my Galaxy Nexus using XDA
I voted. I'm in South Carolina. I'm pretty sure it's NOT a regional problem though.
twiztidninja said:
Try watching how u hold the phone I'm seriose since I changed the way I hold the phone this is a non issue your prolly plugging the microphone
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
If holding the phone different worked for you, then you don't have the issue this is referring to. This issue can happen with a wired headset, Bluetooth headset, on speaker phone, which none of these would be affected by how you are holding the phone considering you aren't using the mic on the phone. The people on the other end hear a series of clicking sounds, then no audio.
twiztidninja said:
Try watching how u hold the phone I'm seriose since I changed the way I hold the phone this is a non issue your prolly plugging the microphone
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
I realize you're trying to help, but you really don't understand the issue. The OP really didn't describe it properly, as it's not a "microphone" problem, but rather an "outbound audio" problem. I use mine at work as a speakerphone with it sitting on my desk, and I lose outbound audio all the time. Others have the problem with a bluetooth headset. I don't doubt that there are some people who have had an issue with covering the microphone hole, but that is not what this thread is about. This is an ongoing issue that people have been troubleshooting for months, and Verizon/Samsung is supposedly working on a software fix to resolve it (I'm not holding my breath).
I had the same problem on my 2 rogers GNs(GSM version)
after I upgrade my baseband to i9250xxkk6, the problem gone
I like the OP enthusiasm, but I don't think you will be able to glean any info on location. Owners are too spread out. Maybe in a few months.
I'm in Raleigh, NC.
I got my phone on release day and noticed this problem a few days later. I've since replaced the phone, then the SIM card (a theory that it was SIM-card related was floated over at AF).
After changing the SIM card the problem seemed to go away for a couple of weeks, but it came back with a vengeance.
I hate the idea of getting a "refurb" from Verizon (I put refurb in quotes because, based on the FIVE refurb'ed Incredibles I had, I'm pretty sure they don't do anything except replace the glass if it's scratched), but I guess a functional refurb would be better than an aggravating semi-functional new phone.
twiztidninja said:
Try watching how u hold the phone I'm seriose since I changed the way I hold the phone this is a non issue your prolly plugging the microphone
Click to expand...
Click to collapse
I can't help but be reminded of Steve Jobs.... "You're holding it wrong!"
I'm glad your phone is working properly but, as others have noted, this is most definitely not the problem we're talking about.
gabe23 said:
I realize you're trying to help, but you really don't understand the issue. The OP really didn't describe it properly, as it's not a "microphone" problem, but rather an "outbound audio" problem. I use mine at work as a speakerphone with it sitting on my desk, and I lose outbound audio all the time. Others have the problem with a bluetooth headset. I don't doubt that there are some people who have had an issue with covering the microphone hole, but that is not what this thread is about. This is an ongoing issue that people have been troubleshooting for months, and Verizon/Samsung is supposedly working on a software fix to resolve it (I'm not holding my breath).
Click to expand...
Click to collapse
Thanks for clarifying, I edited my original post, unfortunately I can't edit the subject name, but you're right, it's outbound audio and not mic. Thanks again!
adrynalyne said:
I like the OP enthusiasm, but I don't think you will be able to glean any info on location. Owners are too spread out. Maybe in a few months.
Click to expand...
Click to collapse
You're right, I was caught up in it at the moment and thought it would just be interesting to see how the issue maps out, but this little poll in no way is a troubleshooting tool, more of a type of infographic maybe?
The only fix is going to be a software update from el goog. can't wait for it!!!
I just got off the phone with Tech Support about this.
The Level 2 agent found an internal support document about the problem and read me what it said for the fix.... It says that the upcoming software release is going to cover this. It goes on to say that the tentative (dammit) release date for the software release is late March.
I don't want to trade in the new phone that I've babied since day 1 for a refurb of unknown quality if a fix is coming within the next couple of weeks.
If they don't release the update soon (which wouldn't surprise me at all), I'll probably just flash a new ROM & radio.
Flashing a new rom/radio does not help. I'm running nothing stock (leaked radios, CM9 Kang Nightly, Franco Nightly) and I still have this issue.
Good to know I'm not alone, Minnesota is currently winning! :-\ :-(
AnotherHiggins said:
I just got off the phone with Tech Support about this.
The Level 2 agent found an internal support document about the problem and read me what it said for the fix.... It says that the upcoming software release is going to cover this. It goes on to say that the tentative (dammit) release date for the software release is late March.
I don't want to trade in the new phone that I've babied since day 1 for a refurb of unknown quality if a fix is coming within the next couple of weeks.
If they don't release the update soon (which wouldn't surprise me at all), I'll probably just flash a new ROM & radio.
Click to expand...
Click to collapse
I was told the same thing by VZW support, but mid-march... which is NOW! I'm really getting sick of this. Ready for the fix and some info.
I have the same problem on the GSM version. Also Raleigh, NC.
So I'm one of the unfortunate users that has the stupid mic muting issue. I've just been dealing with it and waiting to see if a update from vzw ends up fixing it. Well, it's been five months and still no update. I rooted my phone immediately after the first time I ran into the problem. I'm on the 4.0.4 radio now and it's still there.
So has anybody had luck switching out devices? It sucks because my screen is beautiful and the call muting issue is the only one I have. Should I go through the hassle of getting a replacement?
Edit* crap, can a mod move this to q/a.
Sent from my Galaxy Nexus using Xparent Blue Tapatalk 2
I've never had this issue on my LTE GNex. I don't believe its a common issue. I would definitely get it replaced.
what exactly happens that mutes it, and for how long? does it happen when you are not holding the phone?
reason i ask, is the microphone is a tiny hole on the bottom of the phone, and if you hold the phone like many do, with a finger underneath, even slightly blocking this hole will completely mute the microphone out.
cancerouspete said:
what exactly happens that mutes it, and for how long? does it happen when you are not holding the phone?
reason i ask, is the microphone is a tiny hole on the bottom of the phone, and if you hold the phone like many do, with a finger underneath, even slightly blocking this hole will completely mute the microphone out.
Click to expand...
Click to collapse
To all Verizon Galaxy Nexus users who have no idea what issue we are talking about, read the following:
http://code.google.com/p/android/issues/detail?id=24019
It basically happens on full signal (with LTE and/or CDMA turned off and on), stationary or moving, under bluetooth + speaker + ear piece while physically holding the phone or not, makes our voice turn into a choppy robotic sound and we can hear them but the other party can't hear me.
Only resolution to this problem is hang up and call again.
There is a huge variation among devices, some has this issue as soon as 5 seconds into a phone call, some have it well into 15 mins or even 40 mins into a call. Some happens basically on every other call, some happens once in a bluemoon.
Yes, we've all tried every single ROMs and radios. And yes, we are not holding it wrong to cover our mic with our finger tips.
And yes, it is not user error because it happened to all 2 new gnex and 2 refurbished replacements STOCK without any apps on it. I got mine to happened on pretty much the entire state of california (I travel very frequently from SoCal to NorCal)
The only reason a few might not face this issue is simply because 1) either they picked the cream of the crop out of all these affected devices 2) not using the GNex as a phone as much as some of us do.
I simply do not use GNex for business purposes...
To OP, getting a replacement might help a little but no promises.
Man I'd have replaced it long ago. I would imagine it's hardware related or they would've pushed an OTA to fix it. I read somewhere that Verizon stated an update would be sent out that would fix it, but I'm not buying it.
Sent from my Galaxy Nexus using Tapatalk 2
Yeah I'm just scared to swap it out and receive one with a ****ty screen. Plus I have a invisible shield on here. And there's no guarantee it will be resolved. Has anyone had any luck with swapping them out? I really don't want to switch to a different phone. I've waited for a nexus device to hit verizon for so long.
Sent from my Galaxy Nexus using Xparent Blue Tapatalk 2
Ya know, honestly, I'm not all that impressed with the phone. I've only had it a couple weeks, but it doesn't do anything better than the Epic 4G Touch that I came from. The E4GT was awesome, the Sprint network, not so much. The camera and battery life were just so much better and I'm struggling with that.
Sent from my Galaxy Nexus using Tapatalk 2
bangdrum said:
Edit* crap, can a mod move this to q/a.
Sent from my Galaxy Nexus using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
Gotcha Bro
FNM
I just got off the phone with VZW about this very issue. They said they have a release tentatively scheduled for May, but "tentatively" could end up being August. It's a known issue so, there's no workaround for it and getting a replacement probably won't help.
The only thing they could possibly offer is switching to another device altogether. Spec-wise, the Galaxy Nexus is at the top for me so I don't want another phone. (frustration)
Alas, depending on what's important to you, you may just be better off waiting for the update. :-(
blackdiamond01 said:
I just got off the phone with VZW about this very issue. They said they have a release tentatively scheduled for May, but "tentatively" could end up being August. It's a known issue so, there's no workaround for it and getting a replacement probably won't help.
The only thing they could possibly offer is switching to another device altogether. Spec-wise, the Galaxy Nexus is at the top for me so I don't want another phone. (frustration)
Alas, depending on what's important to you, you may just be better off waiting for the update. :-(
Click to expand...
Click to collapse
This is why I'm glad I asked. I don't want to bother with getting a refurbished phone for nothing.
Sent from my Galaxy Nexus using Xparent Blue Tapatalk 2
I know it's kind of a old thread but wanted to update my experiences.
I am on my second replacement now and I'm sticking with it. I've had the issue maybe 3 times in the month I've had it. My first replacement had a terrible screen, crappy signal, and the muting issue happened just as frequently as before if not more.
I'm assuming this will never be spoken of by Samsung since we've already had the phone almost a year with no acknowledgement. I just hope the next nexus is a different manufacturer (HTC especially) since every Samsung phone I've had has had issues with the actual phone part. My first being the fascinate and now this. Especially since if I want to upgrade from now on ill end up paying full price.
Sent from my Nexus 7 using Tapatalk 2
bangdrum said:
I know it's kind of a old thread but wanted to update my experiences.
I am on my second replacement now and I'm sticking with it. I've had the issue maybe 3 times in the month I've had it. My first replacement had a terrible screen, crappy signal, and the muting issue happened just as frequently as before if not more.
I'm assuming this will never be spoken of by Samsung since we've already had the phone almost a year with no acknowledgement. I just hope the next nexus is a different manufacturer (HTC especially) since every Samsung phone I've had has had issues with the actual phone part. My first being the fascinate and now this. Especially since if I want to upgrade from now on ill end up paying full price.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I have had the same problem.
I've gone through 2 replacements and still the same issues have occurred. The update that was supposed to fix this was released in May and it fixed nothing. I called Verizon several times asking what will be done about this. Their answer is that another update will fix this. I frankly don't believe it.
Verizon also told me that Samsung is aware and they're "actively" working on a fix.
Being that I use this phone to make business calls, I can't have a phone that I can't depend on. Their answer: We can give you the RAZR. Not the RAZR Maxx - the RAZR.
I said that won't work because the RAZR doesn't compare to my phone as far as specs go. It's worth 200 less than my phone on their website.
The only phone that compares to mine is the Galaxy S3. Not to mention, I flat-out don't like the RAZR (or the RAZR Maxx). They said they couldn't give me the S3 because the phone was just released.
So, in short, I'm VERY upset with Verizon, because I don't feel like I'm being treated fairly. I'm willing to wait for this so called fix they will push out since my warranty is until December and they claim they'll get it right this time. But if this doesn't work....well, I feel sorry for whichever Customer Rep catches my evil side lol.
Yeah they are gonna get an earful tomorrow when I call. I've had the phone maybe 18 days and it didn't start this until day 11 and ever since its been non stop. I don't think any of us should suffer through calling 10-15 times per 30 minute conversation.
Sent from my Galaxy Nexus using xda premium
donnieseech said:
Yeah they are gonna get an earful tomorrow when I call. I've had the phone maybe 18 days and it didn't start this until day 11 and ever since its been non stop. I don't think any of us should suffer through calling 10-15 times per 30 minute conversation.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Good luck with that. I'd be interested to know how that works out for ya. Hopefully you'll get a decent answer.
blackdiamond01 said:
I have had the same problem.
I've gone through 2 replacements and still the same issues have occurred. The update that was supposed to fix this was released in May and it fixed nothing. I called Verizon several times asking what will be done about this. Their answer is that another update will fix this. I frankly don't believe it.
Verizon also told me that Samsung is aware and they're "actively" working on a fix.
Being that I use this phone to make business calls, I can't have a phone that I can't depend on. Their answer: We can give you the RAZR. Not the RAZR Maxx - the RAZR.
I said that won't work because the RAZR doesn't compare to my phone as far as specs go. It's worth 200 less than my phone on their website.
The only phone that compares to mine is the Galaxy S3. Not to mention, I flat-out don't like the RAZR (or the RAZR Maxx). They said they couldn't give me the S3 because the phone was just released.
So, in short, I'm VERY upset with Verizon, because I don't feel like I'm being treated fairly. I'm willing to wait for this so called fix they will push out since my warranty is until December and they claim they'll get it right this time. But if this doesn't work....well, I feel sorry for whichever Customer Rep catches my evil side lol.
Click to expand...
Click to collapse
Exact same story they told me. I'm in my 5th device. 1st one camera broke completely and signal issues. 2nd one screen had a nasty yellow tint on half the screen. 3rd one had the worst screen I had ever seen. I wish I would have taken pictures to show. 4th one was great till the ear speaker completely went out and the speaker broke. 5th one that I currently have has a beautiful screen with no issues so far.
Sent from my Galaxy Nexus using xda premium
Having a very strange problem with my S3. I've noticed it at home more than anywhere else but basically what happens is that if someone calls me, the phone doesn't ring on my end but I do get a voicemail notification after they've left a message. Then when I talk to them, they tell me that on their end my phone rang once or twice and then went straight to voicemail. And my phone doesn't show any missed calls so obviously, my phone never detected that there was an incoming call.
BTW, it doesn't happen all the time. Sometimes the calls come in just fine.
I've checked my signal strength and it's always between 3 and 5 bars. I've missed more calls than I can count because of this. Some of them were important calls.
And I don't have any problem making outgoing calls or using the data connection for anything.
Any idea what's going on?
BonesHopkins said:
Having a very strange problem with my S3. I've noticed it at home more than anywhere else but basically what happens is that if someone calls me, the phone doesn't ring on my end but I do get a voicemail notification after they've left a message. Then when I talk to them, they tell me that on their end my phone rang once or twice and then went straight to voicemail. And my phone doesn't show any missed calls so obviously, my phone never detected that there was an incoming call.
BTW, it doesn't happen all the time. Sometimes the calls come in just fine.
I've checked my signal strength and it's always between 3 and 5 bars. I've missed more calls than I can count because of this. Some of them were important calls.
And I don't have any problem making outgoing calls or using the data connection for anything.
Any idea what's going on?
Click to expand...
Click to collapse
Is it just certain contacts? You may have them set to go directly to voicemail by accident. I can't find where the list is in the phone though ahah, I can see how to add them to reject list though.
EDIT: Found it go to dial-pad and hit menu and then call settings and you will see call rejection see if you have anyone in there.
Halmo said:
Is it just certain contacts? You may have them set to go directly to voicemail by accident. I can't find where the list is in the phone though ahah, I can see how to add them to reject list though.
EDIT: Found it go to dial-pad and hit menu and then call settings and you will see call rejection see if you have anyone in there.
Click to expand...
Click to collapse
Nope, has nothing to do with who's calling. Sometimes a call from the same person will come through but ten minutes earlier it didn't.
Ive had similar problems in the past. Turned out the phone signal was going up and down. When it was up, calls came through. And down, well duh. Either way, try a new radio. Maybe it'll hold a signal better. I've heard people complaining about H1, but cant say either way myself. Just a suggestion.
Ends said:
Ive had similar problems in the past. Turned out the phone signal was going up and down. When it was up, calls came through. And down, well duh. Either way, try a new radio. Maybe it'll hold a signal better. I've heard people complaining about H1, but cant say either way myself. Just a suggestion.
Click to expand...
Click to collapse
how can I try a new radio?
BonesHopkins said:
how can I try a new radio?
Click to expand...
Click to collapse
there's a thread in development. some people call em modems, but its the same thing. Choice of 3 i think.
Having the exact same issue is your phone always in lte while this happens?
Sent from my htc_jewel
Andrew149 said:
Having the exact same issue is your phone always in lte while this happens?
Sent from my htc_jewel
Click to expand...
Click to collapse
As far as I can tell.
stay away from LH1 modem it's trash....
BonesHopkins said:
As far as I can tell.
Click to expand...
Click to collapse
Same here
Sent from my htc_jewel
BNaughty said:
stay away from LH1 modem it's trash....
Click to expand...
Click to collapse
My baseband version is UCLG1.
btw, I never had this problem with my iphone 3GS which I had for almost 3 years.
I have to say that even though on paper the S3 blows the iphone out of the water, for pure functionality without problems, the iphone is definitely way ahead of the S3. I'm pretty much stuck with it for the next two years but I have a feeling that if things stay more or less the same in the cellphone market, I'll probably be switching back to iphones after my contract is up. The S3 is very cool but I've just had way too many problems with it that I never had with my iphone. My iphone just..........worked. With my S3 calls don't come through, I'm constantly having to force stop apps so my battery doesn't drain all the time (and even then, half the time the battery drains like crazy no matter what), the visual voicemail is sketchy as hell and doesn't work right half the time, the data connection even when it shows a strong LTE signal is often very slow and times out a lot, and a bunch of other misc. annoyances that I never had with the iphone. I wouldn't say I'm sorry that I bought the phone because I wanted to try out the latest and greatest but when my friends and coworkers have asked me about it, I've been telling them they'll be better of waiting for the iphone 5. Sorry to vent but overall, after having it for almost two months, I've concluded that I'm very disappointed with this phone. Sure, I can do things with it that I couldn't do with the iphone but f*ck me, at least with the iphone I could do basic sh!t like receive phone calls and check my email without the connection timing out all the time.
BonesHopkins said:
My baseband version is UCLG1.
btw, I never had this problem with my iphone 3GS which I had for almost 3 years.
I have to say that even though on paper the S3 blows the iphone out of the water, for pure functionality without problems, the iphone is definitely way ahead of the S3. I'm pretty much stuck with it for the next two years but I have a feeling that if things stay more or less the same in the cellphone market, I'll probably be switching back to iphones after my contract is up. The S3 is very cool but I've just had way too many problems with it that I never had with my iphone. My iphone just..........worked. With my S3 calls don't come through, I'm constantly having to force stop apps so my battery doesn't drain all the time (and even then, half the time the battery drains like crazy no matter what), the visual voicemail is sketchy as hell and doesn't work right half the time, the data connection even when it shows a strong LTE signal is often very slow and times out a lot, and a bunch of other misc. annoyances that I never had with the iphone. I wouldn't say I'm sorry that I bought the phone because I wanted to try out the latest and greatest but when my friends and coworkers have asked me about it, I've been telling them they'll be better of waiting for the iphone 5. Sorry to vent but overall, after having it for almost two months, I've concluded that I'm very disappointed with this phone. Sure, I can do things with it that I couldn't do with the iphone but f*ck me, at least with the iphone I could do basic sh!t like receive phone calls and check my email without the connection timing out all the time.
Click to expand...
Click to collapse
All of the issues you listed are not really S3 specific because I have had none of them and have had my phone since release. Apart from the video voicemail which I can't comment on because I have never used.
BonesHopkins said:
My baseband version is UCLG1.
btw, I never had this problem with my iphone 3GS which I had for almost 3 years.
.
Click to expand...
Click to collapse
I've had my I747 since release in June and not experienced any of these issues. Over the years with Blackberrys and the Galaxies I found most problems result from variances in the network. Signal strength, carrier software and even where the phone is in the house. I dislike much about the iPhone (I do have a 4th gen iPod) and much prefer the openness of the Android OS and NO iTunes. Hope things with S3 get better for you.
Still having the problem. It seems to happen most often when I have LTE enabled. I disabled it using the method mentioned in another thread where you remove the sim then enter a code which takes you to the menu where you can choose what to use.
When I had LTE disabled, it didn't seem to miss as many calls. But when LTE is on, I miss a crapload of calls. I'd leave LTE off but for some reason it keeps re-enabling itself every few days so it's turning into a massive pain in the ass.
Any suggestions?
I have the same issue as you, but I'm on Wind Mobile. This issue happens intermittently anywhere between 1 to 2 days, my phone will stop being able to receive calls. It's very frustrating and Samsung is really no help. After two attempts on trying to "repair" my phone, they have failed each time. The only thing they did was they ran a "RF Test" and everything passed, they said. So they re-flash my phone with the same ROM - again and again.. I told them, "This is my second time sending it in, and you guys are redo'ing the same steps as the first repair. You don't need to be a rocket scientist to know this, but wouldn't you think when you send me back the phone - the issue is still going to be there?!" ... And sure enough, when I got the phone back, I was still unable to receive calls..
So I took matters into my own hands - I flashed it with a older release stock rom and I tested it for 2 weeks, and it was able to receive calls. When I flashed with the earlier release, it also flashed the baseband. Either way, I should not be prevented from using the up to date software! This is a Samsung issue but if you ever tried dealing with them over the phone, it's painful. They said they would send me a REFURB replacement - (believe me, I tried fighting for a brand new phone, since I paid for a brand new phone and this issue came straight out of the box - it's not even my fault to begin with!) it's been 3 weeks and I still don't see any phone replacement nor did I receive any mails from Samsung.
Btw, Galaxy S3 is the phone I have.
If you discover a permanent fix for this issue, please let me know. I've been searching but no luck.
Thanks!
UPDATE: it's been over a month and I still don't see any phone replacement nor did I receive any mails from Samsung. So I called Samsung today after a month and 2 weeks. They said my replacement have been cancelled. First they said it's approved and requested me to send in my receipt for the phone. I had done the the very moment I hung up the phone from when they told me my replacement was approved (that was over a month ago). They want me to sent it in again to Samsung so they can "test". This is just ridiculous and getting out of hand. Does ANYONE have a fix for this????
Other forums are saying this is a wide spread issue...
are u missing imei, or just the problem you descibe... try flashing the latest modem... maybe yell at it while it flashes...
Nope, just having the issue I described... IMEI is exist and is valid.
aftershocks said:
Nope, just having the issue I described... IMEI is exist and is valid.
Click to expand...
Click to collapse
There's some newer modems out you could try but it still sounds like hardware...
Not sent from your phone...
Sorry for the late entry here but I'm also having the issue. aftershocks, and anyone else having this issue, open battery stats - what does your "mobile network signal" bar look like? Mine is mostly tan except for when I make calls, which then it goes green. I also have an HTC One X (AT&T model) and the bar's mostly green on the HOX.
I've flashed back to the original modem (UCLEM) to see if that helps and I'll move forward from there if not. UCDLK3 was the modem I was originally on when I noticed the missed calls. Here's the thread with radios: http://forum.xda-developers.com/showthread.php?t=1831898.