Database Develop

[Q] Sleep/Charge of Death

I been wondering if the phone never had sleep/charge of death before can a kernel and/or ROM be the culprit to it? I been trying to look more into it and haven't found a definite answer to it so I ask you guys what is causing it. I've tried different kernels and ROMs and some do it other don't is there anyway to just know? Or a good way to narrow it down?

I was able to track mine down to a kernel that supported Overclocking. Once I switched to a ROM that had a kernel that wasn't OC supported (older version of same ROM) my charging death went away. I think it has to do with the OC settings, the idle clock speed is too slow, but no matter what settings I used I got sleeping death every other night until I swapped for the other version.
Sent from my Captivate running GR-12

Only time I have encountered the Sleep/Charge of death was when I was OCing the phone and UVing it also. Having too much of a variance in the UV was my problem. Wants I started to UV the same amount across the board or close to it my problems were solved. For instance the most I UV is 75 and the least is 25. if you had a gap like 150 to 0 that could be what is causing your problem. At least that is what I noticed for myself. Now I am perfectly fine for over a month.

The phone boots up to 1/2 way through the kernel when charging in off mode... IBL, PBL, SBL, Params, Kernel... If it hangs, then it's likely hung at a custom kernel.

If the ROM craps out it soft reboots and/or goes into a boot loop. I don't think that a ROM can cause your phone to randomly shut down.

Sleep of Death - Workarounds

I’m creating this thread to help anyone who’s been affected with SOD (Sleep of Death). Here’s a brief history of what I’ve tried so far:
- I was running stock 2.2 for about a year, had lag, choppiness, etc.. but never a SOD
- Flashed CM7.1 2 weeks ago (stock kernel), phone is not amazingly fast but experiencing SODs every few days.
- Created a Tasker profile to wake the phone every 1 hour, (wait 5 seconds command), no SOD for a week
- This morning, got a SOD again.. missed my alarm and was late for work 
- All SODs happen at night while charging.
- Today I downloaded ‘Wake my Android Pro’, supposedly it send a wakelock every 29 minutes and prevents the phone from entering deep sleep.
My next step if this fails and I get another SOD:
- Set CPU min clock to 350 (read that this doesn't help but will try anyway)
- Activate SoftLocker to prevent the phone from ever going to sleep, this is the last resort since it will affect my battery life (wish there was a Tasker plugin to toggle the settings so I can enable it only when charging)
Does anyone know how long after turning off the screen does the phone go into deep sleep (versus regular sleep)?

gabster21 said:
I’m creating this thread to help anyone who’s been affected with SOD (Sleep of Death). Here’s a brief history of what I’ve tried so far:
- I was running stock 2.2 for about a year, had lag, choppiness, etc.. but never a SOD
- Flashed CM7.1 2 weeks ago (stock kernel), phone is not amazingly fast but experiencing SODs every few days.
- Created a Tasker profile to wake the phone every 1 hour, (wait 5 seconds command), no SOD for a week
- This morning, got a SOD again.. missed my alarm and was late for work 
- All SODs happen at night while charging.
- Today I downloaded ‘Wake my Android Pro’, supposedly it send a wakelock every 29 minutes and prevents the phone from entering deep sleep.
My next step if this fails and I get another SOD:
- Set CPU min clock to 350 (read that this doesn't help but will try anyway)
- Activate SoftLocker to prevent the phone from ever going to sleep, this is the last resort since it will affect my battery life (wish there was a Tasker plugin to toggle the settings so I can enable it only when charging)
Does anyone know how long after turning off the screen does the phone go into deep sleep (versus regular sleep)?
Click to expand...
Click to collapse
I'm also using CM7 (nightly #146) with neo kernel..I only have had SOD once (while using stock kernel IIRC). Now I'm booting every evening before going to bed and haven't noticed any problems (knocking the wood..).
Btw, as you came from froyo did you flash GB before going to CM7? Or at least GB bootloaders prior flashing?
Can't really say any solution to your problems since these sods are quite hard to catch..logcat, dmesg, etc are our friends with these kinds of problems
Sent from my GT-I9000 using xda premium

Kurre said:
I'm also using CM7 (nightly #146) with neo kernel..I only have had SOD once (while using stock kernel IIRC). Now I'm booting every evening before going to bed and haven't noticed any problems (knocking the wood..).
Btw, as you came from froyo did you flash GB before going to CM7? Or at least GB bootloaders prior flashing?
Can't really say any solution to your problems since these sods are quite hard to catch..logcat, dmesg, etc are our friends with these kinds of problems
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
No, I didn't flash GB, I installed CWM bootloader and flashed CM7 from recovery (had to find a workaround to get past the e3 protection).
So far with "Wake my Android Pro" I see the screen go on and off quickly (about 1/2 a second) every 29 minutes.. too early to tell if this is helping with SODs, I'll report back regularly to update the results

Woke up today to my alarm, wohoo! Phone doesn't seem to go to sleep and battery life is fine.

charging on a PC.
Hello
Thank you for the informative thread.
I have a Galaxy S i9000 running 2.3.6, XXJW4 and CF-root, and find it frustrating not to be able to fully trust my phone to respond whenever needed, be it listening to Internet radio, using sat nav, getting Facebook notifications (yes I got them back after reinstalling Facebook and clearing Dalvik cache but I should talk about that in another thread) and of course making and receiving calls now and then.
I was wondering whether the fact that I have been hooking it up to a PC to charge it through the day (and of course plug and unplug it a few times during the day) actually made the situation worse.
So far I have been getting an SOD every two days. The 'serious' SOD would come on after a 'less serious' SOD had already happened ie the phone went into coma and then came out of it and lasted for 6 to 8 hours longer before actually falling into the SOD coma.
I stopped using the PC as a charger (using a cheapo replacement micro USB charger) and so far 3 days have gone by without a hint of an SOD. Fingers crossed. Will keep investigating.
Cheers

[Q] Phone runs hot, High Drain - All usual fixes tested.

Device: Samsung Galaxy S GT i9000
Symptoms:
When Charging Device is hot to the Touch in the upper half of the screen and on the rear between the camera and the heat vent.
Battery drains at around 15-25% per hour when IDLE. 15% when in deep sleep in airplane mode with ALL APPS KILLED. 25% when I leave ALL network connections open and allow sync.
Phone was new less than 2 months ago. Still under warranty and I will send it back if no ideas come from this but wanted to see if anyone had a solution as I have noticed HUNDREDS of similar posts all vaguely scattered through different threads on different sites around the web and this seems like the definitive place to come to see if anyone can put their finger on it.
When did this occur?:
A short while after (days) of flashing CM9 nightly from the beginning of June (05/06 I think but can't recall exactly).
Tests performed:
Purchased new battery and fully charged - no change.
Flashed stock GB ROMs where the issue had not occured - no change.
Cleared battery stats several times - no change.
Tried different modems/radios including Nexus S radios- no result
Current ROM: CM 7.2
Kernel: Glitch 13.1
Other ROMs/Kernels where the same results were achieved...
CM9 (latest nightlies)
Stock JVU, JVS, JW4 and JW5
Semaphore Kernel, Devils Kernel
I use Voodoo Sound/Colour kernels apart from the testing I did with stock ROMs
Will leave it on over night after clearing stats so you can see for yourselves.
Any questions ask away.

I should add:
Used OS Monitor and one of the more detailed CPU monitors to look at what was going on.
Did not appear at any time to be using what I would consider high CPU utilisation, typically trending between 0 and 30ish. No background apps running, all radios turned off.
The only anomaly that stuck out at me is that system_server was using ~105% of RAM which I would have thought was rather difficult. Made me wonder if there was something loading/unloading itself from RAM.
As I am a heavy music user I have tested the Mediaserver issue where corrupt files are continually scanned by mediaserver process. Removed all media files from both my external and internal storage then formatted both while on a stock ROM (JVU and JW4). There was no change.
EDIT: I should add - The thing that makes this so strange to me is that the battery decreases at a rapid rate when Battery stats regarding usage DO NOT CHANGE. The percentages for the apps that WERE using the battery - i.e. winamp/mediaserver/android system do not change.
The reason I have posted this is that i have seen literally HUNDREDS of people posting this very same issue but never in the same place and never getting an answer.
Also - Thankyou to the kind mod/admin who approved my account so I can edit stuff. It was getting a bit annoying for the first week there.

Re
Hi,
To be honest I never heard/read of the problem you are describing. Most users report high battery drain on a certain ROM/kernel/modem but you say you have tried quite a lot.
If the phone is new, the only thing that comes to mind is that the USB charging socket is faulty. It may not charge properly or even have some bad connectors that are damaging the battery.
In any case, Samsung support is the way to go here.
Hope this helps

OMG, im having the same exact problem... the phone is super hot on the back where the sim card is inserted. I did everything as you, still no change, my battery lasts like 7 hours on deep sleep. Guess our phone is broken. super crap.

Anyone knows how to fix this? Is there anyway that my phone has some files from previous custom roms even though used odin to flash samsung original ones?

Had the same problem when my device was only 6 months old, the battery was becoming faulty, got a new battery and problem solved.

I bought a new battery and i still have the same problem... which battery did u get?

streakpt said:
I bought a new battery and i still have the same problem... which battery did u get?
Click to expand...
Click to collapse
An official samsung battery from Amazon, re flash you device with another rom and wipe battery stats.

Did all that, the problem still continues... mega battery drain and the phone is at 44C degrees... is there any tool i can use to diagnose the problem?

Hi snaleman,
You could try BetterBatteryStats, to help diagnose your issue further, there is a paid version on the market (Google Play Store). There is also a thread on this forum, from the dev....hint
I tried winamp for android, ages ago, but had similar issues. (This player might well be your issue.) So I now use "PowerAmp". Neutron MP is cool too.
Also, do you use lippol94's kernel cleaning script. I use this every kernel/ROM change.
Search here for this:
ultimate_kernel_cleaning_script
Hope this info helps your baby.

Hey
U can try to flash a stock rom from sammmobile.com..
Use it for a few days and check...may help u..
Cheers
Sent from my GT-I9000 using xda app-developers app

Backup your apps with titanium backup or something else.
Make a backup from CWM recovery
Wipe data/cache/dalvik
Restore user apps and not system app
If your problem is not fixed you can restore your CWM backup

Nothing you guys posted worked... battery lasts 11 hours on sleep...

Another problem that im facing is that when im on a phone call, theres is alot of breaks in the other persons voice and sometimes the voice call goes out and i lose all my network signal.

If you are using the Voodoo sound app that may be the cause. I've noticed on my phone that deep sleep no longer works when the voodoo app is installed, most likely the app is holding a partial wake lock and not releasing it.
See if it happens with the app uninstalled or frozen.
Sent from my Nexus 7 using Tapatalk 2

Signal Strength¿
streakpt said:
Another problem that im facing is that when im on a phone call, theres is alot of breaks in the other persons voice and sometimes the voice call goes out and i lose all my network signal.
Click to expand...
Click to collapse
You've just made me think of something else that it may be.
Do you have 4 or 5 bars of signal strength?
I've found when in certain areas (very close to "deadspots" in network reception), that if I use another frequency, [eg. 900 & 2100 (for my network), yours may be different] I can get a better signal, also much better battery life, as the phone is not struggling to reach the network.
If you use your dialer to enter this code
*#*#197328640#*#*
Then
[1] DEBUG SCREEN
THEN
[8] PHONE CONTROL
then
[7] NETWORK CONTROL
then
[2] BAND SELECTION
you will then have a selection of frequencies available. The asterisk * will tell you what one(s) is/are active.
"Google" your network service providers frequency bands. I found mine were on a "Wiki" page.

Bsod with Idle or DeepIdle enabled

Hi all,
I'm currently running AOKP milestones 6 with the Devil Kernel, and everytime I activate the DeepIdle option with NSTools or with the Devil Kernel manager app I get Bsods.
It's not specific to AOKP rom because I had the same problem when I was running CyanogenMod 7. I tried to use Glitch Kernel or Semaphore Kernel but it's everytime the same thing : I get one Bsod after a few hours, and after they come every 10min or so. If I pull off the battery or keep pressing the power button the phone reboots normally but until I deactivate the Idle option I have always this same problem.
I tried using smartass V2 governor or modifying the voltages, doing fresh installs but I can't solve this problem. I also used the BT killer script to see if it changes anything but it didn't solve my problem.
Could it be my phone or am I doing something wrong?

I'd say its probably just the DeepIdle. I do remember reading that DeepIdle support is kinda... weird. In my own experience I've had trouble getting it to work. Had SoD's only a couple of times but actual DeepIdle state won't be used much. It has improved a lot from the Cyanogenmod7 days though.
Is the phone very hot on such an event?
I'd say just don't use DeepIdle if you've had such a long history of problems with it.

I put devil Idle option permanent and I didn't have Sods since this morning, maybe you're right and the Deep idle doesn't work. It's quite sad because it seemed awesome on the paper
And about your question the phone doesn't get hot when this happens, it just stop responding but I have no memories that this happened when I was using the phone only when the screen was off. I'm not sure if it's important but it happened when the phone wasn't used for some minutes or if quickly press power button multiple times.
How did you managed to get it working?

Shutting down problem

Hi,
I'm experiencing this problem more than 1 month. I'm on CM10 with kowalski kernel. It seems my phone sometimes wrongly read battery status and drop battery level percentage from some value to 0 immidiatelly...and shut down occurs at the moment. I thought it could be caused by old battery, but it's not - I buy the new one and the problem still persist and it's VERY irritating...Any solution?
Thanks Jiri

Hello,
It happens also for me but only when I am around 15% and when somebody call me sometimes it fail down sometimes.
It seems that the deep sleep do not allow the system to read a correct battery value when screen came back and the system shutdown because of a too low voltage.
I did not found any solutions in several type of ROM.
Mike

This is a known problem..if i remember correctly tonyp and pengus will fix it in the neew 4.2.2
Sent from my LG-P990 using xda premium

But it's annoying as hell, for me, it starts when my batter is on 50% and low.... 5 - 10 times a day a have to turn on my phone...I cannot use alarm at all....

Andy HOT said:
This is a known problem..if i remember correctly tonyp and pengus will fix it in the neew 4.2.2
Sent from my LG-P990 using xda premium
Click to expand...
Click to collapse
Mmmhhhh I actually cant remembet them stating that it will be fixed. I remember tony mentioning that its a low priority rom bug. It might be fixed with 4.2.2 but i am not really sure. Regarding the issue I do experience it too but only once every few weeks.
Sent from my LG-P990 using xda app-developers app

I also have this shut down problem. A lot. Maybe 5 times a day and its also driving me nuts. Mine does not happen while phone is in charger - so its probably the "battery reporting wrong charge" problem. Im on new bootloader. I've seen it go from over 50% to 0% battery in an instant.
It might have happened before but much less frequently than now. I started noticing the problem a few weeks ago on Pengus CM10 rom with kowalski kernel (before reading about it). I reflashed the kernel a few times and upgraded the kernel once or twice during that period.
I switched to PA 2.6 - 10 without improvement (KK-116). No apps installed (except Antutu)
I even had the problem in TonyPs TWRP 2.4.3.0 when trying to backup my rom once. Phone shut down while running the backup. Plugged wall charger in while phone still being off and saw that i still had battery left - probably 30-50%. The LG charging graphics icon showed this (you know, the one that shows up if your phone is off and you plug in the charger).
I Tried the following using AIO v5 tool without luck:
1) Reintalled unlocked ICS bootloader
2) Reverting to Old bootloader / partition - then back to new bootloader. Then installed ROM.
I have also tried installing Django Manouche X 1.6.1 (KOB 0.7 kernel) and running Antutu a few times (right after first boot + reboot) with the same result: shutdown. No apps installed.
I can always reproduce the issue: run Antutu benchmark 1-5 times in a row manually on battery. Plugged in, this does not happen.
It happens with or without OC/UV.
I havent tested it extensively, so I cannot be sure, but it seems to me that the rom/kernel isnt the problem since it also happened (once) in TWRP. Could it be the bootloader? Granted this is only a guess, since i have NO knowledge of Android programming or inner workings. Or maybe this is what happens when the LG battery is dying? I got the phone just as it came out.
Edit: BB 30A

I guess i have the same problem but either worse or something totally different.
Regularly around 70%, my battery just drops to 0% and my phone shuts off. It can happen anytime for me and it usually happens just after about 10-15mn of using my phone.
This morning it shut off at more than 90% and then got stuck in a bootloop i presume because it says it doesn't have battery.

Update:
I tried reflashing 30A BB. Didnt help.
Tried Django Manouche X 1.6.1 with kernel without zRAM or ramhack mod. Didnt help.
I Also tried PA 2.6 - 11 on old bootloader, and the battery-jump shutdowns continued when running antutu.
Flashed (completely stock - no rooting etc) ICS 30A with 30A BB through AIO v5. Didnt help. No tweaks or apps (except Antutu) installed. On Antutu run number 5 the phone restarted (with bootloop). Had about 36% battery. Pulled battery, rebooted, phone shut down before booting ROM. Plugged in charger, booted into ROM, showed 100% battery for 10 seconds before showing 30% battery. Tried with quadrant and 30% battery: phone shut down on run 2. Pulled battery, rebooted. Messed around with camera and gallery for 5mins at 26%: phone shutdown.
Im totally lost ... if its not the battery (as indicated by the first post (OP)) i have no idea whats going on. Maybe some other piece of hardware inside the phone is to blame. A piece of hardware that is only called upon when on battery and not when on charger. Maybe a power regulator (or some such thing) is broken?
Next test: Stock GB with GB BB
Edit: Well, the GB ROM + GB BB didnt work either: Gueste2X GoodBye v2.0R + 20L BB rebooted at 75% battery running Antutu. It showed a pop up about low battery and shut down shortly after. For the first time the battery icon still showed 75% when it shut down though.. And this time it showed 21% (not the usual 0% battery) when rebooting to ROM.
I think Im throwing in the towel regarding the software.
My dad also has an o2x, so i will try and swap the batteries and test both phones. I will ofcourse run antutu several times on my dads phone before swapping the batteries..

Update 2:
So i tried my dads O2X battery in my O2X. I Ran Antutu quite a few times and my phone didnt shut down. So I'm pretty certain my battery is messed up which is the reason my phone shuts off "randomly" showing a sudden 0% battery.
Through a google search i found a guy stating that the battery often starts "bulging" when its messed up like mine. His test was to lay the battery flat on a hard even surface and spin the battery. If it keeps going for a couple of seconds it might be messed up. My battery is definitely "bulging" and spins for much longer than my dads. His spins for less than a second. Mine spins for maybe 2 seconds. Not very scientific, but i could definitely see a difference. And i can see the excessive bulging on my battery if i look at it from the side.
So Im ordering a new battery tonight - the originals dont cost much thankfully.
Hope my walls of text can help others in the same situation.

Last update (promise):
Got the new original battery today. Charged it to 100% and used my phone for various tasks until the battery hit 70%. (This was my old batterys absolutely certain "breaking point" when running Antutu benchmark. On my old battery Antutu would crash on first or second run every time when battery is at 70%.)
On the new battery i quit running Antutu after the 13th run in a row without a "battery low" shutdown. The battery was at 40% after the 13th run.
I lay the old and the new battery flat on my smooth metal mousepad and spun them around. The new battery spun for less than 1 second. The old battery spun for almost 4 seconds on one side - almost 3 seconds on the other side.
Two working batteries (my dads 2+ year old battery and my own brand new one) performing equally and at the same time differently to one defective battery. It lends some credence to "the guys" theory that battery defects might result in "bulging" of the battery.
Which means, your battery can be defective but not "bulge". If however, your battery is "bulging" something likely is or will be defective. Fantastic knowledge to posess, if true.
It might seem like a "well duh, thats obvious" revelation, but Ive held my old battery in my hands a lot the last 2 years (especially lately) and I did not notice the "bulging" at any time.