BK> Perhaps you could rewrite it so it reflects reality? - I cant BK> figure out how it works. Commenting out the dim values as BK> suggested by one of the devs sorta works in disabling dimming, but BK> I get some side effects such as brightness randomly jumps back to BK> 20% or 40% at odd times (even with default brightness set to 100%) BK> - usually coincident when some (random?) apps close. The phone is BK> basicly unusable for me with dimming enabled so it would be nice to BK> return to the behaviour older pre-dim enabled versions had. There BK> also seems to be an interaction with shr-today (in that it stops BK> appearing in some circumstances when you disable dimming.) BK> BK> Some information on how it really works (timing of the various BK> stages) and how to reliably disable it would be good. BK> BK> BillK BK> BK>
Timeouts are reached in this order from busy: idle -> idle dim -> idle prelock -> lock -> suspend if you run mdbus2 -s -l org.freesmartphone.odeviced you can see how it works, see here: [SIGNAL] org.freesmartphone.Device.IdleNotifier.State /org/freesmartphone/Device/IdleNotifier/0 :1.2 ( "busy" ) [SIGNAL] org.freesmartphone.Device.IdleNotifier.State /org/freesmartphone/Device/IdleNotifier/0 :1.2 ( "idle" ) [SIGNAL] org.freesmartphone.Device.IdleNotifier.State /org/freesmartphone/Device/IdleNotifier/0 :1.2 ( "idle_dim" ) [SIGNAL] org.freesmartphone.Device.IdleNotifier.State /org/freesmartphone/Device/IdleNotifier/0 :1.2 ( "idle_prelock" ) [SIGNAL] org.freesmartphone.Device.IdleNotifier.State /org/freesmartphone/Device/IdleNotifier/0 :1.2 ( "lock" ) i simply pressed date when it happened: van...@vanek:~$ date Thu Mar 18 08:18:05 CET 2010 van...@vanek:~$ date Thu Mar 18 08:18:11 CET 2010 van...@vanek:~$ date Thu Mar 18 08:18:26 CET 2010 van...@vanek:~$ date Thu Mar 18 08:18:35 CET 2010 van...@vanek:~$ date Thu Mar 18 08:18:37 CET 2010 see my config: [fsodevice.kernel_idle] ignore_by_id = lis302 idle = 5 idle_dim = 15 idle_prelock = 9 idle_lock = 1 suspend = 30 see bellow how it goes in time, minutes and seconds only. as i pressed it by hand, it is not exact, but good for now. state: busy -> idle -> idle dim -> idle prelock -> lock -> suspend config: 0 -> 5 -> 15 -> 9 -> 1 -> real: 18:05 -> 18:11 -> 18:26 -> 18:35 -> 18:37 -> hope this helps Petr _______________________________________________ Shr-User mailing list [email protected] http://lists.shr-project.org/mailman/listinfo/shr-user
