Related
This seems to happen a fair bit. I have no idea if it's the phone or Orange's terrible coverage (well, not really coverage since I've got all the bars, but the network's overloaded by too many geeks like us) in Soho, but when people call me, there's a good chance they won't be able to hear me talk. If I call them back, everything works as it should.
This happened with stock Orange ROM, stock Orange ROM + OTA update and now with generic ROM.
It must be either a network or software issue since it works fine sometimes and always if I call them. It's certainly doesn't happen every time someone calls me.
Just wondering if anyone else had seen the same thing?
Not had any problems like that with mine on the Orange network, have occasional problems when talking to people on 3 but that is the 3 network causing those problems.
Before you flashed the generic ROM you should have sent the phone back and gotten a new one. Don't you think a major issue like a phone not being able to properly make PHONE CALLS might have been a huge talking point up to now? Surely the fact no one else has raised this means it was probably a hardware fault with your particular phone.
Get it replaced and hope they don't notice the flashing you've done.
Your point is of course right, but it hasn't happened ever outside of Soho and I definitely think it's software/network for that and the reasons I initially wrote.
Honestly, Orange in and around Soho has gotten to be almost unusable recently. I have to drop to GSM only a lot to be able to make/receive calls. The same is true for my friends on O2 and it's been that way ever since the smartphones started becoming more ubiquitous. I've complained to Orange and they say they're trying to improve it but they're a bit lax on the details.
It's a matter of time until it's possible to reflash the Orange ROM so if it does get worse and/or turn out to be a hardware fault, then as you say, I'll either send it back as is, or reflash to stock ROM first if poss.
This might sound daft, but I had the same thing, then I realised that it was the way I was holding the phone, I had a finger over the mic at the bottom... Embarrassing cure for me!
Sent from my HTC Desire using the XDA mobile application powered by Tapatalk
:-D Sounds crazy, but I'll check it out the next time I receive a call :-D
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
As many, many other users of the galaxy nexus have reported, I am having some miserable signal problems. Obviously, CDMA nexus here.
I wish the issue was only that the signal on my phone is bad, but unfortunately it extends beyond that: my entire signal is lost at times. Usually it's intermittent and will happen 4 or 5 times a day for only 30 seconds at most at a time, but sometime (Usually late at night), it will lose its signal for even an hour or two, and I'll watch the battery plummet from as high as 54% to 0 as it searches for a signal the whole time.
I realize this is nothing new for some, but I almost feel like the problem went away for the whole world except for me, due to the low volume of threads related to the issue at all on the boards here. At least, recent ones.
What are my options? I don't really like the idea of trading in my nexus for a refurbished phone. Is 4.03 supposed to solve this problem? I had also read that rooting and flashing radios doesn't make much of a difference. To those of you with the CDMA nexus, what have you done to alleviate this problem? Or are you waiting patiently for an update?
Thank you in advance.
If bought new then return as faulty. Easiest solution.
sent from my Nexus Prime using XDA app
Daramue said:
I realize this is nothing new for some, but I almost feel like the problem went away for the whole world except for me, due to the low volume of threads related to the issue at all on the boards here. At least, recent ones.
Click to expand...
Click to collapse
The problem didn't go away. Most people had to make the decision to either live with it or trade it in on a RAZR or Rezound.
Daramue said:
What are my options?
Click to expand...
Click to collapse
You could:
1. Trade it in for another GNex, on the "hopes" that yours is defective.
2. Trade it in for something else.
3. Live with it & wait it out on the hopes that someday Verizon will ship updated radios that will help. Current rumors say that could still be a couple of months away...
I am on the option 3 plan.
The leaked 4.0.3 radios have had limited & mixed results. For those who they do help, they don't seem to do a whole lot. There are a couple of people who had really good luck. Pretty much the same story for those of us who got Hardware version 10 phones - Haven't noticed any appreciable difference between it and the 9 I got on opening day.
Good luck!
strongergravity, thank you, that was extremely helpful; I was curious to how my fellow Nexus bretheren were dealing with the issue.
If a potential update can fix the radio, then I too will stick with number 3 as you have. Call me a masochist, but this thing is just too nice to part with.
Thank you very much for the detailed response.
Daramue said:
strongergravity, thank you, that was extremely helpful; I was curious to how my fellow Nexus bretheren were dealing with the issue.
If a potential update can fix the radio, then I too will stick with number 3 as you have. Call me a masochist, but this thing is just too nice to part with.
Thank you very much for the detailed response.
Click to expand...
Click to collapse
I just saw your thread right after I created the exact same one today! I was just wondering what you ended up doing. No one has answered definitively as to whether or not this is happening on all phones. If an exchange will fix it, I would gladly go tomorrow. I know most phones are having trouble with the 3g/4g handoff but that is not the same issue we are having. What do you think!?
Mike
Same problems I've experienced. I'm on my second gnex, same issues.
Also I pulled speed tests next to other Verizon 4g phones (razor,rezound,TB) they all had significantly higher speeds than mine . I did multiple tests around our site, they had at least twice the speed as mine.
The razr pulled three times my speed most the time. 30+mb/s vs 10
The thunderbolt was around twice as fast downloads but uploads were even.
And the rezound was double on both uploads and downloads
I used the speed test app and speakeasy online.
Sent from my Galaxy Nexus using Tapatalk
Another comparison I did was turning on airplane mode on and off on all phones simultaneously. And switching 3g only on/off. To see which phones would latch on to 4g first.
Again the gnex was the slowest.
I really wish we received an update to fix this I love this phone!
Sent from my Galaxy Nexus using Tapatalk
I posted this earlier on another thread hoping it will get more views here.
So, I'm having the same exact problems but i did a log cat to see what might be culprit.
I have narrowed it down to this:
02-08 11:21:51.912 E/IMSFW (415): IIL: Disconnected from '7467' socket
still have no idea what can cause it yet.
also if you switch to 3g it seems it doesn't happen so maybe its a sim problem on verizons lte network end?
11:22:40.029 E/IMSFW (415): ImsSMSInterface: Registration failed, go for retrying if isim nounce present
that's what i found so if anyone can clarify and maybe see if it is really on Verizons end as this is the 4th phone that has had this problem
I will be going to verizon tomorrow to "try" and get a new 4g sim card and see if that helps somewhat.
that1techguy said:
I posted this earlier on another thread hoping it will get more views here.
So, I'm having the same exact problems but i did a log cat to see what might be culprit.
I have narrowed it down to this:
02-08 11:21:51.912 E/IMSFW (415): IIL: Disconnected from '7467' socket
still have no idea what can cause it yet.
also if you switch to 3g it seems it doesn't happen so maybe its a sim problem on verizons lte network end?
11:22:40.029 E/IMSFW (415): ImsSMSInterface: Registration failed, go for retrying if isim nounce present
that's what i found so if anyone can clarify and maybe see if it is really on Verizons end as this is the 4th phone that has had this problem
I will be going to verizon tomorrow to "try" and get a new 4g sim card and see if that helps somewhat.
Click to expand...
Click to collapse
I just went to the store and swapped out my 4g sim card... I dropped two calls on the way home from the store so I'm not sure it helped at all. Hopefully it didn't make it worse though!
I also checked my speeds and service against some other phones in the store and the Droid Razr destroyed my nexus and some other stock nexus that were there usually 12mpbs vs my 8 and 1mbps upload vs their 3.
Well I got my issues fixed today I was on tech support for an hour and he suggested to go to a store and get the sim card replaced. And that solved all my issues
Another problem I had was when using the headset for calling the person on the other line would here themselves. This has also gone away, I am so relieved I love this phone and did not want to abandone it.
Well, I did a bit of a test.
I kept my phone on 3g the whole day: Signal did not drop even for a single MOMENT in the entire day. Sure, there are times where it was bad, but my connection never entirely dropped. This leads me to believe that the problem lies with transitioning between 3g and 4g, or perhaps is just entirely related to 4g.
With the LTE network, I will have anywhere between 3% - 50% time with "no signal." It's extremely annoying and I'll always watch as my battery tanks extremely fast.
Maybe it's worth replacing the SIM card or at least, pulling it and putting it back in. Posting this here for others that are troubleshooting this same problem. I'll report back.
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.
My wife and I each bought our Nexus phones a couple of months ago from the Play store and signed up for Straight Talk. Overall everything has been great (except of course my wife cracking her screen, but that is another issue). A strange signal issue has happened to each of us a few times. Most of the time everything is fine. However we've both had the situation where the phone completely loses signal and it won't come back on its own. For me, it seems to happen when I am in an area with very poor to no signal. It's like the phone stops trying to get a signal completely. The signal meter shows the empty triangle and the lock screen says "Emergency Calls Only". Even when I get back to a strong signal area it doesn't pick anything up. My wife had no signal for a couple of days since she was on Wifi and didn't notice the lack of calls/texts. Rebooting the phone fixes it and switching the phone to airplane mode and back also fixes it. I am almost always in area with decent to good signal coverage so this doesn't happen too often.
Does anyone else experience this? I'm wondering if this is a Nexus or a Straight Talk issue?
EDIT: I didn't mention before, but I am running both phones stock and never been rooted. So this is definitely not a custom rom issue.
I have had the exact same issue with my nexus, same solutions as soon as I leave the poor signal areas(airplane cycle, reboot) . I am, however with at&t (just using my old s2's sim) and my wife has experienced the same issues with her s3. Leads me to believe that it is a signal issue. My two cents for the same experience, carrier or not.
I777 gets it done, gnex just for fun
I've been getting this issue for the past few days. I'm on T-Mobile. This never happened before and I don't think it's a rom/kernel issue as I've tried a few roms and was experiencing the same issue on all of them.
ragnarok12 said:
I've been getting this issue for the past few days. I'm on T-Mobile. This never happened before and I don't think it's a rom/kernel issue as I've tried a few roms and was experiencing the same issue on all of them.
Click to expand...
Click to collapse
Actually, I probably should have mentioned it, but neither of the phones are rooted. Just stock all around.
I got a similar issue from not flashing JB radios along with CM10, but........
Sent from my Galaxy Nexus using xda app-developers app
Both my nexus, and the wife's s3 are also unrooted, as well. Jb simply hasn't given me a reason to root, I'm not displeased with anything. My issue with signal stopped yesterday, and I confirmed it wasn't a phone issue for myself by popping my sim back in my rooted s2. Still had zero service. Hopefully your issues will also resolve themselves, if they haven't already
Sent from my broken screen swagga machine
My little brother had this same problem on all roms, though he had a cdma version, i don't believe this is a mere coincidence, we were able to replace his since it was within the thirty days. But i think this is a "needle in a haystack" hardware issue, and you're just the unlucky ones. Though I could be wrong, many people have had this issue before as I've searched on Google to try to fix my brother's phone.
Sent from my Galaxy Nexus using Tapatalk 2
I have same problem with both Galaxy Nexus and my previous phone, the Nexus S, only thing I have to do is reboot, after reboot, problem is gone, but it could come back in time, but I recently update radio, and haven't seen this problem quite while.
One other problem is, sometimes when i enable the airplane mode, was unable to disable it unless I reboot it...