Related
i noticed recently that if i press the power button, it sometimes takes a really long time to turn the screen on. i know the hardware works because the backlight in the soft buttons turns on immediately, but the screen remains black for up to 10 seconds. this happens rarely. however, im fairly sure it isnt a software problem because ive wiped completely and installed a fresh rom and the problem seems to persist. perhaps i just recently noticed, and the problem was always there? does anyone else have this problem?
three threads above yours.
http://forum.xda-developers.com/showthread.php?t=681723
could be a hardware issue.
Mine does this every few days.. I am still on the stock 2.1 rom.
Mine also does this, I only noticed it after flashing Cyanogenmod 5.0.6. so I thought it might have been a bug. I also assumed it was a bug because the phone seems to act strangely when you are touching the screen and try to hit the power button.
Hopefully this isn't a hardware issue, I've had the phone since release.
Is anyone else experiencing similar issues?
It happens to me as well, but very infrequently. Maybe every few days... so it doesn't bother me enough to worry about it.
I'm on stock ROM btw.
I am leaning towards thinking this may be software related. A few minutes ago I was at the lock screen and tried about 50 times (yes I waited long enough after each press) and simply could not get the screen to turn off. I then tried long pressing the power button and, sure enough, each time it would bring up the shutdown menu (yes, over the lock screen). Must be a bug right?
Hmm, my problem's slightly different. Around half of the time, I have to press the power button twice to turn the screen on. Sometimes, pressing it the first time doesn't turn the screen on, had to press the power button firmly again.
This started only recently. On stock n1 and bought it during feb.
that means that your power button is dying, like many others' (including mine)
this is the first time, it takes 2 clicks to work....than it will increase.
Expect a repair soon...
Well i am having the issue other way around. i am not been able to put my phone in stand by mode by clicking on it and it is do a hard press then i get options to shut off the phone
any suggestions what might be causing it ?
I'm happy I haven't received this problem yet
-------------------------------------
i want my yogurt lol froyo time
negroplasty said:
Mine also does this, I only noticed it after flashing Cyanogenmod 5.0.6. so I thought it might have been a bug. I also assumed it was a bug because the phone seems to act strangely when you are touching the screen and try to hit the power button.
Hopefully this isn't a hardware issue, I've had the phone since release.
Is anyone else experiencing similar issues?
Click to expand...
Click to collapse
I am having the same issue and i wonder if you were able to find the cause for it. I have the same rom as you do on your phone
negroplasty said:
I am leaning towards thinking this may be software related. A few minutes ago I was at the lock screen and tried about 50 times (yes I waited long enough after each press) and simply could not get the screen to turn off. I then tried long pressing the power button and, sure enough, each time it would bring up the shutdown menu (yes, over the lock screen). Must be a bug right?
Click to expand...
Click to collapse
I have a similar problem. When I unplug the N1 from the charger, the screen comes on showing the lock screen, and I can't get it to turn off. If I unlock the phone, however, then the power button works normally. I don't think it was doing this until recently (I bought it in January the first day it was offered and am running the stock update1 ROM).
So here is my theory if the power button is a problem then it needs to act up both ways and not only one way. right now i can put the phone in sleep mode but i can wake it up. i will post the issues on the development forum and might be able to find an asnswer to it
So seems like the issues is because of Cyanogenmod 5.0.6 because since i have flashed another rom it is working just fine. i will be doing some more testing before i can be certain
Another problem I am experiencing is when I long press the power button, it pulls up the phone options menu but also turns off the screen. It's extremely frustrating as it does this quite frequently; right after I power on the screen again and unlock the device it works properly every time - so much so that I am convinced this is a software issue.
I am now running froyo, rooted with Cyan's minor root patch. I can also say for sure I experienced the same problem on CM 5.0.6, but it definitely occurred less frequently.
Am I alone here?
di2356 said:
i noticed recently that if i press the power button, it sometimes takes a really long time to turn the screen on. i know the hardware works because the backlight in the soft buttons turns on immediately, but the screen remains black for up to 10 seconds. this happens rarely. however, im fairly sure it isnt a software problem because ive wiped completely and installed a fresh rom and the problem seems to persist. perhaps i just recently noticed, and the problem was always there? does anyone else have this problem?
Click to expand...
Click to collapse
I just started having this problem after upgrading to 2.2.
I have this every so often. But sometimes wonder if it is flyscreen doing it
You guys should all just be running the app no lock to take the power autumn out of the equation.
Ahhhhh! I just need trackball wakeup!
I have a similar issue where my screen will turn on but will be unresponsive. When i turn it on and off, the backlight jut comes and goes. If it times out it won't turn back on for a bit(the backlight will come on still).
I just wiped my phone, hoping that'll fix it since it only started happening on a regular basis since I updated to Froyo
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.
Left my phone plugged in over night like a I always do. Woke up today and tried to turn the screen on but there was nothing. It wouldn't come on. Pressed the power button over and over but nothing. Tried a three finger reboot. Felt it vibrate signalling it rebooted. Still no screen.
Removed my bumper case to make sure I was pressing the button all the way down. Was able to get the little vibrate signal that the power menu prompt popped up but still no screen. Held the power button for 30 seconds. Still nothing.
Finally held down power button + volume up and the device rebooted and the boot animation came up. Screen works fine again.
So I guess the point of this post is to let people know my sets in case the encounter this problem. Hopefully it works for you as well and you don't have to send your device back.
efan3719 said:
Left my phone plugged in over night like a I always do. Woke up today and tried to turn the screen on but there was nothing. It wouldn't come on. Pressed the power button over and over but nothing. Tried a three finger reboot. Felt it vibrate signalling it rebooted. Still no screen.
Removed my bumper case to make sure I was pressing the button all the way down. Was able to get the little vibrate signal that the power menu prompt popped up but still no screen. Held the power button for 30 seconds. Still nothing.
Finally held down power button + volume up and the device rebooted and the boot animation came up. Screen works fine again.
So I guess the point of this post is to let people know my sets in case the encounter this problem. Hopefully it works for you as well and you don't have to send your device back.
Click to expand...
Click to collapse
I had a similar situation where I was toggling my nexus 4s brightness settings and when you have it at the darkest setting it is pitch black. Like there's no light on at all. I just had to hit the spot that I did before and bring the light settings back up. So maybe you can boot it up unlock it on the blank screen and two finger pull down and try pressing the light toggle?
apollohay said:
I had a similar situation where I was toggling my nexus 4s brightness settings and when you have it at the darkest setting it is pitch black. Like there's no light on at all. I just had to hit the spot that I did before and bring the light settings back up. So maybe you can boot it up unlock it on the blank screen and two finger pull down and try pressing the light toggle?
Click to expand...
Click to collapse
it was at ten percent brightness and the screen was completely unresponsive as far as i could tell. doing the power + volume up press made it reboot and return to normal.
efan3719 said:
Left my phone plugged in over night like a I always do. Woke up today and tried to turn the screen on but there was nothing. It wouldn't come on. Pressed the power button over and over but nothing. Tried a three finger reboot. Felt it vibrate signalling it rebooted. Still no screen.
Removed my bumper case to make sure I was pressing the button all the way down. Was able to get the little vibrate signal that the power menu prompt popped up but still no screen. Held the power button for 30 seconds. Still nothing.
Finally held down power button + volume up and the device rebooted and the boot animation came up. Screen works fine again.
So I guess the point of this post is to let people know my sets in case the encounter this problem. Hopefully it works for you as well and you don't have to send your device back.
Click to expand...
Click to collapse
Mine did that once too. Exact same thing happened. I was starting to get the feeling in my stomach where my phone had just died and then I hit a random set of buttons and saw the Google logo appear. Must be a software bug.
kingwaffle said:
Mine did that once too. Exact same thing happened. I was starting to get the feeling in my stomach where my phone had just died and then I hit a random set of buttons and saw the Google logo appear. Must be a software bug.
Click to expand...
Click to collapse
exactly the same here. felt like i had dropped a baby on it's head haha. i wish i knew a way to figure out what caused it.
My wife and I have been having the same issue, and I'm surprised that there's not more reports of this behavior The worst part is that I use my phone as an alarm, and the alarm won't go off if this happens in the night.
It has happened to me 3 times now, and 2 times in one day for my wife. Holding down the power button for ~20 seconds will cause the reboot, which is the good news. This morning after holding down the power button I noticed the notification light flashing red.
The phone appears to be still on, because if it happens overnight I will still see the white notification light flashing even though the screen won't turn on.
I had this problem on faux123 kernel on the second day after I got my Nexus 4.
Doesn't encounter it on franco.Kernel...
Sleep of death brozillas! Happens to all android phones. Happened to all my phones listed in my signature. You can reboot the device and you should be good. For the dude that's missing his alarm you should do a factory reset if you are stock or if you have root do not set your min cpu values to less than 3xx MHz.
Sent from my Nexus 4 using xda app-developers app
Same thing happened to me on my N4. Did a hard reboot and it came back on. Has happened at least twice since then, usually after being plugged in.
Sent from my Nexus 10 using XDA Premium HD app
Change chargers, cables. Make sure the charger is 5v 1.2a. Factory reset to stock.
If all that fails, RMA if you can.
Sent from my Nexus 4 using xda
I observed the same issue (going to standby, then cannot switch on within an hour) with my [just bought] Nexus 4 (latest 4.2.2 firmware OTA updated, nothing special in setup, second day of use).
Certainly must be difficult to say if it's hardware of software (that is, JB/drivers, since I cannot see how such issue can be caused by any virtual machine application) and when/if the latter will be fixed. I have another such great device already -- ASUS TF700 transformer, with similar "everything works, just reboots occasionally", which I think is enough for me
As with the ASUS Transformer case, I have trouble understanding: if it's the issue with all devices/firmware, although not too frequent -- then why everybody does not complain/return the units massively: the phone is pretty unusable if it cannot be relied upon. If it's just some isolated cases with particular units -- then what happened to QA/testing at LG...
So I guess I am going to return it while I can.
Too bad, good model otherwise, will have to see other phones or wait/observe.
My point is, I understand: fairly new device, can have quite a few faults to be fixed later -- now everybody seem to work that way, for better or worse.
It can have more or less beautiful (or ugly) designs, more or less features, larger or smaller batteries/working time; it can have problems with data connectivity, it can have better or worse browser (or the lack thereof completely). I'm fine with the lack of text reflow in Chrome although that was surprising.
One thing a phone/communicator/PDA absolutely cannot do, provided its battery is not empty, is going into "sleep of death"-like states -- it just cannot serve its purpose then, I cannot see how people sell it at all...
I have had a similar issue before, but i have experienced it when my phone has been through one of 2 sets of scenarios.
1 - It gets really warm and the screen becomes unresponsive, dead if you will. The hard reboot fixes this.
2 - When the signal to my phone is sporadic. An example of this would be my recent trip to London. I was on the underground quite a lot, and I'd lose signal quite often whilst travelling. On a couple of occasions i had to reboot my phone the hard way to get it going again.
Hope this helps?
In my case the device was lying near me on the sofa, the time between its going to standby and my attempt to switch it on was something within 1 hour. Nothing especially intensive had been done before.
BTW, while the phone was in that state, trying to call it resulted in long tones, i.e., apparently the radio/cell was online.
Hope this will help somebody, I returned mine.
Good evening. First post but long time lurker. My N4 is unrooted and on 4.2.2. I'm troubled with this as well especially so when the alarm doesn't ring in the morning after it's crashed overnight and I'm late for work!
Not sure if this is relevant though. I don't listen to music frequently on my N4 but the 3 times it had crashed overnight I had been listening to music before going to bed. Twice using Google music being streamed via my home wifi and once using poweramp with music on internal memory. I remember on 2 occasions the phone feeling rather hot as I was plugging the charger in as I was about to turn in.
I suspect there's a process that's causing the the phone to overload/ overheat and then switch off as a result. Because it's plugged in, it'll just continue to charge overnight and present you with a 100% battery in the morning once you've got it to reset again.
I have also found that doing a soft reset before going to bed prevents this from happening.
Just my observations.
Hi all, I got my Nexus 4 a week ago to replace a broken HTC One X (The cost of repairs was almost equal to the cost of a new Nexus 4). Since I got it, SoD happened twice, both times when I left it to charge overnight. The weird thing is that I have this LED application that blinks the notification light when charging with screen off. When I unplugged the phone, the LED was still blinking as if charging, so the phone is definitely not dead. I will try to set it to day-dream while charging and see if it helps. If it does, it might be considered a way of Google encouraging developers (like myself) to create more daydream apps .
Good morning from beyond the pond,
had the same thing happening as described in the first post solution (pressing POWER+VOL UP) helped to reboot my device.
Only thing that was showing was the led, flashing a blueish white light.
Now runs again on rasbeanjelly. Thanks to OP.
EDIT: since this happened the first time, I thought about what I had altered in my setup.
Only thing that was new was "Greenify". Maybe it sent the APEX launcher into standby?!
Having same problem on my 1 week older n4, my friend having the same problem . only thing in commune we have is the WHATSAPP app that once the phone restart it give a notification that the phone date is wrong,once I look at the date settings yes it is wrong, it says 1970 ,so I have to reset it. It does it every time the problem happens ,can this be a clue???
Sent from my Nexus 7 using xda app-developers app
guinnes.s said:
it says 1970
Click to expand...
Click to collapse
UNIX equivalent of Pol Pot's year zero
I'm having similar problems.
The first time I believe it was just an issue of slight overheating. I turned off the screen but left Google Maps running & put it in my bag. It didn't actually turn off, but the screen didn't want to come on when I took it out later. I did notice it was hot, and after it cooled for a couple mins, it worked fine again. I haven't done this again, and so far, so good.
However, now, on occasion the phone won't respond to the power button. I've never had to actually do a reset - it will eventually decide to work after a couple of presses.. but when it does, it will be slow to come on. The screen will be backlit (but black) for a few seconds, then it will load and respond as normal.
Since the light comes on prior to the screen, it seems like a software rather than hardware issue to me. If the screen was damaged, I don't think it would act that way. I don't know phones, but that's my intuition. I'm going to try and remember to turn it off on occasion and see if that helps. I don't think it's been reset since the last push update.
(I'm rooted, but stock)
Sorry if this is the wrong place for this. Feel free to point me in the right direction if it needs moved.
Fifth gen Kindle Fire, running Fire OS 5.3.3.0. All current updates, OEM otherwise.
It very often goes into a state where the System & Notification sound bar keeps beeping, like it's constantly trying to turn the volume the entire way up, but the button is not being pressed. The button does not appear to be stuck. When I press the volume down, it'll go down but then go back up on it's own when I let it go.
I've tried a factory reset. If I put it in Do Not Disturb mode, the System & Notifications drop down box still appears at the top of the screen, but it's grayed out.
At the same time, the power button stops functioning properly. It does not lock the screen, but if I hold the button it eventually it will hard shut down the device, and then start in Safe Mode when I power it back up.
Something to note is that it behaves this way often, but not constantly. There are brief periods where it is 100% functional. Just today I turned it on, ran some updates, and all was normal for an hour or so. After that it started with the volume nonsense.
It has barely any use since I purchased it forever ago and was always taken care of, so I don't suspect hardware unless something is defective from the factory. It has done this for as long as I can remember, but it literally saw almost no use for the first year and by the time I noticed it, the warranty was expired.
Any thoughts or suggestions?
SlightlyOpaque said:
Sorry if this is the wrong place for this. Feel free to point me in the right direction if it needs moved.
Fifth gen Kindle Fire, running Fire OS 5.3.3.0. All current updates, OEM otherwise.
It very often goes into a state where the System & Notification sound bar keeps beeping, like it's constantly trying to turn the volume the entire way up, but the button is not being pressed. The button does not appear to be stuck. When I press the volume down, it'll go down but then go back up on it's own when I let it go.
I've tried a factory reset. If I put it in Do Not Disturb mode, the System & Notifications drop down box still appears at the top of the screen, but it's grayed out.
At the same time, the power button stops functioning properly. It does not lock the screen, but if I hold the button it eventually it will hard shut down the device, and then start in Safe Mode when I power it back up.
Something to note is that it behaves this way often, but not constantly. There are brief periods where it is 100% functional. Just today I turned it on, ran some updates, and all was normal for an hour or so. After that it started with the volume nonsense.
It has barely any use since I purchased it forever ago and was always taken care of, so I don't suspect hardware unless something is defective from the factory. It has done this for as long as I can remember, but it literally saw almost no use for the first year and by the time I noticed it, the warranty was expired.
Any thoughts or suggestions?
Click to expand...
Click to collapse
You can try to reload (sideload) FireOS via the stock recovery menu to rule out a software glitch. However, based on symptoms I suspect the board holding the buttons and/or associate ribbon cable is the culprit. Not much you can do about either unless willing to crack open the case.
I wouldn't mind opening it up to replace some things, but I was hoping that based on it working fine for 20 minutes, and then out of nowhere showing problems, that it was software related. I've had it turned off since I posted, fired it back up now, and it's working as it should. I suspect within the hour it'll be back to broken, though.
Edit: Also, as mentioned, the power button stops behaving normally when this happens as well. I haven't looked into the layout of the buttons internally, but I would think that the volume and power buttons would be on separate ribbons leading to separate places?
SlightlyOpaque said:
I wouldn't mind opening it up to replace some things, but I was hoping that based on it working fine for 20 minutes, and then out of nowhere showing problems, that it was software related. I've had it turned off since I posted, fired it back up now, and it's working as it should. I suspect within the hour it'll be back to broken, though.
Edit: Also, as mentioned, the power button stops behaving normally when this happens as well. I haven't looked into the layout of the buttons internally, but I would think that the volume and power buttons would be on separate ribbons leading to separate places?
Click to expand...
Click to collapse
You can view the internals on a self-repair site such as iFixIT or by searching YouTube. The delay prior to acting up suggest heat may play a role. Not necessarily overheating, just the normal warming that electronics emit with use. Good luck.
Hi there,
My home button often stops responding. It will appear pressed correctly but doesn't actually go home. Sometimes the back and switch window buttons also don't respond, but that's less common. This happens about once a day.
The screen is fine as the buttons visually change to show I've tapped them, but they simply do nothing.
I can always fix it by restarting. It's only been happening on 12.1 v61 firmware.
There's no physical damage to the phone, it's in mint condition.
Any ideas? Anyone else having this?
I'm hoping the next software update fixes it because it's super annoying.
Thanks!
Global power management will cause erratic behaviors. A 3rd party app, does it happen in safe mode? Any apps installed or uninstalled before this happened?
Clear the system cache if you have this option.