I miss the option for this...
The widget only makes the brightest or darkest setting... :-(
Sent from my LT15i using XDA App
when you use the standard "Power Control" widget you can toggle min/user/max
with user being the setting that you set in the display settings.
and if you have a user setting somewhere in the middle, then it will adjust to the ambient light.
If you install widgetsoid (a massively enhanced version of the powercontrol widget mentioned above) the brightness control has an auto option, which works fine.
For ARC, you can enable and disable by executing the following command in a terminal. You can write it in a script file and make it one-button action with the help of "gscript lite".
echo 1 > /sys/devices/i2c-0/0-0040/leds/lcd-backlight/als/enable
1 to enable, 0 to disable
In addition, by adjusting cutoff frequency of low pass filter of ALS output, you can adjust the changing speed of brightness relative to ambient lighting. The command is listed below:
echo 2,4,2,0 > /sys/devices/i2c-0/0-0040/leds/lcd-backlight/als/params
2nd figure "4" is to define cuf-off frequency to 4Hz for
increasing brightness. Range 0~7, larger value for faster change
3rd figure is for decreasing brightness. This example, 2, is to define 2Hz for cut-off frequency.
cruxlin said:
For ARC, you can enable and disable by executing the following command in a terminal. You can write it in a script file and make it one-button action with the help of "gscript lite".
echo 1 > /sys/devices/i2c-0/0-0040/leds/lcd-backlight/als/enable
1 to enable, 0 to disable
In addition, by adjusting cutoff frequency of low pass filter of ALS output, you can adjust the changing speed of brightness relative to ambient lighting. The command is listed below:
echo 2,4,2,0 > /sys/devices/i2c-0/0-0040/leds/lcd-backlight/als/params
2nd figure "4" is to define cuf-off frequency to 4Hz for
increasing brightness. Range 0~7, larger value for faster change
3rd figure is for decreasing brightness. This example, 2, is to define 2Hz for cut-off frequency.
Click to expand...
Click to collapse
I think I just fell in love. Thanks a lot!
daveybaby said:
If you install widgetsoid (a massively enhanced version of the powercontrol widget mentioned above) the brightness control has an auto option, which works fine.
Click to expand...
Click to collapse
I have widgetsoid installed and the auto brightness control just sets my brightness to the minimum..
DemonicHawk said:
I have widgetsoid installed and the auto brightness control just sets my brightness to the minimum..
Click to expand...
Click to collapse
Are you sure? Works here just fine.
Try holding your thumb over the light sensor, see what happens.
Yeah, i've tried covering it and putting a flashlight to it, neither do anything when on auto. I even went into the service menu to make sure it was working properly.
I guess i'll just have to stick with a fixed brightness and let it "auto adjust" as needed. Maybe its the generic .181 build im using?
Hmm, i don´t know who is wrong but i was thinking that the arc only has an automatic brightness that can not be disabled. I have a german arc (unbranded, .181 FW) and it doesn´t matter to which level the brightness is set the automatic is always active and permanently regulates the brightness. Woul be very gald if SE would integrate an automatic brightness on/off setting with the next firmware
cruxlin said:
For ARC, you can enable and disable by executing the following command in a terminal. You can write it in a script file and make it one-button action with the help of "gscript lite".
echo 1 > /sys/devices/i2c-0/0-0040/leds/lcd-backlight/als/enable
1 to enable, 0 to disable
In addition, by adjusting cutoff frequency of low pass filter of ALS output, you can adjust the changing speed of brightness relative to ambient lighting. The command is listed below:
echo 2,4,2,0 > /sys/devices/i2c-0/0-0040/leds/lcd-backlight/als/params
2nd figure "4" is to define cuf-off frequency to 4Hz for
increasing brightness. Range 0~7, larger value for faster change
3rd figure is for decreasing brightness. This example, 2, is to define 2Hz for cut-off frequency.
Click to expand...
Click to collapse
Genius!! Many thanks
Strange! with the update to 2.3.3 it stopped auto-dimming (not sure if it was due to the update or due to me installing juice defender)
And i can not get turn it on with the Power Widget.
cruxlin said:
echo 1 > /sys/devices/i2c-0/0-0040/leds/lcd-backlight/als/enable
1 to enable, 0 to disable
Click to expand...
Click to collapse
I get "permission denied" trying to do that
but "cat" ing the vqalue gives me a 0
do I have to root?
cruxlin said:
echo 2,4,2,0 > /sys/devices/i2c-0/0-0040/leds/lcd-backlight/als/params
2nd figure "4" is to define cuf-off frequency to 4Hz for
increasing brightness. Range 0~7, larger value for faster change
3rd figure is for decreasing brightness. This example, 2, is to define 2Hz for cut-off frequency.
Click to expand...
Click to collapse
cat /sys/devices/i2c-0/0-0040/leds/lcd-backlight/als/params
gain,filter_up,filter_down,offset
2,0,0,0
any clues what gain and offset are used for?
this works brilliantly
Thank you so much
And yes you need ROOT
cruxlin said:
For ARC, you can enable and disable by executing the following command in a terminal. You can write it in a script file and make it one-button action with the help of "gscript lite".
echo 1 > /sys/devices/i2c-0/0-0040/leds/lcd-backlight/als/enable
1 to enable, 0 to disable
In addition, by adjusting cutoff frequency of low pass filter of ALS output, you can adjust the changing speed of brightness relative to ambient lighting. The command is listed below:
echo 2,4,2,0 > /sys/devices/i2c-0/0-0040/leds/lcd-backlight/als/params
2nd figure "4" is to define cuf-off frequency to 4Hz for
increasing brightness. Range 0~7, larger value for faster change
3rd figure is for decreasing brightness. This example, 2, is to define 2Hz for cut-off frequency.
Click to expand...
Click to collapse
Hi cruxlin
Thanks allot for your information on how to change this. I have found on my ARC with 2.3.3 that als/enable is allways configured to "1". Doing echo "0" > als/enable will not change this value. It is working fine for als/params where I managed to change how fast the brightness are changing.
I also discovered an odd way of manually disabling/enabling the light sensor by using the default sony ericsson brightness toggle widget. Setting this to "dim" will disable the auto brightness and you can set the brightness manual to whatever level you wish. When you toggle the widget to enable brightness it will both enable auto brightness and change brightness to the value you previosly used as minimum.
I had for testing added echo 2,6,6,0 > als/params for fast brightness change and using a flashlight. This made the brightness update the same second I moved the flashlight over the light sensor.
I actually very much like the sony ericsson way of controlling this as it enables me to define minimum brightness with auto brightness enabled and very quickly use the dim toggle to quickly change to some other preffered value.
So with that second script you can also get rid of the backlight stuttering higher and lower in some situations?
Ambroos said:
So with that second script you can also get rid of the backlight stuttering higher and lower in some situations?
Click to expand...
Click to collapse
I do not think I have experienced this backlight stuttering, how do you notice this?
I have just yesterday managed to get my auto brightness working, my SE brightness widget had been set to dim shortly after I got the phone and I had not touched it until yesterday unknowing that this also controls the auto brightness
hygge said:
I do not think I have experienced this backlight stuttering, how do you notice this?
I have just yesterday managed to get my auto brightness working, my SE brightness widget had been set to dim shortly after I got the phone and I had not touched it until yesterday unknowing that this also controls the auto brightness
Click to expand...
Click to collapse
It's just that in some low-light situations the automatic brightness flips out, and switches between two settings at an extremely fast speed, creating a flickering effect. Doesn't happen a lot, but it is pretty annoying when it happens.
Ambroos said:
It's just that in some low-light situations the automatic brightness flips out, and switches between two settings at an extremely fast speed, creating a flickering effect. Doesn't happen a lot, but it is pretty annoying when it happens.
Click to expand...
Click to collapse
I do experience that on my Neo too, try to move your phone a bit, or hold your thumb over the light sensor and release it. Works sometimes.
I ran the script in glite and it makes no difference for me any pointers thx
hygge said:
I also discovered an odd way of manually disabling/enabling the light sensor by using the default sony ericsson brightness toggle widget. Setting this to "dim" will disable the auto brightness and you can set the brightness manual to whatever level you wish. When you toggle the widget to enable brightness it will both enable auto brightness and change brightness to the value you previosly used as minimum.
I had for testing added echo 2,6,6,0 > als/params for fast brightness change and using a flashlight. This made the brightness update the same second I moved the flashlight over the light sensor.
I actually very much like the sony ericsson way of controlling this as it enables me to define minimum brightness with auto brightness enabled and very quickly use the dim toggle to quickly change to some other preffered value.
Click to expand...
Click to collapse
It works perfectly for me, thank you.
After upgrading to 2.3.4 where power control widget is missing (I dont know why), I was not able to set auto-mode.
With this solution I recovered it and, more ahead, I have now something I was looking for, the way to set the low brightness intensity, that was very high when dark night.
I cannot set the other paramethers, since I lost root while updating (I'll need to fix this), but for the moment, it works fine.
Again, thanks a lot.
daveybaby said:
If you install widgetsoid (a massively enhanced version of the powercontrol widget mentioned above) the brightness control has an auto option, which works fine.
Click to expand...
Click to collapse
Even if you uncheck auto, it will use the light sensor to set the brightness, the input you give is just the minimal brightness. Try putting the brightness on ~8% in a place with light, then hold you hand above the light sensor. Screen will still become darker.
Related
I use the Auto setting as it seems to work very well except when out in direct sunlight. It will adjust up to 80-90% but not go all the way. If I am in direct sunlight and switch from Auto to High the screen definitely brightens a bit (and vice versa), does this happen to any one else?
While we are at it, a simple Toggle or Live tile to get to the brightness would be nice. Having to go through Settings etc. is a pain.
What setting do you have brightness set to when Auto is enabled? I believe that Auto also uses the Low/Medium/High settings to determine the range of what Auto will change to. So, there are really six different brightness settings: Low/Med/High with and without Auto.
ElNino77 said:
What setting do you have brightness set to when Auto is enabled? I believe that Auto also uses the Low/Medium/High settings to determine the range of what Auto will change to. So, there are really six different brightness settings: Low/Med/High with and without Auto.
Click to expand...
Click to collapse
High. Try this please, set your phone on high brightness, go outside and then toggle the 'auto' switch on and off, you should see a difference. Thanks for the reply though!
I highly recommend you do not use auto brightness setting. It guzzles the battery. Use Low inside and Med outside to maximize your battery life. Use High outside if really needed.
Seed 2.0 said:
I highly recommend you do not use auto brightness setting. It guzzles the battery. Use Low inside and Med outside to maximize your battery life. Use High outside if really needed.
Click to expand...
Click to collapse
Oh, do I understand that! High will devastate the battery in no time but.... When I'm outside I need to actually see the display so high it must be. Just wish Auto would actually set it to High instead of "sorta High"
I see exactly the same thing. It seems to be by design.
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.
Hi, guys.
As you'll already know, Xperia Ion Stock ROMs have no auto-brightness toggle on settings, apparently. And even if you use a 3rd party app to fix the brightness at a value, it keeps blinking around that value according to light sensor.
Light sensor has always been told to be such a battery-drainer, so here's my doubt:
Would it be possible to create a mod, app, flashable ZIP or something to disable that auto brightness feature at all?
Thanks in advance.
Lol? Light Sensor isn't battery drainer. You have wrong informations.
Sent from my LT26i using xda developers-app
Light sensor constantly reads an input, that obviusly uses a substantial amount of battery.
Anyway, is there any toggle solution?
If you want to really disable it, try this -
0. MAKE A NANDROID BACKUP (VERY IMP)
1. Use a root file manager and go to /system/etc
2. Open hw_config.sh
3. Search for this line - echo 1 > $dev/lcd-backlight/als/enable
4. Change 1 to 0, then save and reboot
5. Hopefully it should disable als now.
Thanks for the method! But wouldn't that disable brightness at all? I want brightness on, but light sensor-based automatic brightness disabled.
Greetings.
Serede said:
Thanks for the method! But wouldn't that disable brightness at all? I want brightness on, but light sensor-based automatic brightness disabled.
Greetings.
Click to expand...
Click to collapse
No no, you can adjust brightness in settings. It only disables the ALS sensor(Ambient Light Sensor). I have tested it myself.
My tablet when on auto brightness becomes very dark in unlit rooms and I can barely see it videos or detail.
Sent from my GT-N5110 using Tapatalk
Mod to adjust auto brightness
6Flip9 said:
My tablet when on auto brightness becomes very dark in unlit rooms and I can barely see it videos or detail.
Sent from my GT-N5110 using Tapatalk
Click to expand...
Click to collapse
I am not sure if this works with stock roms, but if you install PhilZ touch recovery from the thread... http://forum.xda-developers.com/showthread.php?t=2367151
You have options in the advanced menu to change the response time for auto brightness. The default is 1 minute, you will need to tap about 4 times to get it down to 0, as it counts up to 5.
Which sped up the delay from going from one extreme to the other in ambient lighting.
If you install his custom roms you also get options to adjust the brightness intensity in 5 steps while auto brightness is on. I found this out after some time messing with my settings.
6Flip9 said:
My tablet when on auto brightness becomes very dark in unlit rooms and I can barely see it videos or detail.
Click to expand...
Click to collapse
Lux Auto Brightness - perfect app for brightness tuning - you can set you own profile - matching desired screen brightness to sensor reading, and the process is very easy.
Short info, taken from app description:
Lux isn't your ordinary brightness app. It intelligently adjusts the brightness of your display based on the environment you're in. If, for example, you step into a dimly lit room, Lux will automatically lower the brightness of your display to make it not only comfortable to read, but to also preserve battery power.
Lux provides the option to automatically adjust the backlight at fixed intervals (periodic mode), when a change in environment is detected (dynamic mode), or when the phone wakes from sleep. It's also possible to adjust the backlight manually. Simply disable automatic mode and you can use it like a traditional brightness tool!
Perhaps the best thing about Lux is that you can teach it how to behave. If the backlight is too bright or dim for your liking, simply open the provided Dashboard, adjust the brightness slider to the level you desire, then hold the link button. Lux will use this new 'link' as a reference in future.
lux and velis both work. i paid for both, but i prefer lux.
Im not sure if these watches have auto brightness but im assuming they dont as there is nothing for that in the settings.
So what I did is with tasker and autowear i wrote a task that looks at my phone brightness every time the screen turns on and off and adjusts the wathc brightness to the same +15% (as it was a tad dark)
Anyone using a different way of auto adjusting the brightness?
Attached it
So i set some minimum values for watch brightness which is 50
also when i set my watch birghtness same as phone it was a bit dark so i added 10* in the one formula where it says *1.1
you will have to play with it
I created a action so it will run when screen turns on or off
HW2 has auto brightness, test with put it under a lamp
Grumps said:
Im not sure if these watches have auto brightness but im assuming they dont as there is nothing for that in the settings.
So what I did is with tasker and autowear i wrote a task that looks at my phone brightness every time the screen turns on and off and adjusts the wathc brightness to the same +15% (as it was a tad dark)
Anyone using a different way of auto adjusting the brightness?
Click to expand...
Click to collapse
I've tried to do the same but couldn't get it to work because my tasker skills are lacking. Please share your tasker profile and task(s).
dersie said:
HW2 has auto brightness, test with put it under a lamp
Click to expand...
Click to collapse
I know but hw2 sucks....
JimSmith94 said:
I've tried to do the same but couldn't get it to work because my tasker skills are lacking. Please share your tasker profile and task(s).
Click to expand...
Click to collapse
just added it to my first post
Grumps said:
Im not sure if these watches have auto brightness but im assuming they dont as there is nothing for that in the settings.
So what I did is with tasker and autowear i wrote a task that looks at my phone brightness every time the screen turns on and off and adjusts the wathc brightness to the same +15% (as it was a tad dark)
Anyone using a different way of auto adjusting the brightness?
Attached it
So i set some minimum values for watch brightness which is 50
also when i set my watch birghtness same as phone it was a bit dark so i added 10* in the one formula where it says *1.1
you will have to play with it
I created a action so it will run when screen turns on or off
Click to expand...
Click to collapse
Thanks for the task but shouldn't there be a profile to go with it? I'm not sure, but I think if you export the profile instead, the associated tasks get exported with it.