Database Users

Vibrant turns off in sleep mode

Hey evweryone,
Found a VERY strange issue, that seems to be affecting Captivate users as well. This is my second phone that has had this issue, so its not isolated.
The phone works fine when using it, but when it goes to sleep, occasionally (more and more frequently it seems) it will actually turns off. Meaning, when I pull the phone out of my pocket, its off. Has occurred 3 times today, and I'm SURE i didn't accidentally hold the power key.
First, I thought it was the OC kernel, so I reverted to JAC's non-OC kernel, still turns off. Reverted to stock kernel, still happens. I have a slight hunch maybe SetCPU may be causing it to sleep incorrectly, so I un-installed that.
Anyone else run into this issue? Its a PITA when your phone randomly turns off, cant rely on it at all. Thanks!
EDIT: Phone was ON while sitting on my desk while I was writing this, tried to wake it up....it was off

It happened to me too, and I believe it was because of Set CPU, I had it set low when it went into sleep mode and it would shut down, and i would need to remove battery and start it up again. So I just deleted the profile and it seems fine now.

Puushiki said:
It happened to me too, and I believe it was because of Set CPU, I had it set low when it went into sleep mode and it would shut down, and i would need to remove battery and start it up again. So I just deleted the profile and it seems fine now.
Click to expand...
Click to collapse
I will try that and see. Anyone else have this issue on any Galaxy S based device (Captivate, Vibrant or Generic Galaxy-S)?

Oh btw, I have the Samsung Vibrant

Puushiki said:
Oh btw, I have the Samsung Vibrant
Click to expand...
Click to collapse
Okay, confirmed by one user. There is a large number of captivate users having this same issue, and a discussion about it in a SetCPU forum (Link ).

No problems here, stock ROM + RyanZA using SetCPU since day one.
Two profiles: conversative
Battery <100%: 400 min; 1000 max
screen off: 400min; 400 max

Are you guys using SetCPU for OC'ing, or for scheduling?

I was having the same issue, wasn't sure what it was and was going to return my Vibrant, and with that in mind had wiped the phone and gone back to stock. Due to a delay in getting to the store, I did re-install things (hey, I do need my phone) and found that the issue had stopped. I did have SetCPU on originally and have not re-installed it, but it's difficult to recall if I had SetCPU on before or after the issue started. I suspected it could have been SetCPU and since I didn't really feel the need to use it, I just didn't bother to install and and wanted to see what would happen.
It did happen again yesterday, but the phone seemed to just lock up on me while I was using it (was as I was using Navigate, got to my destination, locked up, then shut off, more or less), so it might have just been another fluke due to overheating or something.
Anyway, the problem that I had was that I couldn't get the phone to come back on without having to remove and replace the battery. But fortunately, other than yesterday, the issue has not happened since the past Friday (where it happened 4 times that morning vs once per day the 3-4 days prior). The inability to turn it back on might just be an issue with my phone (and it only happens after this force shut down).

ytj87 said:
Are you guys using SetCPU for OC'ing, or for scheduling?
Click to expand...
Click to collapse
Mainly for stress testing, as the OC kernel doesnt need to be configured to OC, its already running at 100/1200. Mainly for scheduling and stress testing. Occasionally for detailed info about CPU (temp, current speed, etc). Hopefully this issue\bug can get worked out, cause SetCPU is a GREAT app.

I can almost guaruntee that it is SetCPU causing the issue. Make sure it is set to "Conservative" mode and try not to use the "Screen Off" profile.

hockeyrcks9901 said:
I can almost guaruntee that it is SetCPU causing the issue. Make sure it is set to "Conservative" mode and try not to use the "Screen Off" profile.
Click to expand...
Click to collapse
Had NO issues today, seems SetCPU was the culprit. Thanks!

Well I have SetCPU for Screen Off Conservative at 400, and haven't had a problem yet, so I'm not sure

Puushiki said:
Well I have SetCPU for Screen Off Conservative at 400, and haven't had a problem yet, so I'm not sure
Click to expand...
Click to collapse
I think it's kind of hit or miss. Some people have no issues with it and others do. My first phone would not wake from sleep if I was using the "Screen Off" profile. I haven't tried with my second phone as I've noticed it seems to be really good at lowering **** speed on it's own.

I have had the same problem and am using SetCPU. I love it, but this shutting down in sleep mode thing is driving me crazy. Gonna try to turn off notifications and move to conservative and will report what happens.

I use SetCPU regularly on my Captivate and only see issues if I change the governor or polling interval, or if I use profiles.
Sent from my SAMSUNG-SGH-I897 using XDA App

hockeyrcks9901 said:
I think it's kind of hit or miss. Some people have no issues with it and others do. My first phone would not wake from sleep if I was using the "Screen Off" profile. I haven't tried with my second phone as I've noticed it seems to be really good at lowering **** speed on it's own.
Click to expand...
Click to collapse
**** speed aye?

Don't use setcpu!!!!
Sent from my SGH-T959 using XDA App

xaisomboun said:
**** speed aye?
Click to expand...
Click to collapse
lol. That's swype for ya...
Typos and other gibberish courtesy of Swype

I have this problem several times a week. The phone is NOT rooted. What are my options for curing this problem besides rooting?
Thanks for the help.
Samsung Vibrant, Android 2.1, T-Mobile

I read somewhere that Galaxy S users should NOT use conservative and use on demand instead for this reason... not sure though.

[Q] a500 shutting off when press power button

I have a problem, my a500 is rooted with taboonay 3.2 and the newest thor kernel, except now anytime I press the power button to shut the screen off, it will turn the tablet off completely, does anyone know how to fix this problem? Any help would be appreciated, thanks!

y2kcamaross said:
I have a problem, my a500 is rooted with taboonay 3.2 and the newest thor kernel, except now anytime I press the power button to shut the screen off, it will turn the tablet off completely, does anyone know how to fix this problem? Any help would be appreciated, thanks!
Click to expand...
Click to collapse
The sleep of death
It happens. I would guess maybe you might try to increase your minimum cpu speed to 312. Or just let the display time out by itself instead of doing it manually. See if that helps.
(and I believe it's taboonay 2.2, and not 3.2)
Also with Thors kernels, you should set your governor to "interactive". Although I run mine at "on demand", but you can change the setting around and see if it helps.
Currently, I'm running Harkon with the supplied Kernel, (richardTrip's I believe), and it happens to me as well on occassion. But, if that's the worst that happens, I can live with it.
All cooked kernels have voltage adjustments to increase overclock stability and battery life. And for some tablets, some odd things happen because of it. One of the things we just have to live with.

[Guide][Theory] Samsung Galaxy Note ICS Build SOD Fix!

I have found the fix for SOD's on ICS builds (based on i9220 leak kernel)!!
THIS YOU DO BY YOUR SELF! I TAKE NO PART IF YOU HAVENT READ THIS THRU AT LEAST 2 TIMES BEFORE DOING THESE STEPS!
First of I had a theory of the i9220 kernel and its CWM that in one way it does not represent our hardware right. It has its differences and they are more on a file level then anything. This can be shown easy by trying to format /system. By doing so you will get in to a world of trouble (so don't try it, just trust me)
So my first thing as I have never had a SOD was try to RECREATE a SOD. So my theory is/was that the kernel provided for the i9220 is the real culprit in this scenario and that by flashing RADIOS with its built in CWM is a MISTAKE!
And boy was I right! I installed a random N7000 radio .zip thru CWM (Now when I say CWM I do NOT mean some crappy .apk or app that does it FOR you. I mean the CWM you enter by starting the phone with Power + volume up + home button) and rebooted the phone.
I played around with it and let it rest for 30min. When I was going to wake it up again... SOD!!
Mission Accomplished!! Recreated Error!
So now ... how to fix it...
First off wee need to learn how Mobile Odin works and why this method works to fix it. When Mobile Odin is instructed to flash a ROM or anything else (like a radio) it boots to ITS OWN KERNEL! That is the file that Mobile Odin downloads on first run!
Now IF you are going to use Mobile Odin while on any ICS build (except the original i9220leak! Important! Mobile Odin will NOT work on stock i9220 leak!) you have to be 100% sure that you are PROPERLY ROOTED!
So Steps...
Step1: Get ZCLP1.zip Radio from the Radio Thread and extract the modem.bin file.
Step2: Get Mobile Odin and just flash modem, nothing else. The modem.bin you just extracted.
Step3: It should reboot and enter the Blue Odin Droid Kernel and flash radio.
When its done it will reboot again. And you will probably be SOD Free!
Hit the thanks button if this worked for you guys. Thanks for reading.

Oh btw I don't think that it is locked to use only that modem. I had la3 radio before and I didn't suffer any sods so don't get to blind on just the Chinese radio...
| GalaxyNote ICS | Tapatalk |

im on midnight 2.0 ics.i done what u said in the post.i just had a sod.
here is how it happened.i pressed wifi in pull down notification.it was stuck ..wifi would not turn on after the screen turned off and try to awake by using power button.it was dead.it would not do anything.had to hold power button for couple of min to restart.

Im currently on gb, used ics for a couple of weeks since chinese leak. Im not a 100% sure, but i really think it has something to do with wifi. I never really tested but I always had the most sod at home while connected. Rarely had sod at work, which was cellular data H+.

There is another method and that is to increase min CPU speed from 200 to 500mhz. Has worked for some...
| GalaxyNote ICS | Tapatalk |

Thanks mate, i'm gonna try some of that.
These SOD are making me crazy :/ Some day i can have 0 SOD and the day after 1 per hour...

You can use Wakelock and no more Sod...
Sent from my GT-I9220 using XDA

super_sonic said:
You can use Wakelock and no more Sod...
Sent from my GT-I9220 using XDA
Click to expand...
Click to collapse
But wouldn't that drain the battery faster?
Sent from my GT-N7000

I only get sods when wifi doesn't activate too. If it doesn't switch on immediately then the phone won't come out of sleep. I just restart manually when this happens instead of letting it sleep.
Sent from my GT-N7000 using XDA

I get SOD with or without wifi completely randomly. I'm going to try increase CPU see if that works.

excuse me wt is SOD issue meaning ?
i know its a very stupid Que
but i hoppe to till me wt is it
thnx

It's not specific to the radio. I've done Mobile Odin Pro to try many different radios. Each time, I'd get an SOD.
Folks have also reported getting an SOD WHILE in Airplane mode. This completely puts the baseband issue out of the picture together.
If it's in airplane mode, it can't be a WIFI issue too.
The kernel itself is just bad and it has its quirks.
Due to the inability to get a logcat when it is in a SOD state, it makes it very hard to pinpoint what is causing the SOD.

MaZaGnGy said:
excuse me wt is SOD issue meaning ?
i know its a very stupid Que
but i hoppe to till me wt is it
thnx
Click to expand...
Click to collapse
SOD is Screen Of Death or Screen Of Darkness; meaning that the screen will not wake up up after you turn the phone on and you have to restart/reboot the device. Various things cause it... Have a search and you will learn more about it!

robmeik said:
SOD is Screen Of Death or Screen Of Darkness; meaning that the screen will not wake up up after you turn the phone on and you have to restart/reboot the device. Various things cause it... Have a search and you will learn more about it!
Click to expand...
Click to collapse
Nope, it's Sleep Of Death. The rest is correct
Sent from my GT-N7000 using XDA

We need a SOD-off app

Look for wake lock power manager in play store. It creates a wake lock, preventing deep sleep, and consequently a SOD. For the price of a low battery autonomy.

I was having lots of sod's on aosp v7 and the reason was not related to ROM. it was something to do with the cpu frequency and voltage in the chainfire ics kernel.
Steps I performed to reproduce.
1. Use setcpu or system tuner to set the cpu frequency to 500 mhz when screen off.
2. As soon as the screen is off you can see that note is not responding to keys. Sod reproduced !!!!
In my opinion it has some thing to do with the voltage at frequency 500 mhz, may be the voltage is a little bit less for that frequency and it refused to wake.
Hope it helps some one with the similar sods.

masiullah said:
I was having lots of sod's on aosp v7 and the reason was not related to ROM. it was something to do with the cpu frequency and voltage in the chainfire ics kernel.
Steps I performed to reproduce.
1. Use setcpu or system tuner to set the cpu frequency to 500 mhz when screen off.
2. As soon as the screen is off you can see that note is not responding to keys. Sod reproduced !!!!
In my opinion it has some thing to do with the voltage at frequency 500 mhz, may be the voltage is a little bit less for that frequency and it refused to wake.
Hope it helps some one with the similar sods.
Click to expand...
Click to collapse
We know that ICS leak comes from i9220 and that it's set to work at maximum 1200Mhz.
Now the question is - do i9220 and n7000 use exactly the same CPU ? If so, then we can rule out voltage problems - unless engineers at Samsung f....up.
For all it's worth, that's an early build leak...when official update will be here, i think our problems will be over as we'll just use the proper kernel with our ICS roms.

Akiainavas said:
We know that ICS leak comes from i9220 and that it's set to work at maximum 1200Mhz.
Now the question is - do i9220 and n7000 use exactly the same CPU ? If so, then we can rule out voltage problems - unless engineers at Samsung f....up.
For all it's worth, that's an early build leak...when official update will be here, i think our problems will be over as we'll just use the proper kernel with our ICS roms.
Click to expand...
Click to collapse
Is there any way or app which stops using certain frequencies.

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.

apps that cause sleep of death

is there a list of known apps that cause the sleep of death?
i'm using the 7/30/12 mirage kang. the fresh install doesn't have SOD problems but after i restore my apps, if i let the screen go dark for ten minutes while wifi is running, i'm pretty much guaranteed SOD.

jeff.p said:
... if i let the screen go dark for ten minutes while wifi is running, i'm pretty much guaranteed SOD.
Click to expand...
Click to collapse
That *is* the SOD. It's not caused by an app so much as meeting those conditions. For a quick fix set wifi to turn off when the screen turns off. Search is your friend for more info/fixes.

jeff.p said:
is there a list of known apps that cause the sleep of death?
i'm using the 7/30/12 mirage kang. the fresh install doesn't have SOD problems but after i restore my apps, if i let the screen go dark for ten minutes while wifi is running, i'm pretty much guaranteed SOD.
Click to expand...
Click to collapse
Like MISRy said, it is not a specific app causing it. It is the fact that you leave wifi on with the screen off. And not just specifically screen off, but in deep sleep. But it is not consistent and not everyone gets it. Some of the devs could never make it happen. Usually it is when wifi is on with screen off and an app is using it that is the problem. So if wifi is on and being used, and at the moment you try to turn it on it is in deep sleep, bingo SOD. As I said in the other thread, look at my tips.

leapinlar said:
Like MISRy said, it is not a specific app causing it. It is the fact that you leave wifi on with the screen off. And not just specifically screen off, but in deep sleep. But it is not consistent and not everyone gets it. Some of the devs could never make it happen. Usually it is when wifi is on with screen off and an app is using it that is the problem. So if wifi is on and being used, and at the moment you try to turn it on it is in deep sleep, bingo SOD. As I said in the other thread, look at my tips.
Click to expand...
Click to collapse
i thought the fixed wifi module was included with all recent kernels

jeff.p said:
i thought the fixed wifi module was included with all recent kernels
Click to expand...
Click to collapse
No, the kernel and wifi kernel module are two different things. The wifi kernel module has to be matched to the kernel (it is a kernel module), but is a separate piece of software. It is in /system/lib/modules/twlan_drv.ko. No SOD patches have been used in any stock CM7 kernels or modules. I think Mrg666 uses a patched kernel for his Mirage build and sometimes it is enough, but SOD does not really stop until the patched module is used.
Sent from my Nook Color running ParanoidAndroid and Tapatalk

leapinlar said:
No, the kernel and wifi kernel module are two different things. The wifi kernel module has to be matched to the kernel (it is a kernel module), but is a separate piece of software. It is in /system/lib/modules/twlan_drv.ko. No SOD patches have been used in any stock CM7 kernels or modules. I think Mr666 uses a patched kernel for his Mirage build and sometimes it is enough, but SOD does not really stop until the patched module is used.
Sent from my Nook Color running ParanoidAndroid and Tapatalk
Click to expand...
Click to collapse
ok. thanks for the info. i'll try the module at http://d01.megashares.com/?d01=8VPCE7N and report back

jeff.p said:
ok. thanks for the info. i'll try the module at http://d01.megashares.com/?d01=8VPCE7N and report back
Click to expand...
Click to collapse
no SOD yet. awesome!

Can u set wifi to go off in settings somewhere or do u need an app like green power? I only ask because that was what I did but after awhile, it won't let the wifi come on at all until I remove the app and reboot
Sent from my NookColor using xda premium

purpleurkle said:
Can u set wifi to go off in settings somewhere or do u need an app like green power? I only ask because that was what I did but after awhile, it won't let the wifi come on at all until I remove the app and reboot
Sent from my NookColor using xda premium
Click to expand...
Click to collapse
Yes there is a setting. Go to wifi networks and select menu and advanced. There should be a wifi sleep policy setting.

I think there is no specific app which causes SOD
Dear all my friends who facing the SOD Sleep of Death issue with their Android devices...
i found that it is totally related to Wifi Sleep policy related... i just changed the setting last night n now after 8 hours it is running absolutely without SOD... i will also be inform u later if i will get my device out of SOD issue... all of u just have to do one thing.
Go to settings>wifi settings>
from the options go to advanced settings
there is one option: Keep wi-fi on during sleep (go to this option)
there is 3 options: 1. Always, 2. Only when plugged in, 3. Never (increases data usage)
u just have to change ur option from 1 to 2 or 3, then i hope u will find that u will get ur device out of SOD issue...
Regards,
Nauman
(sorry for the poor english)

nauman_waheed said:
Dear all my friends who facing the SOD Sleep of Death issue with their Android devices...
i found that it is totally related to Wifi Sleep policy related... i just changed the setting last night n now after 8 hours it is running absolutely without SOD... i will also be inform u later if i will get my device out of SOD issue... all of u just have to do one thing.
Go to settings>wifi settings>
from the options go to advanced settings
there is one option: Keep wi-fi on during sleep (go to this option)
there is 3 options: 1. Always, 2. Only when plugged in, 3. Never (increases data usage)
u just have to change ur option from 1 to 2 or 3, then i hope u will find that u will get ur device out of SOD issue...
Regards,
Nauman
(sorry for the poor english)
Click to expand...
Click to collapse
it's not working on my s6 sprint

Sprint network having any problems here
Sent from my QMobile i12 using Tapatalk