Backlight setting not remembered

[TheGeneral]

In the settings you can specify a percentage value for the screen backlight. After reboot it is always set to 100% again. Should be stored somewhere.

[spaetz]

This is an upstream (FSO) issue. There is nothing shr-setting can do about for now, as it isn't started. I recommend filing this feature request on trac.freesmartphone.org which manages those backlight settings. shr-settings cannot be used for this, as it is not run on FR startup and it also never saves current settings (it is just a frontend for varies settings backends).

P.S. Personally, my low-priority long term plans are to use shr-config to be run at startup and restore setttings to whatever has been saved.

[dos]

As described above. Please open FSO ticket for that.

[TheGeneral]

Done:  http://trac.freesmartphone.org/ticket/438

[mako]

Personally, my low-priority long term plans are to use shr-config to be run at startup and restore setttings to whatever has been saved.

But how about using kernel module parameter on boot? I don't know which kernel module serves the backlight brightness, but it might be

vmlinuz somemodule.brightness=50 == (for 50% zB.)

[spaetz]

Just for the record, mickeyl said the correct way would be to modify oeventd to read the brightness value from a profile value. Then a brightness setting would only have to modify the profile value and frameworkd would use it on startup. This has the additional advantage that we could have different brightness settings in different profiles.

As for the kernel module idea. Would you really want to modify the bootloader to pass settings parameters every time you change the screen brightness? But where would you stop with this madness? Others would want the blank timeout, the ring loudness and other stuff there next. No, I really think we need a better way to handle all kinds of settings on bootup, but not by passing it to the kernel.

[morphis]

Milestone MS1 deleted