Long story short... Any ROM + kernel combo I try, when I press the power button to turn the screen on, there's at least a 5 second delay when pressing the power button to when the screen actually turns on.. It's very annoying
Does anyone else experience this problem? Any fix (really hope so)
Thanks in advance
Sent from my Nexus 4 + 7
qaz2453 said:
Long story short... Any ROM + kernel combo I try, when I press the power button to turn the screen on, there's at least a 5 second delay when pressing the power button to when the screen actually turns on.. It's very annoying
Does anyone else experience this problem? Any fix (really hope so)
Thanks in advance
Sent from my Nexus 4 + 7
Click to expand...
Click to collapse
I experience this issue also, except that I am on stock kit kat, and it has only been an issue since that upgrade. Overall, kit kat seems to be a step backwards for me :-/
That happens a lot on my daughter's N7 ... but rarely on mine. Both are 2012 models hers is 16gb, mine is 32gb -> both on kitkat.
WHAT I've noticed is that it only happens when the orientation is different from when I turned it off & am trying to turn it on. Example: I turn off in portrait mode, set it down, walk away, pick it up in Landscape and press the power button...delay turning on. If I turn it back to portrait, turns on without delay.
That's all I've got. It's reproduce-able on both tablets.
QUOTE=qaz2453;50840249]Long story short... Any ROM + kernel combo I try, when I press the power button to turn the screen on, there's at least a 5 second delay when pressing the power button to when the screen actually turns on.. It's very annoying
Does anyone else experience this problem? Any fix (really hope so)
Thanks in advance
Sent from my Nexus 4 + 7[/QUOTE]
i get this when I use Franco Kernel because the minimum cpu frequency is too low, and it presumably just doesn't want to wake up
m-kernel no problems, where the min freq is set to at least 2000
lolcopter said:
i get this when I use Franco Kernel because the minimum cpu frequency is too low, and it presumably just doesn't want to wake up
m-kernel no problems, where the min freq is set to at least 2000
Click to expand...
Click to collapse
thanks mate, flashing m kernel has fixed my problem (had franco kernel before)
Have you tried just saying "OK nexus" to wake it?
Sent from my N5 cell phone telephone....
Related
hi guys,
i tried CM7 (also latest nightlys) and it seems to be a problem with the option "wakeup phone by volume buttons" .
Sometimes the phone won´t wake up if i hit the volume buttons. 10 times i press the volume button it won´t wake up, then i press again and then it works. i think that is a bug :-(
have you similar problems and is there a fix ?
thanks
Same problem here.
Sent from my Optimus 2X using xda premium
Bump.
Having this problem with the latest temasek kang p204-20. Baseband used is stock 725 and the kernel is .49 [email protected] #1
mine is not working either.
temasek 204-18
It works only for about 5 seconds after phone goes to sleep but beyond that it no longer works.
Yes, same me, Can anyone why's not? I hope to use volume to unlock screen without power button!
bump
still having problems with CM7 temasek KANG 204-37 and vadonka's powersave 32mb kernel.
its because the phone won't respond to these buttons during deep sleep, like when your screen has been off for 5+ seconds... the only way around it is to set your lowest cpu clock to around 500mhz or more with screen off settings using a cpu managing app... but your battery life will suffer from it... badly... your choice... and roms like cm7 automatically set the lowest available clock setting when the screen is off by default... hope this helps...
kemmo123 said:
its because the phone won't respond to these buttons during deep sleep, like when your screen has been off for 5+ seconds... the only way around it is to set your lowest cpu clock to around 500mhz or more with screen off settings using a cpu managing app... but your battery life will suffer from it... badly... your choice... and roms like cm7 automatically set the lowest available clock setting when the screen is off by default... hope this helps...
Click to expand...
Click to collapse
i see.
but can't the developers simulate the power button function while the screen is of with one of the volume buttons ? just to be clear, i assume the power button has some sort of priority/command that wakes the phone.. so it's just a problem to simulate or assign that priority to one of the volume buttons..
I also have the same problem
Please don't tell me that if ONE single button on my phone gets damaged (the power button) it will render the phone completely useless...
Info from another thread: volume button unlock works if you install this:
http://forum.xda-developers.com/showthread.php?t=1507681
select the first option (PARTIAL_WAKE_LOCK) and aquire the lock.
I've been using that only for a few hours so I cannot say how badly this effects the battery.
The other thread about this is here: http://forum.xda-developers.com/showthread.php?t=1505368
Ok, so I have 2 issues with power on and shut down:
1)When my phone was stock with 2.1 Eclair, the power on animation (the "S" forming) was much smoother and synced with the sound. Now, when I flashed to 2.2 Froyo and 2.3.6 Gingerbread, it goes at like 2 FPS and it's way offsync with the sound.
2)Also, the shutdown has a big delay, I mean: it shuts down, but then the BACK and MENU button leds remain lighted and it takes 7 to 13 seconds for them to shut off, and when they shut off the phone vibrates.
How can I solve these 2 problems?
Dont look at the screen whilst turning on and off.
dale24 said:
Dont look at the screen whilst turning on and off.
Click to expand...
Click to collapse
Useful as a pack of emus.
Hey Team!
I've been rooting and tinkering with android phones since the HTC Dream days. Normally, most troubleshoots I can overcome on my own fairly routinely over the years. I kind of feel like I've met my match on this one and I could REALLY use you guys' help!
Here's the story:
So my phone, of course, is the T-Mobile HTC One. What I've done so far? Unlocked the Bootloader. Added a CWM custom recovery. Currently using a 1.29....16 OTA clone deodexed Rom created by Team Nocturnal. I'm using a Faux123 Kernel and have it overclocked to 1.9 GHz with all of his suggested UV settings and Intellidemand Governor chosen. I have the Xposed Framwork installed as well. I've had all of this running smoothly together for weeks with not one random reboot or lockup. The phone has literally been flawless. Until this.....
So, i'm listening to music with headphones plugged in for my Spotify app and relaxing. About 10 minutes into the music session, the music stops. I look down and the app seems frozen. I pick up the phone and turn the screen on. As I swipe the screen to unlock, the phone freezes. I turn the screen off by pressing the power button. From this point on, the screen will not turn back on at all!!
What I've tried:
1) The usual hard reset via power button and volume down. Even power button by itself. The capacitive buttons just keep blinking, but the device never reboots at all.
2) I've tried plugging the device to a computer. The usb connection responds because the computer makes a sound. When I look at the device manager, it does show that it detects the M7 device to be connected. However, when trying to use any ADB commands, it simply states the device is not found (running Windows 8, btw).
3) Freaked out for about 10 minutes before regaining my composure and thinking of one last thing. Only thing I can think left to do is pull the battery. Of course this isn't possible with the HTC One, so my only comparative option would be to let the battery drain completely. The irony is that I boast so much about my phone's battery life, so I know that I'll be waiting 2-3 days for this to happen before I can hope for resolution after.
I've tried to be as specific as possible here guys. I'm far from an expert, but I've owned 4 or 5 android phones since 2008 and have never bricked one. If anyone knows anyway to bring my phone back from this RANDOM sleep of death, please let me know so.
Forever Grateful!
Find a bright light. Hold phone under this light and hold power button down again. Phone lights will blink and the phone will shut off.
gunnyman said:
Find a bright light. Hold phone under this light and hold power button down again. Phone lights will blink and the phone will shut off.
Click to expand...
Click to collapse
I've just been mindf**ked... It WORKED! What kind of crazy HTC Easter Egg is that??? And thank you so much by the way! You have no idea! I use my phone to promote my photography and film to my followers, and I was pretty heart broken lol
Also, what do you think couldv'e caused such a random deep sleep?
Could be the over clock. No need to oc a phone this fast IMHO. The bright light thing is a safeguard against accidentally powering off while in a purse or pocket.
gunnyman said:
Find a bright light. Hold phone under this light and hold power button down again. Phone lights will blink and the phone will shut off.
Click to expand...
Click to collapse
gunnyman said:
Could be the over clock. No need to oc a phone this fast IMHO. The bright light thing is a safeguard against accidentally powering off while in a purse or pocket.
Click to expand...
Click to collapse
I agree completely. Phone doesn't need to be OC'd. I was just being indulgent I guess lol. That's the first thing I changed when booting it back up. And ya, that's a pretty cool trick sir. This is why I love my XDA Fam! Android FTW!
Also I'd turn off mpdecision in faux control app. It doesn't play nice with faux intelliplug
gunnyman said:
Also I'd turn off mpdecision in faux control app. It doesn't play nice with faux intelliplug
Click to expand...
Click to collapse
Yep. That was already turned off based from his recommendations. Only thing I really did was change the OC levels back down to stock.
Sent from my M7 using xda app-developers app
gunnyman said:
Find a bright light. Hold phone under this light and hold power button down again. Phone lights will blink and the phone will shut off.
Click to expand...
Click to collapse
Did the trick. Thank you so much.
Sent with a phone in my hand.
Wondering if anyone else is having this problem, when I click on the home button to wake the phone it takes 4-6 seconds before it takes me to the lock screen. Any thing I can do to fix this?
Thanks
BNish17 said:
Wondering if anyone else is having this problem, when I click on the home button to wake the phone it takes 4-6 seconds before it takes me to the lock screen. Any thing I can do to fix this?
Thanks
Click to expand...
Click to collapse
Just a thought, you might want to check apps like my magazine and S voice settings. They both have options to open via double pressing the home button. If these are enabled the home button may delay to see if a second press is coming. (Although 4-6 seconds seems excessive) I disabled that option in those app settings and have no delay when waking using the home button.
Sent from my SAMSUNG-SM-N900A using Tapatalk
What if the s voice settings weren't the problem with home botton before the KitKat update ?
BNish17 said:
Wondering if anyone else is having this problem, when I click on the home button to wake the phone it takes 4-6 seconds before it takes me to the lock screen. Any thing I can do to fix this?
Thanks
Click to expand...
Click to collapse
Removed your sdcard and test, if you dont have one nevermind
Does this always take a long time? As in if you have device on and press power button to turn off. Then immediately press the home button. Does it take a long time?
Maybe your device is in a really deep sleep and it needs to wake up. If it is in a deep sleep, that's a good thing. If we had a better kernel we could control the situation better. Unfortunately we can't get one at the moment.
Once a day, and sometimes once every other day the screen will naturally go to sleep after a minute or whatever I have it set to, and then wont come back on. I know its just the screen because I can click volume buttons and hear the volume adjustment beep, and when I click the power button I can see the soft keys light up at the bottom of the phone, and then darken again when I click the power again.
The only fix I have found is to hold (POW + VOL UP + VOL DWN) until the phone force shuts down.
I have an AT&T M7 running the latest CM11 nightly.
Wing_Zero_Custom said:
Once a day, and sometimes once every other day the screen will naturally go to sleep after a minute or whatever I have it set to, and then wont come back on. I know its just the screen because I can click volume buttons and hear the volume adjustment beep, and when I click the power button I can see the soft keys light up at the bottom of the phone, and then darken again when I click the power again.
The only fix I have found is to hold (POW + VOL UP + VOL DWN) until the phone force shuts down.
I have an AT&T M7 running the latest CM11 nightly.
Click to expand...
Click to collapse
Test it on another ROM and if the issue occures there too, it's likely a Hardware issue. Then you have to live with it or send it in to the warranty service.
But since it's a CM11 nightly it is likely a ROM related issue, so wait for an update or just change to the stable version.