Database Develop

Nexus 4 Screen Wouldn't Turn On

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)

[Q] Broken Power Switch

Greetings.
Today the power switch from my Note stopped working.
I found a website that will replace it for an original Samsung one, but I would like to ask if anyone has a better alternative here on the US.
This is the one I got:
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-note-power-button-repair/
Also, it is weird that now that the power button doesn't work at all, I have to take out the battery to "turn off" the phone. But when I put the battery back on, the phone turns itself on. Is that normal behavior?
Thank you in advance.

if the phone is working as usual, then instead of removing the battery to switch the phone off, use any widget from the playstore to power off the phone. this way it will power off fine. may be its because the power button is messed up.

After 14 days of having the power switch in a nonworking state, today I woke up, and lo and behold, the damn switch started the work again.
Now I can turn off the phone normally, everything is normal now.
I didn't do anything special, nothing at all.
Before, I couldn't turn off the phone even with apps like QuickOff, thats allows the phone to reboot, turn off and etc, so I had to take the battery out every time.
I have no explanation.

You got lucky there :thumbup:
Sent from my GT-N7000 using Tapatalk 2

So, I think it is just because the power button gets sticky. I was having a similar problem, except that it was working intermittently; sometimes it would turn the phone off, sometimes it would bring up the shutdown screen; and sometimes it would work like it was supposed to. Probably yours started working when whatever was making it stick got dislodged. What I did was just press the button REAALLLY hard for a while while the battery was out. It's been about 24 hours and I haven't had any problems yet, fingers crossed. Another guy in a different thread just wiggled it around. Probably if you take the whole board off you could remove the power button and reinstall it or something, though it seems no one has had to go that far yet. Anyway, if anyone else runs into this problem, just mess around with the button until it starts working again. Though, as always, if you break it, its not my fault.

Recent apps bug?

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"

Black Screen, won't do anything.

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!

(Possible) Random Soft Brick?

So last night I had a very strange issue.. I pulled my S8 out of my pocket and it was completely unresponsive. Held down power for ~30 seconds, volume down+power, volume up+power, and even plugged it in to the charger to see if there was any vibration of screen response. Nothing. I have not tried any kind of modding/flashing or anything that could possibly cause a software issue, and the phone was at 80% charge. The only thing I could think of is I was walking outside earlier that day in 75 degree weather with black pants on.. maybe the phone overheated? But if so, why could I not power the phone back on, even into recovery/safe mode?
I was able to get it back on by bixby+vol down+power, then hitting cancel when it asked me if I was sure I wanted to install a custom OS. Very strange. Should I just take this back to T-Mo and swap it out for a new one, or treat this as an unlucky random occurance? I'm still within the 14 day return period.
Thanks in advance!

it is possible to have random lockup, even radiation from space, if it hits right spot could change memory value or state of CPU (that's why critical servers have memory parity bit, to pick out random memory changes and flag them as error asap), but as far as your phone, no one can tell. If it happens more than once in a blue moon, it still could be either some software or hardware. You may have 14 days to return your phone, but if defective you should be covered for 1 yr under warranty? Usually hardware issues get worse with time until it becomes apparent there is a problem. But it is your call.

pete4k said:
it is possible to have random lockup, even radiation from space, if it hits right spot could change memory value or state of CPU (that's why critical servers have memory parity bit, to pick out random memory changes and flag them as error asap), but as far as your phone, no one can tell. If it happens more than once in a blue moon, it still could be either some software or hardware. You may have 14 days to return your phone, but if defective you should be covered for 1 yr under warranty? Usually hardware issues get worse with time until it becomes apparent there is a problem. But it is your call.
Click to expand...
Click to collapse
For now I will probably just hold on to it, don't want to go through the hassle of setting up another phone. It just seems strange that it locked up to the point where I couldn't even turn it on with a hardware reset.. Like you said, I hope it was just a random occurrence. I just don't want to get a refurb if I do need to trade it in under the warranty
Thanks for the info!

To get it to reboot if it ever happens again just boot into stock recovery then select reboot system now.... Bixby button, vol + and power if it doesnt go into anything and stays in that state try just power and vol - then bixby at same time it will go into download mode it will ask to continue press vol+ to cancel press vol- hit vol- and should reboot.... So there u have two options. Num one is going into stock recov and second is download mode and denying it. Also i think for just a plain old hard reset it should work with vol- and power at same time, although in your case seems u were having trouble. One last thing as a last ditch effort and u cannot reboot phone or some weird sh#t is happening put it in download mode and use smartswitch emergecy fw and reflash fw. Pretty easy straightforward just make sure drivers are installed and smartswitch supports the s8 yet

nathpilland said:
So last night I had a very strange issue.. I pulled my S8 out of my pocket and it was completely unresponsive. Held down power for ~30 seconds, volume down+power, volume up+power, and even plugged it in to the charger to see if there was any vibration of screen response. Nothing. I have not tried any kind of modding/flashing or anything that could possibly cause a software issue, and the phone was at 80% charge. The only thing I could think of is I was walking outside earlier that day in 75 degree weather with black pants on.. maybe the phone overheated? But if so, why could I not power the phone back on, even into recovery/safe mode?
I was able to get it back on by bixby+vol down+power, then hitting cancel when it asked me if I was sure I wanted to install a custom OS. Very strange. Should I just take this back to T-Mo and swap it out for a new one, or treat this as an unlucky random occurance? I'm still within the 14 day return period.
Thanks in advance!
Click to expand...
Click to collapse
There are a few things you could try:
1. Fore close the app then reopen.
2. Redo the voice in google
3. Reboot phone (last resort)
I agree with the other guys. When you have trouble with google just hanging there it's more likely a connection to the internet issue. Good luck!