[wiki] tasker wakelock details

[lordgoata]

Hi Sven,

Pent has given permission to add the following to the wiki regarding the wakelocks associated with Tasker. I think it would be quite handy to have added, as it explains what they are doing, so is useful to understand to eliminate them when debugging the results.

These are the wakelocks:

M (net.dinglisch.android.taskerm.Tasker) E (net.dinglisch.android.taskerm.Tasker) Tasker.UserAbsentWakelock (net.dinglisch.android.taskerm.Tasker)

This is the explaination:

Whenever a new event comes in the monitor 'M' has to get a wakelock while it's processing. Whenever a task is running, the execution service 'E' has to get a wakelock while it runs the task. Whenever you have background checks (e.g. location) the 'userabsent' wakelock is needed to keep the check going every time.

Therefore, they occur a lot. If you want tasks to run and events to be processed while the screen is off, there's no avoiding it.

When the device is not in deep sleep (even if the screen is off), the wakelocks cause zero extra battery drain (as the device is already awake). Most contexts will cause a lot of wakelocks, but zero extra battery drain.

For example, the Power context: Android will only send the signal when it's not in deep sleep. So although the 'M' wakelocks will accumulate, they are only happening when the device is already on, therefore having zero battery impact.