Tasker Battery Consumption: How Big A Hit?


Last Updated:

  1. PeteCress

    PeteCress Well-Known Member This Topic's Starter

    Joined:
    Aug 12, 2010
    Messages:
    333
    Likes Received:
    21
    Logically, it seems like Tasker has to be running all the time - albeit not visible in task manager.

    So there must be a hit on battery life.

    But how much to expect?

    Or does it vary with the number/nature of profiles?

    Right away, I can imagine frequency of GPS checking as a variable....

    Or am I over-thinking this?
     

    Advertisement
  2. electricpete

    electricpete Well-Known Member

    Joined:
    Jan 7, 2012
    Messages:
    1,904
    Likes Received:
    881
    In GSAM battery-monitor, Tasker typically takes between 7% and 20% of my total battery usage.

    That's a big number, but it does not concern me because:
    1 - I have boatloads of profiles and widgets doing things that (as you say) by their nature would tend to consume power. I rely heavily on Tasker so I don't have to use a lot of other programs for these functions.
    2 - A lot of the things I do with Tasker save power. For example turning wifi off when I leave home. Turning display rotate on only for certain applications (so I don't have to leave it on continuously).
    3 - I enjoy the control that Tasker provides... having the phone act exactly the way I want it to.

    How you structure your profiles (particularly conditions of your contexts) will make a lot of differences. See
    Tasker for Android

    So, try to stay away from things near the bottom of the list For example use cell near in preference to wifi near. Having your phone respond to certain shaking gesture may be "cute", but it'll cost you dearly to have Tasker continuously keep accelerometer monitoring for that gesture. And if you're using a high-power context, ADD a low power context to minimize it's impact.... yes adding another context can SAVE power (if the added context is lower power type) because Tasker monitors the lowest-power context and if that context isn't satisfied it doesn't bother monitoring the high power context. Also consider adding Display on as context so things that aren't important other than when you are looking at your phone won't take power while phone screen is off. This reduces the number of times you do the task. Also it costs less power to do a task when the phone is already awake then it does to wake the phone to do a task.

    Also you can adjust monitoring frequecies in the monitoring tab of tasker settings.

    If you are curious about effects of Tasker and about your battery usage in general, I'd highly recommend GSAM battery monitor. Seems much more straightforward than Better Battery Stats and seems to have a wider range of accessible/understandable stats reported (BBS gives you tons of info but what does it mean is not as clear). Once in awhile a program will jump out of the ordinary and you learn something by observing that. For example, I used to use Tasker to "kill" a certain program (Chroma Doz). I observed that on two occasions Chroma Doz kept using ridiculous amounts of power after it was killed. Apparently it doesn't like being killed. So I removed that action from Tasker and do it manually now.

    If you have been making a lot of changes to your Tasker profiles, you might keep an eye out for unexpected behavior (things running too much) by occasionally checking the active profiles (listed in the notification bar profile and in %PACTIVE) as well as running tasks (listed in %TRUN)
     
  3. CodeMonkey

    CodeMonkey Well-Known Member

    Joined:
    Dec 13, 2008
    Messages:
    570
    Likes Received:
    110
    In my experience Tasker battery consumption is primarily impacted by the way your profiles and tasks operate.
    When I first started using Tasker it was registering (on average) 5% of my battery life; after I rewrote my profiles to operate more efficiently it no longer registered on my battery usage stats at all.
    Location contexts have the greatest potential to affect battery, however there is a good primer called Location Without Tears available on the Tasker website that offers guidance.
     
    NewStreetPhoto likes this.
  4. NewStreetPhoto

    NewStreetPhoto New Member

    Joined:
    Jan 18, 2016
    Messages:
    3
    Likes Received:
    0
    In theory tasker shouldn't use up anymore juice than any other event based app. If it's architects properly all it should be doing is registering listeners for various events. That happens with a whole load of apps and system services anyway! Things like smart locking, and location based notifications, timers, alarms, all do exactly the same thing. At it's core an event listener is nothing more than a locked thread waiting for a flag to change. The CPU overhead should be minimal, it's what happens when the event is triggered that could drain your battery! Underneath it all Android is an event driven OS anyway...
     

Share This Page

Loading...