View Single Post
ammyt's Avatar
Posts: 1,918 | Thanked: 3,118 times | Joined on Oct 2010 @ My pants
#61
Originally Posted by Estel View Post
As for SIGSTOP, it definitely *do* the job. The question is, if it provides more power-saving, than monitoring of dbus signals use Remember, that this way *every* dbus signal is monitored, and script only "act" on some of them - but, power/resources is/are used already, even to monitor "other" signals.

That may be cause of why, every measurement show a little more power usage, when power-saving scripts monitor dbus. As opposed to "perceived battery life"
Well in this case, it depends on the amount of times you unlock your device... I mean, if somebody assents a worker to just slide his finger on the lock/unlock switch at the speed of 999 slides/sec he would certainly see a negative effect in battery life.

Dbus-signals are sent - in my script - when the device is locked, and when it is unlocked. The locking/unlocking process should not take long