Database Develop

Screen Randomly Turns on When Unit is Off

Tried Forum/Google search for this and too many results.
Situation: My noob friend buys a refurbished AT&T Tilt after my praises and he reports that the screen randomly wakes up when the unit is off without any action on his part. What could be the common causes? My Tilt doesn't do this even after Hard-SPL, SIM unlock, and third party apps. He has none of this so far, just the stock ROM. Should I tell him to get a replacement? Do refurbished models have this problem?

the screen should turn on after you press the power button. press it again and the screen turns off. hold it and it wil shut down/power off. i thought that was normal -_-

isnt that the whole point?? u press the power button to wake it up??

I am LMAO at the responses so far. He is pressing the power button to turn it off. After it turns off, it will wake up randomly without any action on his part. I will edit the thread title to be more clear.

Camp said:
I am LMAO at the responses so far. He is pressing the power button to turn it off. After it turns off, it will wake up randomly without any action on his part. I will edit the thread title to be more clear.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=378091
Something like this.

JimmyMcGee said:
http://forum.xda-developers.com/showthread.php?t=378091
Something like this.
Click to expand...
Click to collapse
Thanks. I don't know if that is what is happening to him, but I will direct him to that thread.

The screen "wakes up" when ever an alarm goes off or you receive a message. Can you confirm that nothing is happening? i.e.:
1. it did not auto-connect to check for messages.
2. your friend did not receive a text message
3. no alarms went off
???
Bill

whk said:
The screen "wakes up" when ever an alarm goes off or you receive a message. Can you confirm that nothing is happening? i.e.:
1. it did not auto-connect to check for messages.
2. your friend did not receive a text message
3. no alarms went off
???
Bill
Click to expand...
Click to collapse
I will ask him and post the answers here.

I have the same problem on my stock tilt any solutions anyone? I have done numerous hard resets and that seems to the solve the problem for a couple months then it returns.

could be battery check from sprite backup
Sprite backup has an auto backup when it detects low battery. To test for low battery it periodically turns the device on - if you have sprite backup installed this could explain it.

somthin that was happening to mine for a bit was when i logged on to AIM for a while, it started doing that.... then ever since, even if app is completely closed out, it kept doing it!! it would randomly light up for no freakin reason (no auto login, no apps running) jus light up, then go dim???.... tried everything, eventually got new ROM and hasnt done it since. see if he has used the IM app, that was the problem for me...

there could be so many reasons why it would wake. Just the simple slide of the screen will wake it up. Theres a registry tweak to turn it off. There's also power options your friend can play around with.

Screen won't timeout

Very odd...
My screen won't timeout anymore, unless I manually press the power button. It doesn't matter whether the phone is plugged in or not, and it isn't dependent on the screen I am on either. The screen just stays on forever.
Is there a way I can see if a certain program is preventing the screen from sleeping? Has anyone encountered this type of thing before?
Thanks!

yakkamut said:
Very odd...
My screen won't timeout anymore, unless I manually press the power button. It doesn't matter whether the phone is plugged in or not, and it isn't dependent on the screen I am on either. The screen just stays on forever.
Is there a way I can see if a certain program is preventing the screen from sleeping? Has anyone encountered this type of thing before?
Thanks!
Click to expand...
Click to collapse
Did you check the screen time out settings, maybe you got it at 30mins ?

Yeah, it's set to 30 seconds. It must be some program that tells my phone not to sleep?

Even more odd...
It fixed itself!
Rebooting the phone for the last couple days had no effect on the timeout issue I was having, but doing it this afternoon somehow resolved the issue.
Add this to the list of idiosyncrasies that my SGS has.

I'm having this annoying problem with my SGS (JPY) at the moment. Sometimes it'll go to sleep and turn off the screen by itself, but 9 times out of 10 I have to manually turn it off with the power button.
Has anyone else experienced this with JPY? I'm reluctant to wipe and start again, but it's really starting to piss me off now...

might be an old topic, but i am experiencing this right now
i just installed gingerreal guerilla version yesterday and it works fine
however when i connected my phone to usb for charging this morning, it wont turn off the screen unless i do it manually by pressing the power button
weird thing is as far as i remember there's a setting on USB debug mode to turn off the screen when connected to usb. i think it might be related to the rom or is it always like that on gingerbread? i assume that is the root cause,
although i couldn't post the issue directly on the gingerreal thread due to minimum post count.

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] Wierd problem when turning screen off and on

Hey guys, im having a bit of a problem. My phone is shuting off on itself.
Everytime i turn it on, it boots up no problem, but when i hit the power button to turn the screen off, when i want to turn the screen on again by pressing the power button, the screen just goes deep blue, and turns off.
I haven't change anything on it for quite a few months now, so i'm not sure why this is happening. Im on Viper 3.5 i think or 3.7, using faux123 kernel, dont remember which version, but an old one with which i never had any troubles... rooted, s-on
Any ideas?
Thanks!
Coldsun15
PD: Logcat in the .rar file...was too big for .txt

Really?? No one??
Well, just for further info... my phone appeared to fix itself, since it stopped doing that weird thing for a couple of days, but now is back... nothing ever changed, no new apps, or settings or anything...
Any ideas welcome
Edit: Attaching new logcats...

coldsun15 said:
Well, just for further info... my phone appeared to fix itself, since it stopped doing that weird thing for a couple of days, but now is back... nothing ever changed, no new apps, or settings or anything...
Click to expand...
Click to collapse
I think your power button is broken (or you may have a related hardware issue). Nothing but a root app can reboot the phone, and I've never seen that happen by accident.

fenstre said:
I think your power button is broken (or you may have a related hardware issue). Nothing but a root app can reboot the phone, and I've never seen that happen by accident.
Click to expand...
Click to collapse
Yeah, i thought about it being hardware but something is off... i mean, if it where the power button, then i shouldnt be able to turn it on easily, or it wouldnt turn off the screen properly, nor would it just start working alright for a couple of days... plus, it didnt recieve any hits or anything during, before or after the problem.
I also thought it could be the screen, but when its on, it works perfectly, as on the first day...
But yeah, I'm not taking hardware problem out of the table...just seems unlikely to me...
Thanks for your answer!
Coldsun15
Edit: also, I just found out it doesnt actually restart...screen just turns dark blue, then it powers the screen off and it wont turn on when pressing power... but i know its on, because i can still hear notification sounds of incoming messages...
Edit2: Just tried same but instead of using power button, i used logo2sleep and home2wake kernel options, and did the on/off with them, and same result...dark blue screen then off and not turning on... so it cant be power button

Noticeable delay after pressing screen lock button. System reset does not help.

This issue has been driving me mad for the past couple weeks. I'm at my wits' end and I need some expert help to figure this out. Please read this post thoroughly to understand my situation, as this is not a simple matter of uninstalling some apps.
When I first got my Note 9, the screen lock button worked perfectly. The screen would immediately turn on when I pressed the button, and it would immediately turn off when I pressed it again. However, once I got the Android Pie update, the screen lock button stopped working properly. The screen still turns on immediately, but there's about a 0.5 second delay after I press the button to turn it off. It's a relatively small issue, but it's enough to bother me.
I attempted to fix this by performing a system reset. But this did not help. In fact, this issue is still present even before completing initial setup of the phone.
When you perform a system reset, the first screen you see when your phone restarts is the welcome screen. It contains a "start" button that you press to begin setup. On this screen, the lock button issue does not happen. My phone locks and unlocks correctly. On the next screen, you connect to a wifi network. After connecting to a wifi network, the lock button issue becomes present. In other words, this issue with the lock button is present before I even start using the OS, or install any apps, or really do anything at all. It seems to be triggered by connecting to a wifi network during setup.
So I figured there must be something wrong with the firmware. So I used Odin to flash an earlier firmware version. This did not solve the issue. I even tried installing an unlocked firmware version, on the offchance that my carrier (AT&T) was doing something weird. This did not help either.
I have no idea where to go from here. I thought that a system reset is supposed to completely wipe everything from your phone, so that it behaves exactly how it did when I first got it. But that's not the case. It seems like something is carrying over that's causing this issue. Does anybody have any idea what I should do?

Do you have lock instantly with power key on?

funkyverb said:
This issue has been driving me mad for the past couple weeks. I'm at my wits' end and I need some expert help to figure this out. Please read this post thoroughly to understand my situation, as this is not a simple matter of uninstalling some apps.
When I first got my Note 9, the screen lock button worked perfectly. The screen would immediately turn on when I pressed the button, and it would immediately turn off when I pressed it again. However, once I got the Android Pie update, the screen lock button stopped working properly. The screen still turns on immediately, but there's about a 0.5 second delay after I press the button to turn it off. It's a relatively small issue, but it's enough to bother me.
I attempted to fix this by performing a system reset. But this did not help. In fact, this issue is still present even before completing initial setup of the phone.
When you perform a system reset, the first screen you see when your phone restarts is the welcome screen. It contains a "start" button that you press to begin setup. On this screen, the lock button issue does not happen. My phone locks and unlocks correctly. On the next screen, you connect to a wifi network. After connecting to a wifi network, the lock button issue becomes present. In other words, this issue with the lock button is present before I even start using the OS, or install any apps, or really do anything at all. It seems to be triggered by connecting to a wifi network during setup.
So I figured there must be something wrong with the firmware. So I used Odin to flash an earlier firmware version. This did not solve the issue. I even tried installing an unlocked firmware version, on the offchance that my carrier (AT&T) was doing something weird. This did not help either.
I have no idea where to go from here. I thought that a system reset is supposed to completely wipe everything from your phone, so that it behaves exactly how it did when I first got it. But that's not the case. It seems like something is carrying over that's causing this issue. Does anybody have any idea what I should do?
Click to expand...
Click to collapse
It is probably the double tap power button to open camera feature. You can toggle it off and locking will be instant.
If its already off, there my be an accessibility service listening key presses.

xantrk said:
It is probably the double tap power button to open camera feature. You can toggle it off and locking will be instant.
If its already off, there my be an accessibility service listening key presses.
Click to expand...
Click to collapse
Oh my god, that fixed it... Can't believe I spent so much time trying to diagnose this. Thanks!

funkyverb said:
Oh my god, that fixed it... Can't believe I spent so much time trying to diagnose this. Thanks!
Click to expand...
Click to collapse
This delay issue is so silly but it annoys the hell out of me. Where did you turn off this feature in Pie?
Update: Found it. Just use the search box in settings and type in "camera" (or whatever it is in your language). The "double tap power" setting will get listed.
Thanks alot,
Watz

I even turned off the double press for camera app but I'm still noticing a 0.5 sec lag when i press the side key
I even restarted after changing the setting
Nothing is happening
Please help

xantrk said:
It is probably the double tap power button to open camera feature. You can toggle it off and locking will be instant.
If its already off, there my be an accessibility service listening key presses.
Click to expand...
Click to collapse
Thank you bro.