An issue I've had with a few roms I've used in the recent past. Currently on Mourta's Liquid Smooth rom (KK). Sorry if this question has been asked before, I wasn't able to find any info.
Sometimes after turning the screen off, if I try to turn in back on, it won't. Trying to unlock the screen makes the hardware button's backlight light up, for a few seconds like normal, but the screen never turns on till I hard reboot the phone. The rest of the phone doesn't seem to freeze up. For example, music doesn't chop up, I still receive calls, and holding the power button gives me the vibrate signal that the power menu has opened.
I've re flashed the rom a couple of times, but I still get this problem on some level. Even if I leave the phone undisturbed for a long time and come back to it, the screen won't turn on till I reboot. Not sure if this is true, but I think the problem also happens if I try to unlock the phone too quick after locking it. Thoughts?
Already know problem on some roms it is called Screen of death sometimes happends because of low screen cpu freq sometimes because rom just go nuts.
Sent from my Optimus 4X HD
dimi89 said:
Already know problem on some roms it is called Screen of death sometimes happends because of low screen cpu freq sometimes because rom just go nuts.
Sent from my Optimus 4X HD
Click to expand...
Click to collapse
I wanted to know if this particular problem had a name. Screen of death sounds apt. I wouldn't mind having to reboot a couple of times, but this problem has me rebooting well as much as 6 times a day
Lets call it Greg then. Flesh another rom and try it. Cm for example.
Sent from my Optimus 4X HD
dimi89 said:
Lets call it Greg then. Flesh another rom and try it. Cm for example.
Sent from my Optimus 4X HD
Click to expand...
Click to collapse
King lol'd hard
Related
recently my screen has stopped locking when i stop using the phone. if i press the power button, it will go black and will lock. if i use the phone (call, message, anything) and just put it down, the screen dims slightly but does not go black or lock, i just have to touch the screen and it brightens. i have tried setting the screen timeout for different lengths of time, but that didn't help. any ideas?
another example is when the alarm goes off in the morning, i will snooze and have to press the power button to get the screen to go black.
thanks!
oh, i'm running a stock captivate.
Are you using the app "No-LED"?
miztaken1312 said:
Are you using the app "No-LED"?
Click to expand...
Click to collapse
no, never heard of it.
real problem here is it's killing my battery. for the first time since i got the phone it died on me before the end of the day.
barthie said:
no, never heard of it.
real problem here is it's killing my battery. for the first time since i got the phone it died on me before the end of the day.
Click to expand...
Click to collapse
Well I'm not sure how technical you are, but you may want to reflash your phone.
I have an AT&T unlocked Nexus One that I recently flashed to CM-7.0.3-N1 . I have had a problem unlocking the device with the power button both when I was running stock Gingerbread and now that I have installed CM7.
When the screen is off and my N1 is in standby, I push the power button and the screen turns on and then back off almost immediately. Sometimes there is a half second delay before the screen turns on and then off. This usually goes on 2 or 3 times until the screen will stay on and I can unlock my phone.
Has anyone seen or heard of this problem, and maybe knows of a fix? It could be hardware related, but the button definitely sends a signal to the phone and it works fine to shutdown or turn on the device from completely off. Thanks.
ummm the power button on the nexus one has an incredibly high failure rate, all over the forum here. its a design defect from the factory. that's why it has always been recommended to root the device immediately, and use trackball wake, so you avoid using the power button as much as possible. you have to send the device to HTC for repair, that's your only option...
Thanks for the information. I will have to look into repairs.
You are already running a rooted rom with track all wake. Use it. To reboot the the phone use quickboot. At this stage you really don't need the power button on your phone.
pcflet01 said:
... now that I have installed CM7.
I push the power button and the screen turns on and then back off almost immediate
Click to expand...
Click to collapse
This is a problem with CM7. Most advise turning off the screen off animation if it becomes a big problem for you. Make sure you are using the newest nightly and hope for a fix. I don't know if the RC's have this problem, but I would bet it appears on the 7.0.3 release.
At first glance that seems to have helped. Thanks for the advice!
No problem.
Also you can use widget locker to lock the screen then the trackball to wake, with that and quickboot I don't even touch my power button anymore. Although your problem doesn't sound like a broken power button so in your position I would switch ROMs and see what happens.
pcflet01 said:
I have an AT&T unlocked Nexus One that I recently flashed to CM-7.0.3-N1 . I have had a problem unlocking the device with the power button both when I was running stock Gingerbread and now that I have installed CM7.
When the screen is off and my N1 is in standby, I push the power button and the screen turns on and then back off almost immediately. Sometimes there is a half second delay before the screen turns on and then off. This usually goes on 2 or 3 times until the screen will stay on and I can unlock my phone.
Has anyone seen or heard of this problem, and maybe knows of a fix? It could be hardware related, but the button definitely sends a signal to the phone and it works fine to shutdown or turn on the device from completely off. Thanks.
Click to expand...
Click to collapse
I'm experiencing exactly this too on the latest RC. It doesn't seem to be complete button failure but it's acting like I've pressed it twice sometimes. Disabling the screen-on animation does seem to prevent it from popping back on. But it still sometimes goes on-then-off when I wake it with the power button. So now I'm using trackball wake too.
As others have mentioned, this does not sound like a powerbutton issue, because the powerbutton still turns on the screen. The problem is that the screen turns off immediately after it turns on.
When you flashed 7.0.3, did you come from a previous CM verison? From stock? My first suggestion would probably be to wipe the /system partition (in CWM, it is under mounts and storage -- with Amon_RA, you need to find a flashable zip to do it) and reinstall CM and gapps. This will not cause any data loss. Sometimes, if you install a new ROM over an old one, the upgrade script in CM can get confused and carry over files that aren't supposed to be carried over. The system wipe fixes that.
I've been using this RC since it came out in late June. Only this week did it start flipping out on me.
Sent from my Nook Color!
It still can't hurt anything to do a system wipe, just in case something got screwed up (these things can be so temperamental at times). And, like I said, you won't lose any of your data.
bassmadrigal said:
It still can't hurt anything to do a system wipe, just in case something got screwed up (these things can be so temperamental at times). And, like I said, you won't lose any of your data.
Click to expand...
Click to collapse
I'm currently using S2E for apps2ext and some data2ext. How would a system wipe and reinstall interact with that? I'm a bit nervous on that front.
A system wipe shouldn't change any of that. It is one benefit of using S2E as it is a standard app that is stored in the /data partition without any changes to the /system partition.
Anyway, to be safe, it is a good idea to do a nandroid backup anytime you are doing something that involves the majority of the features in recovery.
It's a hardware problem for me. Failed completely as of today.
Sent from my Nexus One using Tapatalk
CM7 7.1.0
My power button seems to be in the process of completely failing. The new CM7 update to 7.1.0 has made it possible for me to lock the screen without using the power button using the "Notification power widget" -> "Go to sleep". Now the only times I have to use the power button are to shut the phone down or wake it up, which seems to be easier when the phone is plugged in to a wall charger. Are there any simple apps for shutting the phone down and maybe waking it up at a set time?
The only reliable trick I found to turn it back on was to plug into the wall and take the battery out/in a few times till it vibrated.
I ended up getting a replacement phone and then I sent the Nexus to HTC. They quoted a $55 repair cost off warranty which my credit card insurance would've covered, but when I asked for an invoice they offered to just waive the charges. Finally over a month later it came back fixed.
The app Easy Reboot can shut the phone down.
Sent from my Nook Color!
I also use an app called Lock Screen, which just locks the screen. I have it stored in my dock, because I don't like the space being used in the notification widget.
CM7 has an option for one of the items in the notification tray widget to be a lock screen button.
cmstlist said:
I'm experiencing exactly this too on the latest RC. It doesn't seem to be complete button failure but it's acting like I've pressed it twice sometimes. Disabling the screen-on animation does seem to prevent it from popping back on. But it still sometimes goes on-then-off when I wake it with the power button. So now I'm using trackball wake too.
Click to expand...
Click to collapse
THANK YOU!!!! This has been driving me crazy. Turning off the screen-off animations did nothing, but turning off the screen-on animation seems to have fixed the issue. My power button is toast (my new power button ribbon cable just arrived... time for surgery), and I've been using the trackball to wake my phone. Before the power button died, it did the same thing. I'm using CM7.2. I installed it after rooting and went straight to cm7.2 from stock, so obviously the cyanogemnod crew haven't fixed the issue since 7.0.3 when this thread started.
Hello, this is my first post and first problem. I have a htc one on viper rom and when I end a call the screen is blank and the phone is locked but I cannot get the screen to turn on to unlock the phone. If I try to reboot or boot into recovery then the flash light turns on and off but it never reboots (after like 5 mins). I can still hear notifications and rings and the led and buttons light up for notifications but the screen will not turn on. Since I cannot reboot I have to wait for my battery to completely die and ten reboot the phone and it works. Someone please help I can't have my phone being out of commision several hours a day because of this and I really like viper rom over the others I have tried. Thanks.
So this happens often?
At least once a day depending on how much battery I have the first time it happens and how long it takes my battery to discharge. I just changed to the stock Android kernel. Maybe this will make a difference.
rblott30 said:
Hello, this is my first post and first problem. I have a htc one on viper rom and when I end a call the screen is blank and the phone is locked but I cannot get the screen to turn on to unlock the phone. If I try to reboot or boot into recovery then the flash light turns on and off but it never reboots (after like 5 mins). I can still hear notifications and rings and the led and buttons light up for notifications but the screen will not turn on. Since I cannot reboot I have to wait for my battery to completely die and ten reboot the phone and it works. Someone please help I can't have my phone being out of commision several hours a day because of this and I really like viper rom over the others I have tried. Thanks.
Click to expand...
Click to collapse
Well, can you try to flash another rom and test if the issue persists?
Sounds like a hardware issue imo...if its a rom related issue, there should me more complaints in our thread. You are the first one mention this.
rblott30 said:
Hello, this is my first post and first problem. I have a htc one on viper rom and when I end a call the screen is blank and the phone is locked but I cannot get the screen to turn on to unlock the phone. If I try to reboot or boot into recovery then the flash light turns on and off but it never reboots (after like 5 mins). I can still hear notifications and rings and the led and buttons light up for notifications but the screen will not turn on. Since I cannot reboot I have to wait for my battery to completely die and ten reboot the phone and it works. Someone please help I can't have my phone being out of commision several hours a day because of this and I really like viper rom over the others I have tried. Thanks.
Click to expand...
Click to collapse
I have the same bug.
I'm not sure,but it happens sometimes when after a call ending I press the power button before or right after the screen wakes up.
There should be something with the light and/or with the proximity sensor, because reseting the device is only performable at high lights.
Sent from my HTC One using xda premium
Fixed.......
I finally fixed the bug on mine. It must have had something to do with the Venom Red Theme 2. After using a recovery to before I installed the theme it didn't happen again and I also flashed the theme again using TWRP and wiped davlink, etc.... After doing so I have the theme working and haven't had the bug since the day following my first post. Think I may have went to the theme in venom hub and hit install and not realized it. At least that's my opinion but I still don't know why it would cause that sort of response from my phone. Try this if you haven't. Good luck...
feenty said:
I have the same bug.
I'm not sure,but it happens sometimes when after a call ending I press the power button before or right after the screen wakes up.
There should be something with the light and/or with the proximity sensor, because reseting the device is only performable at high lights.
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Hey guys, im having a bit of a problem. My phone is shuting off on itself.
Everytime i turn it on, it boots up no problem, but when i hit the power button to turn the screen off, when i want to turn the screen on again by pressing the power button, the screen just goes deep blue, and turns off.
I haven't change anything on it for quite a few months now, so i'm not sure why this is happening. Im on Viper 3.5 i think or 3.7, using faux123 kernel, dont remember which version, but an old one with which i never had any troubles... rooted, s-on
Any ideas?
Thanks!
Coldsun15
PD: Logcat in the .rar file...was too big for .txt
Really?? No one??
Well, just for further info... my phone appeared to fix itself, since it stopped doing that weird thing for a couple of days, but now is back... nothing ever changed, no new apps, or settings or anything...
Any ideas welcome
Edit: Attaching new logcats...
coldsun15 said:
Well, just for further info... my phone appeared to fix itself, since it stopped doing that weird thing for a couple of days, but now is back... nothing ever changed, no new apps, or settings or anything...
Click to expand...
Click to collapse
I think your power button is broken (or you may have a related hardware issue). Nothing but a root app can reboot the phone, and I've never seen that happen by accident.
fenstre said:
I think your power button is broken (or you may have a related hardware issue). Nothing but a root app can reboot the phone, and I've never seen that happen by accident.
Click to expand...
Click to collapse
Yeah, i thought about it being hardware but something is off... i mean, if it where the power button, then i shouldnt be able to turn it on easily, or it wouldnt turn off the screen properly, nor would it just start working alright for a couple of days... plus, it didnt recieve any hits or anything during, before or after the problem.
I also thought it could be the screen, but when its on, it works perfectly, as on the first day...
But yeah, I'm not taking hardware problem out of the table...just seems unlikely to me...
Thanks for your answer!
Coldsun15
Edit: also, I just found out it doesnt actually restart...screen just turns dark blue, then it powers the screen off and it wont turn on when pressing power... but i know its on, because i can still hear notification sounds of incoming messages...
Edit2: Just tried same but instead of using power button, i used logo2sleep and home2wake kernel options, and did the on/off with them, and same result...dark blue screen then off and not turning on... so it cant be power button
When going to bed tonight do these steps.
1. Put your phones brightness display on the lowest setting
2. Plug your phone in for an overnight charge, do not "turn off" your phone.
3. Wake up in the morning
4. Click the power button on your HTC ONE M7
Did the screen turn on? Are the Soft Keys the only part that lights up?
I've been able to replicate this problem over and over on 3-4 different HTC ONE M7's. For some reason the phone's display will not turn on in the morning. The only way to get it to is to either hold down the power button for a few seconds and the restart screen will pop-up which activates the screen again. Or, to do a complete restart.
Eventually the screen starts working again like normal after fiddling with it for 15-20 minutes...
I believe this is either a KitKat problem or light sensor problem or both. I do know this issue was never around before the KitKat upgrade months back.
Soul TKR said:
When going to bed tonight do these steps.
1. Put your phones brightness display on the lowest setting
2. Plug your phone in for an overnight charge, do not "turn off" your phone.
3. Wake up in the morning
4. Click the power button on your HTC ONE M7
Did the screen turn on? Are the Soft Keys the only part that lights up?
I've been able to replicate this problem over and over on 3-4 different HTC ONE M7's. For some reason the phone's display will not turn on in the morning. The only way to get it to is to either hold down the power button for a few seconds and the restart screen will pop-up which activates the screen again. Or, to do a complete restart.
Eventually the screen starts working again like normal after fiddling with it for 15-20 minutes...
I believe this is either a KitKat problem or light sensor problem or both. I do know this issue was never around before the KitKat upgrade months back.
Click to expand...
Click to collapse
I#ve never run across that problem but I know when I enable "ScreenOn" the screen stays on all night and if I just let my phone sit with screen on (because I fell asleep texting ) the screen will be off in the morning.
Soul TKR said:
When going to bed tonight do these steps.
1. Put your phones brightness display on the lowest setting
2. Plug your phone in for an overnight charge, do not "turn off" your phone.
3. Wake up in the morning
4. Click the power button on your HTC ONE M7
Did the screen turn on? Are the Soft Keys the only part that lights up?
I've been able to replicate this problem over and over on 3-4 different HTC ONE M7's. For some reason the phone's display will not turn on in the morning. The only way to get it to is to either hold down the power button for a few seconds and the restart screen will pop-up which activates the screen again. Or, to do a complete restart.
Eventually the screen starts working again like normal after fiddling with it for 15-20 minutes...
I believe this is either a KitKat problem or light sensor problem or both. I do know this issue was never around before the KitKat upgrade months back.
Click to expand...
Click to collapse
I can try it out. I'll report in the morning. ?
Sent from my HTC_0P6B using Tapatalk
Anyone?
Nobody?
Sent from my HTC6500LVW using Tapatalk
Beullar.... Beullar?
with my phone its just a 5 second lag sometimes, and i click the power button again to make sure i clicked it and it instead locks itself back. The third click however, everything works fine.
this has been happening to me for the longest its very irritating, i notice it happens whenever i fall asleep, a nap during the day or when i wake up in the morning its really annoying
Well glad to see I'm not the only one.
I have provided this thread link to HTC and reported the problem. Requested that they chime in if they have any questions.
i had that issue
Soul TKR said:
I have provided this thread link to HTC and reported the problem. Requested that they chime in if they have any questions.
Click to expand...
Click to collapse
Yes I had the same issue as the original post.Long story short I ended up sending the device back. The new one didn't suffer from this problem. This was back in October of 2013.
Same issues, it's probably light sensor:
http://forum.xda-developers.com/showpost.php?p=49918380&postcount=9
nitephlight said:
Same issues, it's probably light sensor:
http://forum.xda-developers.com/showpost.php?p=49918380&postcount=9
Click to expand...
Click to collapse
Nope. I already tried the light sensor calibration trick. It didn't work unfortunately. I ended up swapping out 4-5 HTC ONE's before it worked correctly.
yup, I tried the trick as well a few more times and could not wake the screen either. generally I'm tolerant of stuff like this because I assume it is the byproduct of repeated flashing and combo of mods.. but I I recall this happening quite early on in ownership and now it's back. (was AOSP now Sense base). sigh