looks like i got a lemon, screen will not turn back on however device continues to function. The touchscreen even works but you can't tell what you are clicking on.
Only way to get back to functional is to pull the battery, only happened once last week but in the last two days i've had to pull it 6 times or so.
Just posting this up in case someone else starts having the same problem. I've got a replacement being shipped out this week.
You are not the only one. Mine does it from time to time
Sent from my SAMSUNG-SM-G900A using XDA Premium 4 mobile app
Has any one had problems with maps as well
Sent from my SAMSUNG-SM-G900A using XDA Premium 4 mobile app
I might have had this happen last night. Black screen, buttons lights would only flicker once quickly when pressing the power button. Pressing and holding the power button did not cause a reboot. I did not try any screen action as I could not see anything. Had to pop the battery to get the device back to working.
--pat
I got my replacement, and it still does seem to have this bug to some extent, however, this phone seems to be able to get out of the screen black if something else triggers it.
For instance, I got a phone call, and that brought it out of the black-out. Another time i just kept pushing buttons and it finally woke up.
Hopefully it's just a software bug??
Related
While using "carcast" today my volume went down as if I was holding the volume button. It happened three times. The first time I was looking at tweetdeck, and I watched the media volume rapidly go down. After I turned my volume back up, I checked to see if there was anything under my body glove that may have pushed the button. Ok, nothing there. Just an odd fluke. About ten minuets later it happened again while my phone was sitting on the table. This time I rebooted my phone. Then it was sitting on the table charging on the computer and it happened one more time. This was a half of an hour after the reboot.
Has anyone encountered this, or have any idea what might cause it.
I don't know if this helps, but I'm running cog 2..3b6. I've been using it for a few weeks now with no issues until today.
Sent from my SAMSUNG CAPTIVATE using XDA App
volume
patrickw8 said:
While using "carcast" today my volume went down as if I was holding the volume button. It happened three times. The first time I was looking at tweetdeck, and I watched the media volume rapidly go down. After I turned my volume back up, I checked to see if there was anything under my body glove that may have pushed the button. Ok, nothing there. Just an odd fluke. About ten minuets later it happened again while my phone was sitting on the table. This time I rebooted my phone. Then it was sitting on the table charging on the computer and it happened one more time. This was a half of an hour after the reboot.
Has anyone encountered this, or have any idea what might cause it.
I don't know if this helps, but I'm running cog 2..3b6. I've been using it for a few weeks now with no issues until today.
Sent from my SAMSUNG CAPTIVATE using XDA App
Click to expand...
Click to collapse
Maybe some issues with the ROM or kernel.. Try flashing a different ROM after a complete wipe and see if the issue persists. If it does, there might be something that causes the volume key to get stuck
Perhaps there was a recent update with the app that is causing problems and you could revert to prior version...i would check that before getting flash happy
For now, it's only doing it with carcast. If it keeps up I'll use a different podcast loader. Can anyone recommend one?
Sent from my SAMSUNG-SGH-I897 using XDA App
my power button seem to stop responding at times and it isnt the hardware thats messed up i think it has something to do with the software because when the power button stop functioning completely i do a battery pull and can turn on the phone perfectly fine its only when the phone is on is when the power button stops working...i noticed it mostly happens when i plug it into the dock maybe its the deskhome app not sure tho if anyone have this problem please let me know so i know i wont be the only one
Every phone cab have it's funky moments. I have seen this a couple times. Here is a solution I have found that works on all smart phones, and I believe that most will agree. Your phone is a computer, plain and simple. Try doing a battery pull every day our two.
It sounds like your problem is very defined in when it happens, is that so?
Sent from my VS910 4G using XDA Premium App
I do battery pulls when the power button completely doesn't work then sometimes it works for the whole day then sometimes takes me like few more battery pull after the initial pull for it to respond its annoying in some ways but I guess I'll live with it until I find the problem
Sent from my VS910 4G using XDA App
I haven't seen it that often.... Weird...
Sent from my VS910 4G using XDA Premium App
Problem solved just went to verizon store and just used my warranty to get a new phone
Sent from my VS910 4G using XDA App
hmm i think i figured out the problem if anyone still cares....when my phone is low battery or somewhat low (not above a certain percentage) my power button starts working normally.....dont know whats causing it maybe too much power hAHa
Something is definitely wonky with the phone when the screen is off... I have the lock screen disabled and it takes 3-4 presses of the volume buttons to wake the screen usually. Also, I have gosms wake the screen for certain peoples texts, and sometimes if the screen is off and I get a message from these ppl, the phone will decide it wants to vibrate for 2 mins, keep the screen on and not work at all until it resets itself... eh.
Sent from my VS910 4G using Tapatalk
ok i know im gettin annoying with my theory's on why my power button doesnt work correctly but another thing that my power button starts working normally even at full power is when i change my wallpaper....i wonder would it be a wall paper problem although now i just think im going crazy lol
When I shut down my phone, the screen will go black and it will vibrate like normal. Last I checked the vibrate was to confirm that it was completely shut off. Instead, the four touch sensitive buttons will light up and stay lit until I turn the phone back on or, of course, pull the battery. This is also keeping me from entering download mode. A few days ago the phone was shutting down correctly and I have been able to enter download mode, but now the problem is going on again. I'm on official 2.2 Froyo updated through kies mini. My phone is rooted, but this problem occurred before I rooted.
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Sounds like a warranty replacement.
I've had it for over a year. I wonder why it's just now doing this.
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
I think I have come to a conclusion on why it doesn't seem to shut down completely and would need someone with a captivate that has all fully functional buttons. I believe that since my power button sticks, when the phone vibrates to confirm a shutdown, the capacitive touch button lights will not shut off until the power button is released. So if someone wouldn't mind shutting their phone off while holding the power button and tell me if you can make the lights come on after the vibrate while holding power button? Thanks in advance.
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
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)
Both my wife and I have the S5 att. We don't do anything custom on the phones, my wife plays a few games and I use mine mainly for emails and Web browsing.
Here lately, both of our phones will lock up while using them. The screen will be on and it just freezes. You can click the power button and it will go black, and back on when pressed again. You can't restart the phone, you must pull the battery.
Hers doesn't while mainly texting and mine while waking the phone up.
Any thoughts.
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
Do you have "Power Saving" enabled? How often do you manually restart ur phone?
Sent from my SAMSUNG-SM-G900A using XDA Premium 4 mobile app
Jonny Steele said:
Both my wife and I have the S5 att. We don't do anything custom on the phones, my wife plays a few games and I use mine mainly for emails and Web browsing.
Here lately, both of our phones will lock up while using them. The screen will be on and it just freezes. You can click the power button and it will go black, and back on when pressed again. You can't restart the phone, you must pull the battery.
Hers doesn't while mainly texting and mine while waking the phone up.
Any thoughts.
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
Click to expand...
Click to collapse
Ive had mine lock up similarly, twice. When mine does it, it freezes, i hit the power button, screen goes black. However, when i hit it again, the screen stays black. The capacitive buttons light up, they go back out if i hit it again, and yet again, if i hit it they come back on. Ive let it sit for about 10 minutes but still in the end would up pulling the battery.
No power saving mode. I restart mine every other day, my wife not so much.
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
Mine has done the same. Only once though. I went to unlock it and the water drop touch sound was going off like I was touchtouchtouchtouchtouchtouch like 10-15 times. Holding down power gave me the restart/power menu but touching it was non responsive. It kept swapping itself from the home screen to the screen setting menu (that you get when you long hold the open app button) .. I set it down for about 5-6 minutes and left it alone and it finally fixed itself. Very strange. Ive been running 100% stock out of the box since I got it last weekend.
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
cloudraker said:
Ive had mine lock up similarly, twice. When mine does it, it freezes, i hit the power button, screen goes black. However, when i hit it again, the screen stays black. The capacitive buttons light up, they go back out if i hit it again, and yet again, if i hit it they come back on. Ive let it sit for about 10 minutes but still in the end would up pulling the battery.
Click to expand...
Click to collapse
Same problem as this http://forum.xda-developers.com/showthread.php?t=2726029
Extraordinarily frustrating, i'm on the verge of sending my second phone back as well, just to get the point across. I have to pull my battery 2-3 times a day.
Ive had this issue a couple times, it seems to be triggered for me by the use of some functions within apps, in my case the facebook app brought on a crash, which I needed to pull the battery
mastermarc said:
Same problem as this http://forum.xda-developers.com/showthread.php?t=2726029
Extraordinarily frustrating, i'm on the verge of sending my second phone back as well, just to get the point across. I have to pull my battery 2-3 times a day.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2726029
see this.
Kael ruch said:
http://forum.xda-developers.com/showthread.php?t=2726029
see this.
Click to expand...
Click to collapse
yeah i linked that, no fix though