My new VZW Galaxy Nexus has been occasionally entering a mode where it will not receive any phone calls.
The problem is corrected once I initiate an outgoing phone call.
The outgoing call connects immediately, is clear, and has no issues at all. If I then hang up and try calling the device it will ring immediately and work perfectly.
The problem tends to occur a couple of times per day. I've not found a direct trigger for it.
When the problem occurs, IP network connectivity still works perfectly. I can ping from the device, browse FTP sites, and run a speed test. Using the speedtest.net app (while the phone is unable to receive calls), I'm seeing 26mpbs down and 18mbps up (just like I would if the phone was working).
Powering down and then powering up the device does not correct the issue. Adding a battery pull while the device is powered down doesn't help. Once booted, the device will still not receive calls until you make an outgoing call from the device.
Phone is bone stock. Is not and has never been rooted or modified. Purchased on launch day. Indicated signal strength is great, and service in my area is very good on both 3G and 4G.
There's no indication whatsoever of an issue other than friends later notifying me that I was unreachable.
I believe text messaging may be halted as well, but have not verified this.
Verizon has no idea, indicates everything is provisioned correctly. Device was activated by a VZW store.
Any suggestions or reports of similar issues would be greatly appreciated. I can still take it back to Verizon and replace it with a new item (and I probably will).
I've seen a story of a guy who upgraded to the gnex but left his old phone turned on and used it as a bedside clock. He was saying he wouldn't receive any calls. He powered off his old phone and was then able to receive calls. Seems like a long shot but maybe your having the same problem.
Sent from my Galaxy Nexus using XDA App
Maybe your phone can automatically detect when someone you don't like is calling
Has anyone seen John Connor?
xxprodigyxx11 said:
I've seen a story of a guy who upgraded to the gnex but left his old phone turned on and used it as a bedside clock. He was saying he wouldn't receive any calls. He powered off his old phone and was then able to receive calls. Seems like a long shot but maybe your having the same problem.
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
Thought this was the case as well after a Verizon tech suggested it. In a rare event, I actually picked this phone up at a VZW store and they activated it for me (while my previous phone was remained on).
Since then I've turned off the old phone (and left it off) and rebooted the Nexus immediately thereafter. The problem still occurs at roughly the same interval.
I actually do a lot of switching between phones for development work, but have never seen this before. Then again I always *228 it myself where the "old" phone has to be turned off.
I just experienced this problem today for the first time. I didn't realize my phone was unable to receive calls until my Gmail account notified me that I had a bunch of voicemails waiting. Then as soon as I made an outgoing call, I had about 12 text messages deliver to me. The weird part is that I was still receiving Facebook and Twitter notifications during this time. I haven't been able to replicate the problem again, but it has happened to me as well. Very weird.
My only hunch is that earlier in the day I was out in the middle of nowhere where my signal was dropping in & out and perhaps when I came back to the city, the network didn't connect properly? I don't know if that's even possible? Also, could my home wifi network be interfering somehow?
I have tested it since I made an outgoing call and now people are able to text me and call me, so it all seems back to normal. It's a very odd problem indeed.
I had the same issue this morning and its funny because I just turned my old phone on last night and that could be the problem
Sent from my Galaxy Nexus using xda premium
I've had a Galaxy Nexus on Verizon for a couple of weeks now and noriced this problem early on, but only in the evenings and night. I stumbled upon this thread looking for a solution. Thanks tliebeck for mentioning it.
I was using my old OG Droid as a bedside clock. In the evenings, after getting home from work, I place the Galxy Nexus on the same bedside table as my old cell phone.
Then I saw xxprodigyxx11's response (thanks, btw!) and tried turning off the old phone. Sure enough, my Galaxy Nexus hasn't missed a call since. It seems to be proximity related, since I was receiving calls just fine on my gnex at work even with my old phone on at home; I'll have to do more testing on that to see just how far apart they need to be.
Sorry that did not work for you, tliebeck.
There is very little information on this situation out there, so I am grateful for the help here. Hopefully someone can come up with a more permanent and universal solution.
Good to know I'm not alone, thanks all for posting!
Still a major issue here.
Took the device to a VZW store and had them replace it with a new one. Problem still happens in exactly the same fashion. They did reuse my SIM card.
Phone seems to do it about every day lately. I've had two calls to VZW level 2 tech support. First guy tried changing a bunch of account settings around, to no avail. Second guy thinks it's a bad SIM card, I'll be heading to a VZW to get a new one of those today, but am doubtful that it will be effective.
The fact that this works across battery pulls and on two different phones just plain screams network or firmware problem.
I had the same issue. First swapped out my 4g sim card...worked OK in store, after being home for 45 minutes it did the same thing again...wouldn't accept calls until an outgoing call was placed. Drove back to Verizon and was able to reproduce the issue in the store. They replaced it with a brand new GNex and haven't had the issue since (a couple weeks). Good luck!!
Sent from my Galaxy Nexus using XDA App
Had the SIM card replaced a couple days ago, today it's doing it again.
Based on the responses here, I think this issue may be quite widespread and many people aren't realizing it because it's intermittent (every one/two/three days) and is cured if you place an outgoing call (with no indication there was ever a problem).
For me at least, a replacement new phone, new SIM card, and various account updates have had no effect.
tliebeck said:
Had the SIM card replaced a couple days ago, today it's doing it again.
Based on the responses here, I think this issue may be quite widespread and many people aren't realizing it because it's intermittent (every one/two/three days) and is cured if you place an outgoing call (with no indication there was ever a problem).
For me at least, a replacement new phone, new SIM card, and various account updates have had no effect.
Click to expand...
Click to collapse
Not to belittle your problem, but 3-4 people having an issue =/= "quite widespread."
When you say its not accepting a call, do you mean all calls go straight to VM, don't ring at all, or the call isn't going through(I.e. other person sees call failed)?
Sent from my Galaxy Nexus.
unremarked said:
Not to belittle your problem, but 3-4 people having an issue =/= "quite widespread."
When you say its not accepting a call, do you mean all calls go straight to VM, don't ring at all, or the call isn't going through(I.e. other person sees call failed)?
Sent from my Galaxy Nexus.
Click to expand...
Click to collapse
The reason I think it's not an isolated issue is because very few people are going to notice and correctly identify the issue. It's a new device (small userbase), and the more frequently you're placing calls the less likely you are to notice it. It's intermittent with what appears to be an interval of at least a few hours up to a day or more.
The calling party will either go straight to voicemail or experience between two and four rings before being routed to voicemail.
I suppose I should chime in and saying I'm having this issue also. I've found that toggling airplane mode on and then off restores ability for me to receive calls. This is a particularly bad problem for me as my wife is pregnant. She was PISSED the other day because she thought I was ignoring the 6 back-to-back calls she made. I first thought it was a google voice issue but it wasn't. I verified by calling my actual cell number once I caught it in this "mode" again today. Until we figure this out, I have the luxury of being able to add my work cell to the list of phones that GV rings so that I don't miss another call from her. That's actually how I discovered the GNex was in that "mode" again.
The comment about the previous phone is an interesting one. I also use my old phone as a nightstand deskclock and alarm clock. I will try throwing that one in airplane mode for awhile and see if that fixes anything. I don't believe it to be a proximity issue though because my GNex has entered this mode while I was at work and the old phone was at home. It's a half hour drive and there's a mountain in between.
-Josh
I also think that more people could be having this issue without knowing at all which would lead to less complaining. The caller just thinks the receiver is just too busy to answer and leaves a message. Unless you don't get a really important call that a wife/friend complains heavily about, one would never know.
I had purchased a new GNEX a few days ago and I had a really strange problem where the phone would work (receive / make calls) for about 10 minutes, then the radio would just stop working.
Wait a few minutes, and it would come back to life.
Since it was new, I took it back to the Verizon store and they tried to claim it was due to some software issue that was being fixed in the next two weeks, but I disagreed.
Ultimately got a new GNEX and haven't had the problem since. Seems like maybe there is a bad batch out there with faulty radios?
I don't have anything to add except to say that my father's HTC Raider/Vivid did the same thing last night, and it was spooky. I phoned him a few times, and it went straight to VM every time. As soon as he placed a call, all the VM notifications came flooding in, and his phone could receive calls again.
My guess is that it is a quirk with the way 4g is authenticated. Since it's a new type of connection (requires sim card instead of esn) there's some kind of glitch where the old esn isn't fully un-registered with the network. Does your dad also use an old 3g phone as a deskclock or anything?
Me Too! Galaxy nexus stops receiving calls until I place an outgoing cal
Hi,
This is my first post here. Just wondering if this has been resolved? My Gnexus was on all day Saturday, Sunday and most of today without receiving a call or a text. When I called out it started working, but none of the incomming calls in my voicemail showed up in my log. No text messages were received either. Thanks for starting the thread.
pcnerdman said:
Hi,
This is my first post here. Just wondering if this has been resolved? My Gnexus was on all day Saturday, Sunday and most of today without receiving a call or a text. When I called out it started working, but none of the incomming calls in my voicemail showed up in my log. No text messages were received either. Thanks for starting the thread.
Click to expand...
Click to collapse
Do u have a phone that used to be on that line turned on?
Sent from my Galaxy Nexus using XDA App
Update: have not had this issue come up again since i put my old phone in airplane mode. I always wait for both of my gv phones to ring to ensure this problem is resolved.
Sent from my GalIaxy Nexus using XDA App
This issue is not exclusive to the Verizon Nexus. I have the GSM version through TMobile and quite often (several times a week, maybe more) my phone just stops receiving text messages. I can't even make outgoing calls.
So now, periodically throughout the day I call Google Voice to see if it works. If I get my own voicemail I know that I'm still receiving text messages. If it doesn't connect, then I have to turn on airplane mode, then turn it off again, and the network comes back.
During the outage I still show full bars over 3G.
It's so freaking annoying. I thought the latest update to Android would fix it, but it didn't. There's a Google thread on this too:
http://www.google.com/support/forum/p/Google+Mobile/thread?tid=34ad876196cb21c4&hl=en&start=40
Started developing 2 new issues with the phone.
1. Echoing on phone calls, doesn’t matter if I call a mobile or land line, I can hear my voice echoing back to me, doesn’t matter if I’m using wired headset, blue tooth, or just the phone, it’s happens to about 75% of calls made.
2. Issue, when I get a text message, it shows “Media content sent, click to retrieve” this only happens with texts, not Multi Media Messaging. I’ve called AT&T 3 times; they “re-provisioned my text” all 3 times, it works for about a day or so, then I start getting that error.
Is anyone else having this issue?
The echo annoyance is something that companies have been trying to eliminate from communication devices since the 1950s... It just happens... There are many factors that you can consider to narrow down what might be causing it... Does it ever occur when you're outside of your home or away from any electronic devices? (Especially WiFi)
Next time your phone is echoing, plug it into the charger to see if it might be a battery retention of charge issue.
Regarding the media content sent, click to retrieve message... once you click it what happens? If nothing happens it means that your phone's plan does not support whatever media content that somebody was trying to send you... Sometimes this happens to me if somebody sends me an MMS message with nothing but text in the message... No picture, video or audio... I don't know what the cause of this is but it sounds like a bug, hope they fix it soon..
Anyways, let me know if you find any other possible explanations for the media content text message... I'll do the same...
Batt322 said:
Started developing 2 new issues with the phone.
1. Echoing on phone calls, doesn’t matter if I call a mobile or land line, I can hear my voice echoing back to me, doesn’t matter if I’m using wired headset, blue tooth, or just the phone, it’s happens to about 75% of calls made.
2. Issue, when I get a text message, it shows “Media content sent, click to retrieve” this only happens with texts, not Multi Media Messaging. I’ve called AT&T 3 times; they “re-provisioned my text” all 3 times, it works for about a day or so, then I start getting that error.
Is anyone else having this issue?
Click to expand...
Click to collapse
There is a high probability that these are network issues, not device issues.
Resaolution
efektos said:
There is a high probability that these are network issues, not device issues.
Click to expand...
Click to collapse
After about 1 hour+ on the phone with AT&T, I guess they gave up, they sent me 20+ text messages, and about 50% of the time it said “get media content” (for non-media messaging), they never got to the echoing, so they are sending me a new phone. :cyclops:
So new phone comes today, (re-conditioned). It has scratches all over the back, who ever the previous owner was they must have dropped it on the corner a noticeable chuck out of the plastic , call AT&T to complain about it, they are going to send (over night) a replacement.
Batt322 said:
Started developing 2 new issues with the phone.
1. Echoing on phone calls, doesn’t matter if I call a mobile or land line, I can hear my voice echoing back to me, doesn’t matter if I’m using wired headset, blue tooth, or just the phone, it’s happens to about 75% of calls made.
2. Issue, when I get a text message, it shows “Media content sent, click to retrieve” this only happens with texts, not Multi Media Messaging. I’ve called AT&T 3 times; they “re-provisioned my text” all 3 times, it works for about a day or so, then I start getting that error.
Is anyone else having this issue?
Click to expand...
Click to collapse
I had the same echoing problem with my first L900.
It was replaced with a new one 2 weeks ago now my replacement has the same problem.
Not too happy about it happening a second time as I will be left without a phone for 3 days once again.
---------- Post added at 02:35 PM ---------- Previous post was at 02:27 PM ----------
efektos said:
There is a high probability that these are network issues, not device issues.
Click to expand...
Click to collapse
In my case it was nothing to do with the network. And I think the new replacement is faulty as well. Really getting frustrated with my Nokia L900.
I have this problem too,echo feedback...
Sent from my Lumia 900 using Board Express
I have a Samsung Galaxy Note 4 Edge from Verizon. Everything worked fine on the phone until one day a problem just occurred and even with the help of Verizon’s tech support, I haven’t been able to resolve it. The problem is whenever I receive an incoming call, the caller cannot hear a tone when I press anyone of my dial pad keys. This makes it impossible to proceed through an automated system that requires you to press certain numbers in order to advance. NOTE … I only experience this problem on incoming calls! If I initiate the phone call, the party I’ve called can hear a tone whenever I press a key on my dial pad. That means I can place a call to an automatic system and proceed through it by pressing the keys necessary to reach my desired destination.
Verizon’s tech support suggested that I reset my phone to its new, out of the box condition. I did that and it didn’t fix the problem. I tried starting the phone in safe mode, thus taking any 3rd party apps out of the equation and that didn’t help. I tried changing the DTMF setting from normal to long and that made no difference. Finally Verizon sent me out a new phone and that didn’t fix the problem. And last but not least, Verizon gave me a new sim card, which still didn’t fix the problem. Now I have all new hardware and the same old problem! Verizon keeps bumping me up the tech assist ladder, but so far no one has come up with a solution.
If anyone has any ideas, thoughts or suggestions that would help to solve this mystery, I would be eternally grateful!
Thanks in advance!
Good luck! I'm on my 4th replacement and still have all of the same problems. Now they are sending the phone to Samsung to tear apart and checking my cell area for related problems. Both mine and my wife's note 4s are plagued by the same problems. I guess the next step is trying a different manufacturer.
Sent from my SM-N910V using Tapatalk
I had his same issue on Verizons iphone 6 and iphone 6 plus, could never get through automated menus.
Now that I think of it, I have had this issues on my G4 and G3 and pretty much any device on Verizon.
Hello,
My brother is having a very weird problem with his HTC One M8. He is using a Verizon phone on a T-Mobile network, and I believe he has Android Marshmallow. Things have worked fine for some time, but for the past two weeks his cell signal usually flickers on and off every 1-3 seconds. Occasionally it will work as normal, usually after he makes a call, but generally speaking he cannot receive text messages or phone calls/voice mail until it stabilizes, which causes him to have to wait sometimes 5 or more hours before getting his messages. Location seems to have no effect on the quality of his signal. He's taken it in to T-Mobile and they gave him a new SIM card, but that didn't help. I helped him use HTC Sync Manager's software repair tool to see if that would fix anything, it didn't. We are trying to avoid a factory reset, but will probably be doing that soon. Has anyone heard of this problem or have any ideas on how to fix it? Buying a new phone is last resort.
Thanks!
Hi there.
My M9 has a strange problem where it rejects phone calls on a seemingly random basis. When I try to call the phone from a landline or another mobile it shows no sign that there's an incoming call. The phone making the call hears a ringing tone twice, and then only a beeping (like an engaged tone but with one beep longer than the other). The odd part is that it doesn't always happen. I get the occasional cold call come through, and sometimes people phoning me can get through, but at other times they can't. It seems consistent that when I'm at home in the evenings it rejects all calls. I'm sitting at home now and if I try to phone from a landline or mobile it won't get through yet the phone is showing full signal and can make calls. I've tried with WiFi and mobile data on and off and rebooting the phone to no avail. SMS messages come through fine all the time.
I've contacted my network (Virgin mobile UK) and they've issued a replacement SIM - same problem. I've tried the SIM in a Nokia and it seems to work perfectly, so I've come to the conclusion it must be the M9 causing this.
To start with I was on the stock HTC Android, and I've not got any auto-reject settings turned on (that I can see). To try and solve this I've done a factory reset via the phone, and when that didn't work I tried doing a complete wipe and installing TWRP recovery and ViperOneM9. It still rejects calls!
Anyone got any ideas? I've tried searching for this but all the posts seem to be about setting up auto rejects, or not receiving any calls at all. Are there any logs I could look at to see if the M9 is getting the call but then rejecting it without my knowledge? Any hints here would be appreciated!
TIA
Flash the stock firmware via SD card method. It seems like a cliché but it really solves most problems both software and hardware. If it doesn't then you know you have bigger issues.
I'd place a bet that you have a rogue app abusing it's call permissions but it'd take ages to find it.
shivadow said:
Flash the stock firmware via SD card method. It seems like a cliché but it really solves most problems both software and hardware. If it doesn't then you know you have bigger issues.
I'd place a bet that you have a rogue app abusing it's call permissions but it'd take ages to find it.
Click to expand...
Click to collapse
Thank you. I started doing that but had some problems, so in the end I bought a new phone, and lo and behold I had the same problem as I had with the HTC, and that was when the phone was fresh out of the box before I'd installed any apps.
After a LOT of playing around with settings, I've now figured out that if I have 4G turned on when I'm at home then all calls are rejected, even if WiFi is also turned on. Forcing the phone to use 3G when I'm at home means I get calls, and if I have 4G turned on when I'm at work I get calls OK. I guess the test with the Nokia worked OK as it wasn't a 4G phone.
After repeated calls to Virgin they've finally admitted that there's a fault on the phone mast close to my house, and by the sounds of it they have a lot of open tickets for that mast. As they use EE's network they say they can't do anything until EE pull their finger out, but as I've had the issue for months I bet it won't be anytime soon. For now I'll have to switch to 4G manually whenever I'm away from home and try to remember to put it back to 3G when I get back. Not ideal but at least I know what the problem is now!
Thanks for your suggestion, even though it wouldn't have worked in this case.