Related
Just happened out of the blue. Had wifi on, but wasn't at home, so went to turn it of, did some facebook checking and then checked for a prl update...now no 3g data and EC67.
Looks like it forgot our sprint user name and password.
Tried doing a ##3282#, which did nothing and ##775# doesn't work.
Running Fresh 3.2 and the new htc kernel.
Sent from my PC36100 using XDA App
Have you tried updating profile? That'll usually fixit
Sent from my PC36100 using XDA App
kixcastillo77 said:
Have you tried updating profile? That'll usually do it
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Tried that but of course sense 3G doesn't work, it gave me the same error faster than I could press dismiss.
I'll try again via wifi and 4g.
EDIT: Looks like that fixed it - Thanks! Haha. I can't believe that I didn't think to try it over wifi/4g, but I remember trying to update my PRL over wifi/4g and it wouldn't work, awhile back.
EDIT 2: It didn't work. Haha. The Firmware updated without giving me the error, but now the profile update is giving me a 1020 error.
EDIT 3: I think I fixed it. I remembered that I had that startup cleaner app running and that it might be killing off the handsfree updater. Looks like I'm golden now.
I had the same issue yesterday, I updated profile a few times, didn't work. Updated PRL twice, it worked. I think it was a coincidence that it worked, probably an issue at Sprint's end.
I was having this issue last night and couldnt figure out why.. my wifi tether kept stalling out and my 3g kept going in and out.
Same here, they must have done something yesterday
Welcome to hell, dude. My wife and I have been experiencing these errors for weeks now. I have tried everything in the book and nothing seems to be a permanent fix. Updating PRL and Profile is temporary at best. PRI Update to 1.40, then to 1.77 did nothing either. This bites.
Wow. When it first happened I was taking my Grandma to the store and half expected to find everybody on XDA freaking out and it had been some national/regional bug that screwed everybody's evo up - Must not have been big, but something to hit a few of us.
It's working just fine this morning after I did a ##3282# and turned up startup cleaner.
I had this same issue the last couple days. Fine today so far. Nyc area btw.
Sent from the void...
I just called them and they told me that they are having network issues in my area and there is an "open ticket." I'm sitting here thinking something is wrong with my phone until 3 other people on sprint told me they couldnt make calls.
same here nyc also did 1.7 pri update i figure thats was the problem now i am stuck with 1.34 (hours and hours took me to go back ) now i dont know what to do should i go back to 1.7 since is every one?
sf103100 said:
same here nyc also did 1.7 pri update i figure thats was the problem now i am stuck with 1.34 (hours and hours took me to go back ) now i dont know what to do should i go back to 1.7 since is every one?
Click to expand...
Click to collapse
Not the PRI. I've been with 1.34 forever, never changed it and I had this issue.
wuclan48 said:
Not the PRI. I've been with 1.34 forever, never changed it and I had this issue.
Click to expand...
Click to collapse
i had 1.40 did update to 1.7 had major problems so i had to go back to 1.34 now i cant get 1.40 back (i dont have problems with 1.34 )
Just be clear
sf103100 said:
i had 1.40 did update to 1.7 had major problems so i had to go back to 1.34 now i cant get 1.40 back (i dont have problems with 1.34 )
Just be clear
Click to expand...
Click to collapse
I updated to the 1.7 PRI last night after I got the error codes figured out. Haven't had a problem, yet, but it's been off this morning anyhow.
Never had a problem with 1.34 PRI, but last night, after installing 1.7, I did a few speedtests in bed and I constantly got 150/190 up and 550/600 down, and before I was getting either better than those, by 50% or worse than those by 50%.
This is a frequent occurrence (at least in New York City). It's annoying but don't worry about it. Anything you try to correct it will only be a temporary fix until it eventually goes away at random.
I've had Error Code 67 come up once in a while since I got my phone. Sometimes it comes in bursts, maybe 4 or 5 in a row. Super annoying. I called Sprint today and they had me update the profile a couple of times which did nothing as I kept getting the error while on the phone with them. They are sending me out a replacement Evo in the mail which I should get tomorrow. I'll report if it fixes the problem. Tech Support mentioned they do have them in stock if anyone else feels like they might be in the same boat.
FunkyAroma said:
This is a frequent occurrence (at least in New York City). It's annoying but don't worry about it. Anything you try to correct it will only be a temporary fix until it eventually goes away at random.
Click to expand...
Click to collapse
I'm in NYC as well and I can't stand this error. If there was a way to supress I would be a lot more happy since if the error pops up while you are typing a number into the dialer it will clear out all the numbers after you press dismiss.
The error code is a result of Sprint working on upgrading the network to increase 3G capacity. I was getting the error messages when my PRI was 1.37, and I have gotten them a few times after updating to 1.77. At first I used to try updating my profile, but I would get the error message again. What worked for me was turning off my 4G (I'm in NYC, and there is a few test towers up), then turning on airplane mode for a minute or so, then turning it off again. For me, the 3G would kick in, and I won't have the error.
I am getting the error on 3G with 4g off or 4g since I got the phone. Sprint rep said it's not normal so Lets see what my replacement does.
looks like it hard us in NYC hard.
anyone else have horrendous battery life today after fixing this? I barely used it, I only got about 8 hours. I fully charged it when i got home, and literally watched it go down from 100% to 80% in 15 minutes..
Hey everyone! I have been having a problem with my Samsung Epic. I am in NYC and recently they have turned on the 4G within the city limits. It was working great last week and I was getting a decent 4G connection (8down, 4up). Now yesterday When I went to activate the 4G radio on my phone it wasn't turning on. The 4G button stays grey and it says its turning on but it never turns green. When I go into the 4G settings its grayed out but its says "turning on..." 3g stays connected during this. Wifi works when I turn that on, but I notice back in the 4g settings menu 4g still says "Turning on".. it doesn't even time out. It completely killed my battery after 20 mins.
I tried a factory reset.. didn't work... Tried the Odin full reset (stock everything).. No dice. I never rooted the phone or did anything to it except install Juice Defender (which cause a whole bunch of problems). Has anyone else had this problem? I am within my 30days so i'm thinking of exchanging my phone.. any ideas??? Thanks in advance!!!
I'm having the same problem
Sent from my SPH-D700 using XDA App
My buddy had the same issue on his Epic. Had to trade it in for a new one.
Sent from my SPH-D700 using XDA App
I had the same problem, get to a sprint store and get your phone replaced. I'm guessing it is a radio problem. May be fixable if the sprint techs actually did something more then just resetting to stock.
Flash the DG27 radio then upgrade to DI07 again. Could also force your phone to re-provision itself.
http://firon.net/xda/modem.d700.tar here's the modem, flash it with Odin as Phone.
This is a longshot, but I've been messing around with a few settings menu and I saw an interesting WiMAX setting.
Goto the dialer, input ##3282#.
Goto WiMAX, enter your MSL code. (find your MSL code by opening an adb shell to your device, use the command "getprop" once in the shell, scroll up and look for a line that says "[ril.MSL]: [??????]")
See what it says under ACTIVATED and REALM, should say "ACTIVATED:TRUE" and "REALM:sprintpcs.com", respectively. If it doesn't that might be where your problem is. Tell a level 2 sprint tech.
Next, try to goto WORK MODE, in there you can set your work mode, mine is at 2 and 4G is working fine, I wish I could tell you what work mode 0,1, & 3 did differently, but I can't locate much info on the net. I'll update this if I find out later...
Hope this can be of some help to you.
My phone is doing the same thing. I don't live in a 4g area yet but I would like to be able to use it when I travel. If there is no 4g service, should the 4g still turn green?
Hey guys,
This is actually my first post here but I do A LOT of reading on this forum.
I didn't quite find anything regarding my question (or at least a solid answer), however, so I've decided to post it up.
Has anyone else experienced a sudden loss of data from time to time out of nowhere?
I go from having Full Green 3G bars to grey bars out of the blue. I've heard the green bars is to let you know that you are connected to Google services but I am not able to access anything that uses data.
For instance, when I open up the browser, I receive an error telling me there is no network connection. When I open up anything else that uses a data connection, Market, News, etc, I receive the same error about there not being a connection.
This would make sense if I was moving and going in and out of service areas, but it happens when the phone is simply sitting on my desk and not moving at all. I usually use it to listen to Pandora while at work and have noticed that the songs cut in and out due to this sudden loss of a data connection.
I went from a Nexus One to the Nexus S and have never, not once, lost my full 3G bars in this same exact location. I personally believe its a software bug of some kind and have high hopes for it being fixed in the future. The N1 had similar issues when it first launched and Google / T-Mo were able to remedy that for the most part.
I am actually on my third Nexus S because the first two had some type of hardware issue; the first one's back button didn't work or light up and the second one had a blown ear speaker and would sound like a blown speaker in a car. As an early adopter, I expected this, so it didn't bother me in the least bit.
ALL of them did the same thing, so I know it is not just limited to my exact phone. This is definitely something with the Nexus S in general (or the current build of Gingerbread).
Can anyone shine some light on this situation? Thanks in advance and keep up the great work here guys!
---------------------------------------------------------------
UPDATE: Here are a few steps that I have taken in order to solve my sudden loss of data issue. I'm not guaranteeing this will work for you, but it has worked for me and a couple of users here on the forum.
Do the following:
Activate / Use the Sim Card that came with the phone (this is to ensure you are using the latest sim cards)
Make sure you have a 4G internet plan. (No t-zones, No web2go -- FULL internet only)
Call T-Mobile and have ask them to Reset your phone with their Towers
Here's a more technical explanation posted by Johoja:
1) Having network selection set to manual ( i.e selecting 302490 or TMOBILE) will result in No Service on a reboot. Solutions: - Have to cycle airplane mode to get it to pick up service (can be done with automatically tasker) - OR Use automatic network selection. (you can force wcdma only but that will reset the SMSC which is annoying if you go in and out of wind away/home areas and you want to roam.)
2) Being in a area with no service for extended periods of time 5+minutes(subway, basement, etc) will result in a dead baseband, meaning once you come into an area with service the phone will not reacquire signal, airplane mode will not work as the baseband is now crashed, cant maunally search for a network. Have to reboot to get signal. Solutions: -Use tasker to cycle airplane mode on and off when in no service areas i.e) search signal 4 minutes, airplane mode on 10 minutes. This will keep the baseband from crashing and possibly save battery. -Use NoBars to accomplish thesamething ( taskergivesyou a bitmore flexibilty of course but harder to use) http://www.appbrain.com/app/nobars-b...omdryer.nobars - Use airplane edit to avoid turning wifi/bt off when airplane mode is on. http://www.appbrain.com/app/airplane...kalti.airplane
3) WCDMA perferred does not work. - No solution
http://www.google.com/support/forum/p/Google+Mobile/thread?tid=747f398a6c1bb2b9&hl=en&start=40:
I read one users response on a different thread regarding something similar to the issue that I am having.
They said T-Mobile told them to get a newer sim card and that this may remedy the problem. In my case, this has been the only constant in the 3 phones that I have been through. I have had the same sim card for about 3 years or so now.
I will try activating the sim card that came in the box with T-Mo to see if this remedies the problem. Since I'm at work right now I will have to try when I get home later.
Does anyone think this will have any affect what-so-ever?
The galaxy s phones when first released, all variants, had issues of signal dropping from full to zero bars while sitting in one place. I remember because there were YouTube videos of it All over and it was shortly after the apple antenna issue.
Not sure if or how it was ever resolved. But it seems that Samsung may just have this type of radio baseband performance if we see all these individual units doing this. I don't know maybe others can respond.
I have the same issue as the OP. I travel to the same location weekly with NEXUS ONE, signal never drops in the T-MO Country here locally, and streaming CNET POD CAST never a hiccup, however, with the new NEXUS S, I would lose DATA Connection only, while the 3G will show full signal. I had to reboot the phone to get the DATA back.
is it the S issue or 2.3 issue?
food for though....
If you have T-zones or Web2go or Phones 1st web, you will have problems
I had the same problem too, now I fixed the problem. The thing was that had the wrong data plan on the NS, i had my old web plan from my hd2 which seems like different from the one for the NS. I restarted my phone after 5 mins off and now i have my internet working beautifly. A T-Mobile rep said that it was an error in the system that made the phone think that that was the right plan for the NS for a few. A glitch you may say, but all you have to do is put the right data plan that all, easy. Hope this helped and have a wonderful holidays everyone.
Sent from my Nexus S using XDA App
this is happening to me too, last night for a little while and today for about hte last 4 hours can't get connection back. i have full white bars, with 3g icon but can't access anything
So I activated the new sim card last night and I'm still having the same problem. Albeit it doesn't happen as frequent, but it still does it nonetheless.
I will call T-mo again to verify my plan. I am on a 1500 Minute Family Plan which includes unlimited data and messages. I will see if they need to tweak something and let you guys know if this remedies the problem.
Ok, it seems like the issue has been resolved after I spoke to T-Mobile earlier today.
The rep on the phone verified that the data plan I was on was in fact the correct one. He said he was going to reset the signal from the towers to my phone to see if this would resolve the issue. He asked me to turn my phone off for about 15 seconds after we hung up.
Since then, I haven't seen the problem arise again so my guess is that it somehow fixed whatever was going on.
I'll let you guys know if this changes and the problem occurs again.
Sent from my Nexus S using XDA App
peakaboohaha said:
I have the same issue as the OP. I travel to the same location weekly with NEXUS ONE, signal never drops in the T-MO Country here locally, and streaming CNET POD CAST never a hiccup, however, with the new NEXUS S, I would lose DATA Connection only, while the 3G will show full signal. I had to reboot the phone to get the DATA back.
is it the S issue or 2.3 issue?
food for though....
Click to expand...
Click to collapse
What's with the CAPS? ?
On topic: i have a captivate and I can confirm that all galaxy S phones had droppend data. An official ota update fixes it so maybe you guys need to wait for something official. Isn't there a new firmware for the nexus S already? Try flashing that and see if you still have issues.
Sent from my GT-I9000 using XDA App
Doesn't every android phone from samsung have this problem?
I know the Moment has that problem, after 3 updates samsung called it quits, I still have to reboot mine 2 to 3 times a day for data lockups.
@timur525 Yea, I'm already on 2.3.1.
I manually updated the first hour it came out hoping that it would solve the issue. The problem was still there after the update.
Sent from my Nexus S using XDA App
I have exactly the same issue as the OP. Extremely annoying to reboot the phone every time it happens. One thing I have noticed is that my phone doesn't know its number. If I go to settings, about phone, the number says unknown.
Sent from my Nexus S using XDA App
Memnoch30 said:
I have exactly the same issue as the OP. Extremely annoying to reboot the phone every time it happens. One thing I have noticed is that my phone doesn't know its number. If I go to settings, about phone, the number says unknown.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
That shouldn't affect anything. My number shows up in status.
I had this issue resolved a few months ago as the push-to-talk app Tikl requires this in order to use it.
I was having the problem even with my number showing up. Call T-Mobile and have them reset you with the towers like they did for me and see if that helps you too.
Sent from my Nexus S using XDA App
I posted about this same issue on wrong section of the forum. Ive had this issue ever since samsung vibrant. I have applanet installed on my phone and some of the app that i installed accessed my apn and totally changed my apn setting to "Sirious application disabled.epc.tmobile" or something like that so i wyped everthing off from the phone and so far i havent had the issue ever since yesterday. Also i had the locale and language setting to korean so im thinking that might be causing it also.
Sent from my Nexus S using XDA App
adamr240 said:
Doesn't every android phone from samsung have this problem?
I know the Moment has that problem, after 3 updates samsung called it quits, I still have to reboot mine 2 to 3 times a day for data lockups.
Click to expand...
Click to collapse
That's what I remember too. I think its just an issue with the radio Samsung uses in all their phones. Might not be a way to fix it if even their new phones like the nexus s still have this issue. They prob would have tweakdd it by now if they could.
Same problem here. Xmas eve on shift and I have a phone that had no connection whatsoever (not even phone capabilities) this may be the one thing that takes the phone back. (If it happens again)
robstunner said:
Same problem here. Xmas eve on shift and I have a phone that had no connection whatsoever (not even phone capabilities) this may be the one thing that takes the phone back. (If it happens again)
Click to expand...
Click to collapse
Have you called T-Mobile to see if they can give you a reset to the towers?
I had this done yesterday afternoon and haven't had the problem again since.
Also, if you'really using an old sim, I would suggest activating the one the phone came with just to be on the safe side.
If that doesn't help you then I would at least wait until just before your return period ends to see if there will be an update to address the issue.
Sent from my Nexus S using XDA App
Never had this problem with the captivates I've had.
adamr240 said:
Doesn't every android phone from samsung have this problem?
I know the Moment has that problem, after 3 updates samsung called it quits, I still have to reboot mine 2 to 3 times a day for data lockups.
Click to expand...
Click to collapse
Sent from my Nexus S using Tapatalk
Epiksol said:
Have you called T-Mobile to see if they can give you a reset to the towers?
I had this done yesterday afternoon and haven't had the problem again since.
Also, if you'really using an old sim, I would suggest activating the one the phone came with just to be on the safe side.
If that doesn't help you then I would at least wait until just before your return period ends to see if there will be an update to address the issue.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Ill give them a call on Sunday
Sent from my Nexus S using Tapatalk
Hey guys, I'm hoping somebody might be able to lend me a hand.
After applying the Temp-Root to my EVO Shift (GB, 2.3.3 (temp-root found here)), I'm getting the following error message:
Data Call Failure
Error Code 67: Unable to establish wireless data connection.
Has anybody seen this message? It comes up randomly it seems. I'm still able to connect to the internet via wireless. I'm not really sure what the deal is. It's similar to another one going around, but the other refers to the username/password. This one does not.
I have googled the error message, but almost everything I come across is a mass hysteria of confused people. I've tried the things I've found.
I haven't tried rebooting, yet, as that'll kill my temp-root (doesn't work in most cases anyhow, from what I've read). But, I'm willing to try it tonight if no other options are available. I've tried updating profile and prl, but issue remains. Not really interested in getting Sprint support involved, as from what I hear they're mostly a bunch of... uhm... funny people.
Any help is appreciated!
I should also note: This may have nothing at all to do with the Temp-Root. As far as I can remember, it worked fine for the first day (I applied it about 2 days ago, I think). However, I didn't do anything that day that required use of the Wireless connection (but wireless was still enabled).
i got that error once and just rebooted and retemprooted and havent gotten it again
Upadte profile, thru settings
Sent from my PG06100 using XDA App
-somebody- said:
i got that error once and just rebooted and retemprooted and havent gotten it again
Click to expand...
Click to collapse
I'll try this tonight if no other resolutions come up (not at home currently). Thanks for the suggestion.
madplaya1 said:
Upadte profile, thru settings
Sent from my PG06100 using XDA App
Click to expand...
Click to collapse
As per my original post, I have already updated both profile and PRL. Thanks for the suggestion, just the same.
Edit: The problem may be due to billing issues. Will wait for that to get fixed and see if that fixes is. Will report back.
Another Edit: Does appear this is due to billing issues. Seems to be working just fine again, re-rooted and all.
Was getting this Error message for about a half a day a few weeks back. Updated PRL and Profile, didn't fix the issue. Called Sprint, turns out they were doing some work on the towers. Rebooted the phone and all was good. You might want to try and put the phone in Airplane mode for a few minutes. Then turn off Airplane mode, see if that helps.
prboy1969 said:
Was getting this Error message for about a half a day a few weeks back. Updated PRL and Profile, didn't fix the issue. Called Sprint, turns out they were doing some work on the towers. Rebooted the phone and all was good. You might want to try and put the phone in Airplane mode for a few minutes. Then turn off Airplane mode, see if that helps.
Click to expand...
Click to collapse
I actually tried all of that. In my case it seemed to be a billing issue, because as soon as that was cleared up (the phone didn't have service, and I didn't realize til' I tried to make a call) everything worked fine... and has since. Thanks, though.
No problem, here to help when I can. Glad you got it sorted out.
MikShifted on XDA Premium APP
TEAM MiK
Mik ROMs Since 3/13/11
I have a problem with my 6p where the signal just drops to nothing (Looking for service) and 3 or 4 seconds later it reconnects to a good LTE connection. The problem is not my connection as I live in a good area. I was rooted with xposed but for ****s and giggles I went back to complete stock and it is still happening.
I have reset the APN settings to no avail. Is this a thing that is known to this phone? Should I get a replacement? It started just recently it seems as I have had this phone since launch.
What sucks is, is that this phone is absolutely perfect (or was) and I dont want to get sent a phone with screen issues.
EDIT: I ended up getting an RMA and everything is hunky-dory.
holmgren said:
I have a problem with my 6p where the signal just drops to nothing (Looking for service) and 3 or 4 seconds later it reconnects to a good LTE connection. The problem is not my connection as I live in a good area. I was rooted with xposed but for ****s and giggles I went back to complete stock and it is still happening.
I have reset the APN settings to no avail. Is this a thing that is known to this phone? Should I get a replacement? It started just recently it seems as I have had this phone since launch.
What sucks is, is that this phone is absolutely perfect (or was) and I dont want to get sent a phone with screen issues.
Click to expand...
Click to collapse
What radio version are you on? You can flash a different version in fastboot and see if it helps.
murphyjasonc said:
What radio version are you on? You can flash a different version in fastboot and see if it helps.
Click to expand...
Click to collapse
Im on the newest one. Do I just extract it out of the 6.0 image file and just flash it over the top of the existing one?
I forgot to also mention that I tried getting a new SIM card from Verizon but that did not fix it either.
holmgren said:
Im on the newest one. Do I just extract it out of the 6.0 image file and just flash it over the top of the existing one?
I forgot to also mention that I tried getting a new SIM card from Verizon but that did not fix it either.
Click to expand...
Click to collapse
Yeah. Extract it and flash it over the top in fastboot.
Did you ever find a remedy for this problem? I'm having the same issues on t-mobile so its definitely not network or a similar related issue. Did flashing the radio from the 6.0.0 rom fix the issue? I already tried several different 6.0.1 radios and a radio from 7.0 but to no avail. I'm about to try it and if it doesn't work I'm getting rid of this phone.
I'm going to assume you mean you'll be on LTE for the longest time then all of a sudden signal completely drops then comes back on, but without the LTE signal showing near the bars, so you'll have to airplane mode, then switch mobile data on and off, then do a restart. If this is the case. That has been a documented CM13 issue for the longest time. I had the same issue with the HTC M8...
Sent from my Nexus 6P using Tapatalk
jxcorex28 said:
I'm going to assume you mean you'll be on LTE for the longest time then all of a sudden signal completely drops then comes back on, but without the LTE signal showing near the bars, so you'll have to airplane mode, then switch mobile data on and off, then do a restart. If this is the case. That has been a documented CM13 issue for the longest time. I had the same issue with the HTC M8...
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I am on LTE but as the OP said the signal randomly drops completely for 4-5 seconds them comes back LTE and all. I don't have to reboot or anything. This doesn't have to do with cm13 though, I've tried flashing back to full stock and I still have the problem there too.
Sent from my Nexus 6P using XDA-Developers mobile app
Damn man...I have no idea - possibly radio like the guy above my post mentioned. Wish I were of better assistance.
Sent from my Nexus 6P using Tapatalk
I've managed to get a logcat at almost the exact time the signal drop happens, I had to put it in a Zip since the Txt document was too big for the thread. The drop happened in the last couple minutes. I'm hoping someone here with more experience than me can help me solve this issue. Thanks in advance.
Having the same issue on T-Mobile smh... it gets annoying at times!
Sent from my Nexus 6P using XDA-Developers mobile app
Same problem here. On Verizon
Anyone find a fix? I'm on the latest Android N Beta on Tmobile and still have the issue.