Running the newest UnNamed and I'm trying to find a way to keep the screen on while charging from USB. The point is to keep the screen on while driving. At night I charge with AC power so that's not an issue.
I found posts saying there was a burn in problem with SMOLED screens being on with a static image for more than a couple minutes at a time. I haven't seen it personally but if anyone has first hand experience with this phone or the international model, please speak up before I damage my phone.
Otherwise, once again, it looks like I need Tasker for the job. Have it detect bluetooth connection for the car and upon usb power trigger car mode and keep the screen on at ~50% brightness. something like that.
With unnamed go to Settings>Applications>Development and click Stay Awake.
Try this first,
Menu->settings->Applications ->Development -> Stay awak
If not working , try this
Menu->settings->Display->Screen Timeout ->Never
Now I've never seen permanent burn in on my SGSII or Nexus One (even while on constantly during a 10h drive to Vegas). I was using a stop watch app on my Nexus One, and while only on for 5 minutes or so, I did see it burn in, but it went away after a few minutes of being off (boy was I scared when I first saw it though).
Now, I have personally seen permanent burn-in on a Vibrant (not mine).
Funny thing is the screen timeout is set to like 5 seconds on it, so it's barely on. Yet I can clearly see the clock is burned into the screen.
Have you tried running a car app to hold a screen lock? I know Google Maps can do that. Plus it doesn't require going into settings (at least more than once).
EDIT: As a simple observation, the burn-in seems worse when it's white on a black background.
Related
How do I allow the screen to remain on during a charge?
I use my phone for music in my car, but find it irratating when I have to constantly turn the screen on and enter my unlock pattern.
On other android devices there is the option to Leave the screen on during charging under Applications > Development.
Any Ideas on the Galaxy S2?
Kind Regards
Lewis
I'm pretty sure they took this out because you'd get burn-in with SAMOLED screens...
Even if you do figure out a way of how to do this I would advise you not to. The screen can get pretty bad "burn in" pretty quickly, as I had found out with my old galaxy s.
I'm having the opposite problem the screen will remain on while charging. Cannot find a setting , four example woke this morning and left the phone in the charger returned a hour latter and the screen was still on, dimmed down but still ON.
is there a way to fix this, I'm worried about burning the screen early
This is a standard android feature that was originally found in the SGS but removed in the froyo firmware upgrade, there was no reason given but it was speculated this was to minimise screen burn.
There are a number of widgets on the android market that does the same, Widgetroid is one from the top of my head but even that's a bit of an overkill. Just install to restore the functionality.
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 possibly an LG-exclusive mod to squeeze even more battery life) 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
I was just about to post about this I think it's a bug though... I don't use a Slumber app or anything, I want my screen truly to be always on. But it will turn off occasionally and I don't like that!! I definitely did not have this issue on 4.4W.2
Anyone know what the problem is or how to fix it?
philessthanthree said:
I think it's a bug though... I don't use a Slumber app or anything,
Click to expand...
Click to collapse
Just to be clear, I don't use it anymore and uninstalled it just after getting the 5.0.1 update with its Theater mode. My worry was that having had it installed triggered this behaviour but since you get it without ever installing it I can put that to rest.
I want my screen truly to be always on. But it will turn off occasionally and I don't like that!! I definitely did not have this issue on 4.4W.2
Click to expand...
Click to collapse
Have you ever got it while it is on your wrist..?
Reading this I just removed my g-watch and after a few minutes I see that my screen was OFF. Never happen when I have watch on my wrist the last 2 days. Screen alaways ON and turn on with movement OFF. So yes it is a new feature of the last update 5.01.
Same here, it happened twice on the table, and once on my wrist this morning.
Must be something like the ambient mode in Moto 360 that does this. For one moment I thought I accidentally triggered the cinema mode.
I always take my watch off at work and the screen keeps turning off after 30 minutes. I did a full reset in case it was an overhang from the old version but it's still turning off.
So based on all of the above 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 our friend with the 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, I am trying to time it and confirm it's 30 minutes for me too like StuBFrost says, and may you all please 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, to this end I posted also in the general Android Wear forum but no replies so far. I am going to update that post with our findings and see if we can understand what exactly is this behaviour we are seeing...
Actually, I think it might be a good feature to keep ON in many cases but it absolutely should be an *option*!
I have both options switched on and both work fine except for this new stupid sleep mode that quite clearly hasn't been thought out properly. Surely the theatre mode allows people to turn the display off should they need to and for everythimg else it should do what it did before and stay on.. If it doesn't get "corrected" soon, I will be rooting my watch and putting a custom ROM on it.
StuBFrost said:
I have both options switched on and both work fine except for this new stupid sleep mode that quite clearly hasn't been thought out properly. Surely the theatre mode allows people to turn the display off should they need to and for everythimg else it should do what it did before and stay on.. If it doesn't get "corrected" soon, I will be rooting my watch and putting a custom ROM on it.
Click to expand...
Click to collapse
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 you are 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".
I am running the LG G Watch, version 5.0.1 with accompanying Android Wear app on my phone version 1.0.5
Screen is set to ALWAYS ON.
Tilt to wake is OFF.
It happens BOTH on my wrist and off my wrist. The timing is variable from my limited observation, but I haven't tried to directly time it.
on my lg g watch too
may I ask something related? on mine, it happened to be able to stop display (full black) with a swype from bottom to the top, never been able to do it again. Anybody faced that?
Hi all,
Since Android Wear 2.0 the dock mode while charging with clock doesn't work any longer. When placing Moto on the dock it shows a black screen. When touching the screen de clock appears for a moment and vanishes after about 1.5 seconds. It appears to be a bug. Do you all have this bug or is it just me. Did anyone tried a reset of the watch? I would really like to able to fix it , cause I use that feature a lot.
Same here.
A temporary solution I have found is to enable in developer options 'stay awake while charging' now it stays on. But it is not the same. The display appears to be much brighter. probably because ambient mode (Not sure that's how its called) is not enabled.
Edit: That appears to be the fix. When turning on in settings 'always on display' it works like before. no need to enable stay awake while charging in developers settings.
Although this fixes the issue, I am somewhat disappointed because this option reduces battery life.
I noticed I should have put this question into 'troubleshoot and questions'. I am sorry for placing it here. Perhaps a moderator can place it in the right section for me?
Not a problem here.
Always on is normally activated.
Sent from my m1 note using Tapatalk
I've noticed the same behavior when I upgraded my Moto 360 to AW 2.0
For me, the clock stays on but the background is really bright whereas it used to be black before
Same thing here, background to bright. I don't think this is on purpose. They would probably get out fixed in an upcoming patch(?)
Same here.
I liked docking my watch on my bathroom counter and using it as my clock while getting ready in morning. Now it doesn't stay on and when I tap the screen I can see it for a few seconds. When it is on ....the brightness of the background is terrible.
I sure hope they fix this problem.
I have the same problem
Can't believe there is still no fix for this?
This is really annoying! I was hoping XDA had found an answer. Having always on screen on is not a solution since Moto made a bad design decision on the screen making it best to turn that option off. I assume everyone else's keep awake while charging option doesn't really solve it either because the screen turns off once the battery is full. Anyone think there's a workaround to be found in Tasker and maybe AutoInput (maybe turn always on screen on while charging, off otherwise, or even based on hours). I'm no tasker expert, so I'm not sure if that combo could work on android wear.
Sn0w0nS said:
Hi all,
Since Android Wear 2.0 the dock mode while charging with clock doesn't work any longer. When placing Moto on the dock it shows a black screen. When touching the screen de clock appears for a moment and vanishes after about 1.5 seconds. It appears to be a bug. Do you all have this bug or is it just me. Did anyone tried a reset of the watch? I would really like to able to fix it , cause I use that feature a lot.
Click to expand...
Click to collapse
I have found this to be an issue when I use a charger that is not the Motorola plug that came with the watch. If you switch to the Motorola OEM charger you'll see a lag of about one to two seconds but the clock will always come on.
sebastianraven said:
I have found this to be an issue when I use a charger that is not the Motorola plug that came with the watch. If you switch to the Motorola OEM charger you'll see a lag of about one to two seconds but the clock will always come on.
Click to expand...
Click to collapse
Not on mine. I'm using the factory charger.
vladfan said:
Not on mine. I'm using the factory charger.
Click to expand...
Click to collapse
That's so odd. I'm not having that problem at all
sebastianraven said:
I have found this to be an issue when I use a charger that is not the Motorola plug that came with the watch. If you switch to the Motorola OEM charger you'll see a lag of about one to two seconds but the clock will always come on.
Click to expand...
Click to collapse
I am using Motorola's dock charger. I am positive that the issue lies with Android Wear 2.0 and not the charger. Before wear 2.0 it worked as it should.
I think it's random with AW2.
After flashing a new rom at my mobile, I had to forget and pair again the watch to the Android wear.
From now on, the clock stays on during charging.
This was not the case before that.
Sent from my m1 note using Tapatalk
I have the very same issue (watch paired with a Nexus 4, 5.1.1). Anything I can try? Thanks!
Well, at least this is validation for me. It's been driving me insane, and I'm almost positive it's killing my battery life. I used to be able to stretch a full week on a single charge, but now it's more like a full day.
I'm sure this is what everyone else has been experiencing: there is now a setting called "Always on screen" in Android wear settings. The new behavior for this setting is a strict enforcement of this property; that is, to be either always on or auto off. This seems absurd because before Android wear 2 (not sure if the option existed or not), it seemed to work as we expected, to auto off in active wear but stay lit while docked. There should at the very least be another mode for when docked/standby vs active wear.
Something else that makes it seem buggy is that when the always on screen option is disabled, and the watch is docked and charging, the screen is still faintly lit although only a blank black and no clock. I do think this is a bug and not a feature. For anyone interested, there are also settings for other things you might not be using. I'm turning them off and pray the battery gets better.
wesswei said:
Well, at least this is validation for me. It's been driving me insane, and I'm almost positive it's killing my battery life. I used to be able to stretch a full week on a single charge, but now it's more like a full day.
I'm sure this is what everyone else has been experiencing: there is now a setting called "Always on screen" in Android wear settings. The new behavior for this setting is a strict enforcement of this property; that is, to be either always on or auto off. This seems absurd because before Android wear 2 (not sure if the option existed or not), it seemed to work as we expected, to auto off in active wear but stay lit while docked. There should at the very least be another mode for when docked/standby vs active wear.
Something else that makes it seem buggy is that when the always on screen option is disabled, and the watch is docked and charging, the screen is still faintly lit although only a blank black and no clock. I do think this is a bug and not a feature. For anyone interested, there are also settings for other things you might not be using. I'm turning them off and pray the battery gets better.
Click to expand...
Click to collapse
What r u talking about?
Always On was there since Android Wear 1.5.
And come again?
1 week use of the watch with 1 charge?
How did u manage to do that?
By turning on the watch for 2 hours every day?
Sent from my m1 note using Tapatalk
I have run into these issues several times. They seem to be related, but I can't say for sure.
Every now and then while I'm actively using the phone, 1/2 the screen will go away and the phone will be unresponsive. If I shut off the screen, then turn it back on, it usually clears up. Sometimes the screen won't come back on. It stays off no matter what buttons I press. So I put it on the charger, that triggers the screen turning on and everything is back to normal (the battery is always over 50% or more at this point). Yesterday this got to a point of happening several times in 1/2 hour, so I ended up rebooting to see if it would clear it up. This issue did not come back since then.
On a similar note, I was playing a game this morning in a dark room with the brightness turned all the way down. I was being very active in interacting with the screen. Every now and then the screen would go black, except for the notification bar. I could still see that (time and statuses of things running). The screen would not respond to any touches, so I would shut the screen off and turn it back on and all would be good. This happened 2-3 times over a 45 min period. I play this game quite often, but not usually in the dark and often not as actively as I was doing. My resolution is set in the middle (FHQ+ I think it's called).
Has anyone else run into anything like this?
This S9+ snapdragon through Verizon just seems to be plagued with so many minor issues. I've never had a new phone with this many problems.
Brokk said:
I have run into these issues several times. They seem to be related, but I can't say for sure.
Every now and then while I'm actively using the phone, 1/2 the screen will go away and the phone will be unresponsive. If I shut off the screen, then turn it back on, it usually clears up. Sometimes the screen won't come back on. It stays off no matter what buttons I press. So I put it on the charger, that triggers the screen turning on and everything is back to normal (the battery is always over 50% or more at this point). Yesterday this got to a point of happening several times in 1/2 hour, so I ended up rebooting to see if it would clear it up. This issue did not come back since then.
On a similar note, I was playing a game this morning in a dark room with the brightness turned all the way down. I was being very active in interacting with the screen. Every now and then the screen would go black, except for the notification bar. I could still see that (time and statuses of things running). The screen would not respond to any touches, so I would shut the screen off and turn it back on and all would be good. This happened 2-3 times over a 45 min period. I play this game quite often, but not usually in the dark and often not as actively as I was doing. My resolution is set in the middle (FHQ+ I think it's called).
Has anyone else run into anything like this?
This S9+ snapdragon through Verizon just seems to be plagued with so many minor issues. I've never had a new phone with this many problems.
Click to expand...
Click to collapse
As a followup, I think I have found the problem. It seems to be with a product called Game Tuner. It can black out the screen while leaving the app running in the background. I think it is buggy. Doesn't seem to be a way to shut it off though.
Brokk said:
As a followup, I think I have found the problem. It seems to be with a product called Game Tuner. It can black out the screen while leaving the app running in the background. I think it is buggy. Doesn't seem to be a way to shut it off though.
Click to expand...
Click to collapse
I was able to uninstall, then install an older version of Game Tuner and the problem that was easiest to reproduce was fixed. Hopefully this will prevent the weird 1/2 screen thing as well.
Hi everyone,
I'm sure this question has been asked by many users, but for some reason none of the ones I read seem to match the problems with my S6 Edge.
The other day I was playing music Youtube on my 3 year old S6 edge (for like 30min) and I forgot that autoplay was off, so the screen turned off, within 10 seconds of it doing so, I pressed the home button to 'wake it up again', but the screen won't turn on. the phone reboots once by itself but the screen remains off, and I know the phone's on because of the blinking LED light of messages, or the red when it is charging. The backlight lights up too, and it seems the screen's touch system works, as I am able to turn it off. I wait for a couple of minutes before hard resetting it (Volume down+Power key) and the screen lights up again and it's all good.
However, I have noticed this happening way too many times lately and noticed a bit of a trend. It usually happens when I use any app (except the music app) for 30 minutes or more, and if I manage to keep the screen awake, it works perfectly fine. The problem begins when the screen sleeps due to inactivity, or is voluntarily turned off. It also heats up quite a bit.
I am on the latest firmware, and have already formatted the phone once and tried, yet the problem persists. With that I suppose we can rule out that the problem is due to any third party app, or due to not updating the firmware. I also replaced the motherboard last year at a reputable phone repair shop, so I think it's a safe bet to say that's not the issue, but I am not 100% sure (the problems began 6 months after I 'unrooted' the phone, after replacing the motherboard).
As I kept going with it, it kept getting worse until eventually, now the phone is in a constant state of 'screen off but phone on', where it charges, plays music, can receive calls and messages, but cannot turn on the screen. I kept trying at 15 minute intervals to no avail, even though the phone is at room temperature.
Before I go blow a couple more 100 bucks on fixing this, I would like to hear all of your opinions on what the problem might be (and hopefully the solution).
Thanks in advance.
i have the same problem but i have the galaxy s7 edge. often i can unlock my phone but my screen will stay black. no aod or backlight but the vibration from unlocking with fingerprint is there and the sounds of opening an app are also there...