[Q]How to wake up w/o battery removal? - G2 and Desire Z Q&A, Help & Troubleshooting

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

Related

[Q] SetCPU Superuser Permissions

So I'm on a visionary temp root, overclocked with setcpu. Ive set up several different profiles but I've noticed that my battery life with the profiles isnt as good as other users have claimed.
I have noticed that when i open setcpu sometimes a little message will flash up saying that setcpu has been given superuser permissions. Does this mean that prior to opening the program, it didnt have permissions? If it in fact did not have superuser permissions, could that be why my battery life is less than expected? (i.e. The program didnt have permissions and thus couldnt use the profiles to slow down cpu speed upon screen off, etc.) The message does not come up every time I open setcpu, but it seems to come up when I havent opened the app recently.
Any ideas?
cmccollough said:
So I'm on a visionary temp root, overclocked with setcpu. Ive set up several different profiles but I've noticed that my battery life with the profiles isnt as good as other users have claimed.
I have noticed that when i open setcpu sometimes a little message will flash up saying that setcpu has been given superuser permissions. Does this mean that prior to opening the program, it didnt have permissions? If it in fact did not have superuser permissions, could that be why my battery life is less than expected? (i.e. The program didnt have permissions and thus couldnt use the profiles to slow down cpu speed upon screen off, etc.) The message does not come up every time I open setcpu, but it seems to come up when I havent opened the app recently.
Any ideas?
Click to expand...
Click to collapse
From my understanding, you only set it once. i had set a widget because i thought set cpu had to be running. But i deleted it because if you think about it....superuser app already has the permissions set, and when you open setcpu it shows the current speed.....if it wasnt working it would show 800mhz then KICK into 1 ghz?....thats what i think. You shouldnt need to worry.
Great, thanks for the response.
Sent from my HTC Vision using XDA App
same here. from time to time this popup comes.
anyway i cannot see any benefit from running setcpu as the profiles are not working for me.
i tried setting up screen off profile. this never triggers.
i leave setcpu deinstalled now. battery life is good so far
snudel said:
i tried setting up screen off profile. this never triggers.
Click to expand...
Click to collapse
How can you tell if it triggers or not?
cmccollough said:
How can you tell if it triggers or not?
Click to expand...
Click to collapse
Good question. Can't find anything in logcat.
set notifications.
on the magic you could see him switching profiles right after turning on the screen
you wont see it on the g2
I agree, something is fishy with this. EVERY time I open setcpu it gives me the su permissions granted window like its not being saved in memory
Sent from my HTC Vision using XDA App
EDIT: After shopping around on the market I came across an app called "CPU Tuner". The UI is nice and has roughly the same customization as setcpu if not more. It does take a bit of getting used too but i'm more than willing since the profile notification actually cycles with this app vs. setcpu. I'll give it a shakedown tomorrow as it's getting too late here to test.
cpu tuner doesn't work for me.
in profiles, it just shows 700mhz to 800mhz, which makes it useless as i want to underclock to 200 when screen is off.
That toast pop-up is nothing to worry about, its just something that has featured in the last couple of SU builds, it doesn't mean your app is not working.
I just turn the notification off in the SU settings.
I can now confirm that the screen off profile is not working correctly. Before going to sleep last night, my phone had a charge of 99%. I did not have anything running (no wifi, bluetooth, sync, etc.) and I woke up to 81% battery. It never killed that much overnight before overclocking. We gotta get this fixed.
Sent from my HTC Vision using XDA App
cmccollough said:
I can now confirm that the screen off profile is not working correctly. Before going to sleep last night, my phone had a charge of 99%. I did not have anything running (no wifi, bluetooth, sync, etc.) and I woke up to 81% battery. It never killed that much overnight before overclocking. We gotta get this fixed.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
i have mine set to 1ghz max 245 min profile screen off 245/245 priority--100..and put a widget on my main screen. My phone has been on screen off for the pat 5 hours....and drained only 2% battery life.....i dont understand why it doesnt work with some peoples phones??!!. is it different cause im using a desire z and yours a g2?...i HARDLY doubt that would be a problem :S..
have you tried the widget?.when going to running services, my setcpu app has been running for ever. aka profiles and setcpu working.
jark99 said:
i have mine set to 1ghz max 245 min profile screen off 245/245 priority--100..and put a widget on my main screen. My phone has been on screen off for the pat 5 hours....and drained only 2% battery life.....i dont understand why it doesnt work with some peoples phones??!!. is it different cause im using a desire z and yours a g2?...i HARDLY doubt that would be a problem :S..
have you tried the widget?.when going to running services, my setcpu app has been running for ever. aka profiles and setcpu working.
Click to expand...
Click to collapse
Running the setcpu widget on my phone caused instability issues at higher clocks (feeling ballzy w/ flippy's 1.8 kernel). After removing the widget my profiles were hit and miss for some reason.
As far as the battery issue goes, anyone running CM RC2 and earlier might want to check out nightly 36, apparently there was a memory leak causing battery drainage ( I don't know anything about what it means but common sense leads me to believe a leak is bad lol). If anyone is still not satisfied with setcpu I highly recommend CPU tuner.
jark99 said:
have you tried the widget?.when going to running services, my setcpu app has been running for ever. aka profiles and setcpu working.
Click to expand...
Click to collapse
Yes I have the widget on my homescreen. Weird that so many people get different results
Could the scaling be giving people varying results? I don't even really know what they do, I have mine set on ondemand. Would someone mind sharing what exactly the different scalings do?
cmccollough said:
Could the scaling be giving people varying results? I don't even really know what they do, I have mine set on ondemand. Would someone mind sharing what exactly the different scalings do?
Click to expand...
Click to collapse
http://www.droidforums.net/forum/rescue-squad-guides/47871-overclocking-101-a.html
Centered around the OG Droid but basic concepts still stand.
- Just picked up an app called SuperPower, had it a while back and had issues..but it's been update a lot since then. Looks like it's an all purpose battery management app that has the ability to govern cpu speed also. I'll test drive it and see how it works.
My battery life has improved markedly since installing CM nightly #36 and Pershoot's latest kernel. I've been using my phone pretty heavily over the last 8hours and still have over 50% left. Lots of texts, emails and websurfing etc.

SetCPU Gingerbread

Is anyone using SetCPU with gingerbread?
I'm using GingerVillain 1.5 but I can't seem to find the right profiles with SetCPU.
Oc'd @ 1,2 Ghz without profiles.
Because when I use the screen off profile, my screen sometimes won't turn on.
Screen off - min 245 max 1200
Can someone help me finding the right profiles?
Share your user experience.
In my experience and many others too, the profiles are not needed. The only profile you should ever need is a temperature profile and that's only if you really have it cranked up.
Having a screen off profile is always bad since switching to another profile doesn't happen instantly - there are polling intervals involved and until the next cycle runs your phone will still be using the screen off profile. That makes the phone slow which causes SetCPU to take longer in switching profiles, bogs down the cpu and it becomes a vicious cycle for a few seconds (sometimes a couple minutes). All the while it's draing your battery because the cpu has to work harder. Even regular profiles eat the battery due to the constant querying of the systems status and processing power used for that - which is the main reason you'll hear people whining about their battery life (some aren't effected as much).
Profiles are just not a good idea except for a temp profile for those that oc to the higher GHz (probably 1.4+).
You could try using cpu tuner instead. Gives you way more options.
CM 7
You have a lot of options with cpu tuner.
What triggers and/or profiles do you use?
My screen on/off has been working fine with CM7 nightlies before and after the RC1. I've been using SetCPU with a normal profile of 1017max/245min and a screen off profile of 365max/245min.
I think your issue is with overclocking. Idk about Gingervillain but as far as CM7 goes lots of people are having issues with the on/off animations and wakelock issues when overclocked over 1ghz. Try using your profiles and clocking at or under 1ghz and see how things change.
Not sure why anyone would really need a higher clock than 1ghz but what do I know. I dont see any slowdowns at 1017mhz and I feel that anything faster than that would lead to heat or battery issues?
Yes, screen off profiles work. But they drain your battery faster than if you have no profiles.
Sent from my T-Mobile G2 running Cyanogenmod.
thanks bro, i OC'd to 1017 and there are no issues
ibemad1 said:
Yes, screen off profiles work. But they drain your battery faster than if you have no profiles.
Sent from my T-Mobile G2 running Cyanogenmod.
Click to expand...
Click to collapse
I'm not so sure about this. Have you tested this at all? Starting using screen off profiles of 365max/245min have really increased my battery life, especially when my phone sits idle for a decent amount of time. I don't think you could see more battery life by leaving the clock at 1ghz while the screen is off.
martonikaj said:
I'm not so sure about this. Have you tested this at all? Starting using screen off profiles of 365max/245min have really increased my battery life, especially when my phone sits idle for a decent amount of time. I don't think you could see more battery life by leaving the clock at 1ghz while the screen is off.
Click to expand...
Click to collapse
Every kernel that I know of out there drops down the clock cycle when the screen times out. The reason not having the screen off profile saves the battery is because SetCPU isn't constantly sending requests about the phones state and then checking that against your profiles to see if it meets the parameters set in them.
Now it could be a bit different for you. You might have a different set up or different apps that make having a screen off profile useful (ones that constantly update or run in some way). You just have to watch your phone for a few days and get an app that keeps track of that stuff so you know which route to take.
KCRic said:
Now it could be a bit different for you. You might have a different set up or different apps that make having a screen off profile useful (ones that constantly update or run in some way). You just have to watch your phone for a few days and get an app that keeps track of that stuff so you know which route to take.
Click to expand...
Click to collapse
This is very true. It is definitely hard to make a blanket statement because no two people have the exact same setup. All I was saying is what I've been doin with the screen off animation and I've been having pretty solid battery numbers.

Proximity Sensor Problem w/ CM7?

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

[Q] Screen won't wake due to OC

ROM: Virtuous 1.0.2
Kernel: Virtuous Advanced 2.2.0
I'm having trouble with my screen struggling to turn on when I wake my phone if the cpu speed is anything above stock. If I push the power button once the capacitative buttons light and nothing else happens, if I push it a second time the lights turn off again and I briefy see my lockscreen flicker before my pained eyes
If I do this cycle many times over eventually I'll get lucky, but there's no pattern to the success and it's very frustrating.
The symptoms are similar to this thread: [Q] Phone unlocking screen issues. The method described there to solve the problem was to turn off on/off animations. I don't think this solution applied as I'm not using CM7.
I think the touchscreen input is recieved despite the screen itself having no picture - for example I can unlock my phone by swiping down (stock Sense lockscreen). If I touch the touchscreen in the right place to open the dialer while I've "unlocked" it in this way, when the phone finally wakes after frantic power button pushing, the phone will be in the dialer app.
I think it might be related to Sense as I tried a stock Sense from rmk - [ROM]Vision_Gingerbread_S_HTC_WWE_2.30.405.1_Radio_12.5 0.60.24_26.08.04.16_M and overclocked using both Virtuous Advanced 2.2.0 and Pershoot's Kernel. In both cases I also had wake issues any time I tried to wake when the cpu was clocked above stock speeds (even 900MHz).
Further evidence towards a sense problem is that I don't have any issues when I'm at 1.4GHz when using CM7. I missed the sense apps too much to stay with CM7, however.
I have a workaround using CPU Tuner with a screen off profile of 246-806 Mhz, and I can then overclock freely afterwards. I can live with this but if anyone has an idea why this might be happening then I'd appreciate a solution.
As I've been lurking on XDA for a while but this be my first post, thanks to all you incredible developers who have made it possible for me to customise my phone in these fantastic ways.
Set your screen brightness to something greater than 50%. It's not a fix but a very reasonable workaround .
Sent from my HTC Vision using Tapatalk
Wow that worked perfectly! Thanks!
Was that fix well-documented anywhere, out of curiosity? I'd searched these forums quite heavily and didn't see that anywhere. Makes me feel silly that it was such a simple fix - I'd been flashing ROMs all night to get the same bug
The screen off issue is thoroughly discussed in the Virtuous kernel thread. I forget the exact explanation, but its got something to do with the CPU stepping while the screen if off.
The common fix is a SetCPU/CPU Tuner screen off profile, as you seemed to have discovered. But adjusting the governor type in addition to minimum CPU clocking seems to be the common solution used. I think the interactive governor seems to work best to prevent screen wake issues.
http://forum.xda-developers.com/showthread.php?t=967153
Yeah, I read that thread fairly extensively but the solutions there didn't help. I can easily replicate the problem by setting my cpu with the performance governor to anything above stock speed (i.e. the cpu will be at one single speed the entire time, I think?). The over 50% brightness solution works very well (at the expense of more noticeable battery drain)!
Atomcracker said:
Wow that worked perfectly! Thanks!
Was that fix well-documented anywhere, out of curiosity? I'd searched these forums quite heavily and didn't see that anywhere. Makes me feel silly that it was such a simple fix - I'd been flashing ROMs all night to get the same bug
Click to expand...
Click to collapse
I had seen the workaround mentioned on the CyanogenMod forums yesterday: http://forum.cyanogenmod.com/topic/20943-screen-doesnt-always-turn-on-from-sleep/

Wake problems.

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.

Categories

Resources