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] SC 2.2 NV => 2.4 V & same problem

If I lock my phone, sometimes it won't unlock. It essentially just shuts down. I've reinstalled 2.2 once, and just went to 2.4 last night. When this happens, I have to pull the batter and restart. And yes, it does this with both versions. I wiped cache, etc upon installing the ROM as well.

jbjarko said:
If I lock my phone, sometimes it won't unlock. It essentially just shuts down. I've reinstalled 2.2 once, and just went to 2.4 last night. When this happens, I have to pull the batter and restart. And yes, it does this with both versions. I wiped cache, etc upon installing the ROM as well.
Click to expand...
Click to collapse
When you say it won't unlock...is haptic feed buggy and it seems unresponsive and sporadic?

jenisiz said:
When you say it won't unlock...is haptic feed buggy and it seems unresponsive and sporadic?
Click to expand...
Click to collapse
Not really, seems normal to me. Should I try turning it off, and see if that fixes it?

By any chance, would you happen to be using setcpu? I ask because I have noticed this happening on any rom I use, but changing my setcpu values for when the screen is off has pretty much solved it.
Sent from my SCH-I500 using XDA App

kdaz said:
By any chance, would you happen to be using setcpu? I ask because I have noticed this happening on any rom I use, but changing my setcpu values for when the screen is off has pretty much solved it.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I've been using setcpu with every setup on this device and haven't ran into any problems. Only problem I would see with this, is if you set the levels way to low...that will induce locking up the system.

Ok, downloaded setcpu, what specs should I put it at?

jenisiz said:
I've been using setcpu with every setup on this device and haven't ran into any problems. Only problem I would see with this, is if you set the levels way to low...that will induce locking up the system.
Click to expand...
Click to collapse
well thats basically why i was asking..if i set mine to 200 max and 100 min when screen is off, it sometimes doesnt come back on. i currently have it set to 400 max and 100 min when screen is off and havent noticed any problems.

kdaz said:
well thats basically why i was asking..if i set mine to 200 max and 100 min when screen is off, it sometimes doesnt come back on. i currently have it set to 400 max and 100 min when screen is off and havent noticed any problems.
Click to expand...
Click to collapse
IMHO...that's really low.

Where do I set it for screen off? All I have are two sliders?

jbjarko said:
Where do I set it for screen off? All I have are two sliders?
Click to expand...
Click to collapse
you have to go under the profiles tab and enable then you can set different profiles.

Still doing the same deal. SetCPU is at 400-800 during screen off. Haptic feedback is off.
Any ideas?

I'm not even running SetCPU and I get this happening.

Anyone have any more suggestions? It's not a huge deal, but it sucks watching my battery drop 10% every time I have to pull the battery and reboot.

[Q] G2 screen sometimes won't turn on

I have a T-Mobile G2 that's been rooted and flashed several times (cm6, virtuous, supervillainz, senseginger, cm7) and through I think all of them I noticed an issue with coming out of sleep where the screen doesn't turn on
it still reacts to touch (ie I can slide to unlock), and the bototm touch keys light up, but there's no backlight or picture on the actual screen
sometimes it takes several off-on cycles to get it to work... I've recently noticed (and may be just imagining it) that the trackpad wakes it up with a much better success rate
details:
HTC Vision (G2)
Android 2.3.3
Baseband 12.28b.60.140eU_26.03.02.26_M
Kernel 2.6.32.28-cyanogenmod-g58d929e [email protected] #1
CyanogenMod-7.0.0-RC2-vision
any ideas would be welcome before I lose it and start poking at the kernel, radio and whatnot
thanks,
L

happens to me in virtuous, never happened to me on CM (i havent tried cm7 yet)
i believe its a problem with the cpu scaling, ie when the screen is off, processor drops to 245mhz and when the screen turns on, speed doesnt scale up fast enough
i usually underclock my g2 to 599mhz (governer set to on demand) but if i go any lower than that, getting the screen to come on becomes a frustrating project lol

I have the same problem, its so annoying especially when someone calls. Its been mentioned in other threads and I'm sure its a known problem but like u I need a fix. Stock ain't so bad as long as u can see who's calling and what time it is without trying to wake the phone 20 times. Please will someone finally answer this question? Or do we all need to revert to cm 6.1 or stock????? Small problem but big outcry.
Sent from my HTC Vision using XDA Premium App

thanks, I downclock to 200mhz on screen off
I'll up it and see if it makes a difference

Are you using the screen off animations in CM7?
Sent from my HTC Glacier using XDA App

screen off yes, screen on no

Try disabling the animations all together and see if it helps. Also are you OC'd above around 1.2ghz?
Sent from my HTC Glacier using XDA App

I've disabled them for now, gonna see if it helps...
yeah OC to 1516MHz, do you think this affects it?

There was a known issue with CM7 not too long ago where if you had the screen off/on animations activated in conjunction with being OC'd at around 1.2 or above it would cause the sleep wake issues. Took 3 or 4 on/off cycles with the sleep button on order to get the screen to come back on.
The solution was either to disable the screen animations or not to OC very high.
The other remedy recommended earlier is also legit. Set your screen off CPU profile to around 300 or 400mhz. Your problem should be solved by tinkering with all 3 variables. Failing that I would recommend a wipe/reflash and/or hitting up some folks in the CM7 thread to see if anyone else has that issue after tinkering with the above solutions.
Good luck man, I know those little bugs can be frustrating.
Sent from my HTC Glacier using XDA App

thanks for the tips...
I've now upped the minimum clock to 400 across all profiles and turned off the screen off animation... if that doesn't do it, I'll turn down the maximum clock, and if that still fails disable setcpu completely
I will report back any findings

allixsenos said:
thanks for the tips...
I've now upped the minimum clock to 400 across all profiles and turned off the screen off animation... if that doesn't do it, I'll turn down the maximum clock, and if that still fails disable setcpu completely
I will report back any findings
Click to expand...
Click to collapse
I see you have a strange problem.
I use 275mhz when sccreen is off and about 476 mhz when screen is on and nothing like this has happened to me.
Sent from Mars

Seems like nature of the beast. I get it too. Are yall using setcpu? I think its an issue with it. U might try cputuner and see what happens. But it rarely happens now that i set my setcpu to conservative or smartass.
Sent from my HTC Vision using XDA Premium App

this is indeed an issue with downclocking the phone on screen off profile... as soon as I set the screen off profile to anything below the stock 806 mhz, the issue appears
I've reenabled both screen off and on animations, the issue still hasn't reappeared... so it's the downclock :/

I have seen it on Sense ROMs but not CM7, doesn't clocking your phone at 800 when display off eat up a lot of battery also?

I am, unfortunately, not that techno-savvy when it comes to cellphones. But I am having the same problem.
The most I get is a bit of back light, but everything else about the phone seems to be working. Is there anyone who could possibly help me figure out how the hell to fix this?

[Q] Anyone else having locking/freezing issues with CM 7.1 RC1?

I updated to CM 7.1 RC1 last week and I've noticed a few times where the device has locked up after "going to sleep". Essentially, if I leave it on the coffee table with WiFi on and let the screen turn itself off, it won't respond when I return to it 20-30 minutes later. I have to force reboot via the power button + nook button.
Just curious if anyone else has noticed it or if it's just me. If it's a common issue I'll escalate to the CM folks, if it looks like just me I'll start the long and tedious process of uninstalling apps one by one. =)

I have at least one every day. I figure its just a price I pay. Over all its the best rom I have used.
Sent from my NookColor using XDA Premium App

Only once have I had the issue you described. I leave WiFi on some of the times, but majority of the time I have it off when I am done using it. I know some people have mentioned using Tasker or something similar to turn WiFi off when screen goes off so that it can perhaps be prevented.
EDIT: I don't believe I can link yet on my account, but search General for the post "NC, CM7, Dalingrin OC kernel.. Sleep of Death" and start about post #6.

Thanks bio, that looks like the exact issue I'm experiencing.
For the next guy with this issue: Link to the thread biohazard mentioned

Installing Droid wall has fixed the problem for me and has doubled my battery life
Sent from my NookColor using XDA Premium App

mrkavanagh said:
Installing Droid wall has fixed the problem for me and has doubled my battery life
Click to expand...
Click to collapse
That's a pretty generic statement... what did you blacklist within Droid wall to increase battery life / fix the issue?

I'm facing random freezes when I open an application like tweetdeck or mercury and leave it updating from the internet. After some time, I'm not using it, it just stucks. To get it back to life I have to press for a few seconds the power button to shutdown it and then again to power it on. I have used different nightlies, voltages or governors but it is still here.
Now, I don't have freezes since yesterday that I really reduced the voltages but I'm not sure if my problem is solved.
configuration: 144 nightly 300-1100mhz xlv profile

not sure if anyone has told you that what you describes is called:
Sleep of death.
Felt to be possibly related to wifi being on all the time. In wifi settings, go to advanced change it wifi to off when screen off.

skylar.sutton said:
That's a pretty generic statement... what did you blacklist within Droid wall to increase battery life / fix the issue?
Click to expand...
Click to collapse
I'm sorry. I use the white list feature and only check mark the current application that I want to use and allow to access the internet. It keeps everything else from using background data.
For example right now I selected xda and updated rules.
Sent from my NookColor using XDA Premium App

Phatdawg said:
not sure if anyone has told you that what you describes is called:
Sleep of death.
Felt to be possibly related to wifi being on all the time. In wifi settings, go to advanced change it wifi to off when screen off.
Click to expand...
Click to collapse
It seems that I solved it reducing the voltages. When sod occurs a black screen appears right? I never had sod, only random freezes.
Sent from my Nook Color

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.