When I have my nexus one set to automatically adjust brightness, it doesn't seem to do anything.
I can move it between dark and bright environments and the screen brightness doesn't seem to change at all. Am I missing something or is this feature not working on my phone?
It works fine with mine. I just clicked auto in the brightness setting. Make sure you didn't accidentally change it to a different setting with the settings widget that is by default on the first home page to the right.
works fine on mine yet not a feature i use....i just set it statically.
I find the auto-brightness to be too dim for my liking. It would be great if you could adjust the overall brightness while still maintaining the automatic scaling.
Turns out it does work, it just need to be *really* bright to make it change.
It doesn't change really at all in my office between switching the lights on and off (even though that's a really big change in light levels to me). However, if i go outside, it does get brighter.
As you say though, it does seem to be set a bit low (hence it not brightening up when my office lights are turned on I guess).
If I enable auto-brightness on mine, it seems to constantly vary the brightness in my office. It's annoying as crap and I turned it off. Am I the only one?
It's probably taking a look at the available APIs to see if it's easy to write a quick app to do auto brightness with settings to be able to tweak it.
The auto-brightness feature changes constantly for me as well.
I 'm also having issues of the varying brightness when using auto-brightness -- even though the lighting in my environment has not changed and I avoid contact with the light sensor. It's VERY annoying.
I've since switched to using a static setting for the brightness.
auto brightness was one of the first things i turned off. it was way too dim for me
Not bright enough for me. Doesnt seem to change much.
I do see the variability occasionally. Most of the time it's stable, but it will take spells of shifting up and down repeatedly. Glad to know I'm not alone.
Auto bright annoyed me as well when I first got the phone. Then I realized where the sensor is (top left) and what it was responding to. Depending on where I'm sitting, what light sources are behind me, in front of me but reflecting off of me. It's usually just responding to a light source that's just withing view of its sensor. Also, my hand has shielded the sensor more than just a few times, confusing the sensor.
Now I leave auto bright on all the time, and it more often than not does a good job.
IMHO this is one of the few broken features on the phone. In continuous lighting it jumps from bright to dim to everything in between like a jack rabbit on speed. I still use it to save battery life but it pisses me off regularly.
am also having this problem. it constantly goes much brighter, and then, suddenly goes back to dim.. very annoying... however, the light sensor for calling works well... so, is it a software issue.. hope it gets google's attention and gets fixed in next update...
Bicster_ said:
If I enable auto-brightness on mine, it seems to constantly vary the brightness in my office. It's annoying as crap and I turned it off. Am I the only one?
Click to expand...
Click to collapse
+1 so I also manually go between three on the widget
Note that the light sensor is under the glass on the front of the phone. Some cover-all cases cover this, and if you use one of these I assume your phone will remain on the dimmest setting.
In general, while indoors it will remain on the dimmest setting (for me anyway), but rise to the necessary full brightness when in sunlight.
w00yee said:
am also having this problem. it constantly goes much brighter, and then, suddenly goes back to dim.. very annoying... however, the light sensor for calling works well... so, is it a software issue.. hope it gets google's attention and gets fixed in next update...
Click to expand...
Click to collapse
There are two sensors, one is a light sensor and the other is a proximity sensor to detect when you've taken the phone from your ear. I think you're referring to the second.
w00yee said:
am also having this problem. it constantly goes much brighter, and then, suddenly goes back to dim.. very annoying... however, the light sensor for calling works well... so, is it a software issue.. hope it gets google's attention and gets fixed in next update...
Click to expand...
Click to collapse
+1 constant occiliation on dimmness levles under consistant light. It goes from way too dim, to just right then back dark again. I too hope that google will correct this with the next update. Hopefully the patch gets pushed soon, i'd like that extra memory
Related
Hey guys,
do you think it's possible to wirte a program which automatically can change the backlight according to the actual daylight condition.
Maybe it is possible to start the program when you wake up your device. then the program turns on the built in (front) camera for about a second or maybe more. The camera "checks" out the light intensity. If its very bright the backlight condition is set to the max.
his is only a idea. I'm thinking of it because for example today it's a very sunny and i can almost read nothing on the display of my touch cruise!!
What do you think about it?
greetings
any idea?
Or does any software like this exist?
Maybe the guy who wrote this program below could be of assistance:
http://forum.xda-developers.com/showthread.php?t=379270
Well, it doesn't have to be so hard...
All we need is a small service that reads from a file the approximate sunrise-sunset time and alters the brightness accordingly. If anyone has the time, he can additionally take advantage of the current time zone and calculate those limits automatically all year long!
Destinator 7 does the exact same think by turning night colors on and off. It is actually better than a build in brightness sensor because it never fails!
Nevermind...did not read the question thououghly
Yeah good ideas,
but a time sceduled scenery has also disadvanteges. When its clowdy outside it causes unnecessary battery consumption.
MVBklight 1.4.2 is not working on my polaris!!
w04g005 said:
Yeah good ideas,
but a time sceduled scenery has also disadvanteges. When its clowdy outside it causes unnecessary battery consumption.
Click to expand...
Click to collapse
I come from a rather sunny country (greece) so I really missed this!
Anyway, those PDAs have actually very low brightness screens. In a bright day you cant actually see anything. On the other hand, I have yet to see a rainy/cloudy day that requires a reduction to the maximum brightness level. Overall I think that a time scheduled solution should be the best solution for no sensor-equipped devices.
papajohn said:
I come from a rather sunny country (greece) so I really missed this!
Anyway, those PDAs have actually very low brightness screens. In a bright day you cant actually see anything. On the other hand, I have yet to see a rainy/cloudy day that requires a reduction to the maximum brightness level. Overall I think that a time scheduled solution should be the best solution for no sensor-equipped devices.
Click to expand...
Click to collapse
I second that! Even though I'm not from Greece but it's never too bright during the day. Right now my solution is to map the camera button to backlight so I can change it quickly.
Changing the brightness according to the time of day would not be as helpful as changing it according to the ambient light level. If you walk inside a dimly lit building during the day, you don't need the backlight to be as bright as if you were outside. Also, even outside, a cloudy day can be considerably dimmer than a sunny day.
jfeldredge said:
Changing the brightness according to the time of day would not be as helpful as changing it according to the ambient light level. If you walk inside a dimly lit building during the day, you don't need the backlight to be as bright as if you were outside. Also, even outside, a cloudy day can be considerably dimmer than a sunny day.
Click to expand...
Click to collapse
I totally agree, but given the fact that there is no ambient light sensor in our devices I dont think that we can do any better. Two scales, one for day and one for night and we are OK for most cases. Yes, as you point out this strategy fails but it is better than:
1. No brightness change at all
2. Manual changes.
papajohn said:
I totally agree, but given the fact that there is no ambient light sensor in our devices I dont think that we can do any better.
Click to expand...
Click to collapse
Thats the crux. Some devices especially the newer ones have a camera on the front. I'm no photo-expert but i think every camera is a "ambient light sensor".
The camera also reacts on different light conditions. You can see this by turning on the fps function. But i agree that it would be a lot of work.
Maybe we have to wait till more people and programmers own htcs with such bad displays like the polaris.
Titan Photo Sensor
I found myself thinking about this auto-backlight topic on my way home tonight after a long trip using my 8600 as a GPS. The screen went from being a clearly-visible screen during the day portion of the trip to a flashlight in my eyes at night. While I knew I could adjust the backlighting manually, I didn't want to mess with it while driving. Also, living in Arizona, I can barely make out the screen when in daylight unless the screen is on maximum brightness, but max brightness is horrible on battery life, so I would rather not set it to that by default.
Anyway, the Titan has a photo sensor on the keyboard which is used to determine dim lighting conditions and automatically illuminate the keyboard. I'm not sure if the exact lighting value being detected by the photo sensor can be read, but if it can be, then it should be relatively easy to write an application that would automatically adjust the backlight setting whenever the keyboard is slid open.
The application could both use location-based sunrise/sunset algorithms to set the default backlight value based on time of day, and also allow the setting to be overridden momentarily (perhaps only until the screen is turned off again) by opening the keyboard and sampling the ambient lighting conditions.
Is it just me or does everyone's Epic's have terrible brightness sensor hardware/software? My sensor seems to have about 2-3 settings of brightness, and goes from completely dim to super bright in random situations and nothing in between.
Cyanogen just posted on his twitter that in the past he changed the sensor's abilities through coding modifications. Could we do something of the sort for the Epic's sensor?
Agreed. The sensor is horrible. Also, the transition between brightness settings when set to automatic is near instant instead of slowly transitioning, which makes it more obvious that its changing brightness.
I would agree that it is terrible. Mine also send to sometimes turn auto brightness back on if I've turned it off.
It would be great if someone found a way to mod the code for it!
Sent from my SPH-D700 using XDA App
I thought the screen was just too bright at its lowest setting. Fortunately someone came up with a fix for it that can be found in the developer section. As far as the automatic sensor I would suggest turning off "Power Saving Mode" in the Settings>Sound & Display as well. I've read somewhere that this causes the brightness level to vary on its own.
cfiblc said:
I thought the screen was just too bright at its lowest setting. Fortunately someone came up with a fix for it that can be found in the developer section.
Click to expand...
Click to collapse
Hehe, that was me. Stay tuned for more. I have coded up and will post, tonight, a new version that will let you modify the brightness curve (from the command line, for now)
As for automatic mode, I have figured out how to modify some aspects of it at the kernel level, such as the ambient light thresholds at which it switches to a different brightness level. By modifying the brightness curve, we can achieve at least some more control. But to make it really good may be significantly harder.
Personally, since manual brightness is always available by swiping horizontally on the status bar, I have little desire to use auto mode anyway.
- linuxuberant
The sensor is actually pretty sensitive. It's just that Samsung chose to have a really small range of brightness steps for automatic brightness.
Firon said:
The sensor is actually pretty sensitive. It's just that Samsung chose to have a really small range of brightness steps for automatic brightness.
Click to expand...
Click to collapse
More like they installed an awesome dimmer switch and lights, but the fixture only does three modes; high, medium, and still pretty damn bright.
I noticed that the brightness only brightens but never dims back in automatic brightness display setting. I can reproduce this easy with turning the lamp on my desk on and off. It only goes back to the lower brightness if turning the screen off and on again.
Noticed this too but seems to only occur when I use a widget to toggle between Auto and 100%.
If I leave the setting in Auto from within settings then it seems to work. Brightness widgets seem to break the auto functionality.
Hmm, I don't use a brightness widget. The light of the softbuttons go on if I cover the light sensor, but the screens stays in high brightness.
Strahlenkanone said:
Hmm, I don't use a brightness widget. The light of the softbuttons go on if I cover the light sensor, but the screens stays in high brightness.
Click to expand...
Click to collapse
Must be an all around bug then. If you turn the Atrix off and back on then the auto brightness functionality is restored.
Strahlenkanone said:
I noticed that the brightness only brightens but never dims back in automatic brightness display setting. I can reproduce this easy with turning the lamp on my desk on and off. It only goes back to the lower brightness if turning the screen off and on again.
Click to expand...
Click to collapse
This must be an Android thing. My Atrix does the same thing, as did the Nexus One I had before. I've had several (high end) Nokia's that dimmed/brightened perfectly. After 5 seconds, they would brighten (or dim) accordingly. I was hoping Motorola was better at making phones than HTC (the KING of bad battery life). We ALL lose here. Our precious battery life is being drained by the poor execution of a simple function.
This is a stock android thing (problem). Custom ROMs can allow it to dim and change brightness smoothly rather than in discrete steps (Cyanogen).
That's what I thought. I found this free app called "esdimmer". It supposed to be for Galaxy phones, but it's somewhat working on my Atrix. Does this function work any better in Gingerbread?
Sent from my MB860 using XDA App
Well it's good to hear that it's a stock android problem and not the actual phone. I did find a way to get around this problem but it's very limited. You can get the screen to dim by first putting the phone into standby and then press the standby button once again (which gets you into the lock screen). You'll notice that the screen then dims (if coming from a well lit area/room to a darker one).
When I'm in a light room the screen goes brighter but if I walk into a darker room, the screen doesn't dim unless I lock and then unlock the screen.
Anyone else having similar issues?
Yep got the same here. Thought I had a faulty ambient light sensor but obviously not.
Sent from my SM-G935F using Tapatalk
Just tried it by covering the light sensor to make sure, no problem here (G935F). My only concern related to brightness is that the s7 just has auto brightness, but no adaptive brightness.
Uncheck the auto box and recheck. Then don't touch the slider. It's usually because in marshmallow the slider moves with the auto bright and most people touch it which makes it hold position.
jackdforme said:
Uncheck the auto box and recheck. Then don't touch the slider. It's usually because in marshmallow the slider moves with the auto bright and most people touch it which makes it hold position.
Click to expand...
Click to collapse
There seems to be a bug somewhere still. I just tried to move the slider while auto brightness is ticked and to cover the light sensor afterwards again and it still worked and to my surprise it even took into account that I lowered the brightness and took also a lower brightness at the covered state and took my initial setting after uncovering, pretty nice, so there is indeed still adaptive brightness. After ticking und unticking auto it went back taking the default steps for brightness as before.
Having the same issue here
Definately not touched the slider.
Also, I have tested the light sensor and it appears to work fine so definately a software issue. Though I imagine we will see some software updates to fix bugs shortly after the official release date.
So you can adjust the slider with the box checked and get various levels of auto? Does it learn?
jackdforme said:
So you can adjust the slider with the box checked and get various levels of auto? Does it learn?
Click to expand...
Click to collapse
Yes.
I can't tell for sure, when I change further steps the previous seems to stick, at least to some extend so there is a logic behind it, but I can't tell for sure if it really is based on each step and sets it accordingly or if it's just changes the range it operates in. Anyways I'm a happy camper.
Also, I could reproduce the device not changing the brightness, when I put it to full at darkness it won't move anymore in auto. But as soon as I lower it again it will also change accordingly again, maybe at those with the stuck brightness the min brightness is only raised, but not lowered anymore, but just an assumption and doesn't help anyone atm unfortunately.
Use lux in play store
Sent from my SM-N920W8 using Tapatalk
https://play.google.com/store/apps/details?id=com.velis.auto.brightness
This is the first Galaxy phone I had, that Auto brightness actually works the way I like it.
It seems to be working fine now. It just takes a few seconds for the screen to dim (maybe I was being impatient).
After testing it further it's actually really good auto brightness.
It works, just takes some time to adjust to the lighting. Maybe the default settings are set to a certain time. Maybe with root we can adjust this..
AngioNicholai said:
It works, just takes some time to adjust to the lighting. Maybe the default settings are set to a certain time. Maybe with root we can adjust this..
Click to expand...
Click to collapse
It seems to only do it quickly when the device is lay down (as 954wrecker said). Maybe Samsung did that so it doesn't annoy you when using your phone.
this is definitely a bug imo... the auto brightness doesn't change for me either...
CuBz90 said:
When I'm in a light room the screen goes brighter but if I walk into a darker room, the screen doesn't dim unless I lock and then unlock the screen.
Anyone else having similar issues?
Click to expand...
Click to collapse
I also have an auto briteness issue, when I disable AutoBrite and set it manually about half my apps override the setting and enable AutoBriteness in the app's screen usually dimming the screen? SpadesFree one example and I do not see an override in the app.
Confimed that I'm having same issue, auto brightness not adjusting and slider not movingoing. Have to move it manually
Same issue. It needs to be fixed manually by editing services.jar (root needed)
Nothing else will work. None of google play apps will help with that issue. Does not matter what you do, it will always dimming if you don't fix it in framework.jar
Try it out: http://forum.xda-developers.com/s7-edge/development/auto-brightness-bug-try-fix-t3339858
Hey i received an update for the Always On Display (update number 1.1.22)
after i updated the app i noticed that the AOD is much dimmer in some places than it was before
also i noticed that my girlfriend's s7 AOD is much brighter than mine in the same areas (they were the same before the update)
is there a way to undo the update? (was update through galaxy apps)
Thanks in advance
As far as I know, the AOD dimming is introduced in APD1 and later firmware updates. What is your firmware version ?
Yep, they pretty much ruined the entire feature. Its now too dim to see in anything but outside in full sunlight. Indoors its pretty much just a black screen now. Been a month, they still havent fixed it.
The update is to solve screen burning, this is why is dimmer now.
Cheers.
No, it never burned in since it was always moving. Now it is so dim that i cant even see it, rendering the entire feature useless.
It must be a bug, it cant possible be intended.
Dunno if you tried it but I noticed my AOD accomodates with the lighting condition in the room but im often sitting in the corner where I face the light so when I turn it off I face it to the light so the AOD would be bright. weird habit for now huh hahahah
Still annoys me to hell that they basically took one of the best features of the phone and essentially ruined it (so dark its unreadable indoors, if you dont have a ceiling light shining straight on the sensor). Just by a single little forced software update. Why couldnt they just provide a simple brightness slider in the AOD settings?
Third party AOD apps exist that allow complete brightness control, but sadly none of them run with the samsung AOD "tech" so they all keep the phone hot and running as if fully awake, draining battery more than just the pixels being lit do.
just done the update this morning and I didn't notice difference in the brightness of the AOD. it remained the same. are you sure your dim situation is not caused by some setting, which was reset after the update ? For example, It happened to the fingerprint lock setting in my phone, which become corrupted, unusable after the update. I need to delete the previously saved fingerprint and add a new one again for it to work.
100% certain it was the update. I literally can barely see the AOD indoors anymore. Before the update it was always very bright and vibrant.
Baleur said:
No, it never burned in since it was always moving. Now it is so dim that i cant even see it, rendering the entire feature useless.
It must be a bug, it cant possible be intended.
Click to expand...
Click to collapse
How often does your clock move on your screen, because mine stays stationary unless I turn the screen on and it turn it off again, then it'll change to a different position.