On Mon, Apr 12, 2010 at 16:49, Helge Hafting <[email protected]> wrote: > Sebastian Spaeth wrote: >> >> On 2010-04-08, Helge Hafting wrote: >>> >>> SHR-U no longer uses SIM contacts, but shr-settings can now import from >>> the SIM. Unlike pisi, this actually works. :-) >> >> Yay >>> >>> Editing contacts is somewhat clunky, but at least it is possible now. >> >> Yay >>> >>> And the volume sliders for phonecalls works again, and seem to >>> be remembered from call to call too. :-) >> >> Yay >> >>> What remains, is a way to set the timing for screen dimming. >> >> No :-) >> >>> Before the stepwise dimming, one could simply set the timeout. >>> When stepwise dimming first appeared, nothing could be done. >>> Then, and upgrade brought new settings, so I could set the >>> time to first dimming as well as the delay between steps. >>> Perfect configurability! But the upgrades that brought >>> all the other good stuff, _reverted_ the power settings. (why?) >> >> 1) You can configure the timing in /etc/fsodeviced.conf (actually it is >> in /etc/freesmartphone/conf/GTA02/fsodeviced.conf, but that is >> overwritten on updates, so copy it to /etc/fsodeviced.conf). The >> brightness levels are configured in /etc/phonefsod.conf > > Thanks for the tips. > Seems I don't have a /etc/fsodeviced.conf. > I'll try making one, or did you mean one of: > > /etc $ find . -name "fsodeviced*" > ./freesmartphone/conf/default/fsodeviced.conf > ./freesmartphone/conf/openmoko_gta/fsodeviced.conf > ./freesmartphone/conf/htc_qualcomm_msm/fsodeviced.conf > ./freesmartphone/conf/htc_qualcomm_dream/fsodeviced.conf > ./dbus-1/system.d/fsodeviced.conf > ./init.d/fsodeviced > > >> 2) fsodeviced was buggy in that it did not save the timing changes. That >> was fixed by mickey and changes through shr-settings should be >> persistent on a new shr-U (not shr-T yet though). If that does not work, >> it is a bug. >> > > >>> I understand that shr-settings doesn't always keep up with new features, >>> but why didn't the stepwise dimming simply use the existing backlight >>> timeout as the timeout for the first backlight reduction step? That'd be >>> a backwards compatible way of adding this feature. >> >> AFAIK, it does. It dims on the first "idle" step and dims further on >> "idle_dim", I think. > > Hm. If this is so, then perhaps shr-settings entries can be renamed? > "idle dim" sounds like the timeout till the screen dims, but that is "idle". > But "idle" doesn't say what happens at all.
You shouldn't look at it as timeout to some state, but as "how long this state should be active". So after "idle" comes "idle dim", dimming happens on "idle dim", so if you want screen to be dimmed after 10 seconds, you have to set "idle" to be 10 seconds long. -- Sebastian Krzyszkowiak dos _______________________________________________ Shr-User mailing list [email protected] http://lists.shr-project.org/mailman/listinfo/shr-user
