Related
Some of the devs and I from the Android porting scene came across recently that *228 option 1 on Verizon does not work. After we intiate option 1, it goes 5 secs and then the error message lady pops up and says that it cant be completed at this time and to call customer care. From working with Verizon, I know tech support is useless for this issue so I am wondering if anybody here has came across this issue and if there is a fix for it. Currently we have tried this on Verizon stock rom and both NSFAN's 6.1 and 6.5 roms and its still a no go.
thanks for the new thread, hated to clutter the other one... I'll be calling to try and get a new AKEY shortly.
Ok, done this so far:
flashed imcoke .40
flashed vzw mr1 stock rom
no joy
Customer Support: 18009220204
Option 3. tech support
Option 3. ??
Option 4. winmo/blck/palm/etc
Option 2. all others
(acct pw) -> transferred
CSR:
"phone 'didn't update,' (something in the 'system')"
*228, opt 2
restart
test call, 'exernal operator' message
epst -> edit -> unlock code: 000000
nam -> edit mdn -> (my number)
home sid/nid #1 -> 02/65535 (probably by area?)
upd -> yes -> ok -> restart
test call, 'exernal operator' message
hold -> trouble ticket.
Has anyone tried #8899 (tech support)? See this thread. Apparently requesting a new AKEY shouldn't be a big deal...
Got voice working
Called the #8899 number. He walked me through changing my MSID back to my 10-digit number in EPST. He also did a 'security update' OTA by having me call #2539, which I think is a new AKEY. People may be able to avoid the pain by going into EPST and fixing their MDN, Home SID/NID #1, and MSID.
So voice is working now, but no data yet - and *228 opt 1 _still_ doesn't work. Anyone (really) know the difference between option 1 and option 2?
Edit:
Got data working now, too... ##778, edit, MIP Default Profile, change NAI to reflect your mobile number.
Also see this ppcgeeks thread.
Oh, but *228 opt 1 still doesn't work.
Edit #2:
Sorry for any confusion - for #2539 you need to have a tech support rep already on the phone. They'll call you on a landline and have you call #2539 from your cell. They'll ask you to tell them when you get put on hold. Then they do something behind the scenes. But you can't just call the number, no one will pick you up on the other side.
i had this problem last night they said the phone "malfunctioned" so i brought it in and they sent me a new one i just got it 5 minutes ago and now *228 1 works fine even after i unlocked it and put nfans 6.5 on it
pasqualeparillo said:
i had this problem last night they said the phone "malfunctioned" so i brought it in and they sent me a new one i just got it 5 minutes ago and now *228 1 works fine even after i unlocked it and put nfans 6.5 on it
Click to expand...
Click to collapse
Have you ran the Android port since you got your new phone and what custom rom and radio did you install?
pasqualeparillo said:
i had this problem last night they said the phone "malfunctioned" so i brought it in and they sent me a new one i just got it 5 minutes ago and now *228 1 works fine even after i unlocked it and put nfans 6.5 on it
Click to expand...
Click to collapse
Hopefully that's not the real fix... If it is, those of us without a warranty are screwed!
I should have a new phone tomorrow. I got the same story from Verizon last night. Im thinking it has something to do if you flash the rom while having a data connection allready setup? Maybe if the thing was in airplane mode first it might work better. I dont know, but im kind of thinking it screws their system up if its active. Ill try and flash the new one before activating the phone. Hopefully that will work.
For the record a tech from VZW finally called me today. Told him that it had been resolved but said I still couldn't *228 opt 1. He said 1 and 2 are almost the same so... maybe this isn't a big concern?
tallnerd1985 said:
Have you ran the Android port since you got your new phone and what custom rom and radio did you install?
Click to expand...
Click to collapse
yeah i have quite a few times with all the different versions of android and hero etc.... and now im still using nfans
ok thanks again mrkite but now calls are not working(data is though!) it acts as if my phone is unactivated. i guess im gonna try the #2539
that's weird...
sorry to hear that... I can't see why changing the MIP settings would affect your calls... Sorry about any confusion about #2539, I edited my post above. What message are you getting when you make calls?
I really recommend calling the #8899 number instead of customer service. They told me to look at settings in EPST that customer service didn't, and they weren't shy about sending a new AKEY through #2539.
it turns out that changing msid to my mobile number is what killed mt calls i called tech support and they gave me a different number to put in my msid and it works now i have calls and data(Finally)
thanks again mrkite38
This morning I picked up my EVO and the wonderful people at the Sprint store ported over my number from T-mobile. They told me to leave my EVO off until my old G1 with T-Mobile stopped working. I think they might have screwed something up, though, because my voicemail number is a different number than mine and I can't use the device self service. Here's the skinny so far:
- I've done the profile update in the settings, that doesn't fix it.
- My visual voicemail does not work
- The device self service tells me that it's not the correct number for my account.
Now, this morning I did hear them mention something about a temporary number, so I'm thinking it might be defaulting to that. I'm going to call Sprint in the morning to get it taken care of, but I figured I'd come to the real experts first. Any ideas?
same exact problem.
ported my g1 number to sprint and was told the same, fired up the evo once my g1 stopped working.
the number displayed in settings>about phone is still the temporary number and the same functions do not work for me.
tell me how it goes with sprint.
much appreciated.
Same here as well but your number is actually your ported number. I called sprint and the guy said that's normal it can take up to 2 full days before all that gets sorted out. Once your ported number shows in your about phone your voicemail will work.
P_Dub_S said:
Same here as well but your number is actually your ported number. I called sprint and the guy said that's normal it can take up to 2 full days before all that gets sorted out. Once your ported number shows in your about phone your voicemail will work.
Click to expand...
Click to collapse
Got this from another thread in the general forum: Worse case get your msl and enter ##MSL CODE# this will bring up a menu where you can make sure that your new phone number is correctly placed in both those fields. If not you can save the correct number and reboot. Sometimes the phone provisions properly sometimes it will not.
They should have programmed your original phone number and MSID into the phone even though it had not yet been ported over yet. Call Customer service and get your programming info or go back to the store to have them reprogram it. It's going to be stuck with the temp number until it's manually configured.
Hey everyone,
I went to the Sprint store this morning to get my issue taken care of, and it was as simple as reprogramming. He took care of it in 30 seconds. All fixed!
i went to the sprint store, but i don't think the employee really understood the problem. they ended up doing a hard reset and not being able to fix it.
ended up calling customer care and they took care of it easily.
I had this same issue but with my wife's phone 2 weeks ago. I ended up doing a hard reset (not the one in the user menu for her phone) via a service menu (they provided code).
So my guess is either re-program or this service menu hard reset future reference for anyone with similar problem
I successfuly updated my Stock, non-rooted Spring Epic Touch 4G last week to the newest build.
Battery life got better... signal got better. I lost the ability to use automated touch tone phone menu systems.
Does anyone else have this issue, if so please let me know if there's a fix or a way to revert back to a previous firmware update, etc.
Thanks in advance, I eagerly await your help. For now, I can't even get ahold of Sprint Customer service's phone system. I'm locked out!
-Tim
I to am having this issue. i am a phone tech at a local repair shop in south florida and 2 of my customers are having this issue (as well as my phone).
both of my customers phone are stock / non rooted
my phone is rooted using CALKUKINS E4GT Rom.
ive tried using a diffrent dialer but no help. anyone got a salution for this?
ON TOP OF THAT I HAVE 2 DEMO EPIC TOUCH'S AND THEY HAVE THE SAME ISSUE
Long time problem with dial tones in call
I have been searching for a month now to find a solution to this problem. I feel like I'm not explaining it right, but I'll try again.
For the last 2 years I have been dialing into a conference call line each morning. I dial the number then enter my access code (299542#). Upon recieving my new Samsung E4GT, the phone dialer does not register some or most of the digits entered, but it's not consistent. 95% of the time the 2 does not work, 25% of the time the 9 doesn't work...and so on. I have gone back to Gingerbread EL29, tried ICS FF18....FH13, I've used custom ROMs and those made no difference. There seems to be a few people who have had this problem as well, but there have not been any responses to help that I have seen.
paulsperli said:
I have been searching for a month now to find a solution to this problem. I feel like I'm not explaining it right, but I'll try again.
For the last 2 years I have been dialing into a conference call line each morning. I dial the number then enter my access code (299542#). Upon receiving my new Samsung E4GT, the phone dialer does not register some or most of the digits entered, but it's not consistent. 95% of the time the 2 does not work, 25% of the time the 9 doesn't work...and so on. I have gone back to Gingerbread EL29, tried ICS FF18....FH13, I've used custom ROMs and those made no difference. There seems to be a few people who have had this problem as well, but there have not been any responses to help that I have seen.
Click to expand...
Click to collapse
Your problem sounds like it might be different since you say you can't hear specific digits when you press the keypad, and this makes it so you can't log in.
I couldn't log in to my debit card today. I called my healthcare HSA debit card, and when I tried entering my 16 digit card number, their system kept stopping me after about 13-14 digits and would say it doesn't recognize the account number, then ask me to re-enter the 16 digit number. I tried about four times with the same results. I was using my speakerphone every time.
All I had to do was call back and NOT use the speakerphone. It worked first time and every time I tried! Another thing that works if I want to use my speakerphone is go into audio settings and un-check "Audible touch tones".
I think the loud speaker phone was causing their system to hear double presses sometimes.
Recently I have been having a problem with error 16. It happened of course when I activated on boost mobile. Then 3 days later it hit me 2 days in a row. And now a week later I am getting error 16 again. Did some research and couldn't find a fix. I know how to get it to go away I just need a way to make it stop repeating. Any info? Thanks
Sent from my PC36100 using XDA App
I'm on a boost prl. And a custome Rom.
Sent from my PC36100 using XDA App
Did you flash your phone yourself or did you pay to have someone do it for you? I know how to fix the error but lets figure out why it keeps happening also. The only time I've ever got that error is when I first activated the phone. Also, did you have to apply a fix each time it gave you the error or did it fix itself?
Sent from my PC36100 using xda premium
What prl are you using? Also would that work for me?
Sent from my BOOSTed EVO using xda premium
I just flashed to boost... Would like some input.
Sent from my BOOSTed EVO using xda premium
ERror 16 FIX is .......Just call 365
Sent from my PC36100 using Tapatalk
How do you fix i have recently been having the same issues. it comes and goes. ill make a call and sometimes get the error then i just hang up and try again then will usually fix itself
The only time this happens to me is when I turn on the donor phone, I don't even have to make a call with it, and then turn on the Evo.
This is the only time this ever happens to me.
In my experience error 16 happens when Boost initiates an OTA PRL update and when the flashed phone does not respond correctly (as a Boost phone would) it is flagged and error 16 results.
What you need to do to avoid it is to wait for an automatic PRL update after you activate the donor phone and only then flash the receptor phone.
Error 16 is a "Sprint" security Flag. It not related to Boost at all. What typically causes it is the radio still has some of the old MEID or ESN locations. When you flashed your new phone did you find the correct amount of locations in hex memory? I think 9 for MEID and 11 for ESN? Any less and the old info is still in hex memory and it will NOT authenticate. When you do your ##debug# I bet you'll see AN/AAA authentication = failed or so... check that out.
As far as clearing it, the only I know is to let the call go thru to Sprint. They will verify your Boost account and then reset your account. But if the phone is not fully flashed it will work but error out again later on.
hello i got this error and let teh call go through but instead of sending to a rep it just says please contact your customer support provider at the end -- it hap[pened before but it went to asprint rep who helped me.. any ideas?
I don't know if it's actually related, but I'm getting that error only when I change Network Name through Service Programming from Sprint to Boost Mobile. After i verified account by talking to rep that error never happened again to me. Bt I'm still on old baseband and a PRI for over a month without any issue (except for battery life). Will update PRI and baseband now to see what is gonna happen.
Does anyone know is it ok to update NV from this thread?
[ Radios ][ 9-5 ] All EVO Radio, WiMAX, PRI, NV & HBoot versions
just stay on the line and talk to the rep. they know exactly whats wrong and will fix no ??? asked. just remember to tell them the donor phone when asked what kind of phone
I've had this problem also anytime I turn on the donor phone, it's a super easy fix and you don't have to talk to anyone. What you need to do is find a temporary MEID, there's a topic at http://www.howardforums.com/showthr...ow-ESN-s-for-activations-here-(NO-QUESTIONS!) with tons of them (many are in use but look around) than (while leaving your donor phone off) go into your My Account on the boost website and change your MEID to the temporary MEID, wait a few minutes and change the MEID back to your correct MEID. This will fix the error number 16 problem. Keep in mind as well than anytime I've done this Ive left my Evo turned on, didn't have to restart or anything.
A second solution as the post above, you could wait on the line and tell them you're just trying to make a call, give them the description of your donor phone and they will call you back on another number and have you make a test call etc (make sure you do it from your Evo). They may or may not need to call you back though, this is just what I've always been told. The only solution I ever needed with this problem is the first one.
kc3 said:
I've had this problem also anytime I turn on the donor phone, it's a super easy fix and you don't have to talk to anyone. What you need to do is find a temporary MEID, there's a topic at http://www.howardforums.com/showthr...ow-ESN-s-for-activations-here-(NO-QUESTIONS!) with tons of them (many are in use but look around) than (while leaving your donor phone off) go into your My Account on the boost website and change your MEID to the temporary MEID, wait a few minutes and change the MEID back to your correct MEID. This will fix the error number 16 problem. Keep in mind as well than anytime I've done this Ive left my Evo turned on, didn't have to restart or anything.
A second solution as the post above, you could wait on the line and tell them you're just trying to make a call, give them the description of your donor phone and they will call you back on another number and have you make a test call etc (make sure you do it from your Evo). They may or may not need to call you back though, this is just what I've always been told. The only solution I ever needed with this problem is the first one.
Click to expand...
Click to collapse
Cool thanks i will try your first method next time!!
Offering to sell a service is against the rules. Posting a paid service will warrent a ban
Error 16 Fix!! Only if you have a 2nd working BM cellphone.
I believe that BM Reps are now aware of the main cause of Error 16; Consequently, they may some times be hard to convince....Anyways here is a work around:
You need a 2nd working BM cellphone ( let's call it replacement cellphone), that is not active on any other account:
PS: Your donor phone is not what I am talking about ( matter of fact you should take its battery out and hide it somewhere in your basement )
By Flashed phone I mean your (EVO, EPIC, NEXUS....)
1- Turn OFF Both cellphones (replacement and flashed).
2- Log into your BM account, got to upgrade device, and activate the replacement cellphone
3- Turn ON the replacement cellphone (ONLY) and let it sync with the network... Test it by calling 611, if working call someone you know to double check...
4- Turn OFF replacement cellphone
4- Log into your BM account, got to upgrade device, and activate the Flashed cellphone
3- Turn ON the Flashed cellphone (ONLY) and let it sync with the network... Test it by calling 611, if working, call someone you know to double check...
Hit thanks if I helped you...
It's not that complicated. All you need to do when using this method to fix error 16 is:
1) log into boost acct, go to update handset and enter extra meid, click OK twice until you get to the screen with msl, msid, and phone number at the bottom of screen.
2) now go to main acct info screen and then click on update handset again, enter donor meid, click OK twice and you are set. Just make sure donor is off first and really you do not even have to turn off the flashed phone. I have done this probably 100 times this way with no problems.
Kc3 explained this a few posts above us already, but you don't have to wait more than a second or two before changing back.
Sent from my PC36100 using xda premium
Klown80 said:
It's not that complicated. All you need to do when using this method to fix error 16 is:
1) log into boost acct, go to update handset and enter extra meid, click OK twice until you get to the screen with msl, msid, and phone number at the bottom of screen.
2) now go to main acct info screen and then click on update handset again, enter donor meid, click OK twice and you are set. Just make sure donor is off first and really you do not even have to turn off the flashed phone. I have done this probably 100 times this way with no problems.
Kc3 explained this a few posts above us already, but you don't have to wait more than a second or two before changing back.
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
The problem with this for me is that I'm grandfathered to the old Pay-as you-go. and if I change my handset I loose that service.
Any other suggestions?
thecensor said:
The problem with this for me is that I'm grandfathered to the old Pay-as you-go. and if I change my handset I loose that service.
Any other suggestions?
Click to expand...
Click to collapse
Stay on the phone when you get the error 16, at the end an operator should get on the line, just make sure you tell them about the donor phone if they ask any questions, dont tell them about the flashed phone at all. If they ask, tell them you just went to make a call and started getting this error.
Hope this helps!
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