So I just noticed Tasker is consuming 18% of my battery life. Which begs the question, is it really worth having if the whole reason for having it is to save battery life by disabling services not being used. Is that what everybody else is seeing for battery consumption?
That's quite a bit. What are you having Tasker do that could drain battery? Toggle something? It could be that it isn't toggling whatever correctly due to HTC's implementation and might be causing a huge wake lock. If you can track it down, you may want to shoot it off to the dev to investigate.
i love tasker, but like mentioned, it depends on what you are having it do.
tasker isnt just about conserving battery life, its about automating your phone.
I have 4 profiles for work, home, leaving work and a hotspot location I tend to go to. The work profile turns off my volume and turns my wifi off. Home does the opposite. Leaving work turns just my volume back on and the hotspot location turns on my wifi at that location.
If there is a better way to implement this, I'd surely like to know. I'm a newcomer to android.
Sounds simple enough, and definitely something that Tasker excels at. Not sure why it's eating up that much battery though. Probably best to have it create a debug log and shoot it off to the dev.
I'm a coder and brand new to Android (obviously I'm not a mobile app coder.) Had my S3 for 3 weeks now. No MAJOR battery drain issues but I like to maximize it anyway.
I've got Llama setup to do stuff like turn Wifi off when I leave home and turn GPS off when I turn driving mode off. Lots of other actions/events involving account sync on/off, bluetooth on/off. GSAM last time I looked was giving me a 20-hour average battery life which is probably optimistic as I have been use the phone less than normal.
Anyhoo... I was disabling some location settings in Maps as I noticed Maps is getting triggered when not using the phone (probably mainly by Google Now trying to build my location history) and I thought, wouldn't it be nice if my GPS turned on automatically when I launched Maps and turned off when I closed it? Surprised Android doesn't have this option built-in. But seems only solution is Tasker?
So my question is, knowing Tasker is more complicated to use, are there some MAJOR other benefits that I most likely will discover to using Tasker instead of Llama? Or, if I really don't care much about the GPS auto-toggle, should I just keep life simple and stay with Llama? Is there a problem with using both - as in, will I get more of a battery drain running both or is one more battery efficient (the app itself) over the other?
-- add --
Duh, just saw the first condition in Llama is "Active Application" the problem is, I only want the GPS to turn on when I manually launch the app myself. I hope an app trying to use Maps in the background doesn't trigger the GPS on. Guess I'll find out.
My question still applies. I know you can do more in Tasker, but what MAJOR/COMMON things can you do with it that you can't with Llama?
-- add --
I forgot why this isn't possible. Google doesn't want to allow ANY apps to turn GPS on/off automatically due to privacy issues. Is there a setting to let the user decide this? Make me feel like they're treating me like an idiot!
Secure Settings
Have a look at Secure Settings its a brilliant helper app to Llama, it will allow you to do all the GPS settings.
So I have had this great debate for years now. I want so very badly to use tasker, but it just fails me. Profiles that have only a time context fire early, or not at all. I almost missed work once. Tasker seems to work wonderfully for most people but for me, across a Droid X, THunderbolt, Gnex, and now GS3 tasker is just unreliable. Profiles take too long to fire, if they fire at all and the battery drain is fairly significant despite we designed profiles and tasks.
Llama on the other hand does exactly what it is supposed to. Profiles fire quickly and accurately. Location profiles, compared to the nightmare task offers, are ridiculously simple. IF here DO this, WHEN leave DO that.
Llama is more reliable with better battery life, but does offer substantially LESS.
Here is my master solution:
I run all location and automation via Llama. BUT, I make tasker tasks for car menus, and extended tasks like security etc. Llama turns on tasker, then fires an "app shortcut" to a tasker task. Then Llama closes tasker.
All the best of Llama AND tasker, without having to run both simultaneously.
garvus said:
So I have had this great debate for years now. I want so very badly to use tasker, but it just fails me. Profiles that have only a time context fire early, or not at all. I almost missed work once. Tasker seems to work wonderfully for most people but for me, across a Droid X, THunderbolt, Gnex, and now GS3 tasker is just unreliable. Profiles take too long to fire, if they fire at all and the battery drain is fairly significant despite we designed profiles and tasks.
Llama on the other hand does exactly what it is supposed to. Profiles fire quickly and accurately. Location profiles, compared to the nightmare task offers, are ridiculously simple. IF here DO this, WHEN leave DO that.
Llama is more reliable with better battery life, but does offer substantially LESS.
Here is my master solution:
I run all location and automation via Llama. BUT, I make tasker tasks for car menus, and extended tasks like security etc. Llama turns on tasker, then fires an "app shortcut" to a tasker task. Then Llama closes tasker.
All the best of Llama AND tasker, without having to run both simultaneously.
Click to expand...
Click to collapse
How do turn on and off tasker with llama?
So i got installing all the battery saver apps, greenify etc... they all close apps and not much else, my version comes from the mind of an electronics engineer view point...
hardware drains power NOT some little app running in the background! (Purely software programmer logic... )
So my app grabs what states wifi/gps/bt/modem at the time the screen goes off...
When the screen comes on, it re enables them! Eg go bed with 95% wake up with 94% put in your pocket it just does it...
The 2nd feature is the lost/stolen phone feature while the app itself can not get your gps data (no permissions for it) it can switch gps on/off...
So you send "on" without the surrounding quotes, the app will then switch on gps/wifi/modem/bt... it then disables itself
Now you can use wheres my droid or any other location finding app to easily pinpoint your lost or stolen phone (try getting a location with gps/agps/data disabled which people often do to save power!)
(Includes option to keep wifi/gps untouched from the app)
as for ads!... the ui has 1 ad, no popups or notifications ... and when activated the activity with the ad on is destroyed and can't touch battery life ... at all
Craig's Root Battery Saver!
https://play.google.com/store/apps/details?id=saver.battery.craigs.craigsbatterysaver
Well done
Holy crap! Someone replied (first for me here lol)
Thanks!
To be honest, your app is great when it comes to save battery, but in my opinion your approach is plain wrong in terms of the main purpose of a smartphone - receiving notifications in a timely manner, not when you turn on the screen manually. The same purpose can be achieved by using DS Battery Saver, which will in addition turn on mobile data once per specific time interval to receive push notifications.
And you should reconsider your opinion about "software does not drain battery but hardware does". Check this great thread for example. I am using a combination of different apps (Greenify, Amplify, Power Nap) to tame aggressive services/alarms/wakelocks and I am able to achieve a battery drain close to 0.0% per hour while screen is turned off with WiFi, mobile data and location turned on the whole time without losing instant notifications.
The app supports wake up notifications (well, will... the app's not quite finished yet, been too busy to get everything finished)
If you had gone to the playstore you'd have seen
Also you might want to reconsider what i said..... hardware drains it not software!
You refer to wake locks ... well believe it or not, wake locks turn on hardware which drains the battery, i program microcontrollers with the esp8266 / bluetooth / compass / etc ...
Software can only drain the battery if it's purposely trying to max out the cpu, and if it did you'd know it's malware... there are wakelock detectors too
Craig Capel said:
The app supports wake up notifications (well, will... the app's not quite finished yet, been too busy to get everything finished)
If you had gone to the playstore you'd have seen
Click to expand...
Click to collapse
I came across this, therefore my reference to DS Battery Saver, that already is capable of exact those things. Nevertheless, your app is doing what it was designed for - saving battery (and this is pretty good, indeed).
Craig Capel said:
Also you might want to reconsider what i said..... hardware drains it not software!
You refer to wake locks ... well believe it or not, wake locks turn on hardware which drains the battery, i program microcontrollers with the esp8266 / bluetooth / compass / etc ...
Software can only drain the battery if it's purposely trying to max out the cpu, and if it did you'd know it's malware... there are wakelock detectors too
Click to expand...
Click to collapse
Well, I am familiar with what wakelocks are. But without software, that produces a wakelock, there would be no noticable drain, right? Thus we can go round and round here, I guess. From my point of view the most battery drain on an Android device is the result of poorly programmed software (which results in an unneccessary wakelock) and alarms waking up your device, not from ****ty hardware. You can hunt down those wakelocks/alarms by using apps like Better Battery Stats or Wakelock Detector and reduce them to a minimum without losing functionality. Therefore I consider this as a better approach.
But without software, that produces a wakelock, there would be no noticable drain, right? Thus we can go round and round here, I guess. From my point of view the most battery drain on an Android device is the result of poorly programmed software
Click to expand...
Click to collapse
Unless the software drains it by intensive cpu work, anything else has to be hardware, if i power a gps module, talk to it via uart to enable/disable it... then it's hardware doing it not software..
Take Qualcomm, the newer cpus support an embedded DSP
https://gigaom.com/2014/12/12/5-things-to-expect-from-qualcomms-flagship-mobile-chip-in-2015/
Qualcomm*made that feature possible*in the Snapdragon 800*with its DSP, and they’re pushing hot words even farther. New devices will have the ability to passively listen, using only a small amount of power, for more than just the word “OK.” Qualcomm calls this feature Snapdragon Sense.
The first feature it will enable is a much faster Shazam search. So if you find yourself too slow on the draw when trying to identify unfamiliar music, you’ll love this: When you boot up Shazam, it’ll already have been listening just a little bit, so it can identify the song in a few seconds.
Click to expand...
Click to collapse
As hardware gets smaller and uses less power, then things like the embedded dsp chip will allow you to use wakelocks without little drainage, but were no where near that yet...
think of it like this... software simply carries instructions which can turn on hardware via a field effect transistor, that binary 1 value shows up as 3v logic and the fet begins to conduct between the drain and source, this sets a flip flop and the hardware starts wasting power...
Or to put it another way after the software enables the hardware via a gpio the software stops, or better still, show me software draining the battery with all hardware services disabled... it can't
Good
Does it really work ..
Don't you believe the title? (Really works!)
Craig Capel said:
As hardware gets smaller and uses less power, then things like the embedded dsp chip will allow you to use wakelocks without little drainage, but were no where near that yet...
Click to expand...
Click to collapse
True words. I can also see your other points and do agree with them. But as you said, we are not even close to a system where wakelocks do not drain as much as they currently do. Would we have such a system, your app wouldn't be required, I guess. Therefore taming the unneccessary wakelocks is a good way to achieve a great battery life without losing functionality for the moment.
Awesome
Awesome!!!
Can't open the settings and this sound makes me rly angry lol. Why it makes this sound? (even my phone is silence)
Gesendet von meinem ONE A2001 mit Tapatalk
There are no settings... work in progress (says so in the play store readme)
I've had the flu for the past week so i've not been developing much... expect updates shortly to remove the "settings" option which annoyingly is placed there by default... i never put it there
The sound is cool no? ... it plays a low volume sound to indicate the app is working!
Alright, update includes support for android 4.1 for gps now... i'm slowly working my way through android oddities and different techniques to switch hardware / on and off and with 5 phones to use 4 of them use kitkat!
Had to stop for a break i've had the flu all week, throwing up constantly, later on i'll add the finishing touches to wake up notifications as right now it's extreme power saving mode...
Stay tuned.... oh and i found a bug supporting lollipop, fixed that too, so if you have lollipop and it never worked, it should now ...
Antibiotics did the trick! It was sadly not the flu but some rare bug...
I've almost finished the autowakeup every x minutes 5, 10, 20 min intervals..
Unless someone here can think up a value or maybe add it as an option.
.
I removed the blocking side of things prior i used a thread/sleep now i use a timer event this stops the lag when unlocking the device on older models...
nive work :good:
I dumped the smart check (as far as i can tell anroid never fails, so i removed it)
It should now be seamless between lock screen and the main screen without any more lock up due to the threading...
Enjoy!
great!! will try it. thanks!
Hello everybody.
So, I have just purchased a Gear s2. I know it's late, but it finally got cheap enough for me.
There is something I believe to be very simple to develop and very useful for millions of orthodox Jews: We have issues with electricity on Saturdays. Simply put, an app that turns the smartwatch into a dumb watch for either a given period of time, or until one of the buttons is pushed, would do the trick. This means that the time and date would be constantly displayed in the most energy saving manner possible, touch screen and all other sensors on the watch are off, and all connectivity is off as well.
A simple version of the app will allow the user to turn it on and off manually. A more sophisticated version will know by itself when to switch to "dumb watch mode": the times when a user needs his watch to turn dumb are calculated by ancient Jewish calendar and clock. But they are preset and known in advance. There are many apps, programs, calendars add-ons, etc. that already know to calculate those times. Applying such existing plug into the smartwatch would predetermine when it needs to get dumb and when to get smart again, without the users' need to do anything manually.
Can this be programmed?
I think enabling both Airplane Mode and Power Saving Mode may be what you're looking for.
Is there a way for my PHONE to notify me when my watch battery is under 20%-25%, set maualy the procent.
Not every time wear my watch, any somtime is discharging to 0, an app to notiffy me on my phone is very good.
Haven't seen anything, but would be good feature to have...
I hope a developer sees the requirement
I am willing to pay for the application
It’s not an App, but the functionality you mentioned is possibly with a combination of Watchmaker Watch-Face + Lua-Script and a Tasker-Task. But this is only a workaround or very special use case
It is a good idea. I am not sure why the WEAR app doesn't support it. I suppose they assume you will notice the watch, itself, notifying you. But it only does that when it is REALLY low and asks to switch to low power mode. Plus, doesn't help if you have your watch off your body at the time.