Database Users

Constant Phone/Touchwiz reboots - help if you can

Hello everyone, I've got an interesting problem that I want the experts here at XDA to help me troubleshoot. Feel free to ask questions as I know there's probably a million variables at this point with stuff installed, uninstalled, gps, root, task killers, etc.
alrighty with that said, I did the e-wrecked gps fix (changing the operation mode and server location+port). That seems to work great in terms of time to lock on my position as well as improved accuracy. Over the next couple of days I noticed some really choppy and lengthy phone start ups after the fix.
Eventually it got to (and currently is at) a point where it kept rebooting the phone, or at least touchwiz. It would load up, scan media, search for the network, do all the start up stuff, then lock up, and turn the screen off. Hitting the lock button/power button does nothing while it resets itself. Then it resets to the lock screen, the screen lights up and it goes into "searching" for the tmo network while doing the storage preparations, and other boot up stuff. It does not restart from cold (with the vibrant, tmo, and galaxy animations, only the lock screen and OS boot process)
Anyone else got any funky restarts going on, for whatever reason? I basically want to start seeing what would trigger this behavior. I started uninstalling stuff one by one trying to figure out why its doing that but sometimes it boots up fine, sometimes it boots but doesn't ever find tmo's network, and sometimes it just does the above.
Observations:
1. It will always boot up fine if the SIM card is out.
2. The last time it did it was today while I was at work, listening to music while the phone was charging. Im noticing that the phone gets pretty hot while charging and really hot if you're using while its charging (getting apps, surfing the web, playing games, etc)
So any thoughts from the tech gurus here? anyone have similar behavior in the past on other phones? is the heat affecting the sim card negatively? I can (and have) put my simcard back in my treo 680 backup phone with no issues whatsoever.

New observation, it consistently does the reset process as soon as the "Adjust Time and Date" as it registers/syncs with the network.
UPDATE: so, i did some research, ended up at the setCPU thread and saw that when set to OnDemand some people's phones experienced similar tendencies. Problem is, mine was already set to auto-detect and "Conservative". I un-checked start at boot, and tried again. Same problem. I uninstalled setCPU completely and my phone appears to be back to normal.
I'll update again if anything changes.

so one of the things that i removed during my troubleshooting was my corporate exchange account. When i added it back. it did its initial sync fine and gave me my calendar and contacts. I then rebooted and the problem came back.
I removed the account and rebooted. it went through two cycles of the restarts and on the third one, it worked. I left it alone after that.
I then was showing my friend some things (browser differences) and had 3 browsers open. It froze as i went to close Dolphin HD. Rebooted and now its back to the cycle.

Mine did this also. Installed several apps, woke up to find a slow phone. Resets galore. A quick reset to defaults and app restore fixed it, sans setcpu of course.
From XDA App on SGS-Vibrant

my phone resets itself also as described above, but not really doing anything in particular. i dont have a whole lot of apps installed. i even was using google maps the other day and after it started up the screen went black and the device was unresponsive until the screen came back and it said searching and the media scanner was running.

well first off thanks for responding lol. i thought i was by myself out here.
secondly, i found that if i leave it alone and let it go through its cycle, it does eventually boot up ok (this is recently, before, it was endless). i havent restarted my phone (im afraid to lol) since it did it on its own yesterday (showing my friend the browsers).
since yesterday, i've used it for navigation (motonav), serveral installs, downloaded podcasts, rss feeds, etc and its been ok (even while charging and wifi on). again, havent actually restarted it since yesterday because its actually functioning for once.
Lastly, i unchecked the auto update time and date from network in the settings just to see if that makes a difference because based on previous expereience that is the point where it freezes and resets. Thanks for chiming in and let me know if there's any other advice you have

I'd suggest a reset as mentioned above.

Been checking out this site for awhile but this is my first time posting, today my phone started to have this problem and it just bootloops touchwiz if i have a simcard in the phone.
It works fine without a simcard but my problem is it will not let me turn of auto update of time and date, i have tried disabling this setting and it just enables itself again. I have also noticed that if I started messing around with time and date settings even without a sim touchwiz reloads once. I guess im gonna give a reset a go.

martin0641 said:
Mine did this also. Installed several apps, woke up to find a slow phone. Resets galore. A quick reset to defaults and app restore fixed it, sans setcpu of course.
From XDA App on SGS-Vibrant
Click to expand...
Click to collapse
heygrl said:
I'd suggest a reset as mentioned above.
Click to expand...
Click to collapse
sorry, noob question (i came from winmo and a touch pro 2), what does "a quick reset to defaults" mean? is that like a factory wipe i.e. phone will be brand new again, gotta root again and reinstall everything, change settings, etc?

jblade1000 said:
sorry, noob question (i came from winmo and a touch pro 2), what does "a quick reset to defaults" mean? is that like a factory wipe i.e. phone will be brand new again, gotta root again and reinstall everything, change settings, etc?
Click to expand...
Click to collapse
Root will stick but settings and apps/app data will be gone. It briefs you on what is and isn't lost when you do a factory reset.

Smae problem, its setcpu!
SetCPU with any settings will do this.
It needs an update, the auto detect some how loses and
will set the cpu to 19mhz max and min.
This is too slow to process. I rebooted and pressed settings and uninstalled it
while I could. Seems to behave once out of touchwiz.

For me it was another app not setcpu I never used it. After i did a reset i restored all my apps with titanium backup and once i restarted my phone it looped again. So i did another restore and left off all the apps that i installed right before the problem started and so far i think for me at least one of these caused it
Google maps update
google translate
the extra language pack for translate
barnacle wifi tether
hero of sparta
these are apps that I installed right before the problem happened and without these my phone works fine I am going to see if i can find that one that caused my problem.

It's not the maps update because my phone works fine with it.

It was hero of sparta a gameloft game from there web market funny thing is its suppose to work on the vibrant while dungeon hunter which works fine would only give nexus as a check out option. Anyway im going to try to get a refund tomorrow.

I get the same touchwiz reboot but for me it has only ever happened while using google maps. I do not use set cpu, but I have applied the gps fix. It is more than a little annoying. I have done a system wipe but the problem persists.
Sent from my SGH-T959 using XDA App

yes, if you have setcpu, uninstall it - its buggy with the galaxys
- sometimes you can't wake your phone (if you set a screen off profile), forcing you to do a battery pull
- constant launcher restarts

Judgement5 said:
For me it was another app not setcpu I never used it. After i did a reset i restored all my apps with titanium backup and once i restarted my phone it looped again. So i did another restore and left off all the apps that i installed right before the problem started and so far i think for me at least one of these caused it
Google maps update
google translate
the extra language pack for translate
barnacle wifi tether
hero of sparta
these are apps that I installed right before the problem happened and without these my phone works fine I am going to see if i can find that one that caused my problem.
Click to expand...
Click to collapse
and this is why i started the thread, to make sure i wasnt all alone. i have everything you have installed as well, but it was doing it before i picked up hero of sparta (and nova, and asphalt 5, man those guys make some good phone game lol).
anyways i just installed barnacle wifi tether yesterday so thats not it either (at least for me). That leaves the google stuff, out of the apps in your list, all of which were installed when i first got the problem, and are still on there after I've removed setCPU

heygrl said:
Root will stick but settings and apps/app data will be gone. It briefs you on what is and isn't lost when you do a factory reset.
Click to expand...
Click to collapse
ok so, contacts, text messages, etc stay? Meaning if i do a factory reset, root stays, and all app stuff can be taken care of by, say, AppBrain since it has a running list of everything installed and knows where to get it to install it again? I apprecicate the advice, but this would still be a last resort sort of thing. my phone has worked fine for the past few days but I also havent restarted it yet either

just a quick update, my phone still does this if i reboot my phone (which is never now that i got my 32gb sd card), but for the first time ever hero of sparta caused it to happen while the phone is on. I uninstalled it so we'll see.

Non-rooted Vibrant random restart?

It seems to happen after the phone has been on for an extended amount of time. I don't have lag, and I'm not using the gps when it happens. In fact, it usually happens when I sleep. Has anyone else experienced this? My phone is not modified. I'm even running plain touch whiz. I'm considering returning if I can't resolve with a hard reset. No third party apps are running when this occurs. I routinely close processes before I stop using the phone. I love this phone, I'm just worried I have a bad unit.

i'm having a similar issue, but with a rooted vibrant. the problem has spanned across two different handsets. the first one i rooted almost out of the box. but after a few days it started locking up after sitting for a while and i would have to pull the battery to get it to come back on. so i returned it, got a new one and held off rooting it to see if this one would do the same thing. the non rooted one had no problems at all, so i bit the bullet and rooted this one too, and sure enough later that same day it started doing the same freezes when trying to unlock it.
as soon as i rooted the second phone i downloaded rom manager and made a nandroid backup. after the backup i proceeded to remove some of the bloat, like dual clock, the startup/shutdown sounds, and some of the other crap that the vibrant comes with. i also installed and started up setcpu. it seemed that after i did all of this is when the freezes started up again. so i did a restore to before i removed all that stuff and now the phone is fine again. what is it about my process that is making this phone lock up like this?
EDIT: nevermind...i found some other people with the same problem in a setcpu thread...seems setting the sleep profile too low will cause the phone to not wake up after sitting too long

Uh, I'm not getting any freezing, but I know there is an issue with SetCPU. A certain setting will causes problems on the Vibrant. My issue is just unexpected reboots after the phone has been on for approximately 170 hours.

I had many random restarts and general craziness from my non rooted stock vibrant. A factory restore fixed all problems.
Sent from my SGH-T959 using XDA App

Yeah, if it happens again I'm going to try a factory reset.
Sent from my SGH-T959 using XDA App

Phone locks up at 5am each morning.

I've had a SII for a couple of weeks now (new user to android) and I have flashed it to Lightning Rom 1.5. But even before doing this and also afterwards the phone seems to crash/lockup at 5am on about 5-6 occasions.
Is there any program/app I can install to monitor what is kicking in at this time so that I can disable/uninstall it?
Thanks

What do you mean by crash exactly ? Reboot ? Freeze ?
What you could do is plug your phone to your computer before it crashes, and start adb logcat, wait for the crash, and then look at the log to see what caused the crash.

It is completely frozen. I get up at 6:15am and the phone has a blank screen, but I can press a button to activate the screen and the clock is stopped at 5:01am and you cannot do anything else except turn the phone off and back on.

Maybe its the rom? Have you checked its thread? Try flashing bacm to stock. See if problem occurs.
Sent from my GT-I9100 using XDA Premium App

I checked the thread but doesn't appear to be anyone else with same issue. I might try the stock ROM to see if the problem persists. Although I sure it happened once on the firmware that came on the phone (KE2 I think it was).

scheduled backup?

I couldn't find any backups scheduled. So I wiped the phone last night and applied the Lightning 1.5 ROM again and it seems to have been fine this morning..no lockups.
Thanks for the advice.

I had a similar problem with my Nexus S. It went into a bootloop at around 5am... I'm not sure, but I used to think it might be that network operators refresh their networks at that time, and a buggy radio would crash.. This is not normal, if it does the same thing with stock return your phone for repair, especially if you use your phone as your alarm!
Sent from my Sammy Galactic S2 Beastly Device

OccasionalDroid said:
I had a similar problem with my Nexus S. It went into a bootloop at around 5am... I'm not sure, but I used to think it might be that network operators refresh their networks at that time, and a buggy radio would crash.. This is not normal, if it does the same thing with stock return your phone for repair, especially if you use your phone as your alarm!
Sent from my Sammy Galactic S2 Beastly Device
Click to expand...
Click to collapse
I'll keep that in mind if it happens again..cheers. Been OK this morning so shall see how it goes.

Its done it a few more times since I did a factory reset, always at 5:01am. After rebooting the phone and checking the battery stats it appears that 'Cell Standby' has used 52% of all battery consumption and the battery drained from 100% to 9% over 8 hours. The problem also occurs even if the phone is on charge over night.
So maybe it is a buggy radio? Gonna take it back to the store tomorrow to be looked at.

[Q] Nexus 4 randomly turning off, intermittently not being able to restart

Hi guys,
Not exactly the most positive of first posts but here we go. There's a problem with my phone that I can't find the solution for...
Essentially my phone randomly turns itself off (no power down sequence, almost as though the battery's being taken out if you know what I mean) and then it has difficulty in fully booting again. For some reason it also likes to revert my wallpaper back to the original as stock.
The first thing that I thought of was malware, with the wallpaper - so I tried a couple of anti-malware apps to no avail. As my device was rooted, I then flashed back to stock, locked and unrooted it and checked the behaviour. Again to no avail (then again I've never rooted/unrooted so this may have been done incorrectly). By the looks of it, the worst case scenario is a problem with battery connections/hardware...
So the question is have you guys come across this before? Is there a solution to this or is Google/LG going to have to give me a replacement?
Many Thanks.

Weird, I just had this happen couple hours ago, I was watching a video and close the app. I press the power button to put it to sleep. Just like 20 second later, I press the power to wake it and it don't do anything. I had to hold the power button to turn it on. I check the battery status afterward and it looks like it drop between 5-10 percent in the chart after it turn on. The battery must have failed or something. This also happen to my wife phone couple weeks back, although she had to do a hard reset(power+volume up and down) it have not happen again though.

Hello
First of all, welcome to XDA community!
Now, have you done anything with your phone? As in, root it? Flashed custom kernel? Flashed custom ROM? We would love to help, but you need to provide us what we need

maintains
kyokeun1234 said:
Hello
First of all, welcome to XDA community!
Now, have you done anything with your phone? As in, root it? Flashed custom kernel? Flashed custom ROM? We would love to help, but you need to provide us what we need
Click to expand...
Click to collapse
Okay, here's what I had done when this all started:
- Rooted and unlocked.
- TWRP custom recovery
- Standard Kernel, no custom ROM.
I've reverted as much of this back to stock as possible through a nexus tool-kit, but it still has the issue. If I'm missing anything out let me know.

Thrice87 said:
Okay, here's what I had done when this all started:
- Rooted and unlocked.
- TWRP custom recovery
- Standard Kernel, no custom ROM.
I've reverted as much of this back to stock as possible through a nexus tool-kit, but it still has the issue. If I'm missing anything out let me know.
Click to expand...
Click to collapse
Did this happen before you had the phone rooted? Also did this happen one time only or happened multiple times? I also had this problem, but just turning off and not turning back on part. But that was only one time event and I believe it was because of the custom kernel.

kyokeun1234 said:
Did this happen before you had the phone rooted? Also did this happen one time only or happened multiple times? I also had this problem, but just turning off and not turning back on part. But that was only one time event and I believe it was because of the custom kernel.
Click to expand...
Click to collapse
This started yesterday, and I rooted it as soon as I got it 2 weeks ago, so I don't think the root has caused any issues. It's now happening rather often, to the point where it's unuseable

Thrice87 said:
This started yesterday, and I rooted it as soon as I got it 2 weeks ago, so I don't think the root has caused any issues. It's now happening rather often, to the point where it's unuseable
Click to expand...
Click to collapse
That's odd. Did you download any apps recently that might've caused this issue? Maybe root apps?

kyokeun1234 said:
That's odd. Did you download any apps recently that might've caused this issue? Maybe root apps?
Click to expand...
Click to collapse
The only 2 apps that I downloaded the day before were cerberus and titanium backup, both of which are well known. Either way they were the day before the problems started.

Thrice87 said:
The only 2 apps that I downloaded the day before were cerberus and titanium backup, both of which are well known. Either way they were the day before the problems started.
Click to expand...
Click to collapse
Doubt that these will cause any issues, but could you try uninstalling Cerberus just in case? Thanks
Sent from my Nexus 4 using xda app-developers app

kyokeun1234 said:
Doubt that these will cause any issues, but could you try uninstalling Cerberus just in case? Thanks
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Well, after completely reverting the phone back to its stock version and pretty much everything else, it's still doing it - which surely points to a problem with the chip (or something). So, I've contacted google about a replacement and so far so good - got through in 5 minutes and sorted out the RMA and everything, should be delivered in the next few days.
Thanks for the help anyway. I'm going to avoid rooting this one for the time being to see how it behaves.

I experienced "random shutdowns" and even posted about it here. Turns out it was my belt holster that was somehow the culprit. I don't know if it was mashing some weird button sequence to turn off the phone, or if the magnet interfered or something else, but as soon as I got it out of that holster I had no more random shutdowns.
I doubt yours is the same problem but I thought I'd post mine.

hfuizo said:
I experienced "random shutdowns" and even posted about it here. Turns out it was my belt holster that was somehow the culprit. I don't know if it was mashing some weird button sequence to turn off the phone, or if the magnet interfered or something else, but as soon as I got it out of that holster I had no more random shutdowns.
I doubt yours is the same problem but I thought I'd post mine.
Click to expand...
Click to collapse
Yeah that's not my problem at all Lol. Glad you've figured it out and I bet that magnet caused the issue IMO
Sent from my Nexus 4 using xda app-developers app

Funny I had the same thing happen to me last night. I was using the phone put it down for a minute or two and then could not wake the phone. What was interesting was when I couldn't get it to turn on I plugged in into the charger and let it sit for a few hours. When I was finally able to restart it using the the power, vol button the battery was at the same level before the incident. In other words whatever happened prevented the battery from being charged. I am stock and rooted and haven't loaded any new apps in over 2 weeks
Sent from my Nexus 4 using xda app-developers app

I have almost the same problem as the op but I do have a shut down sequence. It does randomly shut down itself. The first thing I got the phone I rooted it and it was fine working on modaco for 2 weeks then one day it kept shutting down upon boot until like 10 tries later I successfully got back in but lasted only a few mins and sometimes hours. Im gonna rma this pos and I hope I can get it replaced soon. I try it with stock rom and kernel then modaco with stock kernel then modaco with faux kernel. Same problem.

I had these problems earlier ... I just gave HARD RESET by pressing power key for more than 5 sec.
Then i figured, it was due to Undervolting ! and Processor going to a DEEP SLEEP all together !
So i removed UVing and it was cool since then ! ... Although my signature says the rest !

I bought my N4 about 2 weeks ago, and it has turned itself off 3 of the nights I've had it. I don't have any hard evidence, but I have a theory on why it's doing it.
At first I thought it was because I used a Motorola usb cord instead of the stock cord because I read some people's theories on the internet, but it happened again (twice) after using the stock cord.
It seemed like it only shut off if I left WiFi turned on when I went to sleep (even then it was still a random occurrence). I went into my advanced WiFi settings and noticed Wi-Fi Optimization was turned on with the text "Minimize battery usage when Wi-Fi is on". I thought it might be the problem, so I turned it off. I left WiFi on last night, and the phone was still on in the morning. Again, it is still a random occurrence even with WF on, so I'm going to leave WF on at night for a few days/weeks and see if it happens again. I'll post back with results.
If anyone else has already tried this or has figured out a solution, let me know.

The same happens several times a week with my nexus 4 running latest cyanogenmod. I will revert it to clean stock in a few days to see how it goes. I don't think that is a hardware problem but time will tell.

MildewMan said:
I bought my N4 about 2 weeks ago, and it has turned itself off 3 of the nights I've had it. I don't have any hard evidence, but I have a theory on why it's doing it.
At first I thought it was because I used a Motorola usb cord instead of the stock cord because I read some people's theories on the internet, but it happened again (twice) after using the stock cord.
It seemed like it only shut off if I left WiFi turned on when I went to sleep (even then it was still a random occurrence). I went into my advanced WiFi settings and noticed Wi-Fi Optimization was turned on with the text "Minimize battery usage when Wi-Fi is on". I thought it might be the problem, so I turned it off. I left WiFi on last night, and the phone was still on in the morning. Again, it is still a random occurrence even with WF on, so I'm going to leave WF on at night for a few days/weeks and see if it happens again. I'll post back with results.
If anyone else has already tried this or has figured out a solution, let me know.
Click to expand...
Click to collapse
Don't know if anyone is keeping up or cares, but I wanted to update and say that this did not fix the problem. 4.2.2 also did not fix the problem. I guess I could try getting a new one from Google.

My wife and I are both having this problem. Hers is completely stock, I'm unlocked and rooted. I was hoping it would be fixed with 4.2.2, but if it hasn't then it maybe time to get replacement N4s
I can't imagine this issue is very widespread, since there have only been a few threads about it. Its a big nuisance especially because it usually happens at night when I'm expecting my alarm to go off at night.
I hadn't wanted to send for replacements since it seems like a software issue but I'm getting fed up.
Sent from my Nexus 4 using xda app-developers app

Just had this problem occur with my N4 last night..... Phone is 2 weeks old.
Went to bed, plugged in the phone to charge [it was at about 50% or so, so not exactly low].
Woke up at 8.30 wondering why my alarm didn't go off at 7.30.... looked over and the phone was off.
It also didn't want to turn back on either. Took about a minute of holding in the power button for various amounts of time before it finally kicked to life [at 100% charge too].
This is going to be a real problem if this problem reoccurs. At home I have a clock radio but I travel a lot and rely on my phone to wake me up!
Here's hoping we can start to identify what is causing this issue. All I can add is that it is not low-battery related.
As stated in the sig. Phone is unlocked/rooted with stock rom.

No deep sleep

All of the sudden my phone refuses to go into deep sleep, it stays at 300mhz according to cpu spy. Not even if I switch to airplane mode the deep sleep works. This has happened a few times in the last week. A reboot fixes it for a while. Do you think it's an app that is misbehaving? Has someone else seen the same thing on their phone?

jocke_lulle said:
All of the sudden my phone refuses to go into deep sleep, it stays at 300mhz according to cpu spy. Not even if I switch to airplane mode the deep sleep works. This has happened a few times in the last week. A reboot fixes it for a while. Do you think it's an app that is misbehaving? Has someone else seen the same thing on their phone?
Click to expand...
Click to collapse
I had the same thing once I got my Note 4. Turned out that it was my micro SD card, which I popped straight into my new phone from my old phone (an LG). It may or may not be your cause too.
I ended up reformatting it through Android (after copying all my files to my pc). After that, I put all my data back on it. It's been about a month now with my phone always deep sleeping.
If you have a micro SD card in your phone, then remove it for a while to see if the phone sleeps. If so, then backup any wanted files from it, pop it into the phone, and reformat it. Afterwards, you can put your data back on it.
If this isn't your problem, then yeah, it could be an app.
Sent from my Samsung Galaxy Note 4 (sm-910a) using Tapatalk

spexwood said:
I had the same thing once I got my Note 4. Turned out that it was my micro SD card, which I popped straight into my new phone from my old phone (an LG). It may or may not be your cause too.
I ended up reformatting it through Android (after copying all my files to my pc). After that, I put all my data back on it. It's been about a month now with my phone always deep sleeping.
If you have a micro SD card in your phone, then remove it for a while to see if the phone sleeps. If so, then backup any wanted files from it, pop it into the phone, and reformat it. Afterwards, you can put your data back on it.
If this isn't your problem, then yeah, it could be an app.
Sent from my Samsung Galaxy Note 4 (sm-910a) using Tapatalk
Click to expand...
Click to collapse
I don't have any SDcard. Hopefully it is an app that is causing the problem. Right now I have uninstalled all the apps that I have installed lately. Let's hope this helps.
The problem seems to start after I charge the phone and pull if off the charger. But as I said, it started last week. I haven't had the problem before and I bought the phone in early November.

jocke_lulle said:
I don't have any SDcard. Hopefully it is an app that is causing the problem. Right now I have uninstalled all the apps that I have installed lately. Let's hope this helps.
The problem seems to start after I charge the phone and pull if off the charger. But as I said, it started last week. I haven't had the problem before and I bought the phone in early November.
Click to expand...
Click to collapse
If it didn't do it before, then it shouldnt be a hardware problem unless something just randomly broke. As long as the phone isnt getting real hot or anything weird like that, then that shouldnt be it.
I think it may be an app. If uninstalling everything fixes it, then you can reinstall the apps one by one until it happens again. Wait like a day inbetween reinstalls.
If that doesnt help though, then do a factory reset (last resort).
GOOD LUCK!

spexwood said:
If it didn't do it before, then it shouldnt be a hardware problem unless something just randomly broke. As long as the phone isnt getting real hot or anything weird like that, then that shouldnt be it.
I think it may be an app. If uninstalling everything fixes it, then you can reinstall the apps one by one until it happens again. Wait like a day inbetween reinstalls.
If that doesnt help though, then do a factory reset (last resort).
GOOD LUCK!
Click to expand...
Click to collapse
My problem seems to be fixed now. I did uninstall some apps but that didn't seem to help. I then turned off the phone, pulled the battery for some minutes, put it back again, booted to recovery, wiped cache and then restarted. Since then it's been OK. I have an uptime at 350h right now. It must has been something that had got stuck before. Hopefully it doesn't happen again! Now I'm waiting for lollipop