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.
Hi everyone,,
I hope I can tell my problem properly with my poor language!:crying:
my device got a problem in response of the power button, sometimes it does not work and I did use the volume buttons to wake up the screen instead of it!
then one time the device fall down from my hand and the battery pulled out so the phone turned off. I tried to switch it ON but no way because the button became totally not working
I tried every way to make it ON, I unscrewed the devise and I check that the button was not damaged and every thing looks fine.
I tried to use some ways that are mentioned in youtube like unplugging the battery several times and so on.. but still not working.
I took the phone to a service shop in my town and they made an electrical check for the button and it was working well electrically! but they could not doing more with the phone because they don't have spare parts for HTC devices!
after that I expected that this issue is a software problem, because I installed a custom rom recently!
finally I succeeded to make it ON using ADB commands and I changed the rom 2 times, but the power button still not working, then I changed the Kernel, and the problem remains :crying::crying::crying::crying:
so, do you advice me to try anything else?
Please heeeeeeeeelp
i have the same problem
i have the same problem here and i use cmd to reboot :'( but i have a big problem my mobiles keeps on shutting down alone and i restart it by adb but if i am out of home what can i do ? anyune help us
Instal script manager and write a script to do it.
And if you using custom rom write to the author mayby he will change a vendor key for you.
Sent from my HTC One X using xda premium
stona !!
i can't understand what are you writing ? i only need a solution for the shut down problem ?? it keeps on shutting down when i close airplane mode when it's on airplane mode nothng happens so give me a soution plzz what's the problem there ? please help
mo7ammed3adel said:
i can't understand what are you writing ? i only need a solution for the shut down problem ?? it keeps on shutting down when i close airplane mode when it's on airplane mode nothng happens so give me a soution plzz what's the problem there ? please help
Click to expand...
Click to collapse
I was written what you need to make you life easier if you have power button broken. If you have shutdown problem write to developer of rom you're using. Or change it.
Sent from my HTC One X using xda premium
Figured I see if anyone else has had this issue. I went for a walk with the dog yesterday, and was listening to music on my Nexus 6 the whole time, and when I got home I couldn't get the screen to turn on. Music was still playing, it was still connected to my G watch, and holding the power button triggered a vibrate when the power menu opens--but the screen was completely black and unlit the whole time.
Had no prior issues, just wondering if anyone else has had this issue. Figuring I'll probably call Motorola as this seems like a hardware issue...
Any suggestions would be well received!
Try holding the power and volume down buttons together and see if the screen will come on when it reboots to the boot loader. Alteratively you could try to power cycle it by holding the power button down for 30 seconds. Hopefully Motorola will also be able to help you.
me too
same exact thing happed to me music pulled out headphones the phone still works but the screen is dead. I can pull to use phone and **** and have the same vibration. holding power for 20 seconds is a no go. tried tons of holding combinations it seems like I can get it to shut off and on may be but it's just not doing a reset that I can tell that reboots the screen.
joshsunfresh said:
same exact thing happed to me music pulled out headphones the phone still works but the screen is dead. I can pull to use phone and **** and have the same vibration. holding power for 20 seconds is a no go. tried tons of holding combinations it seems like I can get it to shut off and on may be but it's just not doing a reset that I can tell that reboots the screen.
Click to expand...
Click to collapse
you had an sod(sleep of death). it sounds much worse than it actually is. its a rather common issue as well(no fix). try using a custom kernel.
ok crap
simms22 said:
you had an sod(sleep of death). it sounds much worse than it actually is. its a rather common issue as well(no fix). try using a custom kernel.
Click to expand...
Click to collapse
so stupid question how do I do that? I've only tried to root a phone once and it was a g1. please provide a link or something i'm pretty techy but am rather upset right now.
Ambient display fault?
Hey, I had the same issue, i switched off the ambient display and after that the problem is solved. Give it a try, it might help. Go to Settings, Display, and turn off the ambient display .
same problem
Whenever I turn the screen off and on again, at the bottom of the screen it prints "Volume: 100%" or whatever the notification volume is on. This also happens at other times, but I cannot see a pattern in them. It is fixed after a reboot, but after a while it starts again. It is extremely annoying. I tried using CatLog, and it seems every time the screen is turned on AudioService or VolumePanel do something like onVolumeChanged(). Luckily, the actual volume doesn't change. I am using GT-P7310 ICS 4.0.4 running OmarEinea's Ultra Plus Stock ROM. Can someone help?
Fixed
Fixed it! Battery Doctor was causing the problem (dunno why ). Uninstalled it, and IT WORKS! If anyone else has this problem, go through each of your apps and force close them, and see if the problem still persists.
I am curious if anyone else experiences this and what could be the cause. I have a rooted Pixel 4a 5g running stock Android 11. Once per week I have Titanium Backup run a backup and have it reboot when the backup is done (TiBu will stop some apps for the backup and then they won't function again until a reboot). Most times everything is fine but every once in a while when I try to enter my pin after reboot, the screen is unresponsive. I then have to force power it off/on. Usually this resolves the issue but every once in a while I struggle to get the phone powered back on. Holding the power button doesn't work. Holding power plus vol down, or power plus vol up doesn't work either. I then go into a mild panic, put the phone down for a bit then try the power/vol button combos again (I never remember the exact combo that works since I am mildly panicking) and it eventually powers on with working touchscreen.
I find this behavior weird, annoying, and not in the realm of normal operation. Any thoughts what could be causing this? I use the same apps that I have used on all my previous phones and have never experienced this. Is it an Android 11 issue? Would upgrading to A12 fix it?
Appreciate any feedback!
I have similar problem - go to a bookmarked website, no touch response, restart usually fixes it....super annoying