Having response issues with power button. It works just have to hit it two three or four times to wake screen. Suggestions?
It's just slightly worn out from all the use, like any button would be. You could open up the phone and mess around with it. Or maybe try taking it back to verizon and seeing if they will give you a refurb.
try switching kernels, some kernels take longer to respond than others.
Thanks, I will try flashing another kernel. If that does not work I'm still under warranty and will get a refurb.
Sent from my ADR6300 using XDA App
Download CM7 and use any-key wake
Widget Locker also has this feature. I only hit the power button to reboot/power off my phone.
where in settings is any-key wake
Not sure if you are setting your cpu speeds or not....
Make sure you dont set your cpu too low. if you are using set cpu or something make sure its set to 388 ish when the screen is off. Ive seen alot of issue when you get down into the lower ranges. cpu uses alot less battery then the screen anyway.
Related
Hey there every one. When I am unlocking my phone I notice that it will flash the lock screen and then disappear and then immediately re appear. When you try to lock the phone sometimes it wont lock and the buttons will stay lit and will display the lock screen but the display wont sleep unless it times out.
This happens on all ROM's that I flash except CyanogenMod
I used both of the over clock methods but the results are the same.
Please Advise
macfan74318
macfan74318 said:
Hey there every one. When I am unlocking my phone I notice that it will flash the lock screen and then disappear and then immediately re appear. When you try to lock the phone sometimes it wont lock and the buttons will stay lit and will display the lock screen but the display wont sleep unless it times out.
This happens on all ROM's that I flash except CyanogenMod
I used both of the over clock methods but the results are the same.
Please Advise
macfan74318
Click to expand...
Click to collapse
Yeah, it sucks. Theres no real way around this but disabling the lock screen helps it from happening less frequently. But then you end up draining the battery & others by the screen coming on easily by trackpad, volume keys, and power button. Its a lose/lose situation really...
sino8r said:
Yeah, it sucks. Theres no real way around this but disabling the lock screen helps it from happening less frequently. But then you end up draining the battery & others by the screen coming on easily by trackpad, volume keys, and power button. Its a lose/lose situation really...
Click to expand...
Click to collapse
I bumped my minimum clock speed to 368 MHz, and I don't have this problem anymore. YMMV
seancneal said:
I bumped my minimum clock speed to 368 MHz, and I don't have this problem anymore. YMMV
Click to expand...
Click to collapse
Still happens to me when I try that. It occurs when you press the power button twice in succession.
Hi there,
anything new on this topic? I'm currently experiencing this annoying problem as described.
I've already tried to set the minimum clock to 368 Mhz but the bug still exists. Even setting CPU to standard clock (Max/Min @800) didn't solve the problem.
Is it possible that the reason is located already inside the overclocking kernel?
Greets
dktnecro
Generally if you're overclocking and you have lockscreen issues that are not present @ stock speeds, then it sounds to me like the overclock is too much and your system probably isn't stable.
Based on my experience overclocking computers, things can very well appear stable but if you do stress testing (8+ hours straight) things often crop up and show you that it is in fact not stable. This sounds like one of those things. And that's not good. Who knows what other corruption could occur during your use at that speed? I had the same lockscreen issues myself, and once I realized it was due to overclocking too much I ended up solving another issue I had where half of the calls I received were garbled to the person on the other end. No more lockscreen issues or garbled calls since backing off the o/c a bit.
If the issue doesn't happen at stock speeds then maybe it's just the kernel, and hopefully that isn't putting you at risk of any kind of corruption, either.
Keep in mind I really can't be 100% if overclocking will cause corruption on a phone, but based on a lot of time spend overclocking pc's I would have to guess that it can. I'm surprised that this isn't brought up more often on device forums.
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
Is anybody else having issues with their ET going to sleep and you have to pull the battery to get it come back up? I thought it might have been my setcpu settings. So I cleared them and uninstalled it. I tried the midnight rom and the starburst rom. I tried the stable and exp LosKernel. None of these got rid of this issue for me. Randomly through out the day I can try to wake the phone up to use it and nothing happens. After a minute or two I have to pull the battery. I am currently testing the stock kernel.
Thats weird, the only time that happened to me was when i had setcpu, and i tried putting "screen off" value to 200/200.
You should install setcpu again, and make screen off value 500/500, and if you dont have the issue, then try making the value 200/500, if you dont have the issue at this value, then leave it as is.
Sent from my SPH-D710 using xda premium
I agree it is weird and I am not sure why it is happening. If it stays okay with the stock kernel then I may wipe and try the viperrom.
Yep happened twice the other day... Im on stock rom with lost kernel..roooted i put setcpu to 200/1200 after waking my screen for a minute used google came back 3 min later and phone was either off or wouldnt wake .. I had to pull battery twice.
I setcpu up to 1200/1200 never happened again.
This is a nice phone but very touchy.. Seems alot weird things goin on for some Et users.
Worst of all for this phone is Los or just weak /radio signal in general ..which is a samsung issue.
Sent from my SPH-D710 using XDA Premium App
Why people still insist on screen off profiles amazes me. When you hit the power button to wake it - the phone is stuck at 200MHz, you do realize this? If snything else is going on while it's stuck at 200 or SetCPU doesn't sample the phones state fast enough, it never gets out of 200MHz and locks up. Just like any other processor does when you overload it.
All the background processes going on even when the screen is off and somebody thinks setting the CPU max to 200MHz is a good idea? That's just asking for it. Not to mention the screen off profile is known to cause this issue. Notice how Virtuous, Viper, Cyanogen, and many other developers don't use one in their native OC daemons? There's a reason why. The phone sleeps just fine without it, just let it do it's thing.
Don't use offscreen profiles (the kernel is smart enough) and avoid using task killers, as those are likely to be the second leading issue.
I am having the issue even with setcpu uninstalled. I still have not found out what is causing it.
ElAguila said:
I am having the issue even with setcpu uninstalled. I still have not found out what is causing it.
Click to expand...
Click to collapse
Just wanted to throw this out there: beware mislabeling this problem. The setcpu issue causing the phone the permanently lock up and require a bat pull is one issue, yes; slow screen wake up is a different issue. Sometimes if you hit the power button, the screen will not wake up on the first try. If you wait a few seconds and push in the button again for a second or so, the screen almost always will come after. Coming from a mo-pho, I actually had the stupid no-wake problem requiring bat pulls, so I'm extremely paranoid about by e4gt doing this -- but it really has been good about eventually waking up every single time...just try my instructions and see if it works for you, too.
Again, though -- setcpu issues may be a different problem entirely.
did you reinstall a rom and try it again or did you simply just unistall setcpu and try it. I say this because I had an issue when testing setcpu and my system still kept my cpu setting even after I unistalled the app. I had to reinstall the rom after wiping to get it to run properly again.
I think I have found the issue. I did a factory reset and installed the rom but I am getting an error now that is basically saying it can't read the internal storage card. So I think there are some actual hardware issues going on that need to be looked at by sprint.
how often has the sod been happening? I think i got it yesterday, but not sure.
Do you use setcpu?
Sent from my SPH-D710 using Tapatalk
This thread seems a little slow- has there been a solution found or are we isolated cases?
I reflashed the phone back to rooted stock and then flashed Blazer 4.1.
Got 2 SODs in the past week- one just a few minutes ago.
I tried calling the phone from another line, it rings but the screen is black and thus I couldn't answer it.
Power button and vol buttons work fine.
I had to powerdown and reboot.
Getting kinda frustating.
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.
So I searched around in this forum but I can't find an answer. My Note 2 (AT&T obv) takes almost a full second to wake after pressing the unlock button. It's been like this through 2 roms and was the same way on my stock rom. Literally I press the button and it takes a good 1/2 to a full second to wake up to the lock screen. Am I the only person having this issue? I tried removing my SD card and it slightly lowered the wake time but it's still significant. I went from my Inspire 4G to this and even with the perseus kernel and both on cleanROM and Jedix6 or whatever it's called the problem persists and the phone doesn't seem as snappy as my OC'd Inspire. I mean the inspire had little to no lag at all after pressing the button to see the lock screen but it seems odd to have to wait as long as I do on a newer, faster phone. Maybe I'm just being nit picky... Any ideas?
Bliznade said:
So I searched around in this forum but I can't find an answer. My Note 2 (AT&T obv) takes almost a full second to wake after pressing the unlock button. It's been like this through 2 roms and was the same way on my stock rom. Literally I press the button and it takes a good 1/2 to a full second to wake up to the lock screen. Am I the only person having this issue? I tried removing my SD card and it slightly lowered the wake time but it's still significant. I went from my Inspire 4G to this and even with the perseus kernel and both on cleanROM and Jedix6 or whatever it's called the problem persists and the phone doesn't seem as snappy as my OC'd Inspire. I mean the inspire had little to no lag at all after pressing the button to see the lock screen but it seems odd to have to wait as long as I do on a newer, faster phone. Maybe I'm just being nit picky... Any ideas?
Click to expand...
Click to collapse
Ive noticed it as well. Got used to it and it don't bother me anymore but a solution would be nice
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
http://forum.xda-developers.com/showthread.php?p=33492447
Sent from my SAMSUNG-SGH-I317 using xda premium
have you tried to increase your minimum deep sleep cpu frequency from 200mhz to maybe 350mhz or so?
a shot in the dark would be reducing the animation scale in developer settings but this is only if it's considered an animation when you turn on the phone
battery life is amazing on this phone and if you agree and want to try it. There is a app called soft locker on the market that will fix the delay. I dont notice that much of a drain on the battery even though I know it has to have some. Basically the CPU in samsung phones go into a very deep sleep and that helps battery but if you use the above app it creates wakelocks that keep it from deep sleep and fixes the issue.
This can make battery life less but like I said I have used it for over a month and still get over a day out of my phone and I usually have 4 hours or more screen on time and still end day with 25%-50% battery left.
http://forum.xda-developers.com/showpost.php?p=35617276&postcount=2096
Apen83 in the Jedi ROM thread says to do this:
"Settings > developer options > window animations off / transition off / animator duration off"
Looks like its working for them.
If it works for you, hit the link and thank his post.
This doesn't help as it's not an animation.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
It's a characteristic of Exynos processors. It sucks, but what can ya do?
I'm using asylum rom and kernel and see nowhere near the delay that stock had. It's almost instant on for me
Its probably the pegasusq governor, but that's what you have to go with to be able to hotplug CPU cores. This is the price you pay for battery life.
You did not search well enough. There is no solution, and nothing you can do about it other than the aforementioned Soft Locker, which will negatively impact your battery life.
More info here: http://forum.xda-developers.com/showthread.php?t=1983697&highlight=wake+lag
It sucks, but I guess it's a sacrifice I have to live with on an otherwise awesome device.