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
Related
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
As the titles states, I use the SetCPU widget and find that it stops updating after a while (after which, I'll have to remove and re-add). Is there a fix for this?
That has been happening to me and I haven't found a fix. I just stopped using it. It's a shame too because I used it a lot for checking the temperature, making sure I wasn't running too hot.
Maybe you can try reflashing the kernel.
Sent from my HTC Desire Z/G2 using XDA App
did it on every rom even stock i have used. i stopped using setcpu, it caused more problems than good
confirmed here too, the widget stops working for me after it's been on charge for like an hour. The status bar/notification bar icon works though (but no temperature)
its the app and the widget itself, for the longest time i had this problem when i was using my n1 and running cm6 and not only that, when i had it set to a certain freq. i go back into the app and it would say its clocked at 800 max, but i had it set to 110, i would have to adjust the freq bar to set it back to that.. i email the dev bout it all he said it was not set on boot, which i replied thats no the issue on hand as the phone has been booted up for awhile, and i manually set my OC, i never got a reply back after, so i check set on boot, and after bout an hour.. i go to setcpu and same issue
my target is set at 110 but its saying its maxed at 800, this also set on performance to always be on that OC, i told the dev again. and still no response so i gave up on setcpu, and glad the Cyanogen made built in cpu govnor
Its the widgets, my data signal widget takes a crap and freezes too. Setcpu works fine even when the widget freezes
Sent from my HTC Vision using XDA App
If running cm7 just use the built in settings. I used setcpu with off screen prifles being slower and others but it actually made my phone run like crap. Battery life has been generally the same without using setcpu so I killed it. If u are running cm7 I wouldn't bother with it.
Love the Overclocked "nonsense" CM7
How to wake up the phone without battery removal? I have Virtuous 1.0.1 ROM with advanced kernel and from time to time I have wake up issue. I would like to avoid removing battery because I have otterbox case on my phone.
Do you know any other way to wake up yhe phone?
Well if you can't wake it up with the button on top it is a problem. Are you overclocked? Try lowering it.
Sent from my T-Mobile G2
Open the keyboard....lol
Sent from my HTC Vision using XDA Premium App
wake up
I have seen the same behaviour with the stock htc latest (1.82.whatever).
top switch -- othing
opening kbd -- noting.
only a removal of the battery seems to help.
Of course it hasn't happened in a convenient place e.g. to see if I can still access it or if charging works etc.
If u installed trackpad wakeup, it seems to distort virtuous roms and keep the device from waking up all together.....there are posts about it in the developers forum
Sent from my HTC Vision using XDA Premium App
Also in some cases this is caused by underclocking with a screen off profile. I actually gave up on virtuous untill that problem gets solved. I havnt tried the latest version though.
Sent from my HTC Vision using XDA App
There are 2 distinct "screen on" issues with slightly similar symptoms.
One is the "screen wake issue" what is common with Virtuous, and typically caused by certain combinations of overclocking, and screen off profiles.
The screen wake issue is very well discussed in the Virtuous thread, and commonly/easily solved with the proper screen off settings.
http://forum.xda-developers.com/showthread.php?t=967153
But the screen wake issue, as far as I have experienced, manifests with screen sometimes flickering on for a second, and sometimes responding to multiple presses of the power button, or by opening the keyboard. There is a different issue, some have called "SOD" (screen of death) where the phone seems completely dead until you pull the battery and reboot. This seems to be more what you are describing, but I'm not sure. The cause of the SOD has not conclusively been discovered, and there is currently no known surefire solution. But it may be hardware and GPS related, maybe kernel related. Personally, I've experienced this across several custom ROMs (Virtuous, CM7), kernels, as well as stock. The only luck I have had, is that the stock DZ ROM with the Godspeed kernel is the only combination which seems completely free of SODs. One person sent his phone into HTC due to SODs, and they said it was caused by a faulty GPRS module, and fixed it by replacing the mainboard. Another person send this phone in, and it was returned untouched, with the same problem still present.
http://forum.xda-developers.com/showthread.php?t=857584&highlight=pulling+battery
http://forum.xda-developers.com/showthread.php?t=908095
shortlived said:
Also in some cases this is caused by underclocking with a screen off profile. I actually gave up on virtuous untill that problem gets solved. I havnt tried the latest version though.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Why people still do this just boggles my mind. All current kernels drop the processor down when the screen is off. There's no need - at all, for a screen off profile. It creates a wakeup issue as you can tell since SetCPU has to refresh the phones state then switch profiles in order to allow the processor to move into a higher state. That takes a lot of time (in computer time) thus creating this 'bug' that doesn't actually exist. The OC bug however does exist and is present no matter what you do aside from keeping it at 1.1GHz or less.
KCRic said:
Why people still do this just boggles my mind. All current kernels drop the processor down when the screen is off. There's no need - at all, for a screen off profile. It creates a wakeup issue as you can tell since SetCPU has to refresh the phones state then switch profiles in order to allow the processor to move into a higher state. That takes a lot of time (in computer time) thus creating this 'bug' that doesn't actually exist. The OC bug however does exist and is present no matter what you do aside from keeping it at 1.1GHz or less.
Click to expand...
Click to collapse
I had the screen wake issue on Virtuous, with NO screen off profile and OC'ed to 1 GHz. Making a screen off profile, but leaving a wide range for the CPU speed (not underclocking it) and interactive governor solved the issue in my case.
That might work better since most people I've seen tend to use the conservative or powersave gov. in their screen off profile. I'll correct myself too, what I said was from a CM standpoint since I've yet to use Virtuous.
Yeah, the screen wake issue on Virtuous is different from the one on CM7. If I remember properly, on Virtuous, using the advanced kernel results in screen wake issues for everyone or most people, unless you make some SetCPU/CPU Tuner setting adjustments.
Do you have SetCPU, or another program capable of CPU clock control installed? If not, install one of them and bring the max clock down... the Advanced Virtuous kernel boots at 245min/1516max - I noticed this after a fresh install of Virtuous 1.0.1/2 and the Advanced kernel
qzfive said:
Do you have SetCPU, or another program capable of CPU clock control installed? If not, install one of them and bring the max clock down... the Advanced Virtuous kernel boots at 245min/1516max - I noticed this after a fresh install of Virtuous 1.0.1/2 and the Advanced kernel
Click to expand...
Click to collapse
Completly agree.
I am shocked and appauled that most don't seem to understand that the os and it does not matter which(I.e. android,ios,windows) or platform (I.e. smartphone,tablet,desktop,etc) when you overclock more than just ur cpu speed is changed. If u have any experiance overclocking cpus on your home computer, you know u cannot let your system hibernate because it will not wake up. All operating systems allow the cpu to completly turn of in hibernation until it recieves an electrical pulse from the board. But if ur cpu goes from off to high it pulls way to much electricity and can't process then commands because all the recouces went to waking. If you have sleep parameters set with a narrower range the system will have enough resources left to process ur intial command...when it comes to sleep to wake there are no in between frequencies.
Sent from my HTC Vision using XDA Premium App
I searched but couldnt find exactly what I'm looking for. When I press the power button or trackpad to wake the phone up in the dark, it wont turn on. Only the soft keys will light. Any advice?
If you have the CPU overclocked that could be the culprit. CM is notorious for not playing nice with any speeds over 1 GHz. Set is at 1017 or whatever is closest to that and it should be fine.
hiko36 said:
If you have the CPU overclocked that could be the culprit. CM is notorious for not playing nice with any speeds over 1 GHz. Set is at 1017 or whatever is closest to that and it should be fine.
Click to expand...
Click to collapse
I keep mine at 1.4 with no issues
Sent from my Vision using XDA Premium App
I don't see how this is an issue with the proximity sensor...
However, as per the above poster, CM has issues with overclocking. I experienced the same issue when I first installed CM7 and my options were to disable overclocking or disable the on/off animations (I chose the latter).
With CM7 I noticed the cpu is set @ a range of 245-1400. Use setcpu profile for screen off @ 245-368 and a regular profile 700-1017...you will have less diffulculty wakeing ur device. If you keep it @ the default settings it tries to jump to the highest frequency and uses nothing in between and creates a lag and sometimes even a soft reboot
Sent from my HTC Vision using XDA Premium App
My phone sometimes doesn't wake when I try and turn it back on after a while when the screen goes off.
I am running CM7 7.1.
I am using default oc settings. (ONDEMAND, 300-ish min, 1110-ish max, no undervolting as far as I know)
I tried to press the button combo to get fastboot but it doesn't work either. I have to take the batteries out for the phone to restart and then it works again.
What gives?
convolution said:
My phone sometimes doesn't wake when I try and turn it back on after a while when the screen goes off.
I am running CM7 7.1.
I am using default oc settings. (ONDEMAND, 300-ish min, 1110-ish max, no undervolting as far as I know)
I tried to press the button combo to get fastboot but it doesn't work either. I have to take the batteries out for the phone to restart and then it works again.
What gives?
Click to expand...
Click to collapse
368 is the lowest you should go and, even then, you might run into wake issues. Additionally, if you have anything like SetCPU installed, be sure you don't have a screen off profile set with too low a speed.
Sent from my HTC Vision using XDA App
It seems to be mostly a cpu clocking issue. Raise your minimal clock for screen off profile if you have one and it should work.
Sent from my T-Mobile G2 using XDA App
I don't think that is the reason.
Back during CM6 6.0 RC1, I had set CPU with 256mhz off screen, and it was perfectly fine back then...
convolution said:
I don't think that is the reason.
Back during CM6 6.0 RC1, I had set CPU with 256mhz off screen, and it was perfectly fine back then...
Click to expand...
Click to collapse
Are you using SetCPU?
If you are (and it's really not needed anymore) make sure your max on the screen off isn't set low as well. You can sometimes get away with a low min but, if you have a 256min/256max, you're basically telling your device to stay at 256 whenever the screen is off and no amount of pushing the power button to wake it will change that.
Sent from my HTC Vision using XDA App
Not. I uninstalled SetCPU. Using the built in govenor now...
The problem you seem to be having is a bsod or black screen of death.
If you search that term in the forum you will find a few posts about it.
The only thing that i am aware of about the issue is that it is related to the use of your gps.
I have had trouble replicating the issue, it happens very randomly. I sent my phone to bell and they didn't fix it...
Same problem here i think its a cm7 problem
Sent from my HTC Vision using XDA App
tvdang7 said:
Same problem here i think its a cm7 problem
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
In my case it was a battery issue.
To be sure I tried the experience 3 times: OEM battery for a day, ebay one for an other.
At the end I had a black screen ( sleep of death) every time I turn off the screen on the ebay battery (galilio).
The voltage was alright, it was something else.
running virtuous unity 2.37
I've had problems with the screen-on and screen-off animations causing a black-screen-of-death.