Related
my phone often goes into what appears to be sleep mode and won't wake up. Pressing or holding the power button does nothing. It doesn't respond to calls. The only way to get it to reboot is to take the battery out.
The problem has occurred with multiple roms and kernels, and I recently reverted back to the stock 2.1 rom and verified it was happening with that also. see here for what i did to revert: http://forum.xda-developers.com/showthread.php?t=1146976
Also, I'm a battery hog. Always run my phone to the max and carry around an extra battery with me. I typically swap batteries about once or twice a week and have had the phone since it was first released. Not sure if I might have caused hardware issues as a result of all the battery swapping. This issue seems to occur with all the batteries I have so it's not dependent on that).
Are you stock? Are you running custom kernel with OC and undervolting? When ive had this problem on stock, it was caused by minimal brightness or auto brightness on. Does it do it for both batteries?
sent from SGS Captivate 2.3.4 with CM7 or MIUI using Escapist or TKglitch
I'm on stock (eclair, not froyo), and no custom kernel right now (actually I tried a couple of different kernels previously and they all had the same issue). Will try turning off auto brightness.
Also an app can be causing this as well,
sent from SGS Captivate 2.3.4 with CM7 or MIUI using Escapist or TKglitch
doubtful it was an app given all the roms I tried that each have different sets of apps (miui, cyanogen, skyraider, stock). anyways, I really just needed an excuse to get an LTE phone. Just ordered a thunderbolt.
Ljga
Sent from my ADR6300 using XDA App
I don't know if this possible but I really like to find out if there is something causing the SOD that we can actually do something about(as in it isn't hardware causing it). I get SOD's on some repack kernels but not on others. When I get it has quite frequently. I am not running setcpu nor do I have any other software controlling the cpu. I have however been using juice defender. I like the product. I am going to remove it and flash a repack kernel that I know gives me SOD's and see if something in the power saving on the JD might be contributing to it. I would like to hear from others that have this issue and see if you are running anything like setcpu or JD.
I've been thinking of something. I don't have sod at all. For those that do have sod how good is your phone at overclocking? Meaning can it run stable at like 1.6 or where does it freeze at?
I'm wondering if its something to do with the difference of processors.
If anyone needs any help with the epic touch hit me up on Gtalk @musclehead84
I dont really overclock anymore but when i used to, my phone froze at 1.6. This was back when i was on calk eg30 rom. Idk what would now if i tried again
Sent from my SPH-D710 using xda premium
I haven't oc'd mine so I am not sure what it is capable of. Tomorrow I will disable the JD and flash a repack and see if that has any effect. It is frustrating because I love the repack rom's. For now I use mobile odin to flash a repack and boot to recovery if I want to nandroid then flash the stock kernel back again.
I had it until I updated modem, and when I say had it I mean right after flashing an ics rom, and every time after the phone sat with screen off for more then a minute, can run at 1.6 no problem, don't see a point though
Sent from my SPH-D710 using Tapatalk
badname said:
I had it until I updated modem, and when I say had it I mean right after flashing an ics rom, and every time after the phone sat with screen off for more then a minute, can run at 1.6 no problem, don't see a point though
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
I was just curious because on the original epic I had sod on some kernels and that phones processor was terrible. It froze when I tried to overclock it. The next one I got I wad able to overclock and I never had sod. Just seeing if phones with not being able to overclock might have an issue right now.
If anyone needs any help with the epic touch hit me up on Gtalk @musclehead84
Are you using SetCPU? If so, don't fix screen off at 200-500.
Yeah we really meed to figure out what the heck is going on. For the last few days i've been trying to figure out why i've been having SoD. Im on blazer ROM and ive found out that if I don't flash a new kernel i'm fine. But as soon as I flash rouge 1.4.1 or 1.4.0 I get an onslaught of SoD. Things ive tries to fix it are:
-Installing set CPU and raising the voltage and changing gov. to on demand.
-taking all the init.d scripts out of the blazer ROM zip before flashing.
-I find that when the phone is on the charger it never gets SoD
That last point leads me to believe that it has something to do with deep sleep. Because when the phone Is plugged in it isnt allowed into deep sleep mode and idles at 200Mhz. Ill be looking into this more tonight. If anyone would like to work with me i'm always in the e4gt ics dev channel on freenode.
Sent from my SPH-D710 using XDA
Do you run Juice Defender or any other power saving app? I am on an ICS rom and when I flash the repack, almost everytime I power off the screen I get an SOD. I am getting ready to disable JD and flash the repack and see if that makes a difference.
UPDATE: I disabled juice defender and flashed the repack. Have gone for 40 minutes without an sod. I am going to enable the jd but change several of the settings to see if that will allow me to run it with the repack and not get frequent sod's
ElAguila said:
Do you run Juice Defender or any other power saving app? I am on an ICS rom and when I flash the repack, almost everytime I power off the screen I get an SOD. I am getting ready to disable JD and flash the repack and see if that makes a difference.
UPDATE: I disabled juice defender and flashed the repack. Have gone for 40 minutes without an sod. I am going to enable the jd but change several of the settings to see if that will allow me to run it with the repack and not get frequent sod's
Click to expand...
Click to collapse
you know....oddly enough I did install juice defender a few days ago....then flashed the 1.4.0 kernel and thats when everything started.....BUT ive since reflashed the rom a million times without re installing JD and i still get SoD with the 1.4.0 kernel
If you continue to not get Sleep of deaths...will you try flashing 1.4.1 or 1.4.0?
Just to clarify, does the SOD issue include texts/calls not going thru whatsoever while phone sleeping on or off charger for more than ten minutes? I get this with any ICS up to 06, when people call me it goes to VM directly, texts go to sprint limbo. Or, do these leaks just horribly handle low signal areas? I was on stock 85 prl, and signal was about 0-1 bar sprint and force roamed on 1xrtt for 2-3 bars... since this screwed me on a couple important calls I reverted to EL29 and flashed 111115 PRL... anyone have these issues with ICS, or is it just my **** reception and network issues?
Oh, and I SWEAR... no conspiracy theory... but anyone notice pretty much all samsung leaks have issues that are magically fixed for final release? Epic froyo, GB, now ICS on the Epic Touch... just sayin... its like they dont want us daily driving these... just use em enough to beta test (really this site should be renamed XDA Beta Testers)?
The issue you are talking about sounds more like the loss of service bug that has plagued some of these phones. the sleep of death is when the screen turns off and then you can't get the phone to come back on with out holding the power button for 10 seconds or pulling the battery. I am still doing fine. I enabled juice defender but selected advanced settings and disabled jd from controlling the auto sync. I set the controls options to default. So far I haven't had an sod. I will see if I can flash those repacks but I am not sure if it will work right since I am on an ICS rom.
SoD almost certainly involves the cpu going into deep sleep and not coming out. I have never experienced this issue on the E4gT on any rom/kernel combo, but I dealt with the issue extensively on the nook color it it's early days. I can definitively say that because a large number of users are using the repacked kernels and are not having SoD issues, then it is 100% NOT repacked kernel related. SoD is caused by voltage issues or cpu step switching problems. The repacked kernels are identical in these regards across all users, therefore the repacked kernels are not causing the SoD issues.
I've had the SoD a few times on FC05 and FC06 - I'm in the process of downloading FC07 right now. It doesn't happen often (3, maybe 4 times in a few days) and I cannot pinpoint any actions preceding it. I no longer have Juice Defender installed. It's odd though, I've also had problems receiving Kik messages after a reboot. My girlfriend sent me a few messages 6 hours ago that I didn't get until I opened the app, then it's back to normal. This is a pretty regular problem. It's like I have to kick start the app before it starts. But over that 6 hours I streamed Pandora just fine and Gmail has been syncing as normal.
It is a puzzling issue. I also don't think the repack kernels acutally cause it to happen but there is something about the issue that causes it to happen frequently when using a repack. I can go back to any of the stock kernels and it works fine even with juice defender running. That is why I thought perhaps it was some app like juice defender that was causing it but people still have the issue without juice defender. Fortunately for me it seems the fix was to disable juice defender. Unfortunately for my battery though.
Well so far it seems that ive found my solution. All i did was grab the 1 click Odin to Stock Rooted EL29 and wiped everything. I wiped internal storage and flashed back to rooted stock with odin. Then i Odin'd a kernel and flashed back to blazer rom and then had to re odin the rouge kernel that was originally giving me issues. So far all is well. I suggest giving it a shot
Ok I have gsm Gnex with AOKP jelly bean build 1 with Franco kernel overclocked to 1.4 GHz and I am experiencing a random reboot problem starting today around 1 am.
I do have cpu undervolted, but it was undervolted for some time now, but just to make sure, I increased the voltage just in case. No luck.
Next thing I though that might have been a problem is the fact that I dirty flashes the AOKP build 1 from the nightly of AOKP, but I flashed it for a time now and never had that problem until today.
Another thing I changed is that I changed the boot animation from AOKP one to cyanogenmod 10 one. That, I flashed yesterday.
One thing I do like to mention is that I think there might be something to do with SetCPU profiles, because I set the profiles so it underclocks when phone screen is off or if the phone cpu or battery heats up, and one reboot was when I was unlocking the screen and another one was when I was watching youtube, and the third one was when I was playing a game, which heats up my phone. The thing is though, I have set those profiles since day 1 and never have encountered any reboots until today
Can anyone help me? Is it something that I should care about, or something that is temporary? Any recommended actions? I hate factory wiping, so that is the last thing I wanna do. Thanks in advance!
Swyped on my Galaxy Nexus running AOKP with Franco Kernel, overclocked to 1.4GHz
kyokeun1234 said:
Ok I have gsm Gnex with AOKP jelly bean build 1 with Franco kernel overclocked to 1.4 GHz and I am experiencing a random reboot problem starting today around 1 am.
I do have cpu undervolted, but it was undervolted for some time now, but just to make sure, I increased the voltage just in case. No luck.
Next thing I though that might have been a problem is the fact that I dirty flashes the AOKP build 1 from the nightly of AOKP, but I flashed it for a time now and never had that problem until today.
Another thing I changed is that I changed the boot animation from AOKP one to cyanogenmod 10 one. That, I flashed yesterday.
One thing I do like to mention is that I think there might be something to do with SetCPU profiles, because I set the profiles so it underclocks when phone screen is off or if the phone cpu or battery heats up, and one reboot was when I was unlocking the screen and another one was when I was watching youtube, and the third one was when I was playing a game, which heats up my phone. The thing is though, I have set those profiles since day 1 and never have encountered any reboots until today
Can anyone help me? Is it something that I should care about, or something that is temporary? Any recommended actions? I hate factory wiping, so that is the last thing I wanna do. Thanks in advance!
Swyped on my Galaxy Nexus running AOKP with Franco Kernel, overclocked to 1.4GHz
Click to expand...
Click to collapse
Tough one. Myself I'd start off by disabling all OC/undervolt settings & disable SetCPU profiles. If that doesn't resolve the issue, temporarily flash back stock kernel.
Petrovski80 said:
Tough one. Myself I'd start off by disabling all OC/undervolt settings & disable SetCPU profiles. If that doesn't resolve the issue, temporarily flash back stock kernel.
Click to expand...
Click to collapse
For some reason, when I cleared the cache and dalvik, It doesn't seem to reboot anymore. But if it ever happens again, I'll do what you told me
Thanks!
Hi, this happened again today, but I noticed that it isn't a full reboot. (no Google splash screen)
Any ideas?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Been noticing this since last week. Every time I use my phone for like 1 or 2 minutes, the phone starts getting hot. Usually, it gets hot after an hour of use (Facebook, Messaging, Browser, Twitter, Play Store). Went to Performance settings in Settings, then Processor, and notice the Current CPU frequency is always at 1000 MHz, then goes down to 200 or 100 MHz when idle for a few seconds. Switched between conservative and ondemand governor, no OC. Was on PA 2.54 when this happened, but I'm on CM10 Stable now, and it's still getting hot after using it for a few minutes.
This hasn't happened to me before. Not sure if this is normal, but I just want to make sure.
My recent heat and battery drain was coming from an app. I didn't check the CPU.
I checked the battery area of the settings and found a locale add-on that was draining more juice than my screen.
sent from a secret underground bunker
It will happen if your signal is real bad or 3G is down in your area.
I don't think it's my signal. I get 2 or 3 bars almost all of the time at home with the FC09 modem.
Besides opening and/or using an app, it seems that the CPU clock will go max speed if I do something, such as scrolling. Battery is also draining quickly before this was happening to me.
Sent from my SPH-D700 using Tapatalk 2
InsaneHien said:
Went to Performance settings in Settings, then Processor, and notice the Current CPU frequency is always at 1000 MHz, then goes down to 200 or 100 MHz when idle for a few seconds. Switched between conservative and ondemand governor, no OC. Was on PA 2.54 when this happened, but I'm on CM10 Stable now, and it's still getting hot after using it for a few minutes.
Click to expand...
Click to collapse
I think that's a Jellybean-specific CPU behavior (to keep system flowing like "silk", JB put CPU at max the instant you have your finger on screen... At least that's what I heard). Try ICS/GB ROMs and see if problem persists.
Sent from HTC Incredible S @ AOKP
AndyYan said:
I think that's a Jellybean-specific CPU behavior (to keep system flowing like "silk", JB put CPU at max the instant you have your finger on screen... At least that's what I heard). Try ICS/GB ROMs and see if problem persists.
Sent from HTC Incredible S @ AOKP
Click to expand...
Click to collapse
Yeah, you're right. I even looked it up. It's part of Jelly Bean.
I'm going back to CM9 or The People's ROM.
You could try a different kernel, or lower voltage. Sorry not sure what phone this topic is for lol but that's some options. It takes a lot to get my phone hot, and I'm on jelly bean
Sent from my Galaxy Nexus using Tapatalk 2
I don't have this problem on nitest kernel with the ns4g modem
Sent from my SPH-D700 using Tapatalk 2
You likely have an issue with your settings.
If it's not an app, you probably have an issue with your performance settings.
Try turning off some of the eye-candy features in the settings. This will likely include the Cyanogenmod specific setting area as well.
That should at least help.
Ruedii said:
If it's not an app, you probably have an issue with your performance settings.
Try turning off some of the eye-candy features in the settings. This will likely include the Cyanogenmod specific setting area as well.
That should at least help.
Click to expand...
Click to collapse
It didn't help unfortunately.
I flashed CM9 earlier and the issue still exists. I'm now back on CM10 (11/22 nightly).
It's okay if this can't be resolved. I am probably gonna go back to a GB ROM.
EDIT: Issue still persists in GB. I'm guessing it could be a hardware issue? I have no idea. Back to JB. I'm still willing to try anything to resolve this. Thanks to those who posted some solutions.
Sent from my SPH-D700 using Tapatalk 2
Has anyone else noticed that with any of the ASOP or CM builds from time to time the screen will not turn on but the buttons light up? I have had this happen about 3 - 4 times a day no matter what build I am using that is based off of ASOP. The only way out is to hard power off and restart.
Yup. People call it SOD (sleep of death).
It's usually a kernel issue. I found that bumping up the low clock speed voltages helps a LOT. Just one notch in Trickster. The Temasek kernel (I'm using exp6) seems to help as well.