Hi, I started getting a message when I try to place calls this morning, it says "Due to error number 16, the call cannot be completed. Please stay on the line to be transferred to customer service" It then says "Switch 702, please call the number provided by your service provider", and then hangs up.
I called Sprint, the rep there said that they can't really do anything about error 16, there's a special number they transfer those to. Then he told me that the phone should transfer me automatically after playing the error message, so he isn't sure what's going on. So now I'm waiting to hear back from them...
In the mean time, I can't make or receive calls, but I do have data. My shift is rooted, and running Cyanogenmod 7.1.
Anyone heard of this?
I had this same thing. It was a combination of a lot of things that finally fixed the issue. Basically calling 611 and telling them the problem. Forcing the most current prl into the phone and then finally getting the right tech person on the line after 3 days of calling. Its not fixed until you have 2 consecutive days of the phone working right.
Once they get something working on their end you can finally dial the number you are told to enter and it will finally work.
sent from my evo shift through tapatalk
I can't even dial 611 from the phone, I get the same message. Or did you mean dial it from another phone? My wife also has an Evo Shift (Unrooted) that isn't experiencing this problem. I'll try from there.
Any other suggestions would be greatly appreciated....
Thanks
They had me update my PRL, profile and then dial ##087523# to change my MSID. That finally got it working.
I had the same error, and I had it while running CM7.1 The sprint techs told me it has something to do with new security features they are implementing on their end. If you wait long enough after the error message is played, it will connect you automatically, it just takes a minute or two. They ask you all your account information like they would when you call customer service for anything else, then a few more questions like what phone model you have and so on.
I flashed x99's rooted sense gb rom and updated the profile and prl and everything was working fine. Later I nandroided back to CM7 and it immediately put me back on the error. I flashed back to the sense rom, updated again and was still errored so I had to call again and once it got resolved, I just left it with the Sense rom.
I also had this problem since Monday, its annoying because you have no idea your phone is not working, so you have to actually try to send a text message or make a phone call...
When i would send a text message, it would say couldn't send message.
I been calling sprint each time, so far today its been working but I ended up switching it back to stock rom.
Had this issue for the past 48 hours or so. Had to call customer service to resolve it. No PRLs or anything needed to be updated, just had to verify my account info. Apparently the problem has something to do with phones not running official Sprint ROMs.
I ended up telling the CSR that I was running CM7 rooted, and he asked why I didn't just run the official Gingerbread 2.3 for the Shift. I almost mentioned that I was tethering, but caught myself just in time
Had the same issue on my girlfriend's shift (CM 7.0.3.1).. had them fix it automatically then decided to update radios and PRL from a sense rom and moved to CM7 nightly.. problem's back. Fixed it automatically again this morning.. hope it was just the radio changes that did it the second time.. if this happens everytime you flash a new ROM it's gonna be ridiculous.
I had to flash back from MikShift to CM7 today and the problem came back. Maybe this is some new measure to discourage custom roms.
I called again and had the tech run a network refresh on my phone. That fixed it, for about 6 hours.
I finally went back to the stock ROM since I use this phone for my business, and can't have it not working like it was. A crappy ROM is better than no phone
If Sprint is intentionally disabling phones running unofficial ROMs, they suck. Especially since their official ROM is buggy and full of crap I don't need or want.
Having same issue. Only on the Shift not on my Evo or Hero that all are rooted ROMs. I get no help from Sprint and my dialer will not do anything when I input those commands they want us to use.
the problem will be fixed once you update your prl and the other option that is there..
then you have to at least load a few pages on your browser.. turn on 4g and get a gps lock...
then you shouldnt have problems on the next roms.
i was in the middle of playing a game and a box appered something about update, couldent read it all next one said failer of some sort couldent read all that. next thing i know i was gettin unsent text errors then i tried callin someone and got the error 16 message. talked to a rep she said she was resetting my phone. asked me to reboot few times asked me to pull battery, which i couldent since i have a internal one. she said everything looks fine on my end. call back tomorrow if it protists or go to a store. few mins later my screen comes on with message saying updating prl then another message saying updated prl. tried texting it worked fine tried calling it worked fine. was stressin for a bit.
felix161 said:
i was in the middle of playing a game and a box appered something about update, couldent read it all next one said failer of some sort couldent read all that. next thing i know i was gettin unsent text errors then i tried callin someone and got the error 16 message. talked to a rep she said she was resetting my phone. asked me to reboot few times asked me to pull battery, which i couldent since i have a internal one. she said everything looks fine on my end. call back tomorrow if it protists or go to a store. few mins later my screen comes on with message saying updating prl then another message saying updated prl. tried texting it worked fine tried calling it worked fine. was stressin for a bit.
Click to expand...
Click to collapse
Glad you got it sorted out . Sometimes Updating PRL / Profile will correct ERROR 16, sometimes it will not. In that case you have to do as you did call Sprint. They will Reset your Data. One thing though, you mentioned you have an Internal Battery. As in Non-Removable . You do realize this is the EVO Shift Forums. Not the EVO 4G LTE Forums .
Related
My phone is an AT&T LG Incite with a hacked ROM (Winmo 6.1) that has been working fine for a year.
I just woke up, my phone just said that the 3G was being used (which confused me), it never said that I received anything. "Messages" wasn't working at all. My "Contacts" were popping up as blank. And everything ran like garbage. I also was having problems hearing phone calls and people couldn't hear me. I eventually just reformatted. Got everything back to normal and it was all fine.
Then my friend texts me asking if I ever got a pic he sent me through MMS. I never got it so I just got him to send it again. So my phone eventually makes the "MMS recieved" sound and starts downloading it. Well, it never finishes and all the same symptoms are happening again. I eventually find out that he sent me it the first time when my phone messed up, so this is def. what is causing the problem.
Does anyone know how to fix this?
NOTE: also if I go into processes "MMSLOADER" or w/e says 97% cpu usage.
try to insert another sim card?
i think your phone lags, because it tries to download the mms?
I used to have a LG Incite, in fact I just sold it a few days ago . But your problem is your ROM. With the Incite you need to reflash every so often. You said you've had the ROM for over a year right? Well you should try and reflash it every few months to keep it fresh and running smoothly. I suggest moving on to WM 6.5, it's much more stable and fast. I used to use Bigmans 28011 no frills version. Best ROM out their, it's on WWW.LG-Incite.com, even still but I got banned from that forum forum because I made two accounts on accident when I first started because of a bad internet connection. What a rediculous excuse, I never did anything wrong.
I figured out a way to fix it. If you just turn off the data completely then restart it. It stops the download.
Hey guys,
got a bone stock Epic with just a few apps on it, nothing crazy. I keep getting this pop-up error msg that says something like "Network connection failed" and it gives me the option to retry or cancel. Either selection does nothing that I can tell. Theres no rhyme or reason to when or why it happens. I just got off a phone call a minute ago and it popped up again. Probably happens to me about 5-6 times a day. I've got wi-fi, gps, 4g, and bluetooth turned off for battery life. The radio signal shows full service when i get the message and doesn't indicate anything is wrong.
Anyone have this happen?
I'm also having a problem with e-mails not refreshing the inbox on the phone and notifying me i have a new e-mail until i go into the e-mail folder and check it myself. Possibly related?
Hoping froyo will fix this, but I'm hesitant to root the phone if I'm gonna have to take it back to Sprint for service.
For me I get this message in youtube sometimes. Not sured why it happens. It happened in the market only a few times but happened in youtube slightly more. Annoying of course
so its possibly being cause by an app i added? I only installed a handful of apps. I'm tempted to uninstall them one by one until i figure out what the cause is.
bikewiz said:
so its possibly being cause by an app i added? I only installed a handful of apps. I'm tempted to uninstall them one by one until i figure out what the cause is.
Click to expand...
Click to collapse
I'm highly doubting it has to do with an app as my husband gets it all the time too. I'm seeing quite a few network problems with the Epic right now. Errors, GPS taking forever or not at all, and reception sucks. Hoping a new radio is all we'll really need, but I'm not positive that's going to be a cure. Maybe someone else who knows the tech side of this a bit better can jump in here.
I'm thinking it might have something to do with Sprint (in my case) as the board is filling up with posts that not only us, but EVO users are experiencing this. I personally haven't on my HTC Hero though.
Site Moderators you may want to move this thread to the appropriate area
Hello people. I searched for info on this issue, but nothing for the Captivate came up. Intermittently I'll wake my phone up and there will be a little circle with a line through it where there should be network info. Anything I try to do with the network pops up a "Not registered on network" (or something like that) message. Usually rebooting the phone will solve the problem, but last weekend after three reboots it was still doing it. I left my house and an hour later checked it and no circle/line icon. This happens every several days, so not a chronic problem yet. Still very annoying. Any solutions? Thanks.
Stock Captivate.
I would consider warranty return if it were me I havent seen or heard of this before your post. good luck.
I have a stock captivate and let's just say I am incredibly disappointed and annoyed with it and at&t in general I'm tired of all the run around and hold up concerning froyo, but this isn't the thread for that.
My phone has been glitchy since the get go. The newest is the issue with "not registered on network". It has happened off and on, but a couple days ago, after I had turned the phone off for the night and back on, the phone screen blanked out while the bottom touch panel stayed lit and everything became totally unresponsive. After several reboots by removing the battery, my screen finally came up again, but so did that little blue circle and line...voila..."not registered on network"
The guy in tech support from at&t tried to help me out. He stayed on the phone with me for over 2 hrs trying to correct the issue, but even after a factory wipe...nada. Lost all my apps, free and purchased... if we would have froyo like promised, all my apps would have been backed up...UGH...
This is actually my third captivate in as many months. My first phone bricked itself after 2 days. No one could ever figure out why. I am waiting on a replacement as we speak. Of course my "new" phone is being replaced with a refurbished one. I hate that considering my current phone was only 3 months old and didn't have a mark on it, but what can I do?
because you don't mention if you're running stock or a custom ROM, I'm going to assume custom ROM. and if you are, then you must have not searched very hard because this is already a semi-known issue: http://forum.xda-developers.com/showthread.php?t=864903
it happens to me ANY time I use a modem newer than JK3... when I use UGJK3 or older, no problems... but if I use UGJK4 or newer, random "no service" on the lock screen with the "circle with a line through it" in the notification bar. as of right now (I believe) there's no known issue why some modems fail on only some hardware. I have a batch 1006 and it works fine right up until the UGJK3 modem, while some people seem to have absolutely no issues with modems (even the newest ones like UGJL2 and TLJL3). basically, if you're running a JPY based ROM, flash JK3 and see if that helps... if that doesn't, go back to a stock captivate ROM of some sort with a stock modem so you don't have these issues (never happened to be me on JI6/JJ4)
Try changing ur SIM card. That could solve the issue.
In my case, it is original stock all the way. The SIM card is fine because I switched it into two different at&t phones and had no issues at all. Right now my Captivate is a gloried camera and MP3 player.
I forgot to subscribe to my own stinking thread! I know this is stale now, but here goes.
I'm running stock froyo, rooted. At the time of the original post I was using it completely stock on eclair. Shortly after the post, it stopped happening and haven't had issues since. I still don't know what caused it. Thanks for all the input though.
Sent from my SAMSUNG-SGH-I897 using XDA App
NvigR8 said:
I forgot to subscribe to my own stinking thread! I know this is stale now, but here goes.
I'm running stock froyo, rooted. At the time of the original post I was using it completely stock on eclair. Shortly after the post, it stopped happening and haven't had issues since. I still don't know what caused it. Thanks for all the input though.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Happened to me a year or so ago on a different phone. Turned out they were upgrading the tower closest to me with new hardware and were shutting it down intermittently to work on it.
5/19/2013 Update: The bug might be dead! Like for real this time. See this post, post number 14 in this thread with an explanation of what to do.
10/25/2012 Update: TRY THE LATEST BUILDS OF BRUCE'S CM10 STARTING WITH THE 10/25 VERSION!
Bruce has made a change that helps differentiate between the regular data stream and the MMS data stream in an attempt to see if that was what was causing the instability issue. This is only on Bruce's CM10 Kang as of 10/25. If you are only another CM ROM, flash Bruce's (even if just for a minute or two) and see if the data bug goes away. Please report back if it did!
If this does cure it, I'm sure Bruce will share the sollution to all other devs and your favorite other AOSP ROm will have the cure shortly.
Updated 10/24/2012
This is a detailed description of the 6 million or so things that various people have attempted to do in order to rectify the blinking data connection problem plaguing T Mobile USA users on AOSP ROMs for the Sensation. This issue is non existant in Sense based ROMs.
The problem has something to do with how the Sensation authenticates itself with the T Mobile Data Network. It's not based on the cell towers as voice calling is unaffected. The theory is that the AOSP framework lacks the proper authentication certificates for part of the data network and when the phone is routed to that part of the network, it gets kicked off teh network, then continually retries to connect.
This was and issue on the Sense Gingerbread Stock ROM in 2011 but T Mobile and HTC patched it. All Sense ROMs are free from this bug. But no one knows what exactly the patch was so AOSP ROM's have not been able to be cured yet.
Short version....
Problem started for me on Bruce's CM10 rom. But it's reported on all CM10 variants and most CM9 ROM's as well.
One day I noticed that data wasn't connecting well. It would blink on and off. Sometimes it would stay on, but if I turn it off then right back on, it might go back to blinking.
The problem exists on all AOSP roms (AOKP, CM9, all versions of CM10) even after full wipes and restores of known working nandroids.
Cell signal for voice calls works perfectly. No problems whatsoever. So the phone is connecting to T Mobile. It just won't get data.
Long version....
To fix this I've tried the following...and how each does or doesn't work.
Switch to 2G networks only and switch back. Problem remains, and still blinks E on the EDGE networks rather than being solid on them.
Updated the radio. Problem remains.
Updated the entire firmware package. Problem remains.
Superwipe and flashed Sense, verify data works well. Then regular wipe and flash a fresh install of CM10. Problem remains.
Flashed clean version of CM10 and fixed permissions. Problem remains.
Made calls from the phone. Some people have reported that this helps temporarily.
Sent myself a text message. Some people have reported that this helps temporaliy.
Turn on airplane mode for a minute then go back to normal. Some people have reported that this helps temporarily.
It's not related to Wifi at all because I've created the error on fresh installs of CM10 before ever turning Wifi on.
Formatted SD card. Problem remains (and just to be sure I got the error while the blank formatted SD was removed from the device)
Checked the APN's 100 times. They are correct.
Spent an hour on the phone with T Mobile. Their tech said everything looked good on their end. He cleared the SIM and reactivated it. Problem remained.
Other people have gotten new SIM cards and found that while they helped right away, the problem eventually came back.
The only things that have shown any help to multiple users are in bold above. There are various reports of 100 other 'fixes' that people swear fixed the problem for them. But all of them involved the phone disconnecting from the network and reconnecting. That appears to be the key to get data working again temporarily. Making calls and sending yourself text messages also forces authentication on the T Mobile network without breaking the original connection.
If you want more details or want to review the logs to see if you can figure it out, logcats of the problem are located in this post! Click here for logcatty goodness!
Here is the real kicker....
Everyone once in a while...it connects. And once it's connected it'll stay connected until I turn the connection off or reboot the phone. Then it'll go back to blinking in and out when I try to turn it back on.
Just another note, the data is finicky on my old LG G2x also on TMobile with AOSP based ROMs, talk works, but cell data won't come back after going into airplane mode and out, until a reboot. It works fine on official TMobile ROMs. I suspect there may be some proprietary cell data negotiation between handset and Tmobile towers that AOSP code doesn't have.
Whyzor said:
Just another note, the data is finicky on my old LG G2x also on TMobile with AOSP based ROMs, talk works, but cell data won't come back after going into airplane mode and out, until a reboot. It works fine on official TMobile ROMs. I suspect there may be some proprietary cell data negotiation between handset and Tmobile towers that AOSP code doesn't have.
Click to expand...
Click to collapse
Okay here's an update on this for anyone who finds this thread through a search or Google or something....I'll try to describe this using the simplest terms possible so those of us who aren't cell tower engineers can understand it. (And I assume that's most of us, including me!)
The latest running theory is that the issue occurs due to the way the phone is handed off from 1 tower to another.
As you move your phone is handed off from one tower to the next. You get unregistered with tower 1 and reregistered with tower 2. That's normal.
However if you are within range of 2 towers you can't be on both. You have to be registered with 1, and that's supposed to be the stronger one. But AOSP ROMs lack a T Mobile certificate that authenticates which tower is supposed to have priority. So when the data is blinking you are getting bounced between 2 towers because the phone is trying to register with both.
The latest version of Bruce's CM10 ROM (Dated 10/10/12 and with TMOUS DATA in the rom name on the download page) supposedly includes patches that fix how this authentication works. And I only say 'supposedly' because the patches have only been up for about 12 hours so the jury is still out on how well it works. Personally I've been on it all day today and haven't had the data issue yet. But it can be days in between seeing it. So it'll take a while to know for sure that it's fixed.
If this turns out not to be the exact cause of the problem, it's something similar and a final sollution should be found soon.
Update: This have never been substantiated, and several users with the bug have reported knowing for a fact that they experience the problem when in range of only 1 tower.
Hi,
I have noticed with JB ROMS that you get 7 or 8 APN's,most of which do not apply to me.
Have you tried (making a note of your one first) and deleting all the APN's
Reboot,and just install yours.
malybru said:
Hi,
I have noticed with JB ROMS that you get 7 or 8 APN's,most of which do not apply to me.
Have you tried (making a note of your one first) and deleting all the APN's
Reboot,and just install yours.
Click to expand...
Click to collapse
That's one of the 1000 things that's been tried, to no effect. If he APN is set to the correct one the extra APN's are ignored.
Nothing that you do within the phone can cure the problem. At most, forcing the phone to re-register with the tower is the only thing that can help, and that will be temporary if it works at all.
The best bet now is to hope that Bruce fixed it with his latest additions to CM10 now that we understand what the actual problem is (or at least that we think we do)
Update....
T Mobile data is still broken. It has not been fixed yet. The latest theory may just be one more in a long line of theories that turned out to be wrong.
There are days when I really hate this phone.
Thanks for the update. I've been monitoring that thread occasionally, but it has way too much traffic for me to keep up. I was close to switching to it, but I need good battery life and reliable cell service over any smoothness benefits of JB, which is why I'm sticking with HyperNonSense ICS for now.
been experiencing this issue for a couple months myself. currently stuck in a no data bout as we speak. i'm wondering if it has anything to do with the amount of data we've used. i noticed this last bout started right around the time i passed 5gb. should also be noted i'm on the unlimited 4g plan and tether like crazy. i guess i'll know if the problem persists until my next billing cycle. for now i'm stuck with a sense nandroid and crack flashing aosp daily to see if it's fixed.
cpittman said:
been experiencing this issue for a couple months myself. currently stuck in a no data bout as we speak. i'm wondering if it has anything to do with the amount of data we've used. i noticed this last bout started right around the time i passed 5gb. should also be noted i'm on the unlimited 4g plan and tether like crazy. i guess i'll know if the problem persists until my next billing cycle. for now i'm stuck with a sense nandroid and crack flashing aosp daily to see if it's fixed.
Click to expand...
Click to collapse
I have tried the SIM swap fix. And that has apparently worked. I've been using in good for about the last 6ish hours without any problems. :good:
So i'd give that a shot if your willing.
I've been using CM10 KANG since it was available for HTC sensation. Never had the data blink issue. Recently, my phone started to have this issue. Data would simply not connect with CM10 or CM10.1 with any radio/firmware combination. I also noticed that when I travel to work, i get data say after 10 miles away from my home and it continues to work after coming back home. However, after restarting the phone, i hit the blink problem again. Wondering if its because of some cell tower maintenance/upgrade near my area.
So I was on bruce's ROM until a week ago and this never happened while on his ROM. Just upgraded to albinoman's ROM and this started happening. I have to send myself a MMS picture to get it back again. Hope this helps
Fix
Ive had this problem on and the only thing that seems to help is flashing a new ROM but then a few weeks later it returns... I realized that this only happens when I try to send an MMS message or attempt to receive them. I don't know how to stop receiving an MMS but just delete the picture message you're trying to send and your data should stop blinking on and off. Can't guarantee it'll work for you but it worked for me! GL!!
It appears as though this stupid annoying silly obnoxious bug has finally been squished, sprayed with 3 cans of Raid, and its' mangled corpse then burned to a crisp...I hope.
3 weeks ago W1ldFl0wer brought this fix to Albinoman's attention...
In the build.prop under phone>system was the following line....
ro.telephony.ril.v3=datacallapn,signalstrength
This line appeared like this on all AOSP roms for the sensation.
The fix was to add skipbrokendatacall to the line so it looked like this....
ro.telephony.ril.v3=datacallapn,signalstrength,skipbrokendatacall
Save the file, reboot, and data should spine right up and work fine. So far the peopl ewho have run into the data bug have implimented this change and BOOM, data fixed.
So if you use any AOSP ROM 4.0, 4.1, or 4.2 other than Albino's CM10.1 Kang just add skipbrokendatacall to that line and see if it fixes it. Only do this if you on in the US on T Mobile's network. If you are in parts of Europre making this change will screw up your data.
If you are using Albinoman's CM10.1 Kang ROM, he has already included this line in the build.prop for you. You just have to activate it. About 30 lines into the build.prop is the new line that reads...
#ro.telephony.ril.v3=datacallapn,signalstrength,skipbrokendatacall
Just delete the # in front of that line. (The # makes the ROM skip the line when loading everything, but lets it stay in the file so you can read it. Deleting the # means that the phone will read that line when it reboots.) Then go up to the line that says the same thing without skipbrokendatacall and delete that line entirely. Save the file and reboot. If you don't delete the original line without skipbrokendatacall, your phone will go haywire, data might not work at all, and you might inadvertantly trigger Z Day. So if you're not ready to fight in the zombie apocolypse, only leave one of those lines in the build.prop.
Hope this cures it for everyone! Again, don't make this change if you live outside the USA or are not on T Mobile's network! Doing so on other networks in other parts of the world could make things worse for your phone!
Here is the link to the post where W1ldFl0wer informed Albinoman of this fix.
http://forum.xda-developers.com/showpost.php?p=40755845&postcount=9003
I don't think W1ldFl0wer invented the fix, but he certainly is the one who made it public to Sensation users so go to that post and thank him/her bcause I might finally be able to stop obsessing over this stupid bug because of this user!!! :good:
Hey guys, my phone has been working fine until 3 days ago. I am running the latest Eclipse rom. I woke up one morning to send a text and it wouldn't go through, it kept failing, so I restarted my phone to send it, and it worked. Later that day I went to send another message but it didn't work again, so I did the same thing. Now, I can't receive, or send texts (I can't even do calls) without having to turn airplane mode on and off every 5 minutes. I tried factory reset and that didn't work. My brother doesn't have any problem with his iPhone so maybe this is an S3 thing or something.
droidj said:
Hey guys, my phone has been working fine until 3 days ago. I am running the latest Eclipse rom. I woke up one morning to send a text and it wouldn't go through, it kept failing, so I restarted my phone to send it, and it worked. Later that day I went to send another message but it didn't work again, so I did the same thing. Now, I can't receive, or send texts (I can't even do calls) without having to turn airplane mode on and off every 5 minutes. I tried factory reset and that didn't work. My brother doesn't have any problem with his iPhone so maybe this is an S3 thing or something.
Click to expand...
Click to collapse
Not the s3 or verizon so probably the rom.
ok i'm about to install moar.. i'll get back to the thread after installation
droidj said:
Hey guys, my phone has been working fine until 3 days ago. I am running the latest Eclipse rom. I woke up one morning to send a text and it wouldn't go through, it kept failing, so I restarted my phone to send it, and it worked. Later that day I went to send another message but it didn't work again, so I did the same thing. Now, I can't receive, or send texts (I can't even do calls) without having to turn airplane mode on and off every 5 minutes. I tried factory reset and that didn't work. My brother doesn't have any problem with his iPhone so maybe this is an S3 thing or something.
Click to expand...
Click to collapse
Are you from either the 570 or 717 area codes? There are a lot of people from those areas(myself included) that are having this issue on AOSP with no current known fix.
no but i have seen those posts... i flashed the slimkat rom and it seems everything is now fixed
edit: hour later, phone is starting to act up again. only way i can send messages is to toggle airplane mode. i have no idea if anyone is trying to reach me... phone status says i'm connected with mobile network, in service. i have no idea what could be causing this.