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)
My GF was making a call with my Note5 and it popped up Process System isn't responding - OK, Wait - neither of which did anything. also it was vibrating every second or so, probably while trying to bring the system process back up and it crashing again.
Holding power didn't seem to turn it off but eventually it restarted to SAMSUNG screen, where it CONTINUES to vibrate every second and never progress.
Holding power does not shut it down.
What the heck do I do now!?
This is a relatively new phone but I bought it from some guy who I can't get back in contact with. It had been working fine for a week, rooted, running Dr Ketan rom.
edit: OK, after about 5 minutes of it vibrating at the SAMSUNG screen I tried holding power AND vol down, this (perhaps coincidentally) then rebooted it and it seemed to come up fine this time. It's a real pain not having a removable battery when something like this happens.
Hello,
I have a rooted and TWRP installed but otherwise stock 5.something T710 that I had worked on months ago. It's been great and my daughter had been using it to watch videos a couple days ago. I took the tablet from her at the end of our road trip and noticed it had about 63% battery left. I left it in the truck while we went to the movies(about 40 degrees f outsides) and then drove home without ever touching it until we got home. I went to use it when we got home and it would not turn on. I plugged it in to let it charge thinking it died for some reason, using the stock charger, though battery icon never appeared. The next morning I went to check it and it still would not turn on.
When I press the power button or plug in or unplug the charger the Recent and Back soft key lights will turn on for a second, then turn back off again.
I've tried:
Holding the power button down alone for over 3 minutes.
Held the power and volume up button for over a minute
Power and volume down for over a minute.
Home, volume down and power for over a minute
Home, volume up and power for over a minute.
I can connect it to my computer and it recognizes that my Tab S2 is connected but no files show as the default for the device was just charging mode and not the file modes.
Odin3 v3.10.7 recognizes it as connected. But fails to send the TWRP file again.
Any help?
Since the soft keys light up and the computer recognizes the device, it sounds like maybe the tab is still working but with no display? By any chance did you have adb working? I f so you could try rebooting, or booting into recovery to see if you see anything on the screen. It's possible that when you held the button combos, that it did boot into download and recovery but you couldn't see anything? In which case it could be a hardware problem. Hopefully it will fix itself! Sorry I can't be of more help..
Well adb shows the device as unauthorized. Reboot command says the same thing.
The home key is unresponsive to my finger print unlocks and no sound plays when I try to adjust the volume, like the ding sound it makes to hear if this is the volume level I want. There are never any of the capacitive touch vibrations or whatever its called to feel when you press a button on the screen.
I was wondering if it had something to do with hardware it's just strange that it would stop working from just being in my truck. From my knowledge it was never dropped or bumped heavily or anything, at least recently.
I guess it is possible something just burned up inside, that would be inconvenient, I've got to look up if its still in warranty. I love the size and performance of this thing.
Thanks for replying, hopefully more to come.
Still can't get it to work, same issues as above. I let the battery fully die which took about 2+weeks from the initial post. Which is to say that eventually the back and recent buttons stopped lighting up. I recharged it and after holding the power button for a few seconds the same condition repeated itself. If I touch the power button or home button the back and recent button back lights turn on for a moment and turn off again. There is no other indication of life. I would assume if it was just a dead screen then I should feel it try to turn on.
If I had to replace parts which ones should I look at first? Probably just the main board?
Buy a new one. Send yours in as defect. Done.
erase111
I see that is an old thread, but I having the same issue to a certain degree. The screen goes dark, but I can see the back light. If I play around enough times, (pressing the back and process button, before pressing the sensor button... Sometime, pressing the volume buttons and back button before pressing the sensor button), everything goes back to normal. Of course, it some random time, even when I am reading a web page or some other activity, it will go back to black.
So has anyone figured out what this issue actually might be? I thought maybe it was an issue with the ROM I was using, so I just moved over to LineageOS 16, but the problem still continues!
Hello, members. I come here to ask your help because i haven't found any solution for it anywhere on the internet. This is what happened: some days go (around a week or two) i updated my security patch to the last one released by Motorola and the phone was OK, pretty much the same. Then around five to six days ago the problem started: my phone started going off even with full battery, and so i had to hold high volume key + power key for the phone to boot again (this happened twice and was "solved" by the time) and so the headache started. Around four days ago i went to sleep and left my phone charging, then when i woke up some hours later it was completely off, showing nothing on the screen, then i removed the charger and turned it on, and for my surprise the phone booted saying Hello Moto, vibrating and all but the screen showed absolutely nothing but a black/grey screen, not even the boot logo was shown. Once the phone started i noticed the screen touch is working for turning on the flashlight, receiving or rejecting calls and all, but it is completely dark. I have already tried lighting up a flashlight in front of its light sensor to see if the ambient display was active, but it is not. I have also tried turning it on by holding low volume key + power for a lot of seconds and it resulted in no changes. I have tried turning it on by holding high volume key + power key, and even low + high + power keys simultaneously for tons of seconds and NADA. I'm completely desperated because i have found no solutions for it at all anywhere. My phone has not fallen to the ground and neither got watered, so i don't know what the **** has happened to it. It got like this completely out of a sudden, no one even touched it.
I had the same issue with my moto g6 and it happened a few days ago. i unlocked bootloader and rooted the phone and then installed some apps . it happened 2 times. First time happened i solved it. While it was charging screen went black and nothing appeared on screen but phone was working . i called from another phone and it was ringing. I thought an app was causing this issue so i uninstalled some apps that i installed when i got the phone. I turned it off and waited for a while to cool down ( i thought it was heated from over charging ). When i turned on it was ok everything came back. Week later it did the same issue but this time it was completely gone. I removed back cover to check battery . I disconnected the battery and then connected again , turned on the phone , screen was going on and off. After turning it on it stayed around 10 min. and then again everything gone. People who had similar issue are saying hard reset or fastboot mode etc. but nothing appears on screen so how can i do hard reset when i do not see anything on screen. Right now it is unusable . I cannot do nothing with the phone.
I fixed this problem on my G6+
The screen went black after the phone being in the hot sun for a while. I believe the problem was due to a poor connection to the screen because when I pressed hard at the very bottom of the screen the display flickered on. I then pressed very hard at several points along the bottom of the screen and the screen then started working constantly again. Not really a proper fix but I now have a working display again.
---------- Post added at 12:17 AM ---------- Previous post was at 12:12 AM ----------
The screen went black after the phone being in the hot sun for a while. I believe the problem was due to a poor connection to the screen because when I pressed hard at the very bottom of the screen the display flickered on. I then pressed very hard at several points along the bottom of the screen and the screen then started working constantly again. Not really a proper fix but I now have a working display again.