I love cyanogenmod for many reasons, but everytime I try, one thing kills me.
It I hit the power button when the screen is off, it often takes 5 or 6 seconds to turn on. Has anyone else had this problem and solved it?
Mind you, this has happened under many versions of CM (but on 6.1 right now) with different kernels and sometimes having setcpu profiles.
Any ideas?
Thanks in advance.
newsoundwave said:
I love cyanogenmod for many reasons, but everytime I try, one thing kills me.
It I hit the power button when the screen is off, it often takes 5 or 6 seconds to turn on. Has anyone else had this problem and solved it?
Mind you, this has happened under many versions of CM (but on 6.1 right now) with different kernels and sometimes having setcpu profiles.
Any ideas?
Thanks in advance.
Click to expand...
Click to collapse
it normally has something to do with setcpu being clocked to low, try raising the min freq up to 245mhz
Actually, set the SetCPU minimum frequency to 384 MHz. That usually solves problems like this, or with the screen not turning on for a call, whereas 245 doesn't always.
Related
Ok i have my g2 currently oc'ed to ondemand 1497 max 245min and my problem is when trying to wake the phone. i press the power button screen flashes and then get a black screeen. i have to press the power button a couple of times in order to get it to wake up. anyone know how to fix this.....phone works fine when i restart and have a normal clock speed but when i overclock it i always get the wake problem.....
That's the risk you take when overclocking! Weird things start to happen the higher you go. Some phones can go higher than others.
I would back off a little to find your sweet spot.
Some people have had problems with the SetCPU widget, do you have that on your homescreen?
Yup... thats pretty normal behavior. I get it once in a while...
ok yea i lowered the max to 1209 n it seems to be working better now....
That's normal and happens to me. Avoid hitting the power button twice in rapid succession and you won't have that problem.
I always had the same behavior until I installed CM6.1 I have not experienced the issue since and I am still overclocked. My guess is that its a problem with the stock ROM.
Sent from my HTC Vision using XDA App
@cirby944
Hey thanks that worked for me too...now I'm back to 1.4ghz with no problems..
Sent from my HTC Vision using Tapatalk
I was having this problem with SetCPU as well on Virtuous v0.7.2 (Sense, 2.6.32.26-cm-virtuous-v1.1 kernel) and I solved it by creating a SetCPU profile for "Screen Off" with the default settings (806400/245760, scaling set to ondemand, priority 50). Works like a charm and I never get any hang ups after turning the screen on!
I also had this problem with virtuios rom,so i installed the pershoot kernal and that fixed my issues with the screen. No more problems since.
Sent from my HTC Vision using XDA App
So i just swiched from virtouos ROM (sense) to CM6.1 and i am having a problem.
when i first flashed virtouos, sometimes my phone screen wouldnt turn on with
first attempt but after setting profiles on setCPU it was fixed and didnt happen anymore now with CM6.1 i am having a slightly different problem the screen doesnt turn on when i am receiving a call (it rings though) and i have to press the power button couple of times to get the screen on. i have already set some profiles on setCPU ,i am just wondering if there is any fix for it ?
Thanks
Only thing anyone can probably suggest is turning up your min clock speed. What are your profiles set to?
My screen off is 245/368 just to give it that bit extra to guarantee no wakeup issues, not that I had any to begin with, better safe than wanting to throw her up the wall (I get annoyed easy).
bahmanxda said:
So i just swiched from virtouos ROM (sense) to CM6.1 and i am having a problem.
when i first flashed virtouos, sometimes my phone screen wouldnt turn on with
first attempt but after setting profiles on setCPU it was fixed and didnt happen anymore now with CM6.1 i am having a slightly different problem the screen doesnt turn on when i am receiving a call (it rings though) and i have to press the power button couple of times to get the screen on. i have already set some profiles on setCPU ,i am just wondering if there is any fix for it ?
Thanks
Click to expand...
Click to collapse
Doesn't sound normal... did you make ANY customizations at all? Or did you install CM straight up and just use it like that? Any adjustment to "performance settings" or CPU clocking? What SPL and radio do you have installed?
Possible explination posted here by rmk40:
http://forum.xda-developers.com/showthread.php?t=884237
dhkr123 said:
Doesn't sound normal... did you make ANY customizations at all? Or did you install CM straight up and just use it like that? Any adjustment to "performance settings" or CPU clocking? What SPL and radio do you have installed?
Click to expand...
Click to collapse
Thanks
no i didnt make any customization its just CM6.1 although my max clock speed is at 1497 mhz
setCPU
Screen off max 368
min 245
and profiles for temp and battery as well
the wierd thing is it doesnt happen at all when im just waking the phone up it only happens when its ringing i am thinking its my CPU issue ,i dont think it handles overclocking well ,i couldnt go over 1.1ghz (it would freeze instantly) with virouos that was the main reason i switched im gonna play with with cpu profiles for a while and see if i can get it fixed.
btw i have never flashed any radio so im guessing its the stock one
wow this is very intreasting its actually fine without any setCPU profiles
i had something totally different in my mind.
bahmanxda said:
wow this is very intreasting its actually fine without any setCPU profiles
i had something totally different in my mind.
Click to expand...
Click to collapse
With my experience I've noticed the phone runs better, and lasts longer on a single charge WITHOUT setCPU profiles. Just my opinion
bahmanxda said:
although my max clock speed is at 1497 mhz
setCPU
Click to expand...
Click to collapse
And there you have it. Overclocking can do weird things.
dhkr123 said:
And there you have it. Overclocking can do weird things.
Click to expand...
Click to collapse
Fair enough
Sent from my HTC Vision using XDA App
I just flashed the vision rom on g2 about 6 hours ago earlier today from Rom Manager and its running great except that when the phone goes into screen off mode, and then i try to turn the phone back screen on the screen stays black but the bottom 4 buttons still glow, and when i click stuff on the screen it clicks them but its black and there is NO brightness at all NO LIGHT lol, now this isn't the phones problem because on the normal froyo backup i have it works fine, but i am in love with sense, except it really pisses me off that it does this, if anyone can help it would be great or if someone has experienced this issue and found any way to solve it, please let me know how. If you want a video let me know i can make one.
TheRealEvo said:
I just flashed the vision rom on g2 about 6 hours ago earlier today from Rom Manager and its running great except that when the phone goes into screen off mode, and then i try to turn the phone back screen on the screen stays black but the bottom 4 buttons still glow, and when i click stuff on the screen it clicks them but its black and there is NO brightness at all NO LIGHT lol, now this isn't the phones problem because on the normal froyo backup i have it works fine, but i am in love with sense, except it really pisses me off that it does this, if anyone can help it would be great or if someone has experienced this issue and found any way to solve it, please let me know how. If you want a video let me know i can make one.
Click to expand...
Click to collapse
You have overclocked right?
this is a very common problem
what you need to do is set up a screen of profile on setcpu
min:245
max:368
scaling : powersave
and make sure you tick Enable on profiles menu
this should solve your problem.
bahmanxda said:
You have overclocked right?
this is a very common problem
what you need to do is set up a screen of profile on setcpu
min:245
max:368
scaling : powersave
and make sure you tick Enable on profiles menu
this should solve your problem.
Click to expand...
Click to collapse
Thank you for the information, just set everything up the way you said to and gonna give it a test now, thank you!!
Edit: also, i have it clocked at 1420 max and 800 min, and a set profile for the one that you gave me and one so if it overheats to clock itself down, should i keep the min to 800 or should i make it lower, this is for when the phone is on, when it goes screen off it goes into the profile you gave me, thanks.
TheRealEvo said:
Thank you for the information, just set everything up the way you said to and gonna give it a test now, thank you!!
Edit: also, i have it clocked at 1420 max and 800 min, and a set profile for the one that you gave me and one so if it overheats to clock itself down, should i keep the min to 800 or should i make it lower, this is for when the phone is on, when it goes screen off it goes into the profile you gave me, thanks.
Click to expand...
Click to collapse
why do you have your min at 800 mhz anyway?
there is no need for that put the min at 245 your phone will scale up when it needs
to. and for scalling, ondemand works for me best ,you can can try different ones to see which on gives you better performance and battery life. dont use performance scaling for everyday use though .
Sometimes when I lock my phone, the screen is unable to comeback up again when i try to unlock it. It just faintly appears when i press the power button but then dissapears back to a black screen. I am able to control (unlock etc, can feel the vibrations and stuff) but there is nothing on the screen. only after about 15-30 mins will the screen recover. Is there anyway to fix this?
This is generally related to governor of your CPU. At least I've fixed that problem by setting greater minimum MHz value in my tablet and experimenting governors.
Are you using any custom roms / kernels ?
could be due to undervolting as well
Djabolic said:
This is generally related to governor of your CPU. At least I've fixed that problem by setting greater minimum MHz value in my tablet and experimenting governors.
Are you using any custom roms / kernels ?
Click to expand...
Click to collapse
Yep currently on BAMF but happened on androidme too. My setcpu sleep profile is at lowest mhz and ondemand. Using franco latest nightly.
crixley said:
could be due to undervolting as well
Click to expand...
Click to collapse
I dont do any under volting.
Happens on every rom (currently on a cm10 nightly) ... phone is stable in just about every other way, but 1/50 (guessing) the unlock just goes sour.
It's as if the screen doesn't come on....
I tried raising my min cpu freq while sleeping- even at 512mhz it still did this occasionally.
Any thoughts?
pcguru000 said:
Happens on every rom (currently on a cm10 nightly) ... phone is stable in just about every other way, but 1/50 (guessing) the unlock just goes sour.
It's as if the screen doesn't come on....
I tried raising my min cpu freq while sleeping- even at 512mhz it still did this occasionally.
Any thoughts?
Click to expand...
Click to collapse
I've had this problem for quite some time as well, and I've read about it in the forums before. I believe that and the reboot in the camera app (try unlocking) are the two biggest issues right now. From what I've read in the android development forums these are likely kernel issues that won't be solved easily.
pcguru000 said:
Happens on every rom (currently on a cm10 nightly) ... phone is stable in just about every other way, but 1/50 (guessing) the unlock just goes sour.
It's as if the screen doesn't come on....
I tried raising my min cpu freq while sleeping- even at 512mhz it still did this occasionally.
Any thoughts?
Click to expand...
Click to collapse
CM10 has been notorious for this since day one. I haven't used a CM10 nightly in about 2 months, but I had quite a few BSOD's in ParanoidAndroid. I've been using tdmcode's AOKP41 for the past few days and so far I haven't had a BSOD, but from what I read in his thread in the development section I'm lucky.
One thing that makes it "less" of a hassle is that you can hold the power button until it reboots (around 10 seconds, maybe 15 or so) instead of pulling the battery.