Database Users

phone keeps turning on

my htc hd2's backlight keeps coming on even after i lock it. i have done everything i thought i could but yeah. after it dies completly and i charge it, the phone acts okay but then after a lil bit it goes back to tweaking. what do i do?

puckstar33 said:
my htc hd2's backlight keeps coming on even after i lock it. i have done everything i thought i could but yeah. after it dies completly and i charge it, the phone acts okay but then after a lil bit it goes back to tweaking. what do i do?
Click to expand...
Click to collapse
Here is a friendly suggestion for you.
If you can supply more information you are more likely to get helpful suggestions. For example, what ROM are you using, what cabs have you installed, and what tweaks have you made. Without this sort of information it is impossible for anyone else to get enough of a handle on your problem to make useful suggestions.

you obviously have something acting in background that wakes up the phone from standby, check the list of installed applications from the settings and remove one by one those which you think have any reason to be always active on the phone.
I know for certain that HD2proximityscreenoff has te habit of turning on the backlight in standby at random intervals.

Goes out of Standby by itself

I have noticed that my x2a goes out of standby when I am putting it into its case (on my belt). This causes the display to turn on again -- wasting battery time and possibly starting programs.
Has anyone else noticed this? I find that if I hold the phone for an additional 3 seconds befor I place it into the case, going out of standby does not appear to happen ... but that could be just operator error ... and I have tried to avoid hitting any of the buttons when inserting the phone, but the whole thing could be operator error ... or, like I think, that the phone is sensing a position change and jumping out of standby ...
Is there a fix for this?

I thought I'm the only one experiencing that problem.. The thing is, my phone is just on the table and in standby mode and then for some reason it just opens... Very weird..

Sometimes it happens to me too. i don't know why it happens.

Razzino said:
Sometimes it happens to me too. i don't know why it happens.
Click to expand...
Click to collapse
Just a far shot:
Are you guys by any chance using the OneBridge syncronisation software?
I had this problem but it disappeared when my company switched to Activesynch/WMA for Exchange syncronisation.

i noticed my phone was doing this to, so i set it down and watch it for a while and noticed the screen will turn on when it is updating my weather or email, so this may happen when ever it automatically connects (due to some email, weather, ect.) you can try turning off data connection, and see if that changes anything. good luck

yummy-fun said:
i noticed my phone was doing this to, so i set it down and watch it for a while and noticed the screen will turn on when it is updating my weather or email, so this may happen when ever it automatically connects (due to some email, weather, ect.) you can try turning off data connection, and see if that changes anything. good luck
Click to expand...
Click to collapse
mine was off all along... so I guess it doesn't update anything when this happens...

sorry that didn't work, i'm just thinking out loud now, but my phone has recently stopped turning the screen on by itself. uhm things i've downloaded recently was the SDfix.cab and the htcSDK.cab but both of those wouldn't effect it. uhmmm. is there possibly something running in the background? the only other thing i can think of is lock your phone so you won't push button while its in your pocket, and wait for an update (which an update is unlikely to come out). sorry i couldn't help

yummy-fun said:
sorry that didn't work, i'm just thinking out loud now, but my phone has recently stopped turning the screen on by itself. uhm things i've downloaded recently was the SDfix.cab and the htcSDK.cab but both of those wouldn't effect it. uhmmm. is there possibly something running in the background? the only other thing i can think of is lock your phone so you won't push button while its in your pocket, and wait for an update (which an update is unlikely to come out). sorry i couldn't help
Click to expand...
Click to collapse
It's okay dude, I did what you said.. I locked my phone whenever I have to put it in standby mode, and great... It doesn't turn on by itself.. so I'm guessing that I pushed some buttons while the phone is in my pocket...
cheers mate!

It's the magnet!
I know the question was asked a while ago, but noone has posted this as a possible reason.
There is a magnetic sensor for opening the keyboard in the top left corner of the device. When you move your phone near a magnet (most phone cases' covers are held by magnets) it will detect opening the keyboard and go out of standby.

matt69 said:
I know the question was asked a while ago, but noone has posted this as a possible reason.
There is a magnetic sensor for opening the keyboard in the top left corner of the device. When you move your phone near a magnet (most phone cases' covers are held by magnets) it will detect opening the keyboard and go out of standby.
Click to expand...
Click to collapse
I just tried that, and it does some out of standby when I pull it out of the case ... I was wondering why that happened -- sometimes, and not others -- and that answers the issue of pulling it out of the case ...
Thanks for that explaination ...
But there are other times when it goes out by itself ... but I have it is the case most of the time now, and not on the charger ... so it is not really an issue for me anymore, but it is another mistery solved ...

Yup, my X2 does the same annoying thing.
I agree, best way is to lock the screen.
I noticed that the screen part of the phone is kinda wiggly...

sleep of death

I'm now on my third nexus 7 and in general absolutely love the device but I'm getting fed up with the issues.
My first device suffered from sever flickering, the second had the backlight bleed and now the third refuses to wake after the screen is turned off about fifty percent of the time.
This is not the same issue as people are reporting in other posts as the charger is never connected when I have a problem. It doesn't matter if the screen times out or if I press the power button to after I finish using the device.
I'm using the stock ROM (with the 4.1.1 update), no root and have only installed the kindel app so its about as vanilla as can be.
The second nexus I had did this once but I had already organised the return and didn't think much of it.
Anyone else having similar issues or able to recommended a fix as this nexus is perfect in every other way?

Factory reset, leave it that way for a while, does it happen? If no, then you probably have an app doing something wonky.

Turn off automatic backlight, manually set it to around 40% and see if the flicker and the "SOD" goes away.

As the poster above said, turn off automatic brightness and see if that fixes it.

Nospin said:
As the poster above said, turn off automatic brightness and see if that fixes it.
Click to expand...
Click to collapse
Automatic brightness is on my N7 (and other devices) 100% of the time... No SOD problems here.

lol, so far there's not an issue for you. But some have noticed that depending on the brightness settings it reads when you power on the screen, it can "think" it's either too bright or too dark and leave you with a screen you can't see.
This gets mistaken for "SOD" because you never see the screen-Why? Because it looks like the ratio for the lowest automatic brightness setting is a bit, um, TOO low. LOL
Most other devices won't exhibit this using stock settings, but the N7 will.

THANKS!
Just got my first nexus 7 yesterday and after pretty much falling in love, was dismayed about the unexplained black outs for no apparent reason. Could not wake up the device afterward without holding down the power key for 10 sec then leaving it alone for a while.
After reading your post, I realized that the incidents occurred after switching from manual to automatic brightness in a dimly lit room, followed by mysterious recoveries when moving to brighter room. I will monitor, but hope for the best. (Will probably just use manual settings as I found the automatic mode to be too dim in all settings anyway - old eyes!)
I am already pretty raw on this point as I just spent the last 10 years or so with a laptop that would not wake up from sleep, and just learned to live with it after wasting SO much time trying to get to the bottom of it. If you have saved me from that, or from having to exchange the n7, I owe you big time. Thanks again!
Compusmurf said:
lol, so far there's not an issue for you. But some have noticed that depending on the brightness settings it reads when you power on the screen, it can "think" it's either too bright or too dark and leave you with a screen you can't see.
This gets mistaken for "SOD" because you never see the screen-Why? Because it looks like the ratio for the lowest automatic brightness setting is a bit, um, TOO low. LOL
Most other devices won't exhibit this using stock settings, but the N7 will.
Click to expand...
Click to collapse

did you solve it or what?
I have the exact same issue and I'm about two second from returning this crap
so annoying

seven2099 said:
did you solve it or what?
I have the exact same issue and I'm about two second from returning this crap
so annoying
Click to expand...
Click to collapse
well that didnt fix anything.
Its a hardware issue, so i'm going back to stock and see what I can do, because if not, this baby is going back

seven2099 said:
well that didnt fix anything.
Its a hardware issue, so i'm going back to stock and see what I can do, because if not, this baby is going back
Click to expand...
Click to collapse
i have similar issue with forced sleep, it cannot waken sometimes. TnT
anyone can help?

Further investigation shows this has nothing to do with brightness and that all tablets with this issue should be returned/exchanged immediately.
Quick google search will allow you to find that comes directly from Asus support.
Total fail, asus ftl

new tab rendered more quality issues. opened it at the shop, returned it immediately and went samsung.
Asus will always be asus.. too bad cuz my tf300 was pretty decent in terms of quality, just had wierd screen lift and squeecky issues.
Galaxy Tab 2.0 7inch is a much better choice now.

I have exactly the same problem with my current device. About 30% of the time, the power button would just stop working so I couldn't turn the unit on or off, unless I plugged it in to the charger. It didn't turn on for a full day once so I did a full factory reset which included re-flashing the stock rom and the problem persisted, the button would still not work! So I packaged it up for return and left it sitting for a couple of days. Just before I went to post it, I checked that the issue remained and to my surprise it turned itself back on again! I kept it and since then, it has only happened once.
I do intend to return it though, but only when I hear Asus are shipping units which are built properly. Clearly a hardware issue but pretty weird since it seems random and is not reproducible by any means I know of.

I am experiencing a similar issue. Does setting a manual brightness fix the issue?

It is my 3rd Nexus now with exactly the same problem.
I found out that the Nexus is in APX-mode (NVFlash) when it's in this state (SoD). Windows tries to install a APX driver when it is connected via USB.
The problem occured always with 16GB Nexus. A friends 8GB works fine.
Nexus 7 (C9) - Stock Rom 4.1.2. - locked - not rooted

Turning off the auto-brightness fixed the issue for me. Minor workaround to a major problem.

Display turning OFF after a while..

I have an LG G Watch with 5.0.1 since a few days and I tried and sent back an identical LG G watch on 4.4W.1 a while ago and didn't experience it. Basically, I am noticing that after leaving the watch alone lying somewhere (I don't wear it at home) for some time (can't really say how long but at least an hour, I think) the display turns OFF. A single tap and it wakes up and then works "normally" until the next time...
The other G Watch with the older Wear version didn't have this behaviour so is this a feature of the latest Wear version or is it maybe an "issue"..?
I am saying this especially because I installed the Slumber app to automatically turn the display OFF while charging but realized that it's easier and more elegantly done by simply choosing the new "Theater mode" in Android Wear 5.0.1 and uninstalled the app. I don't know if what I am seeing is due to having installed Slumber but I really don't think so.
Does anybody know for sure what it is and how it exactly works..?
TIA

No replies here but several in the LG G Watch forum.
Other G Watch owners are seeing the same behaviour I described here so I can rule out that it's something which has been triggered by my having had the Slumber app installed.
One poster there says that his G Watch turns off after 30 minutes leaving it lying on a table. I am timing mine.
So based on all of those replies it seems it's a feature of the latest Android Wear. I am not calling it a bug because, except for a single reported case from a poster there with a Moto 360, it seems to never happen while wearing it, so the logic appears to be "save the battery when not in use".
Just to "investigate" it some more, may somebody else here with Wear watches from other makers please confirm you get the same behaviour on your watches (on 5.0.1)? And may you also confirm you have Ambient turned ON (i.e. the display is always ON) and state whether you have the new Tilt to wake up setting ON (i.e. the Display lights up from its dimmed state when you tilt your wrist).
My settings are Display always ON and Tilt to wake up OFF.
It would be good to have some more reports from owners of different Wear smartwatches and see if we can understand what exactly is this behaviour we are seeing...
Actually, I think this might be a good feature to keep ON in many cases but it absolutely should be an *option*!

UPDATE: Trying to time it, I think I can say (I am still trying to cover all of the different scenarios) that any event which normally wakes the display up to normal brightness (i.e. an incoming call) resets the countdown. BTW, I think the poster StuBFrost, in the other thread, is right and it's 30 minutes off the wirst with no movement, no tapping on it and no event like the ones just mentioned. "Normal" incoming notifications don't seem to reset the countdown.
Like I said, I don't think it's a bad idea in and of itself (I would use it in most cases) but they should have made it an option! And, ideally, they would let us set the time after which the display turns itself off.
I use and *strongly* prefer Android instead of limited and dumbed down Windows Phone and even worse Apple's useless crap exactly because of its customizability and powerfulness...

"Funny" thing is that from further testing, this feature doesn't kick in while on the charger (which could actually be pretty useful for most people...) LOL
ADDENDUM: the kind of events which resets the countdown to this "deep sleep" state (i.e. an incoming call) also wakes the display up from "deep sleep".

How to disable front buttons when device is locked?

I don't wish to entirely disable the front buttons, I only want them to stop responding when the phone is locked (I want them to function when the phone is unlocked). Don't misunderstand: I am not looking to simply disable the light. I want the buttons to be completely 'dead' when the phone is locked up. It's actually my bf's phone, and the buttons get accidentally pressed a lot when it's in his pocket. The phone will drain 60% in just 5 hours with no screen time, just locked and in his pocket (at work). I'm tweaking the phone to last longer, but I feel that having the buttons able to be pressed even while locked can't be good for the battery. :/ Someone correct me if I'm wrong with that (but even if I am, it's still annoying... what is the purpose of the buttons being 'live' while the screen is off???). The phone is a i9505, rooted on CM12.1 with Xposed, so modules could be suggested if any such fix exists. I have the home button disabled from waking the screen, but there doesn't seem to be an option anywhere about the back and menu buttons. I know the battery on my own phone, a Huawei, is much larger, but I only experience about 6% battery loss when the screen is off for 7-9 hours, so losing 60% seems excessive to me. I've checked battery stats on the Samsung, nothing seems abnormal. Is it even possible to fix what I'm asking? Thanks to anyone who helps!

zombunny said:
I don't wish to entirely disable the front buttons, I only want them to stop responding when the phone is locked (I want them to function when the phone is unlocked). Don't misunderstand: I am not looking to simply disable the light. I want the buttons to be completely 'dead' when the phone is locked up. It's actually my bf's phone, and the buttons get accidentally pressed a lot when it's in his pocket. The phone will drain 60% in just 5 hours with no screen time, just locked and in his pocket (at work). I'm tweaking the phone to last longer, but I feel that having the buttons able to be pressed even while locked can't be good for the battery. :/ Someone correct me if I'm wrong with that (but even if I am, it's still annoying... what is the purpose of the buttons being 'live' while the screen is off???). The phone is a i9505, rooted on CM12.1 with Xposed, so modules could be suggested if any such fix exists. I have the home button disabled from waking the screen, but there doesn't seem to be an option anywhere about the back and menu buttons. I know the battery on my own phone, a Huawei, is much larger, but I only experience about 6% battery loss when the screen is off for 7-9 hours, so losing 60% seems excessive to me. I've checked battery stats on the Samsung, nothing seems abnormal. Is it even possible to fix what I'm asking? Thanks to anyone who helps!
Click to expand...
Click to collapse
The keys are never on by default when the screen is off. So you either applied a setting to enable it or you have some mod applied.

Lennyz1988 said:
The keys are never on by default when the screen is off. So you either applied a setting to enable it or you have some mod applied.
Click to expand...
Click to collapse
I wouldn't have enabled a setting for this purposely, as it's quite annoying. I may also be wrong, but if I remember correctly, this was existent even on stock non-rooted. I have CM12.1 on it, Xposed modules are: Always Correct, APM+, BootManager, Secure Settings, Xposed Additions, YouTube AdAway, and YouTube Background Playback.
If there is a setting for this, let's say he or I accidentally enabled it, so would you know any suggestions of how to find such a setting, so it can be switched back? I appreciate you taking the time to answer.

zombunny said:
I wouldn't have enabled a setting for this purposely, as it's quite annoying. I may also be wrong, but if I remember correctly, this was existent even on stock non-rooted. I have CM12.1 on it, Xposed modules are: Always Correct, APM+, BootManager, Secure Settings, Xposed Additions, YouTube AdAway, and YouTube Background Playback.
If there is a setting for this, let's say he or I accidentally enabled it, so would you know any suggestions of how to find such a setting, so it can be switched back? I appreciate you taking the time to answer.
Click to expand...
Click to collapse
When the screen is off then menu and back don't work. Do you have ambient display enabled by any chance? Disable it.
Did you try a different battery? Maybe his battery needs to be replaced.

Lennyz1988 said:
When the screen is off then menu and back don't work. Do you have ambient display enabled by any chance? Disable it.
Did you try a different battery? Maybe his battery needs to be replaced.
Click to expand...
Click to collapse
Oh no, you're right about that. Back and menu doesn't actually do anything when touched while locked, but they do light up and respond in that sense (interestingly, they do also wake the screen while it's locked in TWRP, though perhaps that's irrelevant). Ambient display isn't enabled. We haven't tried a different battery, he just got the phone about a month ago. Then again, I also haven't the health of the battery. Maybe it came with a bad one.

When the screen is off, the back and menu buttons should not work. Not even the lights.

zombunny said:
Oh no, you're right about that. Back and menu doesn't actually do anything when touched while locked, but they do light up and respond in that sense (interestingly, they do also wake the screen while it's locked in TWRP, though perhaps that's irrelevant). Ambient display isn't enabled. We haven't tried a different battery, he just got the phone about a month ago. Then again, I also haven't the health of the battery. Maybe it came with a bad one.
Click to expand...
Click to collapse
I understand you now. Yes when they the phone is locked and the screen is on, they will light up. That's normal and does not give any battery drain. Post some battery screenshots and post screens of the app betterbatterystats.

Lennyz1988 said:
I understand you now. Yes when they the phone is locked and the screen is on, they will light up. That's normal and does not give any battery drain. Post some battery screenshots and post screens of the app betterbatterystats.
Click to expand...
Click to collapse
Ah got it. Good to know it's not impacting his battery, but that also leaves it open as to what IS (though, the buttons lighting up while it's locked still makes me scratch my head at what Samsung was thinking). Currently going to sleep at the moment, so I'll have to take a look at it tomorrow. I know Opera Max, a VPN data compression app, was chewing up battery (did this on my phone too, but eventually it settled down with the ROM), but I froze it for the moment so it won't run until I figure out what else is causing the problem. Battery life was poor even before the installation.
Other than that, battery stats have been normal, with the display taking the majority followed by Opera browser and the Android system, with some others. Nothing outrageous.
But since you mentioned about the battery, I did start noticing more things about the phone today. Perhaps it runs so hot because of it, and I also saw that when he unplugs it from the wall charger, it will immediately drop from 100% to 90-some% (varies). Might be the calibration, but with everything else, I ended up ordering an Anker replacement from Amazon to test.

The S4 heating is normal.
Also, it's not healthy for the battery to spend extended periods of time at 100%. That is why it drops faster from 100%.