Does anyone know if this is possible, either in Android Wear or on the watch itself? Right now the backlight remains on (but very dim) and drains the battery too much to make it worth using, but I think it would still be visible enough with it off entirely.
Related
I'm looking for an application or something that will keep the backlight off at all times while it's running. Sometimes late at night out in the country I don't need it to be able to see the screen very well and I'd like to save battery power as much as possible. Battery life is a constant concern when you're away from AC outlets.
The app is called LUMOS (it changes the backlight setting depending on the light around you) you can find it here it saves a lot of battery also NueDynamicClock is a must have if you want longer battery life I hope it helps
I have a similar problem - how do I prevent the backlight timeout from triggering ?
I use g-watch countdowntimer and when using that I wan the backlight to remain on but unless I keep touching the screen the backlight goes off after a few minutes.
Is there a registry key or something I can change to make g-watch an exception ? - I know my TOmTOm works fine
Sorry to clarify, I have found my problem is not backlight related and hence will start new thread.
I was thinking that since the OLED screen does not use any backlight, lighting up a few pixels just to form a little led blinking would not tax too much the battery.
I don't know, however, whether waking-up the phone entails significant increase in battery usage. A middle solution would be to wake it every 2 minutes for 10 seconds in order to display the notification and the let it sleep again.
What do you think?
Sounds good good but im not to sure about that... there was another post about having the illuminating back button flash, maybe both menu and back buttons.. alternating between each one with a speed setting?
i love the idea, but the screen is 'off' for a reason...
first of all i don't know if oled screens can 'burn' (meaning the pixels are still showing when they are suppost to be 'off', because they have been 'on' to long)
Also, if it means the chips that control the screen have to be active instead of inactive, your battery drain may be kinda big....
I don't know that OLED would have burn-in (that's more a CRT thing), but they might well burn out - they do have a finite lifespan.
But you're probably right, it would likely mean that the phone couldn't completely go to sleep.
Mithent said:
I don't know that OLED would have burn-in (that's more a CRT thing), but they might well burn out - they do have a finite lifespan.
But you're probably right, it would likely mean that the phone couldn't completely go to sleep.
Click to expand...
Click to collapse
well, in such a case we could rotate randomly the pixels to be lit up (as in real old time screensavers).
With regard to out of sleep battery consumption you have a point. Maybe we could just wake it up for a few seconds and then have it sleep again. In any case if we assume that the major battery draw is the typically screen, then such an arrangement might prove to be acceptable - at least in some cases.
Why not use the backlight on the menu and back button? They shouldn't use too much power or get burned?
Keychar said:
Why not use the backlight on the menu and back button? They shouldn't use too much power or get burned?
Click to expand...
Click to collapse
Yes - I agree this is a very good alternative - yet I do not know how bright these leds are.
Nevertheless, I noticed that the screen is able to display a big animated icon of the battery charging even when the phone is off! (I just received it and I put it in the charger). Thus, I assume there is some kind of control of what the display shows without having to wake-up the system (at least the whole of it).
If this is the case, we could have some led like notification even when the android is in sleep!!
what you say is not necessarily true.. that icon is when the phone is off. which does not translate to being able to display something on a sleeping phone when it is on.. two totaly different issues ..
lgkahn said:
what you say is not necessarily true.. that icon is when the phone is off. which does not translate to being able to display something on a sleeping phone when it is on.. two totaly different issues ..
Click to expand...
Click to collapse
True. I will check whether it is displayed when the phone is on sleep (still off and charging). It implies, however, that the screen can be controlled (also?) independently of the OS.
(all in all the touch buttons respond / light up when touched though the phone is off and charging).
Go guys!
I'm waiting this modification to buy this phone!
I belong to you!
Up !
Very funny topic one year later !
NoLED, BLN ...
The community is very powerfull !
Thank you all
Guys, just search NoLed on market and it's already made ^^. However, following neldar thread on BLN, NoLed use about 10% more battery per hour than off screen. BLN which is found in most of the kernel ( Except damianGTO one ) use about 1% more battery per hour and turn on the backlight of the touch key. Hope this will help you
Firstly I love this phone. After working through 4 Samsung Galaxy S's to finally ask to be switched away from it to this, I was very happy.
This phone is rock solid.
BUT. I have a problem. I like to use maps or nav in my car. I have the phone plugged in but after the timeout period the screen goes dim. I'm normally OK with that but the dim setting on this phone seems to be ridiculously dark!
To your knowledge, without rooting it to get the Cyanogen settings, is there a way to brighten the dimmed level of brightness?
I have tried disabling the auto-brightness and bumping it up but still after the timeout period it dims very dark.
How about a toggle or widget to keep the screen always on? There are quite a few available I reckon. I know its one extra step to carry out whereas you are looking for something more automated. Maybe there is an app that can let you make a list of apps that enable screen always on?... Not sure about that but worth a look eh?
i do use a switch with Extended Controls widget.
the problem isnt that it dimms, it's that when it does dim it is far too dark.
When the samsung went to the dim setting it was still viewable.
If i remember right when i had it plugged in it would not dim if i was viewing maps.
anyways, the phone as it is is useless when it dims. i can touch the screen to bring back the brightness. I can set the timeout period to 30 minutes, but all of this requires that i re-activate the screen to bring it back.
i guess i am seeing one more reason to root the device. i'm nervous about rooting and would prefer to not have to if i dont need to.
groaner said:
Firstly I love this phone. After working through 4 Samsung Galaxy S's to finally ask to be switched away from it to this, I was very happy.
This phone is rock solid.
BUT. I have a problem. I like to use maps or nav in my car. I have the phone plugged in but after the timeout period the screen goes dim. I'm normally OK with that but the dim setting on this phone seems to be ridiculously dark!
To your knowledge, without rooting it to get the Cyanogen settings, is there a way to brighten the dimmed level of brightness?
I have tried disabling the auto-brightness and bumping it up but still after the timeout period it dims very dark.
Click to expand...
Click to collapse
This is a characteristic of the software that you are using. The software needs to establish a WAKE LOCK in order to keep the screen bright. If it isn't working, then there is something wrong with the software you are using. I suggest using COPILOT for navigation. It works properly.
dhkr123 said:
This is a characteristic of the software that you are using. The software needs to establish a WAKE LOCK in order to keep the screen bright. If it isn't working, then there is something wrong with the software you are using. I suggest using COPILOT for navigation. It works properly.
Click to expand...
Click to collapse
agreed, the software is probably working properly. google navigation does not time out. google maps does and they dont give you an option to have it not time out when plugged in. silly if you ask me.
i dont mind that as much as i mind how much it dims.
Does anyone else find that the desire z dims too dark?
anyways, i may be beating a dead horse here. trying to get blood from a stone and all that.
well if anyone has any other ideas that would be helpful. thanks for the suggestions thus far.
Does anyone know why when I turn off auto brightness, my screen gets so much brighter? Even if I have brightness set as low as it can go, it still seems alot brighter than it should be. Which must kill the battery.
Sent from my R800a using XDA App
If you'd like to compare battery life between the two theres apps for it
But as its been said, better for the battery to have the light a little brighter than constantly be changing.
If you're rooted, Rootdim (search the Market, I can't post links yet) allows you to power down the backlight below the lowest option in Display Settings. It's nice for using the phone in the dark or with a bedside lamp and should minimise battery use if you've got auto-brightness turned off as well.
The only worry is the reviewer on the Market who said its lock option kept the backlight on (at a dim setting) after shutting the screen off on his Droid Bionic but I can't say I've noticed that on my Play.
Thanks, that Rootdim is what I needed.
I tried setting it to MAX, who in the hell needs it that high?! I didn't even know it could go that high, make it a white screen and you've got a flashlight!
Has anyone noticed ambient screen mode working differently since the update, or is it just me? With all the talk about better battery life, I thought I'd try keeping ambient mode on to see what kind of battery life I'd get. I didn't regularly use ambient mode before the update, but I did play around with it. Before the update, it seemed that the watch stayed dimly lit (ambient mode) most of the time while wearing it, but bringing my wrist up would make the screen come fully on. Now, it seems like it goes completely off immediately when I drop my wrist, and when I raise it, it lights up dimly in ambient mode, and I actually have to touch it to get the fully-on mode. It does seem to be more sensitive and reliable coming (dimly) on in ambient mode than it is in non-ambient mode, but still, in bright light conditions, it means I actually have to touch it before I can even see it (or use it).
Am I the only one seeing this?
Nothing changed, that's the way it's always worked
Sent from my XT1080 using XDA Free mobile app
Are you sure? I don't remember it being that way, and if that were the case, Ambient mode would be BETTER for battery life than regular mode, because the 360 goes off just as fast as regular mode, and won't come fully on unless you actually touch it. When I played around with it before, I'm positive it would come fully-on when I raised my wrist. Now it never will.
jt3 said:
Has anyone noticed ambient screen mode working differently since the update, or is it just me? With all the talk about better battery life, I thought I'd try keeping ambient mode on to see what kind of battery life I'd get. I didn't regularly use ambient mode before the update, but I did play around with it. Before the update, it seemed that the watch stayed dimly lit (ambient mode) most of the time while wearing it, but bringing my wrist up would make the screen come fully on. Now, it seems like it goes completely off immediately when I drop my wrist, and when I raise it, it lights up dimly in ambient mode, and I actually have to touch it to get the fully-on mode. It does seem to be more sensitive and reliable coming (dimly) on in ambient mode than it is in non-ambient mode, but still, in bright light conditions, it means I actually have to touch it before I can even see it (or use it).
Am I the only one seeing this?
Click to expand...
Click to collapse
Just tried it out and I remember it being different as well. But I now use facer. And some faces do not show when dimmed. You have to manually update that setting in facer or whatever program you are using. But saying that if you tilt your watch away from you further, the face will shut off and for me, when it becomes more horizontal, the face dims on. So, yes, it worked like it did as it first did, but to me is a bit more sensitive to the angles of the watch.
Nevermind. I saw in another thread that someone recommended restarting the 360 after the update. Did that, and now it's working as I remember, where it still comes on fully when I raise my wrist. It was the fact that I actually had to touch it to make it come on fully that was bothering me. Now, it comes on dimly as I start to raise my wrist, and fully when I fully raise my wrist, without the need to touch it. That's as it should be.
I guess the take-away is that if the 360 is doing something weird after the update, restart it.