Is there a way to tweak the behaviour of the auto-brightness backlight? At the moment it correctly goes up to full brightness in sunlight, but it doesn't go as dim as I would like under artificial light. At home, after dark, under electric light, I can manually turn the screen brightness down to the minimum level, and it's still bright enough - the auto setting is much brighter than that(although clearly much dimmer than it is in sunlight, so it is doing something).
Can this be tweaked? Failing that, is there an easier way to control the brightness manually - something I can keep running all the time, and which doesn't require the stylus to change the setting?
Try GLight
http://www.ageye.de/index.php?s=glight/about
JustBored said:
Try GLight
http://www.ageye.de/index.php?s=glight/about
Click to expand...
Click to collapse
Thanks, I'll give that a try.
I find Lumos to be more stable and reliable
http://forum.xda-developers.com/showthread.php?t=450318
Ok I havn't tried either of them before but I just installed G-Light.
After a bit of config. it's ok. You need to give each backlight number a wider setting.
Otherwise it'll just flip back and forward in brightness.
So far G-Light is proving rather dissapointing. The phone's built-in "Auto" setting works well, apart from the fact that the brightness doesn't go low enough in dim light - in particular, it manages to choose a good level and then stick to it. G-Light, by contrast, keeps changing the brightness up and down all the time.
I think the notion of having absolute brightness bands may be the wrong way to go. You really want a set-up where the threshold values are in different places depending on whether the light is getting brighter or dimmer. So, as the light fades, you cross a threshold and dim the screen - but when the light goes slightly back up over that threshold, you don't brighten the screen again until it gets significantly higher than that. That way, regardless of the light level, the screen brightness will be steady unless the ambient light level is changing a lot. If you use single threshold values then whenever the ambient light happens to be very close to a threshold value you will always get the brightness going constantly up and down.
Edit: some of the things Lumos does (like averaging across multiple readings) sound hopeful, though. I'll give that a try.
Shasarak said:
So far G-Light is proving rather dissapointing. The phone's built-in "Auto" setting works well, apart from the fact that the brightness doesn't go low enough in dim light - in particular, it manages to choose a good level and then stick to it. G-Light, by contrast, keeps changing the brightness up and down all the time.
I think the notion of having absolute brightness bands may be the wrong way to go. You really want a set-up where the threshold values are in different places depending on whether the light is getting brighter or dimmer. So, as the light fades, you cross a threshold and dim the screen - but when the light goes slightly back up over that threshold, you don't brighten the screen again until it gets significantly higher than that. That way, regardless of the light level, the screen brightness will be steady unless the ambient light level is changing a lot. If you use single threshold values then whenever the ambient light happens to be very close to a threshold value you will always get the brightness going constantly up and down.
Edit: some of the things Lumos does (like averaging across multiple readings) sound hopeful, though. I'll give that a try.
Click to expand...
Click to collapse
Let me know how Lumos is.
Yes as I said earlier you need to widen those settings.
For now I have 5 set to 0-81
6 set to 82-200
8 set to 201-600
10 set to 601-1000
All the rest are disabled by setting the values to -1 to -1
HeavyComponent said:
Let me know how Lumos is.
Click to expand...
Click to collapse
Lumos is also proving dissapointing. It's partly the fault of the hardware - the sensor seems to read 0 even in surprisingly bright light, so the app has no way of telling whether you're at a light level where backlight 1 is appropriate or a light level where backlight 3 is appropriate - both read 0 on the sensor. (This is probably why the default auto option doesn't go below 3 in the first place).
As for Lumos, the author needs to realise that perception of brightness is actually based on an exponential curve. That means that all of the values between level 1 and level 5 are somewhere between 0 and 80 sensor reading. The graph interface is useless for editing custom values with that level of precision - it's trying to squeeze over 2000 values into less than 800 pixels of screen space, and the pixels are tiny! I think you can edit the values directly in the settings.txt file, but that's fiddly - there should be spinboxes, really (as with G-Light).
In any case, you don't want to be editing the values directly! What you want to be doing is taking the phone out of your pocket, looking at it, and thinking "hmm, the screen is too bright at the moment" then adjusting the brightness to whatever level is comfortable for the current ambient light level. The programme should then interpolate the curve that you want, and progressively refine it each time you decide it isn't quite right and tweak the brightness.
I haven't tried to Lumos program yet, but I've been using Glight for a few days. At first I had some issues with it but then I realized that you have to turn the auto light adjustment off in settings first. If not, they'll both be fighting against one another.
Also, you have to set your thresholds pretty carefully as has been already stated. Mine is set to go bright only in bright outside and lowest in a dark room with no light at all.
1 0 to 5
3 10 to 799
8 800 to 2500
I've got mine set low for better battery life and the screen is always readable to me no matter what anyway.
Also, if you're using a the snap on rubber protector (I got a T-Mobile one) it will interfere with the light sensor. I just got one and the lighting is all over the place now. Time to order a full body screen protector.
GLight doesn't seem to work for me. keeps crashing, and the settings don't seem to save at all.
I don't want a sliding scale that Lumos has since i don't think the light sensor is all that accurate (sometimes thinks it's too bright and sometimes thinks its too dark). would rather just have a few settings (pitch black setting, super bright setting, and in the middle) as shawndh suggested.
i have the verizon tp2 - not sure if this might be causing some of the glight probs.
Hello all,
I'm just curious as to how this feature is supposed to work. I have my device set to automatically adjust while it's on medium brightness and I've noticed that the brightness jumps from low to medium frequently, especially when I'm on just one page.
manny84 said:
Hello all,
I'm just curious as to how this feature is supposed to work. I have my device set to automatically adjust while it's on medium brightness and I've noticed that the brightness jumps from low to medium frequently, especially when I'm on just one page.
Click to expand...
Click to collapse
I believe it just counts the number of white pixels on the screen on the omnia. this is why it jumps so much. The only way to prevent the jumping is to set the birghtness on low, with the auto setting off. Even on medium or high it jumps when the page has a certain % of white pixels. Like for opening the browser its really annoying however on low brightness the colours are really nice and its just perfect for me. Its just too bright on med or high brightness for my preferences.
But the way how the "feature" itself work I have no clue. Maybe a light sensor. But the jumpiness is caused by the number of white pixels on the amoled screens, and occurs only on samsung devices I believe.
Marvin_S said:
I believe it just counts the number of white pixels on the screen on the omnia. this is why it jumps so much. The only way to prevent the jumping is to set the birghtness on low, with the auto setting off. Even on medium or high it jumps when the page has a certain % of white pixels. Like for opening the browser its really annoying however on low brightness the colours are really nice and its just perfect for me. Its just too bright on med or high brightness for my preferences.
But the way how the "feature" itself work I have no clue. Maybe a light sensor. But the jumpiness is caused by the number of white pixels on the amoled screens, and occurs only on samsung devices I believe.
Click to expand...
Click to collapse
Thanks for that explanation, Marvin
Hey everyone. I've been trying to get better battery life out of my INC2 with CM7.2 and Aeroevan's kernel. The display of course, its the main reason why the battery life suffers. I like the automatic display brightness option because it is convenient, but sometimes it just doesn't behave the way I like it. Right now, with the current settings, it behaves ideally but I wish it was literally a couple of notches dimmer in every situation. Here they are:
Light Sensor Filter
-----------------
Enabled
Window Length: 10 seconds
Reset Threshold: 800 lux
Sample Interval: 1 second
Light Levels
-----------
Use Custom
Screen Dim Level: 20 (default)
Edit Other Levels: All of these values are their respective defaults
Allow Light Decrease
Decrease hysteresis: 40%
So guys, using automatic brightness....how can I do what I'm trying to do? (Literally make it dimmer at every "level")? I didn't edit the values/options that looked in-depth, while some of them I just took some tips online.
I am using miui 2.3.7 from months and I notice that in display settings, sensor (filtred/raw) is usually 10 in low light conditions. So if I set for example 50 for level retroillumination, I had the same illumination of the screen in a totally dark room and in twilight light in outside. This is annoying because I want to set lower level for the first situation and higher for the second. A solution can be to use manual settings but if someone have an idea on how resolve the automatic levels I will be glad. Thanks
The brightness of the LED flashlight can be changed by modifying the value in /sys/class/leds/flashlight/brightness (or alternatively /sys/devices/platform/flashlight.0/leds/flashlight/brightness).
I've managed to vary the brightness, however there seem to be only 3 settings which stay (0, 64 and 128).
The max_brightness file is set to 255, which implies the brightness could be doubled (not that it necessarily should) - however setting it to that will increase the brightness to "very bright" and then switch off (presumably to "0") shortly after. I also tried 192, and the same things happens (I'm not sure if the brightness is set to "192" or "255" for that case before turning off).
This implies the levels are being overwritten shortly after to "0", "64" or "128" by the device/system.
Kevin (the author of TeslaCoil) writes saying that HTC devices only support 3 brightness levels (can't post outside links as under 10 posts):
ht[REMOVE_ME]tp://stackoverflow.com/questions/5970188/can-i-change-the-led-intensity-of-an-android-device
Is there any way to bypass these preset levels and have the LED at e.g. 255 or any intermediate level in the range [0,255]? I'm making the assumption that the LED's brightness can be comfortably varied without damaging it (please say if you know otherwise ).
Cheers, Arite.
Not sure if this will help, but there is a camera apk in the oxygen rom that has a high brightness mode. Might be worth having a look at that to see what level it's setting it to?
Thanks - I'll check it out. The default/normal brightness is actually 64 (I thought it was 128), and then the can be raised to 128. The level is forgotten after though (goes back to 64). Will have a look at the Oxygen camera.
Cheers, Arite.
Sent from my HTC Desire using xda app-developers app
Of course by camera apk, I did mean torch apk
Ah OK, cheers .
Arite.
Sent from my HTC Desire using xda app-developers app
I did: cat /sys/class/leds/flashlight/brightness with the brightness on normal and then high, the results were 127 and 3.
Yes, unexpected but a brightness of 3 was much higher than that of 127. When I tried setting the brightness to 3 manually, as you experienced it automatically turns off.
I can only imagine the app either uses a loop or turns off a safety somewhere before ramping up the brightness (it does require root).
Edit: Also, the source can be found here: http://code.google.com/p/n1torch/source/checkout
I tried values of 1, 2, 3 and 4: values of 1, 2, and 4 just enable the normal "64" brightness. 3 appears to be the max brightness (same as 255) and turns off shortly after.
Interesting how "3" seems to be a special value. This, and 255 can be kept on by continuously re-setting the value - so a timed loop could be written to have it "permanently" on like langers2k said. Don't think I'll do that though as there might be a good reason it get turned off shortly after.
Anyway - I think there are only 4 possible states: off, "normal", "brighter" and "max brightness" (which turns off after something like 750ms). TBH I'm not sure a LEDs intensity can be smoothly adjust from off to max - not like an incandescent bulb. It was an interesting experiment with it anyway.
Cheers, Arite.