Screen goes black wont turn on power button and volume rocker unresponsive. Have to pull battery everytime. Disabled the lockscreen. Any suggestions
Turn on screen animation, turn min CPU up from 128 or whatever. If it keeps up you might have to reflash
Sent from my PC36100 using xda premium
Has anyone consistently had this problem, and then had it permanently fixed by raising the minimum CPU speed or re-flashing their phone? My friend and I both have Nexus S, both on CM7, and both have this issue of perma-black screen with non-responsive volume rocker/power button. The 4 capacitive buttons at the bottom (turned on due to a notification?) respond to touching and blink (turn) off when pressed and re-light when released. Screen animations are on, lockscreen is enabled. This has only started happening after rooting and flashing the CM7 mod, and not on an unrooted stock rom.
Should I be increasing the minimum CPU speed, or increasing the maximum CPU speed? I have SetCPU and am currently on smartassV2 when screen off, which has CPU speed from 100-200 MHz. Since the phone goes to deep sleep anyways, would I need to be raising the deep sleep cpu speed (is it 0?) to over 128, or what? The maximum speed is already over the 128 MHz, and the min speed of 100 MHz shouldn't have an additional effect (since deep sleep is already lower than 100 MHz).
Is a reflash necessary, or just a wipe of the cache/Dalvik cache?
Anyone with personal experience in fixing this issue?
I had a a similar issue and I found that for some reason with my phone and particular roms I just could not use them. Not 100% sure Y. I would try a different Rom and see if the problem happens again.
Oh and if you are going to re-install the same one again to make sure it was completely done I would wipe both caches and user data just to be sure.
Related
So basically I just rooted my phone and flashed to cyanogen mod 6.1 and I'm loving it. Thanks xda for the rooting and flashing process. I decided to go into overclocking my mytouch slide and everything seems to work perfect except for the fact when I turn off my screen and turn it back on the screen is at the dimmest setting it can get. I reset the brightness back to how I want it and then turn off the screen again and turn it on, and it reverts back to the dimmest setting. I booted up without having setcpu running and the screen settings stay the same after I turn the screen on and off. has anyone found or seen this before?? And if so, is there a solution to this problem??
Thanks
I've never heard of setCPU causing that problem. You may want to trouble shoot a bit more before pinning it on that. We need to knock some things off the list of possible culprits too.
What is the brightness set to, automatic?
Custom oc kernel (dumfuq's) or what's integrated into CM?
What are your clock settings in setCPU?
What governor are you using in setCPU?
Do you have profiles set, if so, what are they?
Have you messed with the light sensor or done any custom brightness tweaks (CM settings)?
You need to answer some of those first so we can narrow it down, you may have something set up wrong. There is also the issue of the phone not coming to full brightness when you try to catch it on the screen time out (screen is off - but not locked). That's fixed by locking it and unlocking.
[Q] [Idea] Overclocked and have the "wake-up and screen stays black" problem?
I'm running CM6.1 and using Pershoot's kernel, and running at 1.5ghz, on-demand. Probably once a day, I have the issue where a call will come in, or I'll press the power button, or I'll slide out the keyboard, and the screen will stay black (though the backlight for the soft-keys does come on).
I noticed that I can appear to interact with the screen still (answer a call by swiping where the answer slider is, even though I can't see it), which indicates that it's simply the backlight not being turned on.
For others that have the same problem, the next time it happens, try pressing your camera button to open the camera application. For me, the screen comes right up as soon as the application opens (the camera application sets your backlight to high while in it). Anyone else?
I'm going to take a look at the wakeup code this afternoon, I have an idea for a _hacky_ fix that can be done.
I also wanted to confirm - do others have the same problem if not overclocked?
I've been getting that a lot too before (more than once a day for 2 weeks) until I got desperate and wipe/reflashed CM6.1.1 and I haven't seen it in the last 3 days.
I don't know anything so maybe its coincidental. My OC settings are the same as before. The only difference this time was i wipe/factory reset before flashing CM6.1.1.
instead of flashing CM6.1.1 on top of CM6.1 which was what i did 3 weeks ago.
What does your setcpu profiles look like? Set a profile for when you turn the screen off to set the cpu to 245/245. Then set a new one at xxx/806 conservative (xxx being the freq you desire)
Test it out and let me know how it works out.
PanCubano,
Others have suspected that it has to do with the CPU being at high speed the split second before you wake the device, and I agree that it's likely the problem.
Unfortunately it's quite hard to prove that the problem has gone away.
I am having screen wake issues with my evo. Basically for those of you who don't know it's when you press the power button to unlock the phone and the screen doesn't turn on. Sometimes the buttons light up and sometimes they ddon't but I have to clclick the power buttons a few times before the screen wakes up. The following is my configuration:
Running CM7.0.1.2 with SavagedZen 2.0.2 CFS min CPU speed 245 Max 998 OnDemand governor.
I've tried to wipe and reinstall and it didn't help. Clearing Dalvik Cache didn't help either. Any help would be greatly appreciated because this is killing me!
Sent from my PC36100 using XDA App
This is a well known problem with savage-zen kernels. Try toastcfh new kernel in the dev section
This happens to me too, that's why I usually end up back on a sense ROM. Do you use a lock screen widget? Im thinking that might have something to do with it. I wasusing no lock, and it was doing that real bad, I removed the widget and wake up seems to be behaving normally now.
Edit: I too am using a savage kernel, I'll flash a different one and see if I still have the problem.
Try turning these on. Go to settings, then cyanogenmod settings, then display.
Also you could bump up your min frequency to 460 and max to 1113 with the governor on conservative.
Sent from my PC36100
When you turn it on, push the power button slowly, I find if I do that it seems to more reliably wake up. Also, when the screen is black but the bottom lights are on, a quick tap anywhere on the screen always wakes it up for me.
I had the same issue. My fix was to turn on both the Screen-On and Screen-Off animation in Cyanogen Mod Settings.
dirkyd3rk said:
Try turning these on. Go to settings, then cyanogenmod settings, then display.
Also you could bump up your min frequency to 460 and max to 1113 with the governor on conservative.
Sent from my PC36100
Click to expand...
Click to collapse
+1
Sent from my PC36100 using Tapatalk
HI,
i m having screen issues wid cm10 only.when installed cm10 it worked fine, but when i lock and unlocked it screen seems to not turn on but touch works,i came to know it by the vibration while unlocking ,also the unlock sound plays.but this problem is not with an other rom.:crying:
Afnanshareef said:
HI,
i m having screen issues wid cm10 only.when installed cm10 it worked fine, but when i lock and unlocked it screen seems to not turn on but touch works,i came to know it by the vibration while unlocking ,also the unlock sound plays.but this problem is not with an other rom.:crying:
Click to expand...
Click to collapse
It's a wake up issue in CM10. Should have read bugtracker before installing it.
Workaround:
- Wait 4-5 seconds after turning off screen to turn it back on.
- Low brightness may turn off screen but touch will work. (weird), change the brightness to auto or high.
- Enable wake by volume button as they respond better than power button.
Don't set your min CPU freq under 200Mhz. This causes lags.
THANKS.......
Cm10
Its also a question of the brightness u have set...
if its totally low, u will be greeted with a black screen on waking the device up...
I have had the same problem all the tym..
workaround:
1. update to the latest cm10 version(benjamyn's one)...
2. cpu 245 min and 600 max..
and
3. brightness 25% to be safe..,,,,,
if I helped click thanks....
Does Power saving mode still work when using an app like SetCPU, or do the OC apps overrule the CPU underclock setting of that mode?
I understand that power saving mode does other things as well as just underclock the CPU (ie lower brightness etc), but I was specifically thinking about the clock settings.
I've not decided whether I will OC or not yet. I will definately play with the voltage settings though. I'm finding that my tablet gets extremely warm in the lower left hand side when put under intensive use. But back to my original point. Id like to be able to underclock it on the fly at a push of the button and find im enabling that setting alot with the stock set up...
Thanks