Database Develop

Captivate random shuts down

I was wondering if anyone else's Captivate has shut down automatically? It happened 3 times yesterday the screen goes into standby mode but if you try waking it up you had to pull the battery.
Last night I let it completely drain then completely charged it. When I picked it up it read 99% battery immediately. I went to get ready for work and check my email and it was shut off. I had to restart it again. Since then it seems as if the battery is lasting longer.

random shutting down
Okay so i had this problem but it only arises for me when i do a few things. i have spent hours scratching my head about what it could be and through process of elimination i found on my phone it was one of two things.
1.) make sure that if you are using the auto kill feature in ATK that its not set to anything above safe
2.) if your using setcpu with profiles selected and have a very low profile for when the screen is off then try ramping that profile up a little bit to give the phone a chance to run background processes a little easier and actually wake up when you want it to!
hope it helps and if you give me info about what is going on then that should help us help you.

ice3186 said:
Okay so i had this problem but it only arises for me when i do a few things. i have spent hours scratching my head about what it could be and through process of elimination i found on my phone it was one of two things.
1.) make sure that if you are using the auto kill feature in ATK that its not set to anything above safe
2.) if your using setcpu with profiles selected and have a very low profile for when the screen is off then try ramping that profile up a little bit to give the phone a chance to run background processes a little easier and actually wake up when you want it to!
hope it helps and if you give me info about what is going on then that should help us help you.
Click to expand...
Click to collapse
I havent been using ATK at all. Also does SetCPU really work with the hummingbird processor? When it boots it always kicks down to 19.2 which is obviously too low. I removed it just in case. I also set it back to the default settings. I would really enjoy SetCPU to save battery if it works of course. I thought it only works on HTC devices and Motorola devices?

i had setCPU on my phone yesterday and it was freezing like you describe when trying to bring it out of standby. I pulled the battery twice before i said F-it and took the program off. If you were using setCPU i'd say that was your problem.

domin8 said:
i had setCPU on my phone yesterday and it was freezing like you describe when trying to bring it out of standby. I pulled the battery twice before i said F-it and took the program off. If you were using setCPU i'd say that was your problem.
Click to expand...
Click to collapse
I deleted SetCPU and I thought it might be Screebl so I disabled it. Sure as hell it just went to a black screen and shut off again. God this is beyond annoying. I dont want to have to bring back this great phone but I need the phone to work.

We've also got to think, Samsung just released this phone. The more we do to it from the market, the more things are gonna happen.
Most devs haven't had the time to really test and relay bugs from this phone that would cause other errors.

madjsp said:
We've also got to think, Samsung just released this phone. The more we do to it from the market, the more things are gonna happen.
Most devs haven't had the time to really test and relay bugs from this phone that would cause other errors.
Click to expand...
Click to collapse
Yes but if I am correct none of these issues will be fixed until they decide to release FroYo?
EDIT: I just tried removing the MicroSD to see if that resolved the issue. Shocker...it didnt...

spyz88 said:
I was wondering if anyone else's Captivate has shut down automatically? It happened 3 times yesterday the screen goes into standby mode but if you try waking it up you had to pull the battery.
Last night I let it completely drain then completely charged it. When I picked it up it read 99% battery immediately. I went to get ready for work and check my email and it was shut off. I had to restart it again. Since then it seems as if the battery is lasting longer.
Click to expand...
Click to collapse
This has happened to me once. Came out of a meeting, pulled it out of my pocket, and couldn't get it to wake from sleep. I have not installed SetCPU, so it's not that. Not sure what the root cause was.

What apps do you have installed would probably be the more relevant question. And what have you changed?

Mine is doing the same **** and it is driving me NUTZ!!! I thought SetCPU first so I uninstalled and rebooted. Phone is still doing it. Please someone figure this out quickly. I am going through my apps one by one and uninstalling them to try to pinpoint the problem. Subscribing to the thread.

Interesting.... I haven't heard this happen to me yet so its probably an application or process your guys all have in common.
Sent from my SAMSUNG-SGH-I897 using XDA App

I have a feeling it is setcpu. I just did a reboot after installing and now it is not happening. Cross my fingers!

I'm having the same issue and I never had setCPU installed. sucks..
-Teklock

Like a lot of you, I started uninstalling my apps one by one when this happened. It stopped restarting after I finally uninstalled Launcher Pro. After that, the phone stayed on the whole night last night. It's weird because it worked with Launcher Pro for a good 2 days.

I'm also experiencing this issue, ad i've only downloaded a few apps.
Has anyone exchanged their phone over this yet?

Teklock said:
I'm having the same issue and I never had setCPU installed. sucks..
-Teklock
Click to expand...
Click to collapse
I reflashed to stock firmware and I'm still having an issue. I noticed that if you take the battery cover off the battery and push on it then it seems like it has a little give to it. Can anyone who is not having this problem confirm? Also, anyone who has this issue, please see if your battery has a little give to it.
It should be on the side WITHOUT the contacts. Also, if this doesn't work I'm bringing the phone back. I already had a problem with the first one and since this is my 2nd exchange AT&T wont exchange it anymore. They told me I need to go through the warranty. They are out of their minds the phone isn't even a week old. Never had these problems with HTC...
EDIT: I uninstalled ADW Launcher as a test to see if thats it.
EDIT 2: Make sure the battery door is covered tightly. I pushed mine all the way down until it clicks. Hold it down and then close the slider. I think this actually might fix the issue.

Anyone figure out why this keeps on happening? I've reflashed the stock as well and it still occurs randomly.

Strange this dosnt happen to me, and i installed setcpu(performance governor 1ghz/800mhz) but uninstalled it after seeing that it ****'s up gles 2 rendering...

I found this thread via Google search, and I just wanted to add that my phone started doing this last night, however, I have not added anything to my phone, nor is it modded in any way. It's completely stock. The only thing I have done thus far was remove all of the extra home pages and rearrange some app icons, and that was on Thursday and Friday. It does it both when it goes to sleep normally or if I hit the sleep/power button.

I narrowed mine down to SetCPU being underclocked while asleep. Bumped up the minimum clock and took off the profile I had set, phone hasn't rebooted in 4 days.

blank screen but phone ON!!!!

Has anyone had this issue?
I have tried a few different ROM's and have had this problem on all, the phone will work but sometimes when the phone is locked and asleep you cannot get the screen back.
If you ring the phone it will ring but you can't wake the phone up (the screen is off).
If I then pull the battery and reboot all is well until the next time, which is random.
I will remove all my programs to see if there is one of them causing the issue, I don't believe it is the rom as it has happened on a few of them.

Have you wiped your phone when flashing the different roms? I've had it sometimes, i think it could be a ram management issue...

Talon26 said:
Have you wiped your phone when flashing the different roms? I've had it sometimes, i think it could be a ram management issue...
Click to expand...
Click to collapse
Yeh, I always do a factory/wipe, dalvik cache wipe.
I think it might have been TW4.5, I did some research and installed TW4 Manager I then updated TW4.5 to the latest Version. So far it hasn't happened yet but i'll give it a couple more days.
Thanks.

Yh ive been reading and TW4 generally accelerates the issue (because its a ram hog? not sure i dont use it) Im currently using Golauncher with system tweaks, but was told that nemus launcher and system tweaks was a better combination... Seems to be working, ive had less force closes or issues of that type

it's the proximity sensor. needs replaced.

pch.radu said:
it's the proximity sensor. needs replaced.
Click to expand...
Click to collapse
I don't think so...
The proximity sensor is only used when your in a call. It should not have any effect when he tries to wake it from his pocket after a while...

Well i am on 2.3.5 and using golauncher and never had any problems. Still my best guess is the damn sensor. On samsung apps there is an app called sensors i think and that app tells u what is working inside the phone.
Sent from my GT-I9000 using XDA App

If I recall correctly yeah I had this issue once on JVR and once on JVS and now on JVT I got it a few hours ago
---------- Post added at 06:30 PM ---------- Previous post was at 06:29 PM ----------
pch.radu said:
Well i am on 2.3.5 and using golauncher and never had any problems. Still my best guess is the damn sensor. On samsung apps there is an app called sensors i think and that app tells u what is working inside the phone.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Sounds like a great app but seeing as the screen doesn't turn on that app might as well be useless in this case

No screen turns on, its just when it turns off it wont come back on...

I have the same issue with my SGS. Running stock version of JVT.
Wake up in the morning to phone alarm but screen is black. Pushing home button or any other button does nothing. Had this happen a few times now and only solution is to pull the battery

In order to help you we need to know what you are running currently and what you have tried to resolve the issue so far, can please make as detailed account as possible

It's seems that everybody have this same issue. I have exactly this same - phone is working - buttons are lit, but the screen is blank. I'm on 2.3.5 stock firmware.
Trying to solve this I already did wipe and even formatted the internal storage.
What's more interesting is that this same happens to my wife's Galaxy Mini (S5570) !!.
I can remember though that when my phone was on v2.2 about a year ago it was working ok.
small tip:
What you can do instead of pulling the battery out is to press the power button for about 10 seconds ( phone will turn off) release and the press it again for few seconds to start again.

You don`t need to press power again, just keep it pressed until you see the samsung bootlogo.
Mine has started to blackout too, maybe it`s related to some installed software. It worked ok still few months ago. My galaxy mini is working ok tho, has only few market apps installed.
Sent from my GT-I9000 using Tapatalk

poyda69 said:
Has anyone had this issue?
I have tried a few different ROM's and have had this problem on all, the phone will work but sometimes when the phone is locked and asleep you cannot get the screen back.
If you ring the phone it will ring but you can't wake the phone up (the screen is off).
If I then pull the battery and reboot all is well until the next time, which is random.
I will remove all my programs to see if there is one of them causing the issue, I don't believe it is the rom as it has happened on a few of them.
Click to expand...
Click to collapse
The bug is called SOD (Sleep of Death). Apparently a Gingerbread only bug (I think deep sleep was introduced in Gingerbread).
Your phone is going into deep sleep, and can't be woken agian.
I don't know if there is a fix for it, but you could try search for SOD on these forum pages.

Herman76 said:
The bug is called SOD (Sleep of Death). Apparently a Gingerbread only bug (I think deep sleep was introduced in Gingerbread).
Your phone is going into deep sleep, and can't be woken agian.
I don't know if there is a fix for it, but you could try search for SOD on these forum pages.
Click to expand...
Click to collapse
i had this issue on cm7 with neo kernel, but sometimes it responded after some time
i think its black magic made by apple and will kill our cats

As Herman76 said, this is the SOD, I used to get them quite frequently. I created a thread with a possible workaround. So far haven't got any new SODs.

[Q] Galaxy Note not waking up?

I can't put my finger on this issue I've been having with my Note.
Don't get me wrong, this device is a godsend!
The problem I've been having is that sometimes when I take my Note out of my pocket and try to press the unlock or menu button it doesn't show anything on the screen. I've read about people having issues with delay before it pops up, but it doesn't pop up even after 10 seconds or a minute, it feels like the device 'hangs' or doesn't want to wake up. The only way I can turn the phone on again is by pressing the unlock button for like 10 seconds and the phone reboots.
I thought it was a problem with Green Power, I thought it maybe had issues turning off the wifi or data when the screen was locked and that the service would cause the OS to crash or 'hang'. When I look at my battery history after the reboot it shows that I lost a significant amount of battery (5-15%, depending on how long it took for me to 'discover' the crash) and there's a 'jump' in the graph.
Things I've tried:
Stock rom - problem persists
Different kernels - tried all the kernels available in the market including stock, problem persists
Add a bit of paper between back-cover and battery (to make sure it doesn't lose contact)
Checked if there was dust between battery connections
Tried different sim card
Tried disabling wifi and data all day (mysteriously persists)
DIfferent governors (ondemand and interactive) (the phone reverts to default governor after the forced reboot, normal? i have my phone set to interactive on boot, but somehow it skips that after the forced reboot)
I've attached a picture of the battery graph. According to the stats there's a 25 minute gap where the phone was 'stuck' and you can see that the screen was on and active for that duration.
There are NO funny apps running in the background, this is is a clean install with some standard Samsung apps frozen.
tl;dr version: phone randomly won't wake up; battery loss after forced reboot;

I might have found the issue myself. Now when I come to think of it, I think it always occurs after I've been in my car for like a 30 min drive... Maybe the phone is having trouble switching networks? Anyone know what might be causing this?
Or better yet, how can I research this issue? Can I enable some logging somewhere to track this?

I had the note for about 10 days and today, about 1 hour ago it happened to me for the first time. I tried the home button to wake the screen but nothing, tried the power , nothing and holding the power but nothing happened. I had to pull the battery.

I had this problem in the beginning, but no more.
It's one of two things, in my case. Restoring apps (with data) from Titaium backup, or SetCPU or both. Do a factory reset, reinstall apps without data. If using setCPU, disable it for a while to see if it happens again. It's been over a week and the problem is gone.

tamarian said:
I had this problem in the beginning, but no more.
It's one of two things, in my case. Restoring apps (with data) from Titaium backup, or SetCPU or both. Do a factory reset, reinstall apps without data. If using setCPU, disable it for a while to see if it happens again. It's been over a week and the problem is gone.
Click to expand...
Click to collapse
I was using System Tuner instead of SetCPU to freeze apps and change governor, maybe I've just been using the wrong app? I deleted it just in case. Will see if the problem persists, thanks!
The nasty thing about it is that it seems to happen randomly (but it most likely doesn't) and is pretty rare (happens once every 3 days).
Still, I don't like the fact of not being available for X amount of time, even if it's 30 minutes.

I'm on stock room and unrooted. Like I said first time it's happened.

i've had the GNote since 4 days now , and yesterday same thing happened as the device was in my pocket and i couldnt wake it up at all , battery pull solved it.
im on stock , non rooted

I can't believe that we are the only ones with this issue. Anyone else? OR better yet, how did you resolve it?

Dont know if this is the same issue as the streak had, but with the streak if you kept it your pocket with the screen facing your body this would sometimes happen. Flipping it so that it that the screen doesnt face your body in your pocket solved this issue.

kirkla79 said:
Dont know if this is the same issue as the streak had, but with the streak if you kept it your pocket with the screen facing your body this would sometimes happen. Flipping it so that it that the screen doesnt face your body in your pocket solved this issue.
Click to expand...
Click to collapse
Thanks for your reply. I did some research, and apparently it had to do with static being built up in the screen from wearing it towards your body in your pocket.
This issue was that you couldn't swipe the lockscreen cause the touch screen wouldn't respond. The problem we are having is that the screen won't even turn on and that the system locks up.

Same issue here with my 2 days old Galaxy Note, that's how I found this forum. In my case it went from not waking up occasionally to every time WIFI was ON (I did some experimenting with settings to see which one could be the one causing the problem). But then...occasionally it would not wake up even with WIFI OFF: very annoying. And this is my first Android, so I didn't have any custom anything, pretty much same as out of the box when I got it The only solution was to reset the handset. And definitely has nothing to do with having it in my pocket as I don't carry it in my pocket. Rang Samsung, they told me it was faulty, I returned it. Now I'm concern the next one is going to have screen issues? As so many people complain in this forum? we'll see.

My issues have been resolved after flashing AbyssNote 1.4 and when I stopped using System Tuner. I've started using Voltage Control instead and now I'm not even having problem @ 100Mhz undervolted 50mV from stock.

Same problem with my wife's Gnote, totally stock, just a small handful of apps installed. Happened twice, about a week apart.
She does a lot of travelling, maybe you're right about that. But it happens after she gets home when it's still OK.

Had the same same issue twice in two days and had to do a battery pull, just did a master reset and re -installed the applications manually, so far so go.
YOu guys think its a hardware or a software issue?

Hmm.. Happened to me too about three times in the last two weeks. I am on stock rom but rooted, and running Green Power. Hopefully samsung will fix it in the next updates. Seems like a software bug to me. Maybe not enough juice when in deep sleep?

metus666 said:
I was using System Tuner instead of SetCPU to freeze apps and change governor, maybe I've just been using the wrong app? I deleted it just in case. Will see if the problem persists, thanks!
The nasty thing about it is that it seems to happen randomly (but it most likely doesn't) and is pretty rare (happens once every 3 days).
Still, I don't like the fact of not being available for X amount of time, even if it's 30 minutes.
Click to expand...
Click to collapse
Hello
its the problem of your kernel. try Abyys 1.4 and use XDA Superpower to adjust the CPU-Frequency automatically

neunzehn77 said:
Hello
its the problem of your kernel. try Abyys 1.4 and use XDA Superpower to adjust the CPU-Frequency automatically
Click to expand...
Click to collapse
problem is it also happens on stock rom.

mfractal said:
problem is it also happens on stock rom.
Click to expand...
Click to collapse
It's very well possible that the stock kernel has faulty settings for the CPU. Haven't had the problem again with AbyssNote 1.4 and Voltage Control (even with custom cpu frequencies)

I just got my note today.
Battery in, turnt it on a few mins playing around.... the problem started
and hasnt since stopped...
Anyone tried contacting samsung about this?
software fix or hardware issue ??

qazkamakazi said:
I just got my note today.
Battery in, turnt it on a few mins playing around.... the problem started
and hasnt since stopped...
Anyone tried contacting samsung about this?
software fix or hardware issue ??
Click to expand...
Click to collapse
at this point we're just guessing, there haven't been any official confirmations of the problem as far as i know.
But if it's so accute that it keeps happening all the time you must have a faulty device.. call samsung ?

Xperia TL (LT30at) sleep of death issues

So, just this last week after having my new Sony Xperia TL for a month I started experiencing the sleep of death issues, I haven't tried to do the restore via PC companion yet, if it does it again tonight I will. (I'll probably want to do that before updating to JellyBean anyways).
So far it's only happened at night, when on the charger for four+ hours, it's been hit and miss, happened two nights in a row, then worked two nights in a row, then locked up again last night.
The locked state; the screen is off doesn't respond to lock button, the notification light is blinking. I have to reboot it with the Volume Up + power button.
I thought I had fixed it by removing the PSM store (Installed that shortly before this fun started)..
Any other tips?
here's some links:
Xperia V sleep of death
http://talk.sonymobile.com/thread/60422?start=0&tstart=0

So, on Saturday (when I posted this) I disabled the ATT wifi hotspot software, and also in the apps section of developer options;
Checked "don't keep activities"
I'm not sure if I've solved the problem but the last two nights it hasn't locked up and yesterday the battery life was the best I've ever had.

I have only experienced this with wifi on. So long as wifi is off, it's not had a SoD issue. Irritating.

Seems legit
scythekain said:
So, on Saturday (when I posted this) I disabled the ATT wifi hotspot software, and also in the apps section of developer options;
Checked "don't keep activities"
I'm not sure if I've solved the problem but the last two nights it hasn't locked up and yesterday the battery life was the best I've ever had.
Click to expand...
Click to collapse
That's what happened to me just now. I checked "don't keep activities" but left wifi on. I'll see if it happens again. No point in having a smart phone if i cant use my wifi.

S0UND.w4v said:
That's what happened to me just now. I checked "don't keep activities" but left wifi on. I'll see if it happens again. No point in having a smart phone if i cant use my wifi.
Click to expand...
Click to collapse
Did you have any more sod issues?
Since I've rooted and installed XperimenT version 1.7.1 I haven't had any sod.

scythekain said:
Did you have any more sod issues?
Since I've rooted and installed XperimenT version 1.7.1 I haven't had any sod.
Click to expand...
Click to collapse
Sod returned for me last night.
The only thing I changed yesterday was installing dead trigger. I rebooted into recovery and cleared the cache and dalvik.

I saw this thread for the v and noticed that this is also in our Rom.
http://forum.xda-developers.com/showthread.php?p=38609008
Might be worth a try.
Sent from my LT30p using xda app-developers app

I have had the TL for about a week now and have had this sleep of death happen twice. First time it happened i was charging it during the day with a little bit of use here and there. The second time it happened was overnight while i was sleeping. I was depending on the phone's alarm to wake me up, it never did. Woke up an hour later on my own and luckily wasn't late to work. I read somewhere else that killing active apps before putting it on the charger helps. It's been two night using this theory and so far so good. I am not rooted or unlocked. 1) Does anyone know if this is a hardware or software issue? 2) Should I return it for another device? I have a few more days to return it if need be. 3) Does the update to Jelly Bean bring a fix? Rumor has it March 12th is when the TL gets JB.
Oh and I have wifi on when I'm home.

No jellybean doesn't fix it. I'm running rooted jellybean (xperiment 2.0).
Friday night while charging it did the sod. I didn't change anything and its been fine the last four nights. I have no idea what causes it. I thought it was the line in build.prop, but not anymore.
Sent from my LT30p using xda app-developers app

Sod this morning, made me wake up late.
I'm gonna have to play with the settings see what I can figure out.
Sent from my LT30p using xda app-developers app

scythekain said:
Sod this morning, made me wake up late.
I'm gonna have to play with the settings see what I can figure out.
Sent from my LT30p using xda app-developers app
Click to expand...
Click to collapse
Have you tried leaving wifi off?

Rashkae said:
Have you tried leaving wifi off?
Click to expand...
Click to collapse
Turned it off last night and the phone didn't SOD. The interesting thing is the night before I checked my phone about an hour before my alarm was supposed to go off and it woke up fine.
Any idea if it is wifi, why? Is there a build.prop tweak we can do to sort this out?

I have been keeping my wifi on for the last few days, and so far no more SOD. Only thing I have been doing is clearing any active apps before going to bed. As long as this keeps working, I'm good with it. Think it's been about 5 days so far. Will post if anything changes.
Sent from my Xoom using Tapatalk 2

If clearing active apps keeps it from locking up, one of the apps has to be the problem. Wonder if it'd be worth posting an app list?
Sent from my LT30p using xda app-developers app

I downloaded a system cleaner Friday and since I've run that there hasn't been any sod.
I've left WiFi on overnight all four nights.
Sent from my LT30p using xda app-developers app

So in my drunken state last night I forgot to clear my apps before passing out. I did not get a SOD. I probably got lucky. I also want to throw out there that the first week of ownership, I kept everything stock and only added my email apps since I heard jelly bean was coming out. I always do a factory reset after a big change in OS, so I didn't want to have to set up all my screens again. Anyway, I hot my SOD's during that time. So I think the issue is bigger than an app related one. Maybe the Jelly Bean update fixed it.
Sent from my Sony Xperia TL (LT30at) using Tapatalk.

Seems like the consensus on the net is leaning towards Wifi setting "don't keep activities" for solving this. Just picked up my V last week and promptly had 3 SoD's after changing the wifi setting to "only if connected". Yesterday switched back after some searching and so far no issues. We'll se how it goes coming week.
BTW, my phone came with latest 4.1.2 and still has.

Since I've installed that system cleaner app, the phone hasn't locked up overnight.
I have wifi set to location mode, which seems to turn wifi off when the screen is off.
So, it's either a file problem, or a wifi problem.
Up time; 83 hours, xperiment 2.3.
I'd be curious if anyone with sod, flashed cm10.1 and still experienced them.
Sent from my LT30p using xda app-developers app

scythekain said:
Since I've installed that system cleaner app, the phone hasn't locked up overnight.
I have wifi set to location mode, which seems to turn wifi off when the screen is off.
So, it's either a file problem, or a wifi problem.
Up time; 83 hours, xperiment 2.3.
I'd be curious if anyone with sod, flashed cm10.1 and still experienced them.
Sent from my LT30p using xda app-developers app
Click to expand...
Click to collapse
My guess is the latest Sony firmware has solved this problem. I haven't had any strange settings since anything above .141 and have not had any SOD's.

even i am using the TL... haven't experience a such issue yet.. but one thing.. mine gets heated very soon and battery drains really fast..can notice it clearly

[Q] Note 3 screen wont turn off

As stated, screen will not go off via timeout or power button tap. Power button is recognized and will bring up shut down menu like normal.
Device is rooted (thanks DG) and had been running well for over a week. Defrosted all apps from tibu in case I got over zealous but no better. A factory reset has not cleared it up either. Hoping the oneclick from the root package will correct the issue, but thats not until I get home later this evening.
Has anyone experienced / recovered from this issue?
Smart stay is turned off

I've had noticeable lag like a few seconds and sometimes I wonder if it's going to shut off but it always does. Better set a dark lock screen wallpaper to conserve your battery
Sent from my SAMSUNG-SM-N900A using xda app-developers app

I know this is kind of basic, but what is your setting here:
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app

Thanks for the thoughts.
I had already gone through the standard - double check the settings, remove recent apps. When all that failed and a factory reset still didn't clear it up I was beginning to worry about some kind of hardware damage (don't see how since I treat it better than my child ).
Fortunately the one click from the root seems to have restored proper operation. Back to rooting and rebuilding!

3496255310
papashex said:
Thanks for the thoughts.
I had already gone through the standard - double check the settings, remove recent apps. When all that failed and a factory reset still didn't clear it up I was beginning to worry about some kind of hardware damage (don't see how since I treat it better than my child ).
Fortunately the one click from the root seems to have restored proper operation. Back to rooting and rebuilding!
Click to expand...
Click to collapse
I'm having the same problem, I rooted through vroot.... what do you mean one click fixed it little my incite would be helpful....
thank you

Mine just did this, scared the hell out of me It also didn't go into deep sleep before it started. (Not rooted).
Pulled the battery, waited 30 seconds, plugged it back in.... same thing. Waited a few minutes, seems to have sorted itself out.
Scary....

This is definitely a software bug and it is related to the Headphone detection bug that people are having too (it's actually the same bug causing both issues). This happens to me quite often after I restart my phone. It's kind of like the phone hangs during the startup process. I've also noticed that the wifi/bluetooth status that was present before restarting the phone (i.e. whether they on/off) doesn't get applied until the bug sorts itself out.
For me sometimes this works: open an app like Chrome and then hit the home button to get back to your launcher. This works 95% of the time for me. I'm wondering if it has something to do with not having Touchwiz set as the default launcher.

I'm experiencing this same problem. If I don't manually turn the screen off by tapping the power button, the screen will not timeout.