Database Users

death sleep (doesn't turn on from sleep) - voltage / current issue?

I'm running the twilight zone v1.1.1 kernel and recently my phone has gone to a "death sleep" repeatedly when not plugged in. (when plugged in via usb on computer or wall wart its fine). I end up having to remove the battery and putting it back in to get it to work again (till the next time it falls asleep).
Is this possibly a kernel issue? a kernel controlling voltage issue? (under volting on battery?). A hardware issue? I've been running this kernel for a while now and its only started happening in the past few days.
I figure I'll try out stock soon to see if its a problem (and if it is, as I pay for TEP, I'll just take it into a store), but wanted to check here first
thanks.

thetoady said:
I'm running the twilight zone v1.1.1 kernel and recently my phone has gone to a "death sleep" repeatedly when not plugged in. (when plugged in via usb on computer or wall wart its fine). I end up having to remove the battery and putting it back in to get it to work again (till the next time it falls asleep).
Is this possibly a kernel issue? a kernel controlling voltage issue? (under volting on battery?). A hardware issue? I've been running this kernel for a while now and its only started happening in the past few days.
I figure I'll try out stock soon to see if its a problem (and if it is, as I pay for TEP, I'll just take it into a store), but wanted to check here first
thanks.
Click to expand...
Click to collapse
If I remember correctly, there were a lot of people having this issue with SFR and you shoudl check that thread for more info. However, long story short, this can definitely be related to underclocking and/or undervolting.
Are you using SetCPU to underclock? If so, set your minimum speed to 200 MhZ as I think that resolved it for most people.

ok, set to 200mhz (was at 100mhz) will see if that fixes it. thanks.

I'm having the same issue since flashing Emotionless Beast. Used Voltage Control to set to 200. Is there a way to keep the settings through a reboot?

ok, setting to 200mhz didn't seem to fix my issue, will probably try another kernel.

thetoady said:
I'm running the twilight zone v1.1.1 kernel and recently my phone has gone to a "death sleep" repeatedly when not plugged in. (when plugged in via usb on computer or wall wart its fine). I end up having to remove the battery and putting it back in to get it to work again (till the next time it falls asleep).
Is this possibly a kernel issue? a kernel controlling voltage issue? (under volting on battery?). A hardware issue? I've been running this kernel for a while now and its only started happening in the past few days.
I figure I'll try out stock soon to see if its a problem (and if it is, as I pay for TEP, I'll just take it into a store), but wanted to check here first
thanks.
Click to expand...
Click to collapse
Same thing happen to me a few time on twilight but since I'm been on genocide 2.0 kernel no problem for me genocide is the best for my phone
Try it out with jornaling on
Sent from my SPH-D700 using xda premium

I know this might sound stupid, but I had a problem similar to this the other day. It was only the screen was blank, but would still accept inputs on it. I could unlock the phone (using the TW lockscreen) and then, I was able to hold the power key and select reboot (on-screen location pressed from memory).
Is it just the screen, or the entire phone?

thetoady said:
ok, setting to 200mhz didn't seem to fix my issue, will probably try another kernel.
Click to expand...
Click to collapse
Hmm... Is it also undervolted? Might try changing that. FYI, I have also been using Genocide with no problems for a while now...

Pretty sure its the entire phone. tried dialing it from my desk phone and it didnt ring.
also, the epic's version of ctrl-alt-del doesn't seem to work either (just happened again). will be trying genocide when I get home.

thetoady said:
Pretty sure its the entire phone. tried dialing it from my desk phone and it didnt ring.
also, the epic's version of ctrl-alt-del doesn't seem to work either (just happened again). will be trying genocide when I get home.
Click to expand...
Click to collapse
Try genocide 2.0 kernel & when you use titanium backup don't re install the app &data just install the apps hit the thank you button if I helped you in anyway!
Sent from my SPH-D700 using xda premium

Until you figure out what works for your phone avoid all voltage changes and set minimum frequency to 200 Mhz and to set on boot. There are not enough advantages to over and undervolting to not have a working phone.
Sent from my SPH-D700 using XDA App

kennyglass123 said:
Until you figure out what works for your phone avoid all voltage changes and set minimum frequency to 200 Mhz and to set on boot. There are not enough advantages to over and undervolting to not have a working phone.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
That's good advice. Didn't UV and OV cause some bricks once? My phone does that death sleep thing when I was at 100 Mhz on Genocide. Set it to 200 and no more problems.

uSo things were a bit more involved.
My phone died totally (major FC avalanch on startup), so I reimaged it, installed genocide and restored from backup (over an hour! w/ data) and its behaving well now.
though I do hate the spam genocide puts in the boot image.

Questions about standby mode

I may have asked this before, but I'm not sure.
My A500 has a custom ROM on it, but its had this problem on multiple roms. I haven't tried on stock yet, but that's probably my next step. Anyways, here are my questions:
- How long can you usually leave your A500 in standby mode and still wake it up?
- Is there a way to manually put the tablet into sleep mode?
When I first got it, I remember leaving my A500 in standby mode (it should automatically go into standby when you idle, right?) and being able to wake it by hitting the power button almost a day later. Now I can only do it for a few hours and then it won't come out of sleep. I'll have to turn it off by holding the power button down (even though there is no indication that it is turning off), then I can turn it on again. Sometimes my battery will be depleted, apparently indicating that it did not properly go into sleep mode?

chairhome said:
- How long can you usually leave your A500 in standby mode and still wake it up?
- Is there a way to manually put the tablet into sleep mode?
Click to expand...
Click to collapse
Usually I can leave it in sleep mode for well over a day, and it still wakes.
Press the PWR button will put it to sleep.
I would guess, the problem is Kernel related. This sometimes happens with kernels that supply Over/Under voltage. Usually for overclocking. Most of the newer kernels walk a fine line with trying to get maximum battery life, and your tab may suffer "the sleep of death" and require a hard re-boot.
I would advise one of the older kernels, like RTrips 3.4+ or Thors 3.7. Try to stay away from the most recent kernels.
Also, a few of the custom 500 roms, are really "cooked". Lots of changes to the rom itself.
You may want to try a lightly stock rom with a lower version kernel. This will fix the sleep of death issue.
As with your battery, the usual stuff like wifi/gps on, notifications, syncs, these all cause battery drain.
I leave my wifi on, but my syncs are set to every hour. Mail, Sms, and FB (silent). GPS is hard set to off. Widget refreshes also are 4 hrs.
I lose maybe 6% or so overnight.

All of the above is true there is one more issue that can occur . Google backup and restore.a bad app that you keep getting restored by the above.
if all else fails you can try the fallowing..
download a near stock rom.. with STOCK Kernel .
in cwm
of course wipe all
format all..
flash rom..
wipe all again.. (you know all of that)
if im having a app issue.. to find the app.
when your tablet boots the first time.. when you get to setting up your google account.. untick the boxes for backup and restore of data.. then install your apps one at a time back . to see what app is causing the trouble.. Of COURSE this all only applies if the rom flash does not work.. google often puts the problem back.. Ti backup will do the same .. put issues back.. Trial and Error is only way to solve this issue. ITS THE ONE MOST COMMON AND MOST TALKED ABOUT ISSUE WITH not only our tablet but all of android devices..
GOOD LUCK ..

Moscow Desire said:
Usually I can leave it in sleep mode for well over a day, and it still wakes.
Press the PWR button will put it to sleep.
I would guess, the problem is Kernel related. This sometimes happens with kernels that supply Over/Under voltage. Usually for overclocking. Most of the newer kernels walk a fine line with trying to get maximum battery life, and your tab may suffer "the sleep of death" and require a hard re-boot.
I would advise one of the older kernels, like RTrips 3.4+ or Thors 3.7. Try to stay away from the most recent kernels.
Also, a few of the custom 500 roms, are really "cooked". Lots of changes to the rom itself.
You may want to try a lightly stock rom with a lower version kernel. This will fix the sleep of death issue.
As with your battery, the usual stuff like wifi/gps on, notifications, syncs, these all cause battery drain.
I leave my wifi on, but my syncs are set to every hour. Mail, Sms, and FB (silent). GPS is hard set to off. Widget refreshes also are 4 hrs.
I lose maybe 6% or so overnight.
Click to expand...
Click to collapse
erica_renee said:
All of the above is true there is one more issue that can occur . Google backup and restore.a bad app that you keep getting restored by the above.
if all else fails you can try the fallowing..
download a near stock rom.. with STOCK Kernel .
in cwm
of course wipe all
format all..
flash rom..
wipe all again.. (you know all of that)
if im having a app issue.. to find the app.
when your tablet boots the first time.. when you get to setting up your google account.. untick the boxes for backup and restore of data.. then install your apps one at a time back . to see what app is causing the trouble.. Of COURSE this all only applies if the rom flash does not work.. google often puts the problem back.. Ti backup will do the same .. put issues back.. Trial and Error is only way to solve this issue. ITS THE ONE MOST COMMON AND MOST TALKED ABOUT ISSUE WITH not only our tablet but all of android devices..
GOOD LUCK ..
Click to expand...
Click to collapse
Thanks to both of you. I needed reassurance that my tablet wasn't just messed up. I have a warranty on it and was thinking about getting it replaced and seeing how the new one behaved, but I'll try the suggestions. I'll probably try to reload my ROM after formatting and start with just the base apps and add one at a time as you suggested. If that doesn't work, I'll try a different kernel or ROM with a different kernel. I've already tried not using SetCPU to under/overclock, but that didn't work. Thanks again!

Another (relatively rare) issue is that the kernel you're using actually is flawed and fails to wake the GPU after it went to sleep (this may be a lot later than the device itself, depending on background services!). In this case using a different kernel will solve the issue (stock kernel is works).
EDIT: Posted at the same time... By all means try another kernel, this is a known evil with custom ones.

Okay, so I've tried installing the stock, rooted 3.2 ROM which uses the stock kernel. Did not restore any apps from Google Backup. Still getting the same issue. Does this point to a hardware issue? I have a warranty on this tablet, so I want to know if I should try trading it in.

OK, before you take your tab back, personally, I wouldn't worry about it.
I have noticed, on some occassions, (yes, I do run stock rooted on occasion), that sometimes, the tab will get what we call the sleep of death. And usually, this may occur over a long period of time. Also, sometimes, I have to hit the pwr button several times, before it wakes.
+1 with the PP on overclocked kernels. This happens with the most recent ones.
Fortunately, System Tuner Pro, will increase MB voltages, so you don't get this.
If it does it again, and you are on stock, try to press the pwr button several times.

cool, thanks. I'll try this today.

chairhome said:
Okay, so I've tried installing the stock, rooted 3.2 ROM which uses the stock kernel. Did not restore any apps from Google Backup. Still getting the same issue. Does this point to a hardware issue? I have a warranty on this tablet, so I want to know if I should try trading it in.
Click to expand...
Click to collapse
Mine has never worked on any rom with any configuration. Turning off wifi helps sometimes.

Bug Report (Zip's ROM)

Hello All,
I'm really not sure if this a bug or setting adjustment. When the phone goes in the sleep mode, it will not wake at all and I have to pull the battery. This happens intermittently and there is not one app that it does it the most. I have Zip's 4.03 on my phone, but it has been doing it with all the Zip ROMs. I've searched dev forum and I can't seem to find anything, so it's probably something with my phone. I tried to make adjustments the performance settings with both the built in set cpu and the setcpu from the market and it still happens.
On this last update, I formatted data and dalvik cache and flashed the ROM in CWM and the aroma installer came up with no problems.
Again... love the ROM and don't kill the posting Newb. Just trying to help out.
Thanks
Eric

cybereric518 said:
Hello All,
I'm really not sure if this a bug or setting adjustment. When the phone goes in the sleep mode, it will not wake at all and I have to pull the battery. This happens intermittently and there is not one app that it does it the most. I have Zip's 4.03 on my phone, but it has been doing it with all the Zip ROMs. I've searched dev forum and I can't seem to find anything, so it's probably something with my phone. I tried to make adjustments the performance settings with both the built in set cpu and the setcpu from the market and it still happens.
On this last update, I formatted data and dalvik cache and flashed the ROM in CWM and the aroma installer came up with no problems.
Again... love the ROM and don't kill the posting Newb. Just trying to help out.
Thanks
Eric
Click to expand...
Click to collapse
Im running the same as you and i haven't had a single reboot or it not waking up at all. Try this kernel and see if it makes a difference for you. http://forum.xda-developers.com/showpost.php?p=24214386&postcount=3

Shot of awesomeness v2-zip edition
ok...I followed all of the instructions and flashed the zip. I set the cpu at 1228/230. What is the best CPU settings with this kernel?

cybereric518 said:
ok...I followed all of the instructions and flashed the zip. I set the cpu at 1228/230. What is the best CPU settings with this kernel?
Click to expand...
Click to collapse
i use 1305 max 384 min on interactive ...i get great battery life. And make sure you use rom toolbox from the market. Its a great app to have.

yeah..I got the ROM toolbox. thanks for the settings..I will give them a try.

Another lock up
Hey em2drvr03,
I had another sleep lock up today. This time I noted what was going on with the phone when it happen for feedback. I was playing a radio station in the iheart radio app. My phone was in sleep for about 20 minutes when I tried to wake it. Even though I could not wake it, it was still playing the radio station with brief skips. My wifi was off and I was streaming on my 4G. My phone is responding better...it would sleep lock up more often on the old kernel.
Eric

cybereric518 said:
Hey em2drvr03,
I had another sleep lock up today. This time I noted what was going on with the phone when it happen for feedback. I was playing a radio station in the iheart radio app. My phone was in sleep for about 20 minutes when I tried to wake it. Even though I could not wake it, it was still playing the radio station with brief skips. My wifi was off and I was streaming on my 4G. My phone is responding better...it would sleep lock up more often on the old kernel.
Eric
Click to expand...
Click to collapse
To be honest i have never had any of those problems...i've been running zips 4.03 since it was released and no problems. I wish i knew what to tell you.

It's all good
It's fine. It's happening far less with the kernel update. Someone else mentioned it in Zip's Dev forum. They called it the "Sleep of death", so at least I'm not crazy...lol.

[issue] Need some feedback from GB users

hello, I would like to know if I'm alone on this issue, right now I'm running stock 2.3.6 on my i9100 and I have found an issue.
When Power saving mode is activated (the default one), if I open the camera app and turn off the screen for 1 minute, the phone dies and I have to reset it to make it work again.
Some friends told me that on ICS it doesn't happen so I was wondering if I got a faulty unit or this OS has this bug.
I would like some feedback from you guys with gingerbread onboard, thanks.

ellokomen said:
hello, I would like to know if I'm alone on this issue, right now I'm running stock 2.3.6 on my i9100 and I have found an issue.
When Power saving mode is activated (the default one), if I open the camera app and turn off the screen for 1 minute, the phone dies and I have to reset it to make it work again.
Some friends told me that on ICS it doesn't happen so I was wondering if I got a faulty unit or this OS has this bug.
I would like some feedback from you guys with gingerbread onboard, thanks.
Click to expand...
Click to collapse
This has never happened to me, but maybe try to turn off the device and take the battery out, leave it for a minute and reinsert the battery and restart. Then try to reproduce the problem.

Never happened to me or even heard of it
Sent from my GT-I9100

have you tried to see if this bug would occur without power saver mode on?,i never had this issue before nor heard of it

thanks everyone for your answers and concerns, the problem has been isolated:
It was a bug caused by a underclock that I did have that so far only occurs on the circumstances that I had on my phone.
When your phone turns off the screen, it will go to sleep mode or deep sleep mode depending on the running apps you have in that moment, these modes allow the CPU to low the frequencies (CPU Clock) in order to preserve battery life.
Comes to public interest that when using the camera app, the phone uses a high frequency clock to process photos and videos taken with the camera.
As because I did have a custom kernel that tweaks the CPU in order to gain more battery life, when battery saver option (which slow the max freq. clock of the CPU) was ON in my phone, the phone couldn't jump directly from sleep mode to max freq mode to keep camera app running and the CPU kept "slept"
If serves as interest of anyone, the kernel I was using was Siyah Kernel (don't remember which version, just check out the date this thread was posted and compare it with siyah kernel log to know by that date which was).

fuel_alerted Kernel wakelock bug in India ICS

Yesterday I got the ICS update via Kies.
Saw that my CPU was not going into deep sleep.
BetterBatteryStats showed the problem
fuel_alerted is forcing a kernel wakelock.
I tried searching the forums, and there are some fixes in some custom kernels.
However, I could not find out what exactly is fuel_alerted, why does this happen, and does it happen on all phones?
I believe taking out battery and putting it back in should fix the problem. Right?
Will it come again?
Whats the root cause of this problem?

I powered off, removed battery, and then put it in, powered up the phone. Now phone is going into deep sleep.
But I still cant figure out what is fuel_alerted, and whats the issue, why does it come?

i dont have this issue. i flash DDLP8 india yesterday.

tsk1979 said:
I powered off, removed battery, and then put it in, powered up the phone. Now phone is going into deep sleep.
But I still cant figure out what is fuel_alerted, and whats the issue, why does it come?
Click to expand...
Click to collapse
I had this on LPY, Did same as u did and its gone. Now yesterday i flashed LP8, its not yet there. Let us know if it comes again.

weng_cas said:
i dont have this issue. i flash DDLP8 india yesterday.
Click to expand...
Click to collapse
All ICS roms have this issue. You just have not hit it. Its a bug in the kernel. Somebody has fixed it in an open source code. I googled quite a bit, and also found the offending function
https://github.com/CyanogenMod/samsung-kernel-c1/commit/5f6d8422629002c530dcf30891c241fe3ee2e0ab
katyarevishal said:
I had this on LPY, Did same as u did and its gone. Now yesterday i flashed LP8, its not yet there. Let us know if it comes again.
Click to expand...
Click to collapse
Will do
Here is what the bug report says
"However, when the SOC starts rising, the wakelock was only destroyed"
Now what is SOC referring to? System on Chip? Does not make any sense. Can somebody look at the github page?

Try disabling the power saving mode and restarting.
Don't use power saving mode. I've only seen this Wakelock after I've checked the powersaving option.
Ironic. But true.
Sent from my GT-N7000 using XDA Premium HD app

SoC = State of Charge in this case.
It's another classic case of Samsung failing to fix well documented and fixed bugs. Not as severe as the eMMC brick bug (documented since before November by Google during Galaxy Nexus development), but still - documented and fixed by the community for many months.
I fixed this in I777 Gingerbread kernels back in October, I9100 kernel developers pulled in the fix fairly quickly. Despite the bug being documented and fixed by the community for months, it is still present in all of Samsung's ICS kernels.
It has been fixed in the CM9 kernel since the day I9100 Update4 sources were released.
It's also fixed in DAFUQ. (However a lot of other stuff is currently broken in DAFUQ.)
No need to pull the battery when you encounter it, just reboot. Rebooting is the only fix without flashing a kernel that has the bug fixed.

Thanks entropy!
Actually reboot did not make the bug go away. I had to pull out battery.
I am on DDLP8(India ICS)
I guess, with kernel source released, we should see everything like FM etc., supported in CM9. I will move to CM9 then

tsk1979 said:
Thanks entropy!
Actually reboot did not make the bug go away. I had to pull out battery.
I am on DDLP8(India ICS)
I guess, with kernel source released, we should see everything like FM etc., supported in CM9. I will move to CM9 then
Click to expand...
Click to collapse
I just noticed this param, I am not sure it was there before (I am on LPY)
Rebooting and it's still there!
Doing Power off now..

tsk1979 said:
Thanks entropy!
Actually reboot did not make the bug go away. I had to pull out battery.
I am on DDLP8(India ICS)
I guess, with kernel source released, we should see everything like FM etc., supported in CM9. I will move to CM9 then
Click to expand...
Click to collapse
No - FM is a userspace issue, as is MHL.
For CM9, the only things the source release affects are:
1) Speakerphone (already fixed)
2) Possibly a more reliable wifi driver (although CM9 may just kangbang pawitp's great work on the Aries kernels)
3) Backporting some performance features such as improved busfreq control

Entropy512 said:
SoC = State of Charge in this case.
It's another classic case of Samsung failing to fix well documented and fixed bugs. Not as severe as the eMMC brick bug (documented since before November by Google during Galaxy Nexus development), but still - documented and fixed by the community for many months...
...No need to pull the battery when you encounter it, just reboot. Rebooting is the only fix without flashing a kernel that has the bug fixed.
Click to expand...
Click to collapse
Found this thread after seeing this causing wakelocks in my i9100 S2. Thanks for the explanation.
However, rebooting - as well as powering off and switching on again still did not eradicate the fuel_alert problem and CPU Spy was showing my phone couldn't enter deep sleep.
Only after pulling out battery (and waiting for 1 minute for good measure) and powering up again did the bug go. CPU spy then reported my phone had entered deep sleep and the fuel_alerted entry was no longer showing in BetterBatteryStats.

Remove the battery and wait for 1 minute and reboot the phone , it will fix the problem.
To avoid it from happening again , remember to wake and unlock the phone every time before removing the phone from charging(Data cable & charger both).

I never unlock the phone before plugging and unplugging, and inspite of that problem is not reappearing.
So it may be completely random. I looked at the github code, but somehow could not figure out any relation to lock/unlock while charging.

It happened to me once and i removed the battery for 15 mins and it disappeared. But today it happened again. I do have power saving mode enabled but i dont want to again and again remove the battery to fix it. I charge my phone by turning it off and once its charged i remove the charger, let the display go off and then only turn on the phone. Do i need to turn on the phone before i remove the charger?

I think the power save mode has something to do with it. I didn't check the battery history before turning it on though but after a few days the Note didn't last 12 hours with only 1 hour of usage. The processor was awake even when the screen was off.
As suggested here I removed the battery for a few mins. I reinstalled the battery and charged it while the phone was still off. After a few hours of charging I turned the phone on and date/time defaulted to base time as expected. I observed battery behavior for a few days and the processor is now sleeping when the display is off and only wakes up every once in a while maybe to sync. BTW I only have Gmail sync on everything else is set to manual. And I haven't touched the power save option since