Calise

Just changed the equation that calculates the percent. Now fits more with the real values but uses a bit more CPU. I'll optimize in next releases. The parameters have been modified a bit: since there are no more logarythms, the --base parameter ... [More] changed to --delta parameter and has totally different usage/values than before. Added also the --steps switch. For LCD with more than ten steps of backlight. [Less]

Just changed the equation that calculates the percent. Now fits more with the real values but uses a bit more CPU. I'll optimize in next releases. The parameters have been modified a bit: since there are no more logarythms, the --base parameter changed to --delta parameter and has totally different usage/values than before.

Changed a bit: now if there is a drastic change in ambient brightness (>15%) then the program changes / asks to change the backlight level, else it calculates an average to avoid useless and annoying changes of backlight level when you move a bit ... [More] in front of the camera. drastic changes == turned on/off thethe light average == sunlight during the day [Less]

Changed a bit: now if there is a drastic change in ambient brightness (>15%) then the program changes / asks to change the backlight level, else it calculates an average to avoid useless and annoying changes of backlight level when you move a bit in front of the camera.

Changed a bit: now if there is a drastic change in ambient brightness (>15%) then the program changes / asks to change the backlight level, else it calculates an average to avoid useless and annoying changes of backlight level when you move a bit ... [More] in front of the camera. drastic changes == turned on/off thethe light average == sunlight during the day [Less]

Cleaned and changed a bit, cpu usage improved: now with a time gap of 1sec, the cpu usage on my machine (DualCore 1.5Ghz) is always below 3%, average on 2,7. Now the only performance problem is the memory usage that is fixed at ~50MB.

Cleaned and changed a bit, cpu usage improved: now with a time gap of 1sec, the cpu usage on my machine (DualCore 1.5Ghz) is always below 3%, average on 2,7.

Cleaned and changed a bit, cpu usage improved: now with a time gap of 1sec, the cpu usage on my machine (DualCore 1.5Ghz) is always below 3%, average on 2,7. Now the only performance problem is the memory usage that is fixed at ~50MB.

Added some improvements, cleaned a bit the code. Now the program runs in a loop cycle. Now, on linux, with writing rights on the backlight (or running as root !not suggested!), you can change the $acpi_path, $verbose and/or $time_gap vars to make the ... [More] script fully automated. I tested for the past two days and it was really cool. If you want to try I adwise to nice the process so it will has lowest priority: "nice -n 19 camsensor.py" PS: The $time_gap var is set mainly for cpu/memory usage... anyway also with no-gaps the CPU usage is really minimal. [Less]

Added some improvements, cleaned a bit the code. Now the program runs in a loop cycle. Now, on linux, with writing rights on the backlight (or running as root !not suggested!), you can change the $acpi_path, $verbose and/or $time_gap vars to make the ... [More] script fully automated. I tested for the past two days and it was really cool. If you want to try I adwise to nice the process so it will has lowest priority: "nice -n 19 camsensor.py" PS: The $time_gap var is set mainly for cpu/memory usage... anyway also with no-gaps the CPU usage is really minimal. [Less]