After running on a stock ROM(but rooted /w TWRP), I decided that I wanted to install a custom ROM so that I could tether if needed. Well, big mistake. I wiped stock and accidentally wiped my stock backup when going to flash a custom ROM and so far I've tried XenonHD, Jedi X19, IllusionROM, and now I'm on a Stock-Tweaked. So far, every single ROM has caused massive delays in receiving SMS messages and syncs from stuff like gmail.
Data is definitely working, and i've tried both the epc.tmobile.com and fast.tmobile.com APNs but my phone keeps hanging when it trys to send some texts and, if I have texts "waiting" to be delivered to my phone, I only receive them once I turn on my phone screen or only if the screen is on. So what the hell is going on here?
I am not installing anything on the ROMs aside from what's coming with them. The issue presents itself immediately after I boot for the first time and set up gmail.
It seems that if I go to 4G/3G/2G mode only the issue doesn't persist. Or at least not as much. But then I can't use LTE! =/
I've tried multiple ROMs that were TW and multiple that were simply AOSP. So 4.1.2, and 4.3 roms. I even accidentally flashed a 4.2.2 AOKP ROM.(for the Note 2, of course). I am not back to the stock Odin recovery with a root injected stock image but i'm still suffering from the same problem =/. This really sucks. Is there a way to completely wipe EVERY trace of an older Android install off of the phone?
I haven't tried the total stock bare bones one yet because the mirror is so slow, it's currently at 641 / 895 MB downloading and has about an hour left. It's the 4.1.2 June release.
I'm attaching a logcat to this post as well, from when I had the screen on, locked it, turned the screen on, and unlocked the phone.
I just realized the logcat is about 58k lines long, so I'd start from the bottom and go up since that was the most recent phone activity of when I actually went through the motion described earlier.
Let me know what happens when you try the stock sw.
Sent from my SM-N900T
I had this problem is well. I had to call at T Mobile I told him I was getting long delays in my text messaging, yes I know you're not getting delays it's only happen to you when your phone is in sleep mode. I told him I already did all the normal stuff to correct the problem. they reset their network connection. That fixed it for me. Hopefully your problem is that simple.
Sent from my SGH-T889 using XDA Premium 4 mobile app
Related
I'm curious if others are seeing their EVO reboot with random use. It doesn't seem to be related to one specific application although it is hard to say if a background app is the cause. I will be using navigation or an Internet-based app, then the screen goes black and the phone reboots.
I originally thought it was due to rooting, but I'm seeing it on different ROMs. I've wiped the cache and data when flashing the new ROMs and I've tried running with limited apps loaded with my recent move to the OMJ ROM. Everything actually runs great with the exception of the reboots.
I'm posting the issue here since it doesn't seem to be ROM specific and I'm curious if it may be hardware related. Is there a tool that would allow me to easily catch a log of the potential error to seek further help? A point in the right direction would be greatly appreciated.
I'm running stock 2.2 no root, and with gps on my phone reboots in the middle of 911 calls. (Thank God I wasn't calling about an immediate emergency) but it happened twice, once when I called and the other when they called me back. After turning off GPS, it worked fine. I thought this was a bug in 2.1 before update1, I didn't receive the problem until the 2.2 update.
adb logcat might see an error, but I'm not really sure.
Seeing it here. Not Rom or application specific.
try a factory reset.
That's scary news about the reboots during 911 calls. I can't say that I tested that as a trigger for the reboot and I hope I don't have to in the near future. However, it makes me curious if it is related to the phone's interaction with the Sprint network. In your case your 911 call may have been a direct trigger whereas my reboots are seem indirect while I'm using my data plan.
One reason for my reboot was due to me getting the Error Code 67 "Your PCS Vision username and/or password may be incorrect" when trying to tether (USB or hotspot). Rooting allowed me to tether using 3rd party apps, but there may be the underlying problem with my account.
I also should have mentioned that the reboots happen with GPS on as well as off. I typically have it off to save battery life. I've also done factory resets each time I've changed or updated my ROM.
Thanks for the feedback and suggestions so far. I'll try logcat and continue to monitor the forum for advice. I'll also post back any answers I may find elsewhere.
Thanks again.
I had a reboot tonite, phone was just sitting on table off charger about 90% battery, and I heard the Sprint screen come on looked down and noticed phone was booting up....no idea why first time I've noticed this.
Stock froyo no root...unfortunately :'(
AzmatEQ said:
That's scary news about the reboots during 911 calls. I can't say that I tested that as a trigger for the reboot and I hope I don't have to in the near future. However, it makes me curious if it is related to the phone's interaction with the Sprint network. In your case your 911 call may have been a direct trigger whereas my reboots are seem indirect while I'm using my data plan.
One reason for my reboot was due to me getting the Error Code 67 "Your PCS Vision username and/or password may be incorrect" when trying to tether (USB or hotspot). Rooting allowed me to tether using 3rd party apps, but there may be the underlying problem with my account.
I also should have mentioned that the reboots happen with GPS on as well as off. I typically have it off to save battery life. I've also done factory resets each time I've changed or updated my ROM.
Thanks for the feedback and suggestions so far. I'll try logcat and continue to monitor the forum for advice. I'll also post back any answers I may find elsewhere.
Thanks again.
Click to expand...
Click to collapse
Correction... I meant to say that the reason I rooted (not rebooted) was to get tethering without running into the Error Code 67. I tried the various solutions posted for the Error Code 67, but nothing seemed to work. But I'm curious if this may be part of the underlying issue if my device reboots based on a faulty account configuration when using some aspect of the Sprint network.
sprink0281 said:
I had a reboot tonite, phone was just sitting on table off charger about 90% battery, and I heard the Sprint screen come on looked down and noticed phone was booting up....no idea why first time I've noticed this.
Stock froyo no root...unfortunately :'(
Click to expand...
Click to collapse
The exact same thing happened to me last night. I sent a text, switched to my GMail and then boom. Error message about failure to send an SMS then reboot. Stock unrooted FroYo.
I had reboots only when using Undervolted kernels.
Seemed to be triggered by GPS + Phone call.
Yes, I was also having this problem. Definitely GPS related. Usually it would happen only if I was using the GPS for a long amount of time (navigating) - so I imagine it may be conflicting with cellular data if I received a txt while navigating or something. Who knows.
It was driving me crazy because A. I got lost and B. It started rebooting constantly and would randomly get caught in a boot-loop. I even had the problem after wiping EVERYTHING (even my SD) and reinstalling various ROMs (I tried 5 different ones).
The only solution I found in the end was to find the latest radio and wimax updates, wipe, re-install those - and then install the ROM again.
GPS may be a symptom, but not a cause for me since I typically have GPS off. I find that it typically happens when I'm using a networked based app, like the web browser. Following your post I turned on the GPS, started the navigation app and found that my EVO rebooted after the same amount of time I was experiencing with GPS off.
The more I think about it, it does feel like I just assume that it will reboot after a certain amount of time passes (regardless of app). GPS and Internet are two uses where I will have the screen on for more than just checking email and etc.
Your reply gave me hope and I wiped, reset and reinstalled today. All seemed well and then... auto-reboot. This is driving me nuts. I'm seriously considering reverting back to stock to see if that stops it.
AzmatEQ said:
GPS may be a symptom, but not a cause for me since I typically have GPS off. I find that it typically happens when I'm using a networked based app, like the web browser. Following your post I turned on the GPS, started the navigation app and found that my EVO rebooted after the same amount of time I was experiencing with GPS off.
The more I think about it, it does feel like I just assume that it will reboot after a certain amount of time passes (regardless of app). GPS and Internet are two uses where I will have the screen on for more than just checking email and etc.
Your reply gave me hope and I wiped, reset and reinstalled today. All seemed well and then... auto-reboot. This is driving me nuts. I'm seriously considering reverting back to stock to see if that stops it.
Click to expand...
Click to collapse
Don't go back to stock. I did and it did not fix the rebooting problem. Now I have the rebooting problem and don't have root anymore. Out of the frying can and into the fire.
What's funny is that my phone went through a few days where it would randomly reboot, and this was before I rooted. When it rebooted for the second time in a meeting, I pulled the battery, and didn't put it back in until the meeting was over a few hours later. Don't know if that did anything, but it hasn't rebooted on its own since.
Sent from my blah blah blah blah
Having same issue and my theory is that its sd card related in my case at least... I think it might have to do with froyo netarchy based kernals found in most of the newer froyo roms combined with a slow sd card. (on hardware rev 2)... try flashing a 2.1 rom like fresh 1 or one of the 2.2 roms with an htc based kernal like the am evolution or cyanogen with snap5 or 7.11 (onyl 7based kernal ive tried so far, was panicking because i thought my evo was wrecked). those have both worked for me and i had that issue with 1.3 baked snack, fresh 3, evio and damage control. got random reboots when phone is totally idle, in use, charging or not. evio runs super smooth but the restarts...)
edit for spelling and update roms that gave me the reboot issue.
+1 for random reboots here... it is CERTAINLY more prevalent during GPS use, but I've gotten it without.
Fresh 3 + King BFS#4 got me in a bootloop requiring wipe reflash, standard baked snack 1.5+whatever kernel it comes with has been doing it.
I dig the battery life I was getting... but if undervolting is causing this... ugh.
I'm also getting the boot loop problem. Stock 2.2, all updates.
I've even done the hard reset.. twice!
I tried to follow it with LogCat, but reboot disconnects adb. I was thinking it was the SprintZone app. The P.O.S. app is doing all sorts of non-sense while booting, but eventually it'll reboot around the 11th time and freeze at the "htc EVO 4G" screen.
I wish we could get some resolve here D;
Random Reboots
Thanks for all the input and I'm sorry to hear that I'm not alone, but it is a bit comforting to know I'm not the only one that is frustrated.
I took gleax's advice and I dropped down to the stock 2.1 release found in the thread number 715915. (Sorry, the forum won't let me paste the link.)
I did the required wipes prior to installing the new ROM and I'm still seeing reboots. I now see the OTA update for Android 2.2 and I'm tempted to accept, then send the phone back to Sprint in the even this is a hardware issue. I'd prefer not to, but there doesn't seem to be a way to identify the issue and work towards a resolution. I've tried logcat, but the log seems to start clean after each reboot. That being the case, I don't know how to capture the log leading up to the reboot that would help identify the issue. Any suggestions on a logging tool and where to post to help several of us that are seeing this issue?
Gleax suggested this is may be SD related, so I bought a class 4 card in addition to dropping down to 2.1. I'll give that a shot and try another clean 2.1 install. I'll post the results here in the event they may help others. I'll likely give it a week before unrooting and seeking help from Sprint. I really need a usable device more than I need root access (although both would be ideal).
I had this problem on a very regular basis when I was running OTA 1.32, 2.1 android.. but since I rooted and went to SteelH's stock 2.2, no issues at all. Updated radios when I did that as well.
Hrm, I may have to try flashing to a stock build for awhile... it'll KILL me, but even fully wiping, new radios, cyanogen, still get crazy reboots.
So I updated through kies to uvlh1, and the phone seemed smooth and responsive at first. But after updating all the apps through google play and now whenever I add/click the accu weather, or other widgets, TwLauncher crashes and the screen goes black for at least 1 minute before becoming useable again. I tried reflashing through odin but it made no difference. Only a factory reset (data clear) remedies the problem. Can anyonr confirm/ help? (besides installing a different launcher)
Edit: the problem seems to be the my account app. After updating it, the phone became unresponsive for a few seconds, and the problem resurfaced.
next time check how much free memory it has left
if it works fine, until you download apps from Android Market
then that means one of the Apps from Market, is most likely the cause of the problem
so, instead of letting it automatically install all the Apps you had in the Market
do it manually, and choose specific apps that you use to install
do it one at a time, and see how the phone responds, rinse and repeat until you find the faulty App
This is the very same reason why i came back to CM9 from CM10, found several Apps that were not behaving properly on JB, but works without any problem on ICS
many Apps has since been updated to be JB compatible, so keep an eye on your favourite apps, or those must have installed apps to make sure they are compatible with JB
AllGamer said:
next time check how much free memory it has left
if it works fine, until you download apps from Android Market
then that means one of the Apps from Market, is most likely the cause of the problem
Click to expand...
Click to collapse
The memory is fine, but after reinstalling every app except the my account one, the error seems to have vanished. However, id like to know if anyone has the same problem. Because otherwise, my phone is crazy and i need to call tmobile for an exchange.
So don't update my account
Sent from my SGH-T989 using xda app-developers app
I have noticed that the new Facebook app have some bugs that makes the phone to crash. I get a white screen and then later it says fb stop responding. but then again I have noticed some lag on the this update and on the one before.
I think they have a new app that is kinda like my account but it uses the browser use that instead. the only thing you cant do right now is pay your bill but they will be adding that feature soon.
luperez said:
So I updated through kies to uvlh1, and the phone seemed smooth and responsive at first. But after updating all the apps through google play and now whenever I add/click the accu weather, or other widgets, TwLauncher crashes and the screen goes black for at least 1 minute before becoming useable again. I tried reflashing through odin but it made no difference. Only a factory reset (data clear) remedies the problem. Can anyonr confirm/ help? (besides installing a different launcher)
Edit: the problem seems to be the my account app. After updating it, the phone became unresponsive for a few seconds, and the problem resurfaced.
Click to expand...
Click to collapse
Thats wierd i had the same problem but vice versa, see im in US Tmobile towers and my device came stock UVLH1 and when i did the kies thing ,,, it gave me UVLE1 so my data and wifi were not functioning correctly one or the other had to be turned off so that i could make or recieve call on data or download and browse on wifi... i found the UVLH1 site and flashed the radio and know both work . maybe u need to flash UVLE1 so that ur problem disapers:laugh::good:
Within the last couple of weeks, I have to enable/disable airplane mode to get my data to work. It's random throughout the day. I've checked to make sure mobile data is enabled when it's not working, and it is. It shows 4G at the top, but just won't send/receive data. I wasn't having this problem when I first upgraded to JB, so I'm not sure what's going one. Anybody have similar problems/tips?
stbtigerr said:
Within the last couple of weeks, I have to enable/disable airplane mode to get my data to work. It's random throughout the day. I've checked to make sure mobile data is enabled when it's not working, and it is. It shows 4G at the top, but just won't send/receive data. I wasn't having this problem when I first upgraded to JB, so I'm not sure what's going one. Anybody have similar problems/tips?
Click to expand...
Click to collapse
Are you running a ROM other than stock? There have been hiccups similar to this on some AOSP ROMs, but I can't immediately think of anything that would be causing this on a (mostly?) stock ROM.
smelenchuk said:
Are you running a ROM other than stock? There have been hiccups similar to this on some AOSP ROMs, but I can't immediately think of anything that would be causing this on a (mostly?) stock ROM.
Click to expand...
Click to collapse
Sorry, I meant to stay I'm completely stock in the OP.
common issue with note II and my GSIII
looks like the same issue is happening on the Note II - thread.
For me, it seems like it happens more frequently when I leave a wifi connection; I have to enable airplane mode & disable it to connect to 4G LTE (band 14). I'm not rooted, so I can't run the logger that's suggested in the Note II thread. FWIW: it appears to affect me with or without Onavo VPN running.
Any suggestions would be helpful. My next thought is to figure out a way to ping/test the connection to the AT&T tower/gateway next time I run into the issue before using the airplane mode fix.
my GSIII config:
AT&T version
Jelly Bean 4.1.1 Stock (Samsung) ROM
Kernel 3.0.31-274808
Baseband I747UCDLK3
My phone seems to do this all too often on a daily basis. I check that I have no received emails, tweets, facebook notifications, etc. The problem is my data uplink arrow keeps flashing and it hangs there. This is usually remedied by putting my phone in Airplane mode and switching back it usually works but there have been times when I have empty bars with no data nothing, but it can be fixed by switching mobile network types from WCDA/GSM back to LTE. Anyway this can be fixed, or this actually a Kit Kat issue with the Note 3?
I'm on Stock Kit Kat Unrooted (unfortunately) because I updated before wanting to root and now I don't want to trip KNOX. I have also run a factory reset on my phone (through the bootloader) but it didn't fix the problem.
Is anybody else having this trouble with their Note 3?
I have this issue too. I'm rooted on Darthstalker v6. It happens daily. I just toggle airplane mode on and off and wait ten seconds. I've reinstalled this rom twice and the issue is still there. Hopefully someone can help.
Same issue here! Stock, unrooted. Must be a kit kat issue, I don't remember having it on jelly bean.
Anyone else with the same issue? Chime in
Sent from my SM-N900T using xda app-developers app
Yup.....been noticing this happen too.....was hoping it was a tower issue soon to be resolved....starting to not sound that way....blah
P.S just started happening (or me noticing it) in the last 2 or so weeks
It's a known bug in android 4.4.2. The new update 4.4.3 has a frequent data connection dropout fix in the change log. Hopefully we get some leak or something for it soon. Now that the s5 is out.
Sent from my SM-N900T using Tapatalk
I didn't notice the data drop out until I tried a KitKat rom. When I restored back to the jellybean rom I was using the data drop out continued. So I ended up wiping and flashing the same jellybean rom and still notice the data drop outs.
Sent from my SM-N900T using xda app-developers app
I have the same issue from the last 4.4.2 update, when the phone is in standby for long time the data connection drop out, or time in time the phone scan the network and some time back to normal after some second or keep scanning and need reboot. when I check the network mode I found all option unselected, I select lte mode and the phone do not respond and have to reboot. I reinstalled 4.4.2 with kie and Odin but same issue . Samsung representative told me that the issue is from T-Mobile , that the phone is ok, and T-Mobile told me that the issue coming with the update from Samsung and affected to note 3 and s4. Who has the fault? my temporal free solution until the next update was replace the sim card in the T-Mobile store. I did yesterday and until now the phone have been ok with the data connection up all time. when it scan the network back to normal with not data drop out.
Last thing, go to wifi - advance option and I put disable (keep wifi on during sleep) and (always allow scanning) maybe these can avoid the scan the network time to time.
I have an HTC M8 converted to GPE, running stock rooted Lollipop 5.0.1. I started having this problem fairly recently, previously everything was fine.
With my screen off, all push notifications are delayed significantly (at least 10-15 minutes on mobile data, 20-30 on wifi). Shortly after I turn the screen on, all delayed notifications start coming through. An interesting point to note is that on mobile data, I don't seem to lose the connection at all (as soon as I unlock my phone, I am connected to the internet) but with wifi, I get connection errors for the first 5-10 seconds.
So far I've tried: factory reset, reinstalling firmware (tried latest Sense, latest stock, and a few older versions), switching to a different ROM (SkyDragon). I'm running out of things to check because I've reinstalled everything that can be reinstalled. I've checked all the silly little things like restricting background data and I don't seem to be using any settings on my phone that could cause trouble. I've also tried several "push notification fixer" apps to no avail.
This is seriously making my phone useless to me, so I would appreciate any help. Thanks a lot.