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
So I had my Evo 4g rooted with Unrevoked3, had some nice ROMs and all that fun bling stuff for a few months without a hitch. Yesterday I had my number changed, didn't bother returning to stock or anything. I couldn't dial out or send texts (but could send texts) but had access to the mobile network. So I unrooted, returned to stock (no OTA cuz I intend to root it again), ran through Sprint's activation again and still exact same issue.
I get this message when I attempt dialing out and also when I dial my new number from a diff line: "We could not complete your call. Please try again." Google voice works fine though - but again, so does the mobile network.
Sprint customer service is no help - and right now the Sprint store is closed, so here I be. Any help would be appreciated.
it sounds like the number is not configured correctly on sprint's end. taking it into the store may be the only way to get it fixed. or go onto the sprint website n try
{ParanoiA} said:
it sounds like the number is not configured correctly on sprint's end. taking it into the store may be the only way to get it fixed. or go onto the sprint website n try
Click to expand...
Click to collapse
This, or call *2.
Problem solved! Turns out it was my Google Voice number integrated with my old Sprint number that was creating conflicts with my phone being able to use the new Sprint number. Talk about a whack attack. I spoke with five diff techs trying to figure this one out.
Man, I did all that unrooting and resetting for nothin! Except, of course, for other Google Voice subscribers to learn from my experience...
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.
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
So I wanted to see if somebody would provide me with the settings they have for the SMSC. Starting this morning I was no longer able to send text messages and I know its not an issue with a ROM or anything because I Odin'd back to factory and I am still having the issue. This isn't the first time I have had an issue with a GNex not being able to text and I had to take my old one back to the store and get a replacement because they were unable to fix. I think I stumbled upon my problem/solution and was hoping that somebody from this great community would help me out. Could somebody do the below and paste what settings they have or give a screenshot. THANKS in advanced.
Open Dialer
Type the following sequence *#*#4636#*#*
Open Phone Information
Well for starters, My first Gnex had this issue a few days after receiving it, approximately one month ago. This morning I noticed I was once again unable to send or receive text messages. Up till now, I have been stock with root. I have been scouring pages and forums trying to find more info on this problem.
Unfortunately the farthest I have gotten is a wiki page on Cyanogenmod that goes through the process of updating your SMSC based on your Carrier's Gateway Number and putting it into PDU format. You can fidn the gage here.
To make it worse, as I thought I was going to be able to manually update it and get SMS back up, i still receive update error.
To make matters worse, for the past four days calls drop out every four to six minutes regardless of coverage. Not just on my line, but my wife's and my sister's lines as well. However they have not been able to reproduce any SMS problem like the one I have once again come across. I'm pretty close to dropping Sprint even if I've got a year left on contract.
Thanks for the reply. When I went to update or refresh the smsc I would get an error as well. This is my second GNex and really frustrated by it. I ended up odin'ing back to factory to and called sprint. they had me re-activate the phone *#*#72786#*#* then a few minutes later it started working again...
Well at least you were able to get yours working again. I've performed several resets via the 72786 menu to no avail. I went to a store today, to see them try it themselves, and eventually reactivate it. After seeing my problem was the same as the last, They decided to order a new/refurb phone. If this doesn't work out I plan on going back to my Evo 4G or just dropping my line on Sprint.
Well last night the modem died completely, this is some bull****. Can't connect to any sprint towers, makes me wish I still had my old phone. With 3 lines I just cant spend that much money to leave sprint.
Sent from my cm_tenderloin using xda app-developers app
I completely understand the cost of leaving sprint. I'm in the same boat with three lines as well. I have read up that in many cases an etf can be waived by returning the phone.
I am currently waiting for a new nexus to get shipped out here. If this third one doesn't hold up I'm going to have some bickering to do with account services. The other two lines are only experiencing dropped calls every few minutes and after talking with several reps, there is ongoing maintenance in my area.
What I want to know is why can't the smsc number be updated. And then why after wiping system and data and then flashing stock, that the smsc still cannot be updated. Something about the smsc cant be updated or there's a read error, corrupted sector, i dunno. I feel like I have exhausted everything I can think and tried everything I can. Not to mention this problem seems relatively isolated.
Sent from my Nexus 7 using Tapatalk 2