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.
New user, first post, if I am missing info then I apologize.
I have the tmobile galaxy s 3 SGH-t999.
Started looking around at different roms, etc, ended up with trying the cyanogenmod 10 first.
Did the required steps, used oden to load the clockworkmod recovery.
Wiped/factory reset, then loaded up the rom. Seemed to work pretty well other than some issues with the cam crashing (seperate issue which I researched and believe I have the answer to). But overall the problem was that intermittently the inbound audio on calls sounded robotic, and reverberating. Also dealt with 4 hour battery life. Tons of info to address later when this issue is corrected however.
Have been digging around on forums, and see this issue, but no articles yet (that i have found) addressed for the SGH-t999.
Ended up re-wiping the phone and put on the liquid smooth rc9 (d2tmo).
So far it appears i am having basically the same exact issues that occurred in cyanogenmod. If I reboot the phone, it will continue. Then for whatever reason the next few calls or so later that are sent or received it sounds fine. Then back to robotic.
End user can hear me fine. The audio issue is just for inbound voice.
Tried to factory reset again, still the same issue.
I have installed the google pack to be able to use play store, etc. Perhaps this is causing the issue?
I did try to get the log cat, but could not replicate the issue while running it, so I am not sure if it would be of any use or not.
Also, this issue does not make a difference whether bluetooth is enabled or not. Am not doing wifi calling, have not tested that yet.
Again very sorry if this article is incomplete.
Thanks in advance for the help!
Resolved
tsm233 said:
New user, first post, if I am missing info then I apologize.
I have the tmobile galaxy s 3 SGH-t999.
Started looking around at different roms, etc, ended up with trying the cyanogenmod 10 first.
Did the required steps, used oden to load the clockworkmod recovery.
Wiped/factory reset, then loaded up the rom. Seemed to work pretty well other than some issues with the cam crashing (seperate issue which I researched and believe I have the answer to). But overall the problem was that intermittently the inbound audio on calls sounded robotic, and reverberating. Also dealt with 4 hour battery life. Tons of info to address later when this issue is corrected however.
Have been digging around on forums, and see this issue, but no articles yet (that i have found) addressed for the SGH-t999.
Ended up re-wiping the phone and put on the liquid smooth rc9 (d2tmo).
So far it appears i am having basically the same exact issues that occurred in cyanogenmod. If I reboot the phone, it will continue. Then for whatever reason the next few calls or so later that are sent or received it sounds fine. Then back to robotic.
End user can hear me fine. The audio issue is just for inbound voice.
Tried to factory reset again, still the same issue.
I have installed the google pack to be able to use play store, etc. Perhaps this is causing the issue?
I did try to get the log cat, but could not replicate the issue while running it, so I am not sure if it would be of any use or not.
Also, this issue does not make a difference whether bluetooth is enabled or not. Am not doing wifi calling, have not tested that yet.
Again very sorry if this article is incomplete.
Thanks in advance for the help!
Click to expand...
Click to collapse
Ok, after 4 different roms, and lots of testing, I finally figure it out.
Using Voxer caused the issue. As soon as a voice message is sent using voxer, the problem starts immediately, and is correct by a reboot. Issue immediately returns once Voxer is used.
Any idea of how to work around this, besides the obvious? =)
I just got an LG G3 last friday (Black Friday) on T-Mobile (got tired of Sprint). Anyway for the most part this phone has been great. A minor glitch with a game (possibly from porting it's data over from my S3). The main problem I have is with the WiFi.
First off WiFi calling sucks. If I don't have 3 or more bars on my WiFi connection the call gets fuzzy. During one call that was clear it just randomly dropped. So that isn't cool.
Secondly, if I connect to a WiFi network at home or work or where-ever and then go somewhere else and come back or go to another place with a network I want to connect to it won't connect at all. It will show all the networks and give me the option to connect. But instead of connecting it will try to connect for a long while and then just give up. I cannot get connected again until I reboot.
I have tried the suggestions found on this thread (and other places): http://forum.xda-developers.com/lg-g3/help/lg-g3-wifi-issues-t2829811
No luck with those suggestions. Which include the following:
Turn off and back on the wifi radio.
Disabling the "wifi signal is weak" option.
Disabling the battery saving for wifi.
Forgetting the network (my network list was automatically imported from my Google account).
Installing the "WiFi Manager" app and enabling the 5GHz channels (US) and changing 2.4GHz channels to "Complete".
Made sure that "Internet unavailable" option is disabled.
Made sure that "Keep Wi-Fi on when screen is off" is set to "Yes".
Disabling NFC.
Disabling BlueTooth.
Disabling Wi-Fi calling.
I don't have problems with a weak signal. So I am perplexed. My Samsung Galaxy S3 worked just fine on these networks. Restarting always seems to allow me to connect again. But I shouldn't have to restart every time I want to connect to WiFi.
All of my other wireless devices connect just fine in the household (a PS3, my fiance's Moto X, my old S3, MacBook Pro, Lenovo Windows 8 laptop, an HP running Ubuntu 14.10, and another Lenovo running Ubuntu 13.04).
Why is an older model phone doing so much better than the G3? Both phones are rooted (old and new). Does anyone have a fix? My phone is currently running LG's factory rom "D85110m". That is with Android 4.4.2 (my old S3 is on a cyanogen rom of the 4.4.x series as well).
Please help me fix this. Otherwise I might return it for an S5.
Thanks!
**** Update ****
Per my below post, it seems I have fixed my problem. I ended up doing two factory resets, unrooted, and did a final factory reset to fix the problem. Then I switched to the PurpleDrake method to root it the second time (and it worked really well without any issues).
Good luck everyone!
**** End of Update ****
Try to factory reset the phone. I don't know what version you are on but I assume its 10m
xmagiicsx said:
Try to factory reset the phone. I don't know what version you are on but I assume its 10m
Click to expand...
Click to collapse
It is on 10m. Do I need to unroot before I do the factory reset? I have never had to do one before.
So it appears that doing a factory reset does not fix it. I guess I am taking it back and having them replace it. And I will demand it be a brand new one since I just got this phone a little over a week ago.
SOLVED!!!!
Ok, so I finally got it fixed. Albeit accidentally as I didn't expect it to be fixed at this point.
Here is what I ended up doing:
Two factory resets.
Unrooted the phone (via these instructions: http://www.androidrootz.com/2014/07/how-to-unroot-lg-g3-all-variants.html).
One last factory reset at T-Mobile store by me (because they forced me to).
The wifi did not start working correctly again until after that very last factory reset that I did. The unroot process also does a factory reset. But, and this may be key, it downgraded my phone to 10c from 10m in the process. I then did an OTA to 10m after the final reset.
I unrooted it because T-Mobile's diag software detected it was rooted and said that made the warranty invalid. And after I unrooted it I took the phone back to the store and demonstrated the problem to the employee that sold me the phone in the first place. He tested it for about 10 minutes and came to the same conclusion as myself. He then had to go to his manager to approve the replacement.
They got out the new phone to replace it with then the manage told me that he was required to have us to one more factory reset. So I went into the settings on the phone and did one last reset. And for some reason, since this point, the wifi problem has gone away.
I think it is possible that something I did to the phone caused the problem in the first place. But since I did so much to it in the first few days (rooted and installed a ton of apps) I am not entirely sure. My two current theories are it was either caused by this malware infected flashlight app I installed that kept popping up the Play Store to install a particular app. Or it was caused by the rooting method I used.
The original rooting method I used was "Stump Root". So the second time around I used the PurpleDrake method. This is a tiny bit more tedious, but very effective and it didn't seem to break anything. Further, when I installed TWRP I made sure that I grabbed the recommended image for it that is specifically for the US T-Mobile LG G3 device and installed that using Flashify.
After I got it safely rooted I tested the crud out of it and it seems to be working fine.
One last thought. It is possible that somehow Titanium backup caused the problem when I restored text and call logs. But I seriously doubt it.
Anyway, if anyone has any questions for me about this please shoot me a message. I am more than happy to help.
Thanks,
Patrick
Hey guys. I'm having a very weird WiFi issue on my A520F.
Today the WiFi froze. It wouldn't turn off when I switched it off. After I while it turned off but took ages to turn it on again.
I factory reseted the device because I thought it was a software issue. It didn't work - after the first boot it was the same.
After a while after this, the WiFi started working again, but only for a period of time, then it would just freeze again for apparently no reason. Switching it off and on solves the issue for a while, then it freezes again saying that my WiFi is limited.
I can't take any logs since I'm not rooted (and don't have a PC to use ADB), and this is really scaring me since it happened out of nowhere. An hour before this started happening WiFi was working just fine.
I haven't installed anything unusual today, just connected for the first time on a new, but trusted, WiFi.
I've also reseted my WiFi router to its factory settings, thinking that it could be the issue, but the problem persisted. My Chromecast works just fine on the very same network.
Did this happened to anyone before? I've tried to root my phone a while back and, since it didn't worked out, I gave up and flashed the latest firmware from my country. This phone originally came with German firmware in it and I flashed it to a Brazilian one, which is the one I'm using and had no issues so far.
Can this be a hardware issue?
Thanks in advance!
So I guess I'll end up solving this on the weirdest way I can imagine.
After I posted I logged into my modem's settings and took a log at its logs. Seems that the moment this issue started to happen was near the time that the DNS server my modem was using started to fail.
I never thought that such a simple thing could mess this things like this. I mean, the DNS server is essential, but how that could freeze my phone's WiFi? Either way, I changed the DNS to Google's DNS and since then I haven't had any freeze or disconnetion. I'll test a bit more to see if the problem is gone.
Well, I do believe that I found the root of the problem.
As some of you may know, modems tend to stay on for a very long period of time (no one wants to lose internet connection, so we rarely reboot then), and for reasons I don't know (and as a tech support guy I've seen this happen A LOT) they freeze sometimes and only work again after being completely turned off and on.
Since the issue started again when I was messing with the modem settings (trying to change the DNS again to see if the problem would return), I decided to give my modem a few minutes of rest.
After that, I've powered it on again and went through the initial setup (my ISP provides an simple wizard when you first connect to the WiFi) and up until now I'm not having issues.
I'll wait a few more hours to report again, but so far so good.
So it seems that giving those things a few minutes rest every month or so isn't a bad thing at all.
Hey so I've been having this issue with my Galaxy A50 where the wifi would keep hiccuping in a constant pattern, this is very noticeable when I try to stream games using either Steam Link or Moonlight, the wifi would cut for like a split second each 5 ish seconds. I did however find a workaround, and that it so enable and disable airplane mode, it would completely fix the hiccups.
So today, I regretted updating my phone so much (7th of July update), because now, the hiccups are back and they are more constant than ever. The trick I'd use to make the wifi stable no longer works, I need to keep airplane mode enabled at all times to avoid these hiccups.
I would like one of either solutions: can I fix this issue once and for all, because it's supper annoying, I tried removing my sim cards and all but the issue persists, if there is no fix for this, then I'd like to revert to the previous version I had, I have already downloaded the files from Sammobile, but I'm worried that it would brick my phone or even refuse to install period, here's the ROM that I'd like to install:
https://www.sammobile.com/samsung/galaxy-a50/firmware/SM-A505FN/SER/download/A505FNPUS5BTF1/347209/
I've explained this issue a bit better on the steam forums, so I'm gonna copy what I typed there;
Thank you very much in advance.
Okay so, recently I got a brand new Galaxy A50 phone, and whenever I'd try to stream games (over local network using WiFi) I'd get frequent and consistent hiccups that last about a split second each 3 seconds ~, I suspected that the issue could be from my phone being faulty or whatever, but I tried my brother's phone which is the same as mine, but the issue persisted.
On very rare occasions, the hiccups would not occur and the stream would be absolutely perfect, so I know for sure it might not be a hardware issue and that a stutter free experience is possible for sure, however I have no clue how to keep it consistent.
Mind you I have tried many other devices, my old Galaxy S5 and S6, even tried a Huawei phone and an Oppo phone and they all seem to work just fine, I even tried different streaming services like Parsec, TeamViewer, Moonlight etc... So the issue is certainly not my network as it is working just fine with other devices.
The A50 is a pretty popular mid-range phone so I'd expect at least someone to use Steam link (or similar apps) on it and experience this problem, yet I haven't found a single post about this issue online, the only thread that pops up is another one of mine related to this issue (on Reddit).
Can anybody help me come up with a solution? I tried quite literally everything I can, including updating my OS and all of my apps.
Thank you in advance
Click to expand...
Click to collapse