Related
Been happy with my Nexus with Cyanogen Rom, but just having a problem with it sleeping:
Suddenly its stopped going into standby/sleep when I press the power/wake button on the top. Pressing and holding still allows me to shut down etc, so its not hardware.
The only thing I thought was I just installed RoboDefence Free Edtn and Android mentioned it will keep the phone awake in the "Program Controls" confirmation page. I've since uninstalled the app but still have the problem.
Anyone know if theres a global setting somewhere for this?
Thanks,
I am having the same problem with my recent Cyanogen
if you are on 5.0.5, i'd wait till tomorrow till 5.0.5.1 comes out and hope that fixes it.
check your end button behavior under spare parts. i changed mine to "sleep" on 5.0.5 and now the power button puts the phone to sleep
had this problem for a few days intermitantly then wouldnt let me power down at all....took my battery out and phone wouldnt turn on...! phoned HTC said they will collect and see for repair/replacement...
tip: back up your data now just in case it is the power button on its way to braking down. just in case!
very helpfull staff tho wen i called up quite pleased so far!
any update?
..im having the same issue, and was
considering calling in & sending it back,
but i'm wondering if they'll snoop around n'
find out that i've rooted & un-bootlocked..
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)
ok so i've been using it a bit but my battery was 70% last i checked. was playing around with throw and just opened youtube and the screen flickered a bit (black lines) then decided to go black completely.
nothing i do will make the screen do anything.
holding the power button for ages (usually the way to turn off/reboot a phone) doesnt do anything. the backlight is on as i can see that. but nothing is on the screen.
anyone got any ideas on how to force a shutdown/reboot on these?
thefunkygibbon said:
ok so i've been using it a bit but my battery was 70% last i checked. was playing around with throw and just opened youtube and the screen flickered a bit (black lines) then decided to go black completely.
nothing i do will make the screen do anything.
holding the power button for ages (usually the way to turn off/reboot a phone) doesnt do anything. the backlight is on as i can see that. but nothing is on the screen.
anyone got any ideas on how to force a shutdown/reboot on these?
Click to expand...
Click to collapse
IIRC the Xperia Z1 has a hard reset button under the sim flap, it's a small red button, give it a shot.
remove sim card and sd card and try again, if it's still not responding do an update repair using SUS or PCC
BTW there is a known fault with the XZU and it could also be on the Z1 as they use similar Firmware, what people have found is that the phone will start up eventually and then they go into the display setting and untick the auto backlight option and that fixes it
I also reboot my Z1in this way when it blackout.
Sent from my C6902 using xda app-developers app
Had the same issue called Sony, push hard reset button all is fine in the world. Known issue Sony is working on it
Sent from my C6903 using Tapatalk 4
Managed to hard reset using power and up volume .
Put it on charge overnight but it doesn't see,m to have taken any charge at all....just trying again using diff PSU and cables but it doesn't want to charge. It recognises that I've out a cable in as I played with the smart connect setting. When it is off completely I get a red light (presumably meaning its charging ) but not in android
Any ideas?
Got it charging again by pushing the red button near sim slot for a couple seconds.
Just had another issue with SD card not being recognised after I removed another (/safely) had to reboot again using power plus vol up as it stuck on the shutdown logo when I tried to power down'...
Wow I can't believe the amount of issues I've ran into within 24hours of having this thing. I really don't know what to do...return it because it sounds like a faulty device (but all the issues are seemingly unrelated) or return and get another phone (is anyone else getting problems like I am?)
Sometimes phones have issues. I got one once that had no speakers or Mic inside... it happens lol
Try to go exchange it, and see if the next device gives you issues.. if not then you're good, if it does pick a different phone..
Do it soon though, most carriers only have a 14 day exchange period, and then after that will charge you all sorts of fees and try to fix your phone rather than just giving you a new one....
Sent from my 16GB Blue Verizon Galaxy S3 running MIUI v5 with KT kernel
thefunkygibbon said:
Got it charging again by pushing the red button near sim slot for a couple seconds.
Just had another issue with SD card not being recognised after I removed another (/safely) had to reboot again using power plus vol up as it stuck on the shutdown logo when I tried to power down'...
Wow I can't believe the amount of issues I've ran into within 24hours of having this thing. I really don't know what to do...return it because it sounds like a faulty device (but all the issues are seemingly unrelated) or return and get another phone (is anyone else getting problems like I am?)
Click to expand...
Click to collapse
sounds like a similar problem I had with my 64gb SD card - as I mentioned above remove all cards then start from there - a reflash of the firmware might help also
thefunkygibbon said:
ok so i've been using it a bit but my battery was 70% last i checked. was playing around with throw and just opened youtube and the screen flickered a bit (black lines) then decided to go black completely.
nothing i do will make the screen do anything.
holding the power button for ages (usually the way to turn off/reboot a phone) doesnt do anything. the backlight is on as i can see that. but nothing is on the screen.
anyone got any ideas on how to force a shutdown/reboot on these?
Click to expand...
Click to collapse
Something happened to mine with Youtube too. I'd started a video and paused it on a frame for comparison with another screen. While I was setting the other phone up, the screen on Z1 timed out. I pressed power, the screen come on and flickered, then went black!
Power and both volume keys function the same as the red button under the flap. I wasn't able to reproduce the bug.
LadFromWales85 said:
Something happened to mine with Youtube too. I'd started a video and paused it on a frame for comparison with another screen. While I was setting the other phone up, the screen on Z1 timed out. I pressed power, the screen come on and flickered, then went black!
Power and both volume keys function the same as the red button under the flap. I wasn't able to reproduce the bug.
Click to expand...
Click to collapse
yeah i've been trying to reproduce it and failing to. very odd. maybe its something to do with the first time you use youtube and do something specific?
gunna phone o2 up tomorrow and see what they say about all my issues. seems to have been fine this last 24 hours though and in their eyes that is prob reason enough not to issue a replacement.
I've had mine since Monday and this happened to me yesterday. I was troubleshooting sending MMS with T-Mobile tech support (not a phone issue as it was happening on previous phones too) and had to restart the phone several times. I noticed upon restarting that the backlight seemed to be on but the phone was not booting up. Had to perform several hard resets (both with the red reset button as well as the power/volume up buttons) before it FINALLY rebooted and stayed on. While trying to figure this out I ran a Google search to see if others were having this problem. One solution was to make sure the backlight option is checked. I had been messing with settings the night before and must have unchecked it. Since I rechecked it I haven't had the same issue.
Every once in a while, my recent apps button starts to go crazy. I will be reading a book or playing a game, and suddenly the recent apps will start pressing itself. I have even held the phone in the opposite landscape with nothing near the button and this still happens. Is this a software bug, or do I have a malfunctioning unit?
Theaccomplice88 said:
Every once in a while, my recent apps button starts to go crazy. I will be reading a book or playing a game, and suddenly the recent apps will start pressing itself. I have even held the phone in the opposite landscape with nothing near the button and this still happens. Is this a software bug, or do I have a malfunctioning unit?
Click to expand...
Click to collapse
I would bring it back and return it for another device. You don't want to ignore it thinking it might be a software issue then end up having to get a refurbished replacement if it eventually becomes a problem. Seems like this is one of the hazards of getting one of the first run of devices off the assembly line. Besides, it's not like you've rooted and messed it up with "unauthorized firmware"
Theaccomplice88 said:
Every once in a while, my recent apps button starts to go crazy. I will be reading a book or playing a game, and suddenly the recent apps will start pressing itself. I have even held the phone in the opposite landscape with nothing near the button and this still happens. Is this a software bug, or do I have a malfunctioning unit?
Click to expand...
Click to collapse
I have the exact same problem. I went to return it to an ATT store, but they didn't have any black ones in at the time, so I'll go back after they get black ones in. I have not idea is it is software or hardware (or both) but it seems the recent apps button is hypersensitive and can go off if you have a finger anywhere near (even though not touching) the button, even when your finger is only on the chrome part.
The problem seems worse if "Touch key light duration" is set to "Always on"
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.