Recently I have noticed when I wake up my phone the screen is super dim for 1/2 second then it gets normal brightness. It is not set to auto brightness.
I am running CM7.1 with the recent incredikernel. I just noticed it after installing incredicontrol and flashing the less aggressive volts. I reset the volts back to default thinking its a power thing but it still does it.
I was using ondemand governor but it also does it with all the others.
Does anyone know what's going on?
Sent from my D Inc using XDA App
update: I wiped everything and did a fresh install of cm7.1. It still had the same dim issues at wake up. This is with only 7.1 no different kerenel or any apps installed.
I then wiped everything again and installed stock+ v3.01 and it doesn't have the dimness at wake up.
Any ideas? Does anyone running CM have or not have dimness during wake up?
Sent from my D Inc using XDA App
I have the same issue, annoying....
Try running SetCPU and set a screen off profile and play with the mix/max speeds. I found 128Mhz will show severe lag, 245Mhz is doable and a bit higher will be seamless at the expense of battery life.
kcrw said:
update: I wiped everything and did a fresh install of cm7.1. It still had the same dim issues at wake up. This is with only 7.1 no different kerenel or any apps installed.
I then wiped everything again and installed stock+ v3.01 and it doesn't have the dimness at wake up.
Any ideas? Does anyone running CM have or not have dimness during wake up?
Sent from my D Inc using XDA App
Click to expand...
Click to collapse
Try turning on the setting allow light decrease:
settings->cyanogenmod settings->display->automatic brightness->allow light decrease.
If that doesn't help, I know that there was a while where the way the light sensor was handled on this ROM wasn't smoothly handling light transitions. Try flashing one of PonsAsinorem's KANG builds, just look on page 1 of development for the thread. It also may be fixed in one of the latest nightlies and personally I think the nightlies are better than 7.1 release.
About 10% of the time when I try to wake my phone up on CM7, it lights up for half a second then turns back off. It still vibrates and responds to touches, but the backlight is completely off until you press the power button again. Which sounds kind of related to your issues.
I've tried every frequency/kernel/kang combination possible to fix it, but no luck.
Related
Hi,
I have this annoying problem regarding waking up my device when its locked. Normally i should press the power button, or the trackpad as im running virtuous rom, and the screen should give me the lock screen. But this does not happen, intead screen stays black, the keys on the bottom do light up, and it registers my touches on the screen as i can put the music player on again.
This is happening for quite some time, but lately its more often and its really frustrating me because i have to hit the power button for like 10 times in a row before it finally goes on again.
When it stays black and i put it off again, touching the power button, moste of the times the screen will flash the lockscreen and go black again.
Ive tried to find a sort of system in it, like a period of time or somthing like that, but it seems as if its completely arbirtrary when it happens and when it doesnt.. Only thing i remarked was that when it's off for a longer time, it will have more chance of getting on the first time then when its off for a shorter period...
Any suggestions to fix this evil thing?
cheers
This is a very comman problem.
what you need to do is setting up a screen off profile on setCPU
min 245
max 368
scalling : powersave
I agree check your screen off profiles. Also try not to oc too high. You might also want to install the pershoot kernel if you haven't already. I had this issue when I fist installed the virtuous rom & switching kernels and tweaking my cpu profiles resolved this issue.
Sent from my HTC Vision using XDA App
Screen off profile doesnt help, What does work is less oc'ing it... stupid thing is i can only oc to 902 mhz for the screen to turn on all the time... Thats like not oc'ing it at all ><... I'm on the virtuous kernel now, will try the pershoots in a min, i'll keep you updated
Oh sorry, screen off profile does help, didnt enable profiles in a whole ... pershoot kernel helps a lot, with that one and the screen off profiles, i can oc to 1517 and even then its just not going on very rarely... thanks for the help... Only thing thats regrettable is that the pershoot kernel does not have the smartass governor ...
EDIT: I realised i didnt enable the profiles while using the virtuous kernel either, so i installed that one again and guess what, it works!! Every single time i hit that power switch it goes on like it should... what a relieve thx guys
grtz
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.
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?
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
Is there anything I can get for the screen to work at all times? Sometimes the screen wont respond to my touch and its annoying...Is there anything to fix this?
Pivo187 said:
Is there anything I can get for the screen to work at all times? Sometimes the screen wont respond to my touch and its annoying...Is there anything to fix this?
Click to expand...
Click to collapse
Do you notice this at any specific times? Not necessarily times of the day, but after using a specific app, before using one, when turning the on screen, etc?
No it actually happend after a reboot...it happens often maybe its the ROM?
I had this problem, but it was due to the fact that I had SetCPU running and set my screen off profile to 128Mhz. So obviously, when I would turn on my phone, the screen would turn on after a small delay. I since bumped it up.
spyd312 said:
I had this problem, but it was due to the fact that I had SetCPU running and set my screen off profile to 128Mhz. So obviously, when I would turn on my phone, the screen would turn on after a small delay. I since bumped it up.
Click to expand...
Click to collapse
Yeah this could definitely be it. You generally don't want to run the Evo below 245.
Sent from my PC36100 using xda premium
Where is the screen off section? I am on ISC mode 7...phone seems a little laggy & still doesnt respond at times when touching the screen... I just installed the savage zen kernel 2.2.1 CFS HAVS+ running smartass governor & seem to be getting better battery life over the stock kernel.