Related
hi guys
For those that haven't heard of or seen an Sleep of Death (SoD) in action , it is where your phone does not respond to any user input whilst it's in sleep mode thus making the phone unusable since you are unable to wake the phone. The only way to recover is to either force reboot the phone, receive a call or call yourself from another phone.
I have encountered SoD four times til now, on KE2, KE7 and Now KF2 .
I don't think its got anything to do with the ROM, this has happened for me on Cognition, VillainRom , CF-root on stock Roms.
looking around the web it seems it might be a kernel/driver issue and remains unfixed (not sure)?
Anyone knows workarounds? Any Devs that are working on this?
Thanks
I haven't encountered this yet and I've also tried a bunch of different ROMs. Are you by chance overclocking or underclovking/UVing at all? If so, that could be the culprit. If not, then its hardto say what may be causing it other than an app the phone may not respond well with.
I had this happen once. I tried many ways to wake it up even charging, the charging sound comes up but the screen wont wake. Had to reboot.
Havent happened again though.
I haven't under/over clocked the CPU at all but from what I understand it has nothing to do with CPU frequency but more so a bug in kernel or in one of the drivers.
Its not easy to reproduce but its definitely there, I'm hoping it'll be addressed in cyanogen rom when its out given the fixed SoD somewhere in 7.0rc I think.
Sent from my GT-I9100 using XDA Premium App
ke3pup said:
I haven't under/over clocked the CPU at all but from what I understand it has nothing to do with CPU frequency but more so a bug in kernel or in one of the drivers.
Its not easy to reproduce but its definitely there, I'm hoping it'll be addressed in cyanogen rom when its out given the fixed SoD somewhere in 7.0rc I think.
Sent from my GT-I9100 using XDA Premium App
Click to expand...
Click to collapse
On my ace this issue occured when the wifi was on. The phone goes into "sleep mode" and needs a reboot (press the power key for 10 seconds).
I was not able to find the exact conditions but it was more promient when 3g was also switched on.
Does your issue occur only when the wifi is on?
This has happened 4-5 to me
as well. I have found that a putting the phone on charge can free it. But its a real pain if it happens out and about, I had to take the battery out to get it to work
i got it 2-3 times while using "Green Power" app.
Again this has nothing to do with an app/rom..etc. you may think a certain app you installed its causing it but in case of SoD that's highly unlikely. The source of problem is else where.
"@cyanogen: @Bradart @1000hams try a nightly build if you are on 7.0. Google fixed bugs for 2.3.4 that can cause that (7.0 is 2.3.3)."
Click to expand...
Click to collapse
The above is a quote in response to SoD question (don't know which device, but android < 2.3.4) which to me suggests another bug in 2.3.3 that has been fixed in 2.3.4.
http://forum.xda-developers.com/showthread.php?t=1238478
Here's the solution I hope it helps... it worked for me
Bug Report - SGS2 (Sleep of Death)
Please use this link to report the bug:
code.google.com/p/android/issues/detail?id=21607&thanks=21607&ts=1320690472
I think I found a way to avoid SoD (Sleep of Death)
I'm new on the forum And that SoD problem annoyed me for so long and I kept searching.... But I think I finally found why we kept getting SoD.
Ok so I'M NOT SURE, but Try following those steps and be sure of every single thing and then tell me if you guys keep getting SoDs..
1- "Do not use two governors as screen-on & screen-off govs, if they both have an upper frequency limit for screen-off state." - droidphile
2- I think some of us don't do "clean flash of our ROM", so you guys need to follow those exact steps from that link
http://forum.xda-developers.com/showpost.php?p=28395322&postcount=3
Or I will just write them again...
1- Reboot into recovery (Turn off your phone then press and hold the keys: Volume Up + Power + Home)
2- Wipe Data / Factory Reset
3- Install the Main ROM file
4- In AROMA installer select "Custom Installation"
5- Choose depending of your taste
6- When AROMA installer finish untick the "Reboot Now" option
7- When you're back on the recovery go to Advanced
8- Wipe Dalvik Cache
9- Fix Permissions
10- Wipe Cache Partition
11- Reboot
12- When you get the step for add your Google Account, if you don't have a WiFi enabled or you can' add it, skip it
13- When you boot into the system, it's probably that you don't have data enabled (3g, H+) just reboot the phone
14- When you boot again into the system, the data will be enabled and you can do the configuration of Google Account (if you don't do this step before)
This is the moment for install all the extras like themes, mods, fixes, kernels, etc.
3- ok and NOW After your "CLEAN Flash of ROM" When you use Titanium backup Root application to restore your applications, DONT restore the things with RED text color. Restore ONLY the things with green text color.
In other words, restore only apps with their data and NOT all system data.
4- Ok and Once you did that. About the Governor you use, I think we push the limits of the CPU and the phone just can't resist the tweaks we did and a SoD appears. So try these settings if you have Siyah Kernel
Minimum CPU frequency: 200 Mhz
Maximum Frequency: 1000 Mhz
Governor: luzactive
Default I/O sheduler: SIO
So try THAT and tell me if you guys keep getting SoD ...
lol I didn't get SoD since 2 days And I hope it could help. Because installing Wake My Android Pro, or WakeLock or Load Monitor just DIDN'T work for me -__-
i stumble upon this problem whenever i use too harsh UV settings(depends from kernel to kernel). also my device SoDs whenever i use 100mhz as the lowest step- again with some kernels it tolerates it. my guess is: every phone is slighty different, so you just have to experiment with yours and find the best settings for your specific hardware (you dont say xD)
screenager said:
i stumble upon this problem whenever i use too harsh UV settings(depends from kernel to kernel). also my device SoDs whenever i use 100mhz as the lowest step- again with some kernels it tolerates it. my guess is: every phone is slighty different, so you just have to experiment with yours and find the best settings for your specific hardware (you dont say xD)
Click to expand...
Click to collapse
I understand your point of view, but by the way, I read a lot of that forum, and putting minimum frequency at 100Mhz might be Bad for your phone for 4 reasons:
1) When you receive a call, the call might lag because it needs absolutely a minimum of 200Mhz, so setting your CPU minimum frequency at 100Mhz might cause probs for phone calls.. ( i read that somewhere on XDA but dont remember where...)
2) Moreover, "It seems 100 mhz uses more power than 200 mhz. According to tests, 100 mhz accounted to 1 W / GHz and 200 mhz to 0.7 W / GHz, when both the cores were online."
3) "200 mhz can finish same task faster compared 100 mhz and thus hit deep idle soon."
4) "200 mhz is the 'sweet spot' of frequency in SGS II. ie, the frequency used in the calculations based on the optimal energy to run (Ex: In Milestone it's 550 MHz). So , 'energetically efficient' frequency for our CPU is 200 mhz."
Those 3 last reasons came from droidphile I'm not the author of this, but minimum frequency should stay at 200Mhz
i want reactivate this thread, because I think there are some users who still have this problem like me.
As far as I recognized there seems to be more reasons for SoD.
All seems to have begun with Android 4.1.2 and just keeps on until now.
I have tried some kernels and runs now Dori 9.33 and see how it works.
It seems that there are some kernel issues as well as some apps and some constellations of SD-cards.
But no one has a real solution.
I read about a "indish kernel" for the i9100g models, but also some who reported SoDs with this kernel.
But I found no real solution for our i9100.
I have attached a logfile (catched with Catlog) which I recorded until my last SoD.
In my case, I can also call my phone and the caller hears it ringing, but my phone stays black without sound and unresponible.
The only thing is to hold the power button for 10 seconds and reboot it.
just to tell:
nearly 24h without a SoD with my combination
BUT: I have not used my camera so far! And I think camera & media scanning has something to do with it.
If everything is running until tonight, I will try my camera and see the result.
after nearly 2 days
:good: nearly 48h working, so I will keep my combination.
But it is interesting, that nobody has any problems although you can read a lot about this problem.
after more than 2 days:
and here we go. SoD :crying: but 48h is better than nothing
a lot of things might come from corrupt files.
There are 2 scripts which will clean your partitions and try to fix broken files
1. GS2ROMclean made by hawkerpaul
2. Fix_Partitions_v1.0.2.zip made by Computoncio
you can run out of CWM and install as a zip.
So far it is recommended to run 1. GS2ROMClean, reboot, then 2. Fix Partitions to ensure you have clean partitions
Be patient! 2. runs very long, up to 2 hours and the phone becomes very hot. So I think power connection is absolutely recommended
BUT NOT TESTED COMPLETELY BY ME
what I do not know is, how often these scripts shall be used
You could run the ROM clean as often as you want. If the other doesn't fix it after one time, no point running it again. In saying that, I'm not sure if there would be any benefit from running the first one more than once anyway.
Sent from a galaxy far, far away
lavemetoo said:
a lot of things might come from corrupt files.
There are 2 scripts which will clean your partitions and try to fix broken files
1. GS2ROMclean made by hawkerpaul
2. Fix_Partitions_v1.0.2.zip made by Computoncio
Click to expand...
Click to collapse
1. runs very fast, took round about 10 seconds. Reboot was successful afterwards. All was working.
Now I run 2. - info will follow - would be great, if there were a kind of progress bar or a kind of information. So you don not know if it hangs or not.
script 2. ended after 1h with a warning. Now run again?
Code:
/dev/block/mmcblk0p10: ***** FILE SYSTEM WAS MODIFIED *****
/dev/block/mmcblk0p10: ********** WARNING: Filesystem still has errors **********
/dev/block/mmcblk0p10: 11854/131072 files (5.4% non-contiguous), 524288/524288 blocks
Checking preload partition:
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
/lost+found not found. Create? yes
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/mmcblk0p12: ***** FILE SYSTEM WAS MODIFIED *****
/dev/block/mmcblk0p12: 544/32768 files (0.0% non-contiguous), 29992/131072 blocks
Automatic Fix Partitions finished at 30-07-2013 14:10:33
attached is the complete logfile
ATTENTION: My phone was connected to USB and lost 10% battery during this script operation!
I would like some help from users having same issues. I bought my SGS II About 3 weeks ago... It was all working fine... stock KG7 not rooted. A few days ago it started doing some weird stuff... like random reboots during standby and freezing unable to turn on unless you take out the battery... tried to restore factory setting i installed the new LightningRom 6.1 and the issue is still there... is there a logging app that can save log before a crash? so i can see what is happening? Or is someone having the same issue as i am. Thank you very much for your time and help Cheers
PS. tried to format usb storage and still have same problem... so really don't know what is the problem...
I have finally found a solution... installed XXKH3 FW stock, not rooted yet, and installed an application from the android market called Load Monitor
Code:
https://market.android.com/details?id=com.landak.loadmon
and enabled only Add Notifications, only notify high load, autostart and only screen on... seems to do the job, no battery drainage and most of all NO SOD (Sleep Of Death) or restarts anymore
Hope it helps someone
Cheers
Bump
Bump... Added VillianRom newest version still have the freeze on standby problem.. Apparently when no apps are running it just crashes and i can't turn it on only by going to CWM or odin... and reseting... Any help would be really appreciated
Do you have a software installed called SetCPU?
No... only facebook, google+, Game Dev Story and Dragon Fly...
Faulty Hardware
Mine did the same; replacement phone is perfect.
Sadly it's not an option for me... i bought it used without warranty papers... it was cheaper... i may have stumbled on a solution... cleared Dalwin Cache and it seems to work good now... we will see in a few days how the situation progresses... i will keep you posted
Installed stock XWKF3 AND IT SEEMS to have fixed the prob. Left it overnight unplugged with wifi off and i had a 1% drain of battery for over 8 hours :-D very sattisfied. Installed standard apps now so.i`ll see how it goes. Keep you posted.
Sent from my GT-I9100 using XDA App
Still having the problem... installed lots of apps and some of them are missbehaving... my phone seems to freeze up and after a while get really hot and the battery is sufficiently drained... is there a program that can log what happened durring the freeze up? and save it to view after restart????
I could really use your help guys pls...
I have finally found a solution... installed XXKH3 FW stock, not rooted yet, and installed an application from the android market called Load Monitor
Code:
https://market.android.com/details?id=com.landak.loadmon
and enabled only Add Notifications, only notify high load, autostart and only screen on... seems to do the job, no battery drainage and most of all NO SOD (Sleep Of Death) or restarts anymore
Hope it helps someone
Cheers
Had to turn on Wake Lock. That means my phone doesn't go to deep sleep anytime. Tried a bunch of roms and all the same result. Tried setcpu configs of all kinds and nothing still. Still get freeze up and insane battery drain durring deep sleep. What helps is flashing syah kernel an putting min cpu freq to 100 that way not that much battery drain.
Any1 have an idea what to do?
Sent from my GT-I9100 using XDA App
I have the same problem i tryed everything. now im waiting for the jig from honk kong
dusnoki said:
I would like some help from users having same issues. I bought my SGS II About 3 weeks ago... It was all working fine... stock KG7 not rooted. A few days ago it started doing some weird stuff... like random reboots during standby and freezing unable to turn on unless you take out the battery... tried to restore factory setting i installed the new LightningRom 6.1 and the issue is still there... is there a logging app that can save log before a crash? so i can see what is happening? Or is someone having the same issue as i am. Thank you very much for your time and help Cheers
PS. tried to format usb storage and still have same problem... so really don't know what is the problem...
I have finally found a solution... installed XXKH3 FW stock, not rooted yet, and installed an application from the android market called Load Monitor
Code:
https://market.android.com/details?id=com.landak.loadmon
and enabled only Add Notifications, only notify high load, autostart and only screen on... seems to do the job, no battery drainage and most of all NO SOD (Sleep Of Death) or restarts anymore
Hope it helps someone
Cheers
Click to expand...
Click to collapse
i also have the same problem on my gt-9100T and still it is still happening. first time it happened when i uninstalled social hubs. at that time i was running lite'ning rom v6.1 and only used the phone for 1 month. then the freeze/ sleep of death occur.
i have tried flashing to stock rom/modem/kernel from intratech thread to no avail.
some people can fix the prob by cleaning the battery contact point. some by cleaning the mini usb port. still no luck for me.
right now running on criskelo latest build (KL1 2.3.6)with T-KL1 modem, siyah .9+ and the problem still persist.
so, installed load monitor and u/v and set the min freq to 100Mhz to preserve battery but still can only last 12hours even unused.load monitor seems to use a lot of juice. very frustrating. i need to tick the wakelock option otherwise SOD right after the screen is off.
I am still hoping someone/anyone who might have the solution the share with us all.
is it a good idea to format /system + /emmc + everything? i have done full wipe, still no good.
wafufufu said:
i also have the same problem on my gt-9100T and still it is still happening. first time it happened when i uninstalled social hubs. at that time i was running lite'ning rom v6.1 and only used the phone for 1 month. then the freeze/ sleep of death occur.
i have tried flashing to stock rom/modem/kernel from intratech thread to no avail.
some people can fix the prob by cleaning the battery contact point. some by cleaning the mini usb port. still no luck for me.
right now running on criskelo latest build (KL1 2.3.6)with T-KL1 modem, siyah .9+ and the problem still persist.
so, installed load monitor and u/v and set the min freq to 100Mhz to preserve battery but still can only last 12hours even unused.load monitor seems to use a lot of juice. very frustrating. i need to tick the wakelock option otherwise SOD right after the screen is off.
I am still hoping someone/anyone who might have the solution the share with us all.
is it a good idea to format /system + /emmc + everything? i have done full wipe, still no good.
Click to expand...
Click to collapse
I'm having the exact same issue. Some stock ROMs seem ok for a while but the issue always returns.
I've tried literally everything I can think of. Done so many full wipes etc but the issue will not go away.
I feel your pain people!
I have the same problem as you im using what you are thank you for that app.
what ive done
SIM card = Removed
Mirco SD card = Removed
so far no problem
thank you..
im trying to get the last thing it did before the phone crashs
I just installed Load Monitor... I just wonder, what exactly is Load Monitor doing? or supposed to do?
This SOD is driving me crazy, I hope it gets fixed
dusnoki said:
Sadly it's not an option for me... i bought it used without warranty papers... it was cheaper... i may have stumbled on a solution... cleared Dalwin Cache and it seems to work good now... we will see in a few days how the situation progresses... i will keep you posted
Click to expand...
Click to collapse
Do you mean Delvik Cache?
Thanks, i'll give it a try :good:
As the title suggests.
Having a very strange issue at the moment where my phone will randomly switch off when it's in deep sleep, then when I've restarted I'll find some of the more recently installed apps have been deleted/uninstalled.
What on earth could be causing this?
Using siyah kernel 2.6.11 and wanamlite rom V7.8 (2.3.6)
Sounds like a to low under volt,(you may not have undervolted)... try neak kernel, its the best by far..
I think that will sort your problem out.
If not then wipe and reflash your rom.
Sent from my GT-I9100 using XDA App
haven't undervolted at all, and it's set at 200-1200 MHz..
I'm not 100% sure if I had the issue with void echo (kernel I was using before), or an older siyah build but it's definitely possible.
What could explain the uninstalled apps though? it's really bizarre...
I'm going to go ahead and bump this as its happening yet again, but slightly differently as well.
I downloaded a game around 3 days ago and have rebooted once since then (yesterday) and just found that I could not launch the game (got a FC pop-up), but it was actually still installed. I then transferred the game installation to my SD card, and it launched. I then rebooted as I switched back to a different kernel via recovery mode, and now the game is uninstalled (along with at least two other apps I've noticed so far).
What is happening??? Surely someone has an idea.
Hello guys,
To get right to it, everything was fine when I was on MIUI 2.5.18 but when I updated to 2.6.1 the issue started happening. I will try to explain the issue to the best of my ability.
About 4-5 times a day my phone will just out of no where become ungodly slow as in it takes the phone ~45 seconds to recognize a touch on the screen or push of a button. So when this starts I have to reboot, and normally I have to Hard Reboot (hold power till GT-i9100 screen appears). I was running Neak at the time so I switched to Siyah and it as still an issue, I also updated to 2.6.8 but that did not help either. Last night, I changed to AOKP thinking it may be a ROM issue and even on the stock Kernel I still have the issue...
At this point I believe it may be a phone issue. Has anyone had something like this happen? How did you fix it if so? Should I attempt a flash back to Stock and run that for a while and see how it goes?
I will try and get a video today if my room mate comes home.
Thanks in advance!
tory13579 said:
Hello guys,
To get right to it, everything was fine when I was on MIUI 2.5.18 but when I updated to 2.6.1 the issue started happening. I will try to explain the issue to the best of my ability.
About 4-5 times a day my phone will just out of no where become ungodly slow as in it takes the phone ~45 seconds to recognize a touch on the screen or push of a button. So when this starts I have to reboot, and normally I have to Hard Reboot (hold power till GT-i9100 screen appears). I was running Neak at the time so I switched to Siyah and it as still an issue, I also updated to 2.6.8 but that did not help either. Last night, I changed to AOKP thinking it may be a ROM issue and even on the stock Kernel I still have the issue...
At this point I believe it may be a phone issue. Has anyone had something like this happen? How did you fix it if so? Should I attempt a flash back to Stock and run that for a while and see how it goes?
I will try and get a video today if my room mate comes home.
Thanks in advance!
Click to expand...
Click to collapse
I had the random slowdown issues with NEAK - but never had that on CM9 or Siyah kernels and not on ktoonsez's MIUI kernel as well.
Basic stuff - did you do a complete wipe - cache, dalvik cache, format /system and ran Jivy's kernel cleaning script just to be sure?
Does it happen during a certain activity e.g. opening a certain app or anything else? Do you have any memory management apps installed?
May need to try the cleaner script but yes complete wipe with both cache's and system when I went to AOKP
and no its totally random just when ever it feels like it. As far as memory management I went through the agonizing long steps when it was slow and only about 500mb of memory was being used and only on occasion does it go over 600mb
What are some good memory management programs?
There are so many variables I would say flash back to.stock completely, (wipe first obviously) then see if problem persists. If it does then u know its a hardware issue.
Sent from my SAMSUNG-SGH-I777 using Tapatalk 2
i had a similiar problem on my captivate after installing a eurokrank rom. i found that if u have the govenor set to powersaver it made my phone really slow/ laggy. once i changed it to ondemand or performance it picked right back up. maybe tinker with that and see if it maybe clears it up a bit
Cleaner script seemed to work! Never thought I would ever have to use it but oh well.
It has not happened all weekend, so we will see how it goes the rest of the week!
Thanks again guys!!!
Firstly an introduction to my problem - I've been having problems with high cpu usage whenever I enable my wifi. I've gone to stock [I9100DXLSD_I9100OLBLSD_XME.zip], tried different kernels [Apolo, siyah, speedmod, dorimanx], tried different roms [slimkat, neatmod, jellysnap], done factory resets for each, flashed quite a few modems [dx's,xx's, currently trying radio-cm-9-SGS2-LP6-signed.zip, there's a whole bunch that I'm still going through as well - can't post urls yet]. I had no luck with all of these methods so far.
Since that approach didn't work I have also been looking at wakelock detector,gsam and betterbatterystats to find out what was chewing up cpu and causing battery drain. I initially thought it was something caused by google play services (SystemUpdateService), wlan_rx_wake, or a pc/router on network with a configuration conflict or something like ipv6 causing bizarre behaviour but so far I have been able to get rid of wlan_rx_wake problems but those were minor on the battery drain problems I was having. Using a static ip also did not improve anything. Wakelock detector/gsam/betterbatterystats were now all showing either android os or android kernel as the culprit but would not show exactly what process was causing it. Once I enabled 'show cpu usage' in developer options I was able to see that dhd_dpc process was causing all this havoc. There does not seem to be much information on the net about this process and problem. When I switch wifi on, I'll be able to use the net fine for a few seconds to a minute before dhd_dpc decides to kick in and using a high amount of cpu causing insane drains and I have to quickly switch wifi off before it locks up requiring a reboot.
What I have found out through all of this by accident is that if I enable wifi and then quickly copy a file from my phone to a pc on the network, I am able to use internet on my phone without any lockups and the speed (cpu) is fine and fluid as usual but only while the file is still copying over the network. During this time dhd_dpc seems to consume cpu like it normally should as I've seen on the other devices I have. Why is this? This has to be a software issue since it works flawless when I do this? Not sure why it would require some sort of lan traffic in order to get wan traffic working without sending the cpu usage to orbit. The battery of course drains but not as bad since it's busy copying files over. Maybe possible that it doesn't like the routers on my network that might be sending arps and copying files over the network makes it ignore that traffic (just shooting in the dark here)?
I hope someone can shed light on this and perhaps give me some other things I can try. Btw, cell radio/mobile data are all fine, except for one or two of the modems that I tried. So is this kernel, rom or modem related? Please help! This is the only thing not working properly on this phone. Thanks for all those that took the time to read and answer.
Currently on my phone:
Rom: I9100XWMS3_NeatROM_v6.4
Kernel: Apolo-4.15b_Regular
Modem: LP6 (this is just what I am currently testing out of the dozens of modems I have)
PS- yes I use kernel wipe and rom wipe scripts. Maybe the problem is somewhere in dhd.ko?
Anyone mind uploading their dhd.ko that doesn't have this dreaded dhd_dpc cpu pegging purge business just so I can rule it out?