Related
i know this has been a fairly well known issue but has anyone with much better comp skills than me been able to get an idea on what is causing the connection to time out?
I was looking through the registry and saw a few things but since I wouldn't have a clue for any commands I don't wanna try.
I have an extra Titan laying around but both were flashed to the new ROM and I can't get 2.17 downloaded again to load on to that one to compare the registry.
Any help at all? ? ?
Everyone seems to be focused on GPS which works just fine for me and no one cares to try the connection timeout problem.
Thanks
yea I realized that happens a lot
i havent had that issue suprisingly, but i use exchange throughout the day...
also does anyone have the 2.17 RUU they could email me (phillips.h @ gmail.com)....i can't get it from the htc site it won't complete a DL.
thanks
yea its a good thing, when im not by a power outlet all day but it sux bc at night i like to stay connected to aim, but it doesnt werk. I have a feeling that its not a bug just a way for sprint to limit the bandwidth that is used.
im having a connection problem as well, mine is a little different though. When i upgraded to the leaked rom, it put me back to prl 60610. i upgraded the prl back to 60611 and everything has been working good except one thing, at my home i get poor sprint evdo signal. I used to be able to roam on alltel's tower and get a full evdo signal. now for some reason on this rom i can only get 1x while roaming on alltel's towers, even with the same prl. I don't understand why that would happen. does anyone here know?
thirdeyeopen23 said:
im having a connection problem as well, mine is a little different though. When i upgraded to the leaked rom, it put me back to prl 60610. i upgraded the prl back to 60611 and everything has been working good except one thing, at my home i get poor sprint evdo signal. I used to be able to roam on alltel's tower and get a full evdo signal. now for some reason on this rom i can only get 1x while roaming on alltel's towers, even with the same prl. I don't understand why that would happen. does anyone here know?
Click to expand...
Click to collapse
did the PRL update help with the dropped connection?? i just checked mine and i
am also back to 60610. time to do a update....
black06c230 said:
did the PRL update help with the dropped connection?? i just checked mine and i
am also back to 60610. time to do a update....
Click to expand...
Click to collapse
i had to manually update my prl and i havent had the dropped evdo that some people have been reporting. my brother has the same rom and prl but lives 3 hours away and has the evdo dropping problem, go figure. i think there are quite a few random problems with this rom. i really would like to get evdo roaming back...
News about the internet connection issues
So I don't know if this is the same as what you are experiencing, but I am able to connect to the network (it shows connected), but it won't load the pages. I went through a bunch of steps with Verizon support and got to the point where I could do what I just described. Initially, I kept getting either the error message saying that I couldnt connect for an unknown reason or username/password was wrong (even though I double checked those). I reverted back to the VZW ROM and everything works again. I'd really like to get the GPS and REV A action going, but I just can't seem to make it work. I followed the instructions everyone gave, too. If I make any progress I'll let you know.
black06c230 said:
also does anyone have the 2.17 RUU they could email me (phillips.h @ gmail.com)....i can't get it from the htc site it won't complete a DL.
thanks
Click to expand...
Click to collapse
Way to big to email.
60 megs
well then could some one put it on a host like rapidshare or the like
any one have this? i did a ##3282#hands ffree failed but now it says welcome to verizon wireless....im so confused am i on some imaginary plan with verizon?
d1eharddan said:
any one have this? i did a ##3282#hands ffree failed but now it says welcome to verizon wireless....im so confused am i on some imaginary plan with verizon?
Click to expand...
Click to collapse
That's odd. Had you messed around with changing your PRL at all? With QPST? That is the only time I've ever heard of getting a verizon customer service is if you were on a Verizon PRL, to force roam. I think it was PRL 00001 or something like that. If not, then I truly have not a clue..
I had this problem when i rooted. I was dog sitting and I roam in and out alot here. I couldnt call sprint to save my life after the Error 16 code because it was roaming. Turn roaming off and call sprint then, worked for me
i had same thing no error 16. i rooted and s-off
worked perfect all worked fine. i went to my inlaws today where i was roaming. no 3G at all and when i tried a call i got the welcome to verizon your phone is authenticated for the network. i ended up calling sprint took literally 3 minutes. pulled battery they re-provisioned it. put battery back in all fixed. idk wtf happened it worked great at home. roam was bunk. now roams fine.
I've been intermittently getting this error. Something about data not being able to connect.
Has anybody else gotten this error and does anyone know how to fix it? I'm completely stock, no root.
Same here! I can't figure out why it's doing this as well.
Yeah I've gotten it too. Flashing different radios didn't seem to help- mine is S-off and rooted. My sister works for Sprint she isn't the phone nerd like me but lol nothing I seem to do can fix it. Will update on how she fixes it if she does lol.
You can still make phone calls and everything else, just no data.
Try making a call, if it doesn't go through you will be connected to someone in tech support who will refresh you connection to the network. They implemented a security feature that will give ya that when you aren't being allowed onto the network.
#Winning# said:
Try making a call, if it doesn't go through you will be connected to someone in tech support who will refresh you connection to the network. They implemented a security feature that will give ya that when you aren't being allowed onto the network.
Click to expand...
Click to collapse
Yep. Exactly what this guy said. Tell the guy the error you got and he'll fix it up right away.
I started getting this same error this morning, right after I flashed Synergy nightly 330. Not sure if it's a coincidence or not, but that's when it started. It's now doing it on every rom. I can connect to 4g just fine. It's only 3g that gives me that error. I've updated PRL and Profile but that didn't fix it. Not sure what I'll try next.
EDIT: Well, right after I submitted this message a second ago, I looked at my phone and 3G was connected and the error stopped. It lasted for a few hours then resolved itself. Strange.
Are you able to post the steps?
I am getting the same error and can't even call *2
Thanks
Apparently there is a national outage, that's why we are getting the 128 code.
I've been getting it all day too. I can make calls though, so I'm not sure what the problem is. I just keep getting the error message pop up.
I was getting it, too. I went on chat with Sprint and they reset me again. Had to take my battery out for 2 minutes and then reboot my phone twice. It's all fixed now.
I think there were network issues on the 20th as it happened to me as well. However, I just left it alone suspecting the network, and about 20 min later, it fixed itself.
This isn't 3d related guys, my evo 4G is doing it as well. It started after that small earthquake over here. Not sure if that's why but I was fine before 2pm today.
Sent from my x3Dvo using XDA Premium App
My daughters phone had that problem. I updated profile seems to have fixed it for now.
Sent from 3D A.W.E.S.O.M-O
Maybe it was due to the earthquake today. There was an announcement from Sprint saying the sprint towers were overloaded.
Sent from my PG86100 using XDA Premium App
aFoodStampBaby said:
Maybe it was due to the earthquake today. There was an announcement from Sprint saying the sprint towers were overloaded.
Sent from my PG86100 using XDA Premium App
Click to expand...
Click to collapse
That was because too many people were trying to call, but I don't see how calling people could affect the data.
my phone just started doing this recently while on 4G. i can make calls, send texts, browse internet, etc. only thing i can't do on 4G is play Scrabble. it tells me no network detected. today i was using Google Nav in Orange County by Anaheim, CA on the 5fwy and i saw the error pop up a few times. i just tapped on the dismiss button and continued on my way. just curious on the error as its starting to annoy me. i called sprint a couple days ago and they were clueless as to why it popped up. they checked the towers by my house and said they were fine and operational. but yet i know there is something wrong here. especially when i can't play Scrabble on 4G...LOL . i've also reset my data profile using my MSL# and updated data profile and PRL... anywho has anyone had this issue recently and has had this corrected??? BTW: I'm rooted running stock RUU 2.3.4 on latest radio and prl...
will survive said:
my phone just started doing this recently while on 4G. i can make calls, send texts, browse internet, etc. only thing i can't do on 4G is play Scrabble. it tells me no network detected. today i was using Google Nav in Orange County by Anaheim, CA on the 5fwy and i saw the error pop up a few times. i just tapped on the dismiss button and continued on my way. just curious on the error as its starting to annoy me. i called sprint a couple days ago and they were clueless as to why it popped up. they checked the towers by my house and said they were fine and operational. but yet i know there is something wrong here. especially when i can't play Scrabble on 4G...LOL . i've also reset my data profile using my MSL# and updated data profile and PRL... anywho has anyone had this issue recently and has had this corrected??? BTW: I'm rooted running stock RUU 2.3.4 on latest radio and prl...
Click to expand...
Click to collapse
Not being able to play Scrabble while on 4G has been an issue with the Scrabble app for sometime. I reported it twice to the company but never got a response. This is totally unrealted to the errors others are reporting in this thread. Scrabble just needs to fix their app.
Did anyone get Sprint to fix their phone. I called them but they were not able to fix it over the phone.
Lately I have noticed my phone going into roaming mode a lot. Sitting in my house today it went into roam. I live in town and get a good 4G signal when I turn it on. I should not be roaming. Here and there running around town I go into roaming too. If I try to make a call it tells me welcome to Verizon this account can not ne authenticated. it won't let me make a call. Now I know we roam on verizons towers but if i can't make a call when i actually need to because I am roaming I am gonna be pissed. If i try to send a text it gives me an error 64 as well. I have been rooted for about a month or longer and just started having problems.
My thought is it is some sort of security thing sprint has been doing to crack down on rooted devices that are forced to roam. I am not forcing mine into roam and have no intention to. Is there any suggestions I can try to keep from going into roam so much.
I live around Austin tx. Anyone else notice more roaming lately?
Sent from my PG86100 using XDA App
I had the same exact problem and searched for a solution for months. Call sprint, ignore everything they try to do to fix it and request an hlr refresh (or reload, reset, etc....). It's the only solution I found and is very easy provided you get the right rep. I've also heard its easier doing this over sprint chat on their website. Hope this helps!
There is a thread in the general section that has a few prls up. I had to switch mine a few times to get good signal back.
I know there are a few towers down in my area because of the storm. Sprint is taking their sweet time fixing them as well. I called a few times to submit a ticket and they always say they will call me back within 24-72 hours and never do. I always have to call back. Really bad customer service if you ask me! Sprint's network right now is a joke! It can't compare to Verizon or ATT in my area.
oohaylima said:
There is a thread in the general section that has a few prls up. I had to switch mine a few times to get good signal back.
Click to expand...
Click to collapse
What area are u in and which one worked best for u
Sent from my PG86100 using XDA App
I live in Fort Leonard Wood. 1115 worked best for me.
I have been having this problem as well. After about 2 weeks of constant phone calls to Sprint, multiple CHLR resets, and even an exhange, the new 1 does the same thing. It will work for a few days, then I'll go into a roaming area, and whamo, the Verizon lady tells me my phone cannot be authenticated! Funny thing is my original 4G, never roams in these areas, and when it does, it roams perfectly well...
Some of you may have seen this in my MeanROM thread, but I thought I'd start a thread for it for others who may have the problem. I noticed a few days ago that my phone was no longer ringing while roaming. People would call and it goes straight to voicemail while roaming. I tried all manner of tricks (some which did work for others) but none worked for me. I did PRL updates, profile updates, wiping dalvik and cache, wiping multiple times, factory resets, multiple factory resets. Bottom line: my phone flat out will NEVER ring when roaming on PRL 25006 (the normal PRL for us now): only when on Sprint. Odd thing is, you can pick up the phone and make an outgoing call fine on roaming: just won't ring. As a last ditch effort before getting mired up in Sprint phone support for an hour, I put back my old 12124 corporate PRL that I had used for about a month and then dumped (only because I didn't see a difference). I've now done this at least a half dozen times: as soon as I push 12124, the phone will ring (and work) every time while roaming! Put 25006 back: won't ring.
Again, I've tried every trick that everyone has mentioned and the only factor is the PRL. Push 12124: works fine. Do "update PRL" and get 25006 back: won't ring while roaming; only when on Sprint. At my house, depending on what part of the house I'm in, that means I can't get calls at least half the time on PRL 25006 so thankfully we have 12124. Now I know 12124 isn't compatible with LTE but I couldn't care less as my area here isn't compatible with LTE either: and I'd rather be able to get phone calls when I need to!
This message is nothing more than a "tickler" to say hey, I think the 25006 PRL might be hosed. Either that or Sprint has changed something on the network that makes 25006 affect some of us this way. I've never had this happen before but the only other explanation I can think of is... maybe by me running 12124 for a month or so, my phone somehow got "re-provisioned" to corporate PRL's and the way it's provisioned now, 25006 doesn't work right. That's possible too: that I caused it by running 12124 for a while. Also possible that Sprint could fix it if I could actually find someone who knows how to reset/fix provisioning. I just don't have time right now for their BS and going through 6 techs over 2.5 hours on the phone. Been hammered lately.
Anyway, might be worth checking if you roam often: if you can actually receive a call when roaming. I know it doesn't affect everyone on 25006 nor does it affect every area. Might have to be special circumstances but I feel like there must be a bunch of people here who don't even know it but can't receive calls when roaming.
Mike
samething for me on 25006. just noticed it last night when i was roaming out in the country and my wife and daughter were trying to call phone never rang once.
mikeyxda said:
Some of you may have seen this in my MeanROM thread, but I thought I'd start a thread for it for others who may have the problem. I noticed a few days ago that my phone was no longer ringing while roaming. People would call and it goes straight to voicemail while roaming. I tried all manner of tricks (some which did work for others) but none worked for me. I did PRL updates, profile updates, wiping dalvik and cache, wiping multiple times, factory resets, multiple factory resets. Bottom line: my phone flat out will NEVER ring when roaming on PRL 25006 (the normal PRL for us now): only when on Sprint. Odd thing is, you can pick up the phone and make an outgoing call fine on roaming: just won't ring. As a last ditch effort before getting mired up in Sprint phone support for an hour, I put back my old 12124 corporate PRL that I had used for about a month and then dumped (only because I didn't see a difference). I've now done this at least a half dozen times: as soon as I push 12124, the phone will ring (and work) every time while roaming! Put 25006 back: won't ring.
Again, I've tried every trick that everyone has mentioned and the only factor is the PRL. Push 12124: works fine. Do "update PRL" and get 25006 back: won't ring while roaming; only when on Sprint. At my house, depending on what part of the house I'm in, that means I can't get calls at least half the time on PRL 25006 so thankfully we have 12124. Now I know 12124 isn't compatible with LTE but I couldn't care less as my area here isn't compatible with LTE either: and I'd rather be able to get phone calls when I need to!
This message is nothing more than a "tickler" to say hey, I think the 25006 PRL might be hosed. Either that or Sprint has changed something on the network that makes 25006 affect some of us this way. I've never had this happen before but the only other explanation I can think of is... maybe by me running 12124 for a month or so, my phone somehow got "re-provisioned" to corporate PRL's and the way it's provisioned now, 25006 doesn't work right. That's possible too: that I caused it by running 12124 for a while. Also possible that Sprint could fix it if I could actually find someone who knows how to reset/fix provisioning. I just don't have time right now for their BS and going through 6 techs over 2.5 hours on the phone. Been hammered lately.
Anyway, might be worth checking if you roam often: if you can actually receive a call when roaming. I know it doesn't affect everyone on 25006 nor does it affect every area. Might have to be special circumstances but I feel like there must be a bunch of people here who don't even know it but can't receive calls when roaming.
Mike
Click to expand...
Click to collapse
Hey Mike.. On 25006 here running your Mean 3.6. When I first forced roam and attempted to call my first attempt resulted in several network courtesy rings but no ringing on my device with it eventurally rolling to voicemail... My 2nd attempt I heard about 4 network courtesy rings then myh device actually rang once before it rolled to voicemail. 3rd attempt and all subsequent attempts afterwords calls rang right through to my phone and I also tested sms text messages and data and they both worked fine. Cant really explain why 12124 works fine for you and 25006 doesnt other than possibly the first preferred roaming partner is different between the 2 because of an agreement change between carriers. Maybe whatever carrier is the 1st prefferred in your area for 25006 is having issues with correctly registering your device to its network to notify of incoming calls.. Most of the time just registering to network by completeting an outbound call but obviously isnt working for you.. Sometimes powercycling will resolve the issue also... On another note.. Im not sure if its the new sense 4.1 or your new rom that has stripped out some of the funtionality of beats audo settings.. But now the only options I get for beats audio is on/off... I no longer get the extendted options of beats ur beats.. beats solo and other.... or the option of the equalizer with beats off... Is it that way for everyone or just me?
Hope mikeyxda doesn't mind....
I have been talking back and forth with mikeyxda, it's a metropcs issue. Sounds like there is an issue with metropcs telling sprint that his phone is on their tower. Unfortunately when a call comes in, sprint thinks his phone is off so it sends it to voice mail.
The 12124 prl doesn't have metropcs in the list for his area. So he sits on vzw which works fine, but 12124 doesn't allow Lte connections. Working on a solution to fix both issues....
Sent from my C64 w/Epyx FastLoad cartridge
Do other phones work when roaming on MetroPCS?
Sent from my EVO LTE
Yeah I have this issue too. And I roam a lot too. That's not good.
Sent from EVO LTE using the XDA app
digiblur said:
Hope mikeyxda doesn't mind....
I have been talking back and forth with mikeyxda, it's a metropcs issue. Sounds like there is an issue with metropcs telling sprint that his phone is on their tower. Unfortunately when a call comes in, sprint thinks his phone is off so it sends it to voice mail.
The 12124 prl doesn't have metropcs in the list for his area. So he sits on vzw which works fine, but 12124 doesn't allow Lte connections. Working on a solution to fix both issues....
Sent from my C64 w/Epyx FastLoad cartridge
Click to expand...
Click to collapse
Mind? I'm hella grateful that we have someone with your knowledge here! I feel a lot better knowing the reason for the problem and feel a little better about Sprint because it seems like a MetroPCS problem. Although, with Sprint doing work on upgrading towers around here, I guess it could still be a Sprint problem where something they did is no longer compatible with MetroPCS. Either way, I think this problem is more widespread than people realize and I suspect anyone roaming in an area that is being upgraded while on a MetroPCS tower might have this problem. Kinda brings to light the fact that PRL's can affect more than people realize. If you're roaming, a PRL can affect data, data speed, whether or not you connect at all, and now whether or not your phone will ring when it looks like you have a signal.
Mike
mikeyxda said:
Mind? I'm hella grateful that we have someone with your knowledge here! I feel a lot better knowing the reason for the problem and feel a little better about Sprint because it seems like a MetroPCS problem. Although, with Sprint doing work on upgrading towers around here, I guess it could still be a Sprint problem where something they did is no longer compatible with MetroPCS. Either way, I think this problem is more widespread than people realize and I suspect anyone roaming in an area that is being upgraded while on a MetroPCS tower might have this problem. Kinda brings to light the fact that PRL's can affect more than people realize. If you're roaming, a PRL can affect data, data speed, whether or not you connect at all, and now whether or not your phone will ring when it looks like you have a signal.
Mike
Click to expand...
Click to collapse
Looking into the issue also... will report back when have an update...
I just chatted with a sprint tech online and so far the issue seems to have been resolved. This was the transcript:
You: well, my phone recently upgraded. Since then, whenever i am roaming, when people call, it goes straight to voicemail
Russ B.: Please confirm which line you are concerned about.
You: **********
Russ B.: Thank you.
Russ B.: Please turn off your phone and let me check this for you.
You: turning off
Russ B.: Thank you.
You: its off
You: i roam a lot, so its a problem
Russ B.: Thank you for waiting.
Russ B.: I have done some basic troubleshooting on your phone.
Russ B.: Please turn on your phone and check if you still face same issue. However I can see you are on data plan and roaming is included in your plan and you will not be charged for roaming.
You: no i know, and thats good, but if i dont receive calls while roaming, then it does me no good
You: ok its on, and im roaming right now. can you call it to see if it works?
You: i have no other phone
Russ B.: I am sorry, we are at chat support and do not have option to call.
Russ B.: I hope you can understand this. Please ask some one to call you.
You: i will try to find someone hold on
Russ B.: Sure.
You: sorry for the wait
You: someone is trying right now
Russ B.: Sure, no problem.
You: it has worked 2 times, but im trying a third just to be sure!
Russ B.: Sure.
You: it worked 3 times
Russ B.: I have just refreshed services on phone by doing some troubleshooting on your phone.
Russ B.: Great. It will be more better once provisioning will get completed.
You: ok oh it says service update right now
Russ B.: Let t get completed. Provisioning is running on your phone.
Russ B.: Yes, however it may take some time. So please do not use services on phone for 10-15 minutes.
Hope this helps. Ive received 5 calls while roaming since, some say it rings 4 or more times, and i only hear one, but it seems to be working!
mikeyxda said:
Mind? I'm hella grateful that we have someone with your knowledge here! I feel a lot better knowing the reason for the problem and feel a little better about Sprint because it seems like a MetroPCS problem. Although, with Sprint doing work on upgrading towers around here, I guess it could still be a Sprint problem where something they did is no longer compatible with MetroPCS. Either way, I think this problem is more widespread than people realize and I suspect anyone roaming in an area that is being upgraded while on a MetroPCS tower might have this problem. Kinda brings to light the fact that PRL's can affect more than people realize. If you're roaming, a PRL can affect data, data speed, whether or not you connect at all, and now whether or not your phone will ring when it looks like you have a signal.
Mike
Click to expand...
Click to collapse
Just making sure, don't want to bring PM stuff out in the public.
When roaming you are at the mercy of whatever the provider gives you. But for the most part, the other provider wants you to use all the minutes and data you can so they can bill Sprint more.
This MetroPCS issue might be just a regional thing and not nationwide. It could be even a smaller subset of users in your area as well. It's going to take quite a few phone calls to get fixed though. The easier option is to just use a PRL that doesn't use MetroPCS.
So the fact that i seem to be working just fine now is a fluke? because ive received several calls now while roaming and they have all worked just fine, whereas before they wouldnt go through at all.
edit: upon reading my post, i feel it may sound accusing. I did not intend for that, I really want to know, if it is a fluke. maybe im just paranoid!
ooonimrodooo said:
So the fact that i seem to be working just fine now is a fluke? because ive received several calls now while roaming and they have all worked just fine, whereas before they wouldnt go through at all.
edit: upon reading my post, i feel it may sound accusing. I did not intend for that, I really want to know, if it is a fluke. maybe im just paranoid!
Click to expand...
Click to collapse
What SID are you Roaming on? Check your 1x engineering screen in the ##DEBUG screen.
Sent from my C64 w/Epyx FastLoad cartridge
digiblur said:
What SID are you Roaming on? Check your 1x engineering screen in the ##DEBUG screen.
Sent from my C64 w/Epyx FastLoad cartridge
Click to expand...
Click to collapse
that would be SID # 4107
ooonimrodooo said:
I just chatted with a sprint tech online and so far the issue seems to have been resolved. This was the transcript:
Click to expand...
Click to collapse
Thanks for sharing. I rolled back to the 25006 PRL so that I have the problem again and started a chat session. They did the same thing, reprovisioned my phone, my phone got the message about starting network services. Still won't ring. Rebooted, did PRL and profile updates after that. They had me call *720 (while NOT roaming). Tried some other things too. Still won't ring on 25006. Push 12124 and it rings every time.
So I guess moral of the story: YMMV.
Mike
I hesitate to post this due to its non-technical nature. Inside the sense music app is a choice to enter Sprint Music+.
When I entered it for the first time the phone automatically went into a PRL update. The actual PRL number (25006) did not change afterwards, the 3g connectivity at fringe did. It could be the placebo affect, but maybe just maybe there was a reason for the PRL update. Just thought it should be mentioned.
BTW I also get a lot of no ring > voicemail calls while roaming. I work in a sprint fringe area.
ooonimrodooo said:
that would be SID # 4107
Click to expand...
Click to collapse
You shouldn't be roaming on 4107, that a Sprint SID.
Sent from my C64 w/Epyx FastLoad cartridge
digiblur said:
You shouldn't be roaming on 4107, that a Sprint SID.
Sent from my C64 w/Epyx FastLoad cartridge
Click to expand...
Click to collapse
My mistake. I wasn't roaming at the time. I'm roaming now and it says 6005.
Sent from EVO LTE using the XDA app
Haha truth be told, I thought it was normal for me not to be able to receive calls while roaming, thought it was just cause I force roam..
Sent from my EVO using xda app-developers app
ooonimrodooo said:
My mistake. I wasn't roaming at the time. I'm roaming now and it says 6005.
Sent from EVO LTE using the XDA app
Click to expand...
Click to collapse
That's Cricket. I'm thinking this is only a MetroPCS issue...it might even just be a regional MetroPCS issue as well.
Just an update, doesn't seem to be am across the board national issue with prl 25006 as many users have reported being able to receive calls fine while roaming. Maybe onto something with it being with certain partners or a certain partner. Definately nothing to do with anything sprint is doing to their towers as your not connected to a sprint tower if roaming..now if you are in good sprint coverage and roaming then a coverage issue may need to be looked into.