Related
New user and I've figured out some stuff but I'm still learning. Tried Glance and am currently using Canvas but one thing I can't seem to get is the weather. It differs on every app I use and is seldom the same as what is showing on my phone. I'd like to get an accurate weather forecast! How do I do that? Are there apps that do weather that I can use outside the 'stock' ones. I have an analog face I'd like to keep but without the weather I'm not so sure.
OK. Seriously? Is there an embargo on answering weather questions? Some taboo I'm not aware of? Cuz I can't get an answer to save my life! Anywhere!
Weather will differ on every app because of several variables:
The apps may be using different sources for weather (e.g. Yahoo, Google, AccuWeather, Weather Channel, etc.) Each service has slightly different data. Even on your phone if you install different weather apps, they will seldom agree 100%.
The refresh period may be set to a long time (e.g. 2-3 hours) to prevent battery drain, and hence you will not get up-to-date information. Some watch apps give you ability to configure this, while others use a hard-coded interval.
Some apps allow you to specify a Zip code, or latitude/longitude coordinates, but most simply use your phone's approximate location to retrieve local weather data. Your location will be inaccurate most of the time, since the apps usually avoid using GPS to once again avoid draining the phone's battery, and instead use cell/WiFi triangulation. This is why sometimes you may even be getting weather data for a different city.
Weather in general is not an exact science, so an "accurate forecast" is a pipe dream.
Chahk said:
Weather will differ on every app because of several variables:
The apps may be using different sources for weather (e.g. Yahoo, Google, AccuWeather, Weather Channel, etc.) Each service has slightly different data. Even on your phone if you install different weather apps, they will seldom agree 100%.
The refresh period may be set to a long time (e.g. 2-3 hours) to prevent battery drain, and hence you will not get up-to-date information. Some watch apps give you ability to configure this, while others use a hard-coded interval.
Some apps allow you to specify a Zip code, or latitude/longitude coordinates, but most simply use your phone's approximate location to retrieve local weather data. Your location will be inaccurate most of the time, since the apps usually avoid using GPS to once again avoid draining the phone's battery, and instead use cell/WiFi triangulation. This is why sometimes you may even be getting weather data for a different city.
Weather in general is not an exact science, so an "accurate forecast" is a pipe dream.
Click to expand...
Click to collapse
Understand that. The apps I'm using all use one of two weather programs (Yahoo or OPenweather), you can set the refresh interval (I use one hour). You can choose My Location but I think that's not working the way it should. You can also put in geo coordinates but I'm trying to not get locked into a fixed location if I can. And if you use geo's they are only going to go to the nearest reporting node. I don't want accurate as much as consistent. Where I work is always 5 degrees hotter than where I live. It's also possible the app doesn't work as well as it should.
Absent of any suggestions I guess this will be "the annoyance" for me. Everyone's gotta have one!
I have been trying on and off for over a year to eliminate these horrible wakelocks without disabling location services all together, and have finally found a solution.
I have tried wakelock terminator, amplify, and various other tweaks without the results I was looking for. I could only stop them by disabling location completely. Even with GPS only enabled the phone will eventually want to find its location and then if you're in a building where there is no GPS single, it will kill your battery trying to find one. So I finally stumbled across SlimLP which is an AOSP rom that has app ops baked into it. I found that if I simply modify the permissions of google play services and not allow it to use location, and also disable its ability to hold a wakelock, the nlp wakelocks (both) are gone forever. However, as soon as nlp is gone, the phone falls back to its backup plan which is RILJ to locate itself. So I then went into the phone apps permissions and disabled location and wakelock for it too. FINALLY these wakelocks are gone forever. My phone now loses 3% over 8 hours without disabling location services. There are literally 10 or less wakelocks system wide over 8 hours while I sleep, which is a huge contrast to the waking once every 25 seconds to check my location (or whatever absurd rate it was doing it). The only thing I can spot thats out of place it that google play services is registering a ton of alarms for location related stuff in better battery stats. I'm happy with this so far but feel it could be even better once I learn more.
What I really want to do is to be able to apply this to any android phone, such as my girlfriends z3. Unfortunately I can only get this to work with AOSP roms that have app ops built into them. I tried adding app ops to google based roms and even aosp roms and it doesnt work the same. If anyone could tell me what is different about roms with app ops built in, that would be great. I think we should look into this more to learn as much as possible because this affects everyone with an android phone. Thanks for reading.
seh6183 said:
I have been trying on and off for over a year to eliminate these horrible wakelocks without disabling location services all together, and have finally found a solution.
I have tried wakelock terminator, amplify, and various other tweaks without the results I was looking for. I could only stop them by disabling location completely. Even with GPS only enabled the phone will eventually want to find its location and then if you're in a building where there is no GPS single, it will kill your battery trying to find one. So I finally stumbled across SlimLP which is an AOSP rom that has app ops baked into it. I found that if I simply modify the permissions of google play services and not allow it to use location, and also disable its ability to hold a wakelock, the nlp wakelocks (both) are gone forever. However, as soon as nlp is gone, the phone falls back to its backup plan which is RILJ to locate itself. So I then went into the phone apps permissions and disabled location and wakelock for it too. FINALLY these wakelocks are gone forever. My phone now loses 3% over 8 hours without disabling location services. There are literally 10 or less wakelocks system wide over 8 hours while I sleep, which is a huge contrast to the waking once every 25 seconds to check my location (or whatever absurd rate it was doing it). The only thing I can spot thats out of place it that google play services is registering a ton of alarms for location related stuff in better battery stats. I'm happy with this so far but feel it could be even better once I learn more.
What I really want to do is to be able to apply this to any android phone, such as my girlfriends z3. Unfortunately I can only get this to work with AOSP roms that have app ops built into them. I tried adding app ops to google based roms and even aosp roms and it doesnt work the same. If anyone could tell me what is different about roms with app ops built in, that would be great. I think we should look into this more to learn as much as possible because this affects everyone with an android phone. Thanks for reading.
Click to expand...
Click to collapse
Wrong section...you might want to try Xposed and Amplify.
EDIT: I just realized I posted wrong section. For some reason, I thought this was Android Dev. Sorry
niral7 said:
Wrong section...you might want to try Xposed and Amplify.
EDIT: I just realized I posted wrong section. For some reason, I thought this was Android Dev. Sorry
Click to expand...
Click to collapse
I've tried amplify as stated in the op. I'm surprised more people aren't bothered by wakelocks. I can't stand them.
seh6183 said:
I've tried amplify as stated in the op. I'm surprised more people aren't bothered by wakelocks. I can't stand them.
Click to expand...
Click to collapse
They're necessary to some degree. Google Now and other location-based/sync programs need them to work. They just get annoying when they're fired up every minute.
niral7 said:
They're necessary to some degree. Google Now and other location-based/sync programs need them to work. They just get annoying when they're fired up every minute.
Click to expand...
Click to collapse
Well I've disabled the wakelocks and every location service including google now still functions as normal. The only benefit is me gaining 50% of my battery back. I just need to figure out what is so special about AOSP ROMs that have app ops baked in so I can apply these techniques to other phones.
So the App Ops Xposed module doesn't work the same way?
hayzooos said:
So the App Ops Xposed module doesn't work the same way?
Click to expand...
Click to collapse
It works exactly the same except for some odd reason the wakelocks won't stop when you start disabling google play services and phone. It will disable other things without any problems. I'm thinking that maybe SlimLp has a different google play services app with different permissions or something. I'm not exactly sure what it is yet but I'm still looking into it on a daily basis. All I know is that 9000 wakelocks at the end of the day from google play services is UNACCEPTABLE and pisses me off. So I set out to find a way to stop them.
seh6183 said:
It works exactly the same except for some odd reason the wakelocks won't stop when you start disabling google play services and phone. It will disable other things without any problems. I'm thinking that maybe SlimLp has a different google play services app with different permissions or something. I'm not exactly sure what it is yet but I'm still looking into it on a daily basis. All I know is that 9000 wakelocks at the end of the day from google play services is UNACCEPTABLE and pisses me off. So I set out to find a way to stop them.
Click to expand...
Click to collapse
Glad you found a way to stop them and more so you decided to post your way to stop them here.
seh6183 said:
It works exactly the same except for some odd reason the wakelocks won't stop when you start disabling google play services and phone. It will disable other things without any problems. I'm thinking that maybe SlimLp has a different google play services app with different permissions or something. I'm not exactly sure what it is yet but I'm still looking into it on a daily basis. All I know is that 9000 wakelocks at the end of the day from google play services is UNACCEPTABLE and pisses me off. So I set out to find a way to stop them.
Click to expand...
Click to collapse
Cataclysm Rom also has a App Ops. So I assume i can get same improvements as you do?
Or am I wrong and thinking the opposite direction?
Zwambo said:
Cataclysm Rom also has a App Ops. So I assume i can get same improvements as you do?
Or am I wrong and thinking the opposite direction?
Click to expand...
Click to collapse
It should work yes. Go into google play services from apps, its in settings, then click modify, then disable location and wake lock. Do the same for phone. There are two phone apps and a dialer making it confusing. You'll want to disable the location and wakelock setting on the phone app which has the location toggle. The other phone app doesn't have a location toggle and you'll know that's not the right one.
After doing this, if you monitor with wake lock detector, you'll see that both NLP wakelocks are stopped completely instead of the 1000 an hour like usual. Same goes for RILJ. Google play services is still generating thousands of alarms each day for location related stuff and I have found a way to fix that as well but it needs more testing.
To put it simply, when my phone goes to sleep, that exactly what I want it to do, not appear as if its asleep and constantly check my location so that it can better offer me ads and places of interest near by.
Doesn't the Phone app NEED to be able to keep the phone awake, so that it doesn't go to sleep mid-call?
setspeed said:
Doesn't the Phone app NEED to be able to keep the phone awake, so that it doesn't go to sleep mid-call?
Click to expand...
Click to collapse
It has no effect on the function of the phone at all except to eliminate the RILJ wakelock. I'm pretty sure this wakelock is the phones radio trying to triangulate your position using cell towers but not sure.
All solutions I've seen or heard about untill now are just workarounds, and I found an elegant solution that allows geoloc to be on all the time.
I detailed it in a battery thread because of the savings it can offer : it consist of an app that replaces nlp with a local db : http://forum.xda-developers.com/showthread.php?p=59184505
I didn't try out with all google goeloc services but maps didn't seem to bother...
Gentaz said:
All solutions I've seen or heard about untill now are just workarounds, and I found an elegant solution that allows geoloc to be on all the time.
I detailed it in a battery thread because of the savings it can offer : it consist of an app that replaces nlp with a local db : http://forum.xda-developers.com/showthread.php?p=59184505
I didn't try out with all google goeloc services but maps didn't seem to bother...
Click to expand...
Click to collapse
My solution has zero impact on location services as well. You're saying that your method totally stops NLP wakelocks and if you were to open maps, it would lock your location precisely?
seh6183 said:
It should work yes. Go into google play services from apps, its in settings, then click modify, then disable location and wake lock. Do the same for phone. There are two phone apps and a dialer making it confusing. You'll want to disable the location and wakelock setting on the phone app which has the location toggle. The other phone app doesn't have a location toggle and you'll know that's not the right one.
After doing this, if you monitor with wake lock detector, you'll see that both NLP wakelocks are stopped completely instead of the 1000 an hour like usual. Same goes for RILJ. Google play services is still generating thousands of alarms each day for location related stuff and I have found a way to fix that as well but it needs more testing.
To put it simply, when my phone goes to sleep, that exactly what I want it to do, not appear as if its asleep and constantly check my location so that it can better offer me ads and places of interest near by.
Click to expand...
Click to collapse
Thx a million!
Will look in to those settings from the phone apps and google play services. Love it when the app ops is included in the ROM!
seh6183 said:
My solution has zero impact on location services as well. You're saying that your method totally stops NLP wakelocks and if you were to open maps, it would lock your location precisely?
Click to expand...
Click to collapse
The fact that the gapps have a mind of their own is not big news, but alternatives exists to avoid dealing with them☺
I didn't say it will stop any wakelock (and I don't want to) : on the contrary, it consist of replacing the stock nlp with a more evolved one that allows to switch to a local db which is far less battery consuming for several reasons.
I didn't say it was "gps precise" either : it will locate you at the nearest antenna if you try a gps app like maps (did you actually read my link ?). Most of the time it has between 500m and 1500m (about a mile) uncertainty reported by the apps.
It just provides precise enough geoloc services for 95% of the apps you're using, even with your screen off like weather, loc. based profile mangers, local news, traffic, job/dating app or whatever... Granted : it won't compete with gps for you navigation or atronomy app but that's the 5% left when you'll switch the gps on ?
There should be a reason why you have so much wakelocks that does not involve blocking calls from a middleware as an answer.
Gentaz said:
The fact that the gapps have a mind of their own is not big news, but alternatives exists to avoid dealing with them
I didn't say it will stop any wakelock (and I don't want to) : on the contrary, it consist of replacing the stock nlp with a more evolved one that allows to switch to a local db which is far less battery consuming for several reasons.
I didn't say it was "gps precise" either : it will locate you at the nearest antenna if you try a gps app like maps (did you actually read my link ?). Most of the time it has between 500m and 1500m (about a mile) uncertainty reported by the apps.
It just provides precise enough geoloc services for 95% of the apps you're using, even with your screen off like weather, loc. based profile mangers, local news, traffic, job/dating app or whatever... Granted : it won't compete with gps for you navigation or atronomy app but that's the 5% left when you'll switch the gps on
There should be a reason why you have so much wakelocks that does not involve blocking calls from a middleware as an answer.
Click to expand...
Click to collapse
If its crippling the phones ability to locate itself accurately then I am not interested as occasionally navigation is important to me. Also of it doesn't stop wakelocks then I am certainly not interested. The way that you word things makes it very difficult to get your point across I might add. I had a hard time following your post.
What I did to get zero battery drain with GPS set on high accuracy:
- Download Disable Service from Google Play: https://play.google.com/store/apps/details?id=cn.wq.disableservice&hl=nl
- Go to System, then Google Play Services and disable everything that has something to do with 'Wear' and 'Fitness' since I don't use any of these features (for me these gave me wakelocks, but I'm not sure if this is the case for everyone), so: BrokeredFitnessService, WearableControlService, WearableService and WearableSyncService.
- Download LBE Security Master (http://forum.xda-developers.com/showthread.php?t=1422479) for its permission manager.
- Disable any location permission of all your apps that you don't want to use GPS (and other permissions to save more battery, but that's another topic).
I have to say I have Google Now disabled, and of course my phone is rooted to be able to use these apps. I run stock rom with stock kernel, and my battery is great with GPS enabled constantly.
seh6183 said:
If its crippling the phones ability to locate itself accurately then I am not interested as occasionally navigation is important to me. Also of it doesn't stop wakelocks then I am certainly not interested. The way that you word things makes it very difficult to get your point across I might add. I had a hard time following your post.
Click to expand...
Click to collapse
I guess you missinterpreted what I said : just enable gps when you need navigation... Gsm based location accuracy is ok for all the rest.
- wakelock issues either came from the way the phone is set up or an uncommon situation causing this (bug, bloat, bad network or gps reception...) : blocking them is not a solution, it's a workaround and, if I undestood you correctly, is only valid for some cases and is fastidious/maintenance intensive. There are already many nexus 5 and other threads dealing with those issues anyway and It would be easier to just disable geoloc when screen is off.
- I suggested a solution less battery draining for 95% of goeloc based needs and is valid for most android phones and roms as long as you have root, not yet another a nlp/wakelock blocking "trick".
It's ok if your girlfriend doesn't mind having her z3 flashed with an ASOP ops enabled rom and learn to block the wakelocks of the new apps she installs, but I prefer not having to explain mine what a wakelock is ☺
- It doesnt cripple your phone at all, it extends its possibilities by adding a gsm based backend to the location provider : your phone was already doing the same except it had to go to a google hosted database to match your location to your antenna or ip when it is set to use network based location.
Gentaz said:
I guess you missinterpreted what I said : just enable gps when you need navigation... Gsm based location accuracy is ok for the all the rest.
- wakelock issues either came from the way the phone is set up or an uncommon situation causing this (bug, bloat, bad network or gps reception...) : blocking them is not a solution, it's a workaround and, if I undestood you correctly, is only valid for some cases and is fastidious/maintenance intensive. There are already many nexus 5 and other threads dealing with those issues anyway and It would be easier to just disable geoloc when screen is off.
- I suggested a solution less battery draining for 95% of goeloc based needs and is valid for most android phones and roms as long as you have root, not yet another a nlp/wakelock blocking "trick".
It's ok if your girlfriend doesn't mind having her z3 flashed with an ASOP ops enabled rom and learn to block the wakelocks of the new apps she's installing, but I prefer not having to explain mine what a wakelock is
- It doesnt cripple your phone at all, it extends its possibilities by adding a gsm based backend to the location provider : your phone was already doing the same except it had to go to a google hosted database to match your location to yourantenna or ip when it is set to use network based location.
Click to expand...
Click to collapse
Your solution is very interesting for sure and something I will try, but my gut feeling is that google play services is still going to look for my location just as often, waking the phone, even though it's communicating with a different database.
Also I'm not sure if you're suggesting that my phone specifically is having NLP wakelocks because it is broken or setup incorrectly, but if so that is totally inaccurate. All android phones are suffering from this wakelock whether the user is aware of it or not. The only ones not having NLP wakelocks are the ones who have disabled location services or somehow turned off the wakelock like I have.
So I just discovered the magical world of tasker, and am loving it! Totally worth the money, and one of the best apps to have (the best if you know how to maximise its use)! I have been experimenting a bit with it, so I don't have many profiles. I'm sure many folks here will be using tasker and would be having some great profiles, so I'm looking forward to hearing some suggestions! The profiles I use are:
1. WiFi off at night, from 00:45 to 08:00, except WhatsApp, Play Store, Quora
2. Airplane mode at night, from 00:30 to 07:00
3. Use of interactive CPU governor when using Real Racing 3, and revert to lionfish governor after exiting app(Kernel adiutor profiles do this for me). I also added a condition to use auto-rotate when playing the game, and revert to portrait orientation after closing the app.
4. Auto-sync every two hours, from 08:00 to 20:00 (I would like to improve this to auto-sync only Gmail, would welcome suggestions on how to do this from any tasker experts out here )
I would love to implement more profiles and automate my phone, so looking for ideas.
Need a tasker profile which can disable my mobile data only for some specific apps.it means If I start those apps then my mobile data would automatically disabled and when I close them Data service should be enbled.If u can help on this then That wud be very helpfull
Nothing very fancy for me - right now just have it turning on my wifi hotspot when it detects my car's bluetooth connection so my stereo can use the internet.
It sounds like you are taking it pretty far, @varunadi. You should check out https://www.reddit.com/r/tasker for more cool ideas.
koimr said:
Nothing very fancy for me - right now just have it turning on my wifi hotspot when it detects my car's bluetooth connection so my stereo can use the internet.
It sounds like you are taking it pretty far, @varunadi. You should check out https://www.reddit.com/r/tasker for more cool ideas.
Click to expand...
Click to collapse
Yep, I am looking to maximise the use of this app, so thanks for that link, will check it out!
anks095 said:
Need a tasker profile which can disable my mobile data only for some specific apps.it means If I start those apps then my mobile data would automatically disabled and when I close them Data service should be enbled.If u can help on this then That wud be very helpfull
Click to expand...
Click to collapse
I'm still finding my way around tasker, reading a lot of tutorials so once I figure it out I'll let you know.
anks095 said:
Need a tasker profile which can disable my mobile data only for some specific apps.it means If I start those apps then my mobile data would automatically disabled and when I close them Data service should be enbled.If u can help on this then That wud be very helpfull
Click to expand...
Click to collapse
I don't know if you can disable mobile data entirely (not just background which Android can do already) for just certain apps.
Perhaps it would be easier to use something like Netguard.
I've never used it but the description says "Applications can individually be allowed or denied access to your Wi-Fi and/or mobile connection."
koimr said:
I don't know if you can disable mobile data entirely (not just background which Android can do already) for just certain apps.
Perhaps it would be easier to use something like Netguard.
I've never used it but the description says "Applications can individually be allowed or denied access to your Wi-Fi and/or mobile connection."
Click to expand...
Click to collapse
Can't the secure settings plugin be used for that purpose? Toggle data on/off I mean.
varunadi said:
Can't the secure settings plugin be used for that purpose? Toggle data on/off I mean.
Click to expand...
Click to collapse
I was actually going to suggest that as I have it installed already but when I tried it didn't work.
The "Mobile data" toggle was unavailable because it claims I don't have root. However, I'm definitely rooted and there's no listing (saying denied or otherwise) in SuperSU for Secure Settings so it didn't even ask for root. I'm not too surprised as SS hasn't been updated in over a year and a lot of the Play Store comments mention mobile data toggle specifically not working either (among other things). Too bad as it was pretty powerful and of course I think I paid for it right after its last update.
Not getting SS working for me might just be my problem and perhaps someone else can get it going.
I was also going to suggest [APP][2.2+][ROOT] Toggle Data 5.0 (xda-exclusive free version) but then I read more about what @anks095 said which was "can disable my mobile data only for some specific apps" so I'm guessing he just wants certain apps restricted and not all (although the next sentence seems to say otherwise but I might be reading it incorrectly). I'm not too sure that can be done via Tasker/SS - my guess is that it's an "all-or-nothing" kinda thing for mobile data so the VPN thing might be the only way.
I use a similiar app called automagic but some of the things that I got my tasker like program to do are: lockscreen enable/disable through wi-fi at trusted places (don't like geofencing due to battery), when connected to the bluetooth of my car. Auto silent 5 min before a meeting, but if not connected to my smartwatch then vibrate. And lastly sms emergency location request where my family can send a keyword and my phone will automatically send location.
joeanca said:
I use a similiar app called automagic but some of the things that I got my tasker like program to do are: lockscreen enable/disable through wi-fi at trusted places (don't like geofencing due to battery), when connected to the bluetooth of my car. Auto silent 5 min before a meeting, but if not connected to my smartwatch then vibrate. And lastly sms emergency location request where my family can send a keyword and my phone will automatically send location.
Click to expand...
Click to collapse
How is the lockscreen one working for you? I find the built-in SmartLock to be really unreliable but when I tried to do lockscreen stuff before (last year) there was some bug in either Tasker or Secure Settings that would sometimes keep your screen black with just the nav buttons visible present. I'll have to re-try now.
That sms emergency request thing sounds cool! Can the recipient open the location in Maps to see exactly where you are?
Without issues I set it so that it clears the password. Makes it so that I have to swipe to unlock. As for the location, yes it sends coordinates and the user in the other end taps it to bring up Google maps.
Sent from my XT1563 using Tapatalk
joeanca said:
Without issues I set it so that it clears the password. Makes it so that I have to swipe to unlock. As for the location, yes it sends coordinates and the user in the other end taps it to bring up Google maps.
Sent from my XT1563 using Tapatalk
Click to expand...
Click to collapse
Thank you very much - clearing the password was the key! I had been trying before to disable the keyguard entirely so I wouldn't even have to swipe but that's where the problem/bug came in. Thinking about it that makes more sense to have at least a swipe because I'd end up calling people from my pocket by mistake. So thanks again!
Tasker...hmmm. Bought it, but much to complicated for me. Macrodroid is much easier to understand and can also do complicated automation with a normal user friendly interface. I tried to like Tasker, but the more and more I tried the more stupid I felt.
Hello people,
I don't know if anyone else is experience this but I thought I mention it. Also I apologise if this is the incorrect place to start this thread, but I have looked on xda for a tasker dedicated section for troubleshooting.
Now I have a automated WIFI profile that basically enables whenever I load a specific app. But for some strange reason it does not always execute, when a specific app does load and other times it does?
Does anyone else notice this strange behaviour going on with tasker?
If so is it a bug that needs reporting or is there something wrong with my profile?
Thanks in advance!
In Tasker settings/preferences/monitor put to "Always" the Use Reliable Alarms option.
GrippingSphere said:
In Tasker settings/preferences/monitor put to "Always" the Use Reliable Alarms option.
Click to expand...
Click to collapse
It seems the profile triggers, but not the task.
HatchetEgg said:
It seems the profile triggers, but not the task.
Click to expand...
Click to collapse
You can test the Task by manually executing it. Maybe you're using a plug-in that requires permissions to run.
GrippingSphere said:
You can test the Task by manually executing it. Maybe you're using a plug-in that requires permissions to run.
Click to expand...
Click to collapse
If I run the task manually everything executes just fine.
The task does use one plugin and thats for secure settings, but thats about it.
UPDATE: I think I might know what the problem is, and I think that tasker is unable to wake the device to execute the task, so I added a wake device action in my task and see if this works.
In LL and MM there is battery optimization where Tasker and Secure Settings should be excluded. Other 3rd party battery saving apps might also affect the operation of Tasker and its plugins.
GrippingSphere said:
In LL and MM there is battery optimization where Tasker and Secure Settings should be excluded. Other 3rd party battery saving apps might also affect the operation of Tasker and its plugins.
Click to expand...
Click to collapse
This is true I had taken the advice from here >
As far as I am aware tasker and it's plugins are whitelisted from other 3rd party on my device, so I still don't understand why it still does not work unless I add the wake device action from secure settings.
Any luck on this? I'm noticing that tasker is very slow to execute any actions outside of the app. Meaning, if I create a task that simply has one step..."beep". Next, add that task as a shortcut to my nova launcher desktop. Click the shortcut...it takes almost 30seconds for it to execute the beep. I've been a tasker user for years. Not sure why this lag is occurring.
Tried this...
Tasker is not battery optimized.
Reinstalled Tasker.
rooted Pixel, 7.1.1
I have the same problem with my periodical Wi-Fi check.I have to add the 1 second CPU wake, but it's still not very reliable.maybe the best way to get over this is turning on the screen, but this is kind of defeat the purpose for me so....
any other suggestion?
soundneedle said:
Any luck on this? I'm noticing that tasker is very slow to execute any actions outside of the app. Meaning, if I create a task that simply has one step..."beep". Next, add that task as a shortcut to my nova launcher desktop. Click the shortcut...it takes almost 30seconds for it to execute the beep. I've been a tasker user for years. Not sure why this lag is occurring.
Tried this...
Tasker is not battery optimized.
Reinstalled Tasker.
rooted Pixel, 7.1.1
Click to expand...
Click to collapse
There is one thing that you can try go to Tasker > preferences > misc and untick reduce resource usage.
alienyd said:
I have the same problem with my periodical Wi-Fi check.I have to add the 1 second CPU wake, but it's still not very reliable.maybe the best way to get over this is turning on the screen, but this is kind of defeat the purpose for me so....
any other suggestion?
Click to expand...
Click to collapse
I have tried the screen wake function, but even then it doesn't work.
I did notice however that Google connectivity was causing issues for me, such as not able to connect to my ap automatically.
Hello guys,
I'm trying to do this in Tasker:
AFTER display OFF
WAIT for x seconds
CHECK if screen OFF
IF yes, activate Power Save task (Kernel Plugin)
IF no, do nothing.
Do this every time display is turned off.
Any help on how to go about it would be appreciated, thanks!
I guess you know about event screen off already...use it. In the task:
WAIT xx
IF current profile is still active:
do your stuff with your plugin
alienyd said:
IF current profile is still active
Click to expand...
Click to collapse
https://tasker.dinglisch.net/userguide/en/variables.html
Checking %PACTIVE can be useful. I have started using it instead of custom global variables, so that I don't need Tasker running in the foreground. The typical recommendation is to match the following, which does not update if you ever happen to change the profile name.
%PACTIVE ~ *,Profile Name,*
In this case there's also a Tasker variable to check, so just testing the following is another possibility.
%SCREEN ~ off
alienyd said:
I guess you know about event screen off already...use it. In the task:
WAIT xx
IF current profile is still active:
do your stuff with your plugin
Click to expand...
Click to collapse
alluringreality said:
https://tasker.dinglisch.net/userguide/en/variables.html
Checking %PACTIVE can be useful. I have started using it instead of custom global variables, so that I don't need Tasker running in the foreground. The typical recommendation is to match the following, which does not update if you ever happen to change the profile name.
%PACTIVE ~ *,Profile Name,*
In this case there's also a Tasker variable to check, so just testing the following is another possibility.
%SCREEN ~ off
Click to expand...
Click to collapse
Thanks a lot for replying guys!
Now, if I understand it right, this should do the trick. (check attached pic please)
Any corrections to be made?
I think a * is typically used before and after the comma to allow the possibility of multiple active profiles, similar to the example.
Sharan A. said:
Thanks a lot for replying guys!
Now, if I understand it right, this should do the trick. (check attached pic please)
Any corrections to be made?
Click to expand...
Click to collapse
I have a question: why do you need both %SCREEN and %PACTIVE? imo PACTIVE should already be enough, it checks if all conditions for your profile still meet after the wait. These conditions are of course not limited to screen state only like the SCREEN. Of course you can use SCREEN. I just prefer PACTIVE for its flexibility.
Also, you should really consider enclosing profile name in the *, as it could eventually come to the point that you have more than one active profile at the same time. Therefore I would recommend ~*Profile_name* too. I never had any problem NOT including the commas though.
alluringreality said:
I think a * is typically used before and after the comma to allow the possibility of multiple active profiles, similar to the example.
Click to expand...
Click to collapse
alienyd said:
I have a question: why do you need both %SCREEN and %PACTIVE? imo PACTIVE should already be enough, it checks if all conditions for your profile still meet after the wait. These conditions are of course not limited to screen state only like the SCREEN. Of course you can use SCREEN. I just prefer PACTIVE for its flexibility.
Also, you should really consider enclosing profile name in the *, as it could eventually come to the point that you have more than one active profile at the same time. Therefore I would recommend ~*Profile_name* too. I never had any problem NOT including the commas though.
Click to expand...
Click to collapse
Oh okay, I didn't see the star in the link that was provided I guess. Will include that.
@alienyd So I re thought about it and now I think, in my case, just the SCREEN usage will be enough.
I have some confusion regarding PACTIVE. Should I match it to the profile that I WANT to activate or is it something else?
Edit: Finally got it working! Check pic please.
http://pasteboard.co/BgYZ2sOC8.png
Thanks again for your support guys!
Sharan A. said:
Oh okay, I didn't see the star in the link that was provided I guess. Will include that.
@alienyd So I re thought about it and now I think, in my case, just the SCREEN usage will be enough.
I have some confusion regarding PACTIVE. Should I match it to the profile that I WANT to activate or is it something else?
Edit: Finally got it working! Check pic please.
http://pasteboard.co/BgYZ2sOC8.png
Thanks again for your support guys!
Click to expand...
Click to collapse
Hi,
just to clear things up, and also to share this trick, which I think is very helpful when using Tasker:
As explained, PACTIVE checks if a profile is active - not only enabled, but all conditions are met.
Imagine this scenario, you have a profile triggered, but want to make sure it was not an accident, like covering proximity, turning upside down, screen on/off.
You have a wait at the beginning of the task of that profile, so when the profile is triggered, first it does nothing, then rechecks if itself is still qualified to run.
Of course it can be used to check other profiles, but I'm just talking about this self checking case here.
alienyd said:
Hi,
just to clear things up, and also to share this trick, which I think is very helpful when using Tasker:
As explained, PACTIVE checks if a profile is active - not only enabled, but all conditions are met.
Imagine this scenario, you have a profile triggered, but want to make sure it was not an accident, like covering proximity, turning upside down, screen on/off.
You have a wait at the beginning of the task of that profile, so when the profile is triggered, first it does nothing, then rechecks if itself is still qualified to run.
Of course it can be used to check other profiles, but I'm just talking about this self checking case here.
Click to expand...
Click to collapse
Oh so that means
%PACTIVE ~ *, profile that I want enabled when screen off (power save),*
So in this case, first it's going to wait x seconds, then it'll check if Display is still OFF (by checking if display off profile is active) and finally it'll run the task that I want. Correct?
Sharan A. said:
Oh so that means
%PACTIVE ~ *, profile that I want enabled when screen off (power save),*
So in this case, first it's going to wait x seconds, then it'll check if Display is still OFF (by checking if display off profile is active) and finally it'll run the task that I want. Correct?
Click to expand...
Click to collapse
no, what you are having is already correct I think.
I was just trying to explain how use PACTIVE in general, not only in your case.
The idea is, when profile A is active, have it do nothing first, than recheck if profile A is still active, to make sure that it was not triggered by mistake, than carry out its actions.
So if you have something like:
(Screen-off-profile)
IF screen is off
DO:
wait
check again, Screen-off-profile is still active? (not accidentally turned off)
do the rest
alienyd said:
no, what you are having is already correct I think.
I was just trying to explain how use PACTIVE in general, not only in your case.
The idea is, when profile A is active, have it do nothing first, than recheck if profile A is still active, to make sure that it was not triggered by mistake, than carry out its actions.
So if you have something like:
(Screen-off-profile)
IF screen is off
DO:
wait
check again, Screen-off-profile is still active? (not accidentally turned off)
do the rest
Click to expand...
Click to collapse
Oh yeah that's what I meant, thanks! Pretty neat trick ?
How about this? Screen off set variable myDISPLAY=off, on screen on set variable myDISPLAY=on
On your profile set an if action
if variable value myDISPLAY=off then...
loogielv said:
How about this? Screen off set variable myDISPLAY=off, on screen on set variable myDISPLAY=on
On your profile set an if action
if variable value myDISPLAY=off then...
Click to expand...
Click to collapse
Thanks, though I've got it working by just using SCREEN!
Sharan A. said:
Oh yeah that's what I meant, thanks! Pretty neat trick ?
Click to expand...
Click to collapse
I tend to stay away from wait tasks as it's a battery CRUSHER and basic bad programming.
Instead, set low lvl variables such as myDISPLAY=off/on/locked/unlocked and myPHONESTATUS=in call/offhook etc and do variable value checks. Or do variable events and activate your profile on the variable set
And then on your low lvl profiles set their priority to extremely high, and add stop actions for entry and exit tasks so that way you're never waiting. Avoid wait tasks and you'll see your battery life jump immediately. Also never do app contexts, as app polling will crush battery too
loogielv said:
I tend to stay away from wait tasks as it's a battery CRUSHER and basic bad programming.
Instead, set low lvl variables such as myDISPLAY=off/on/locked/unlocked and myPHONESTATUS=in call/offhook etc and do variable value checks. Or do variable events and activate your profile on the variable set
Click to expand...
Click to collapse
Is there any battery efficient alternative to WAIT? I'd like to have a window of time before power saver activates.
Sharan A. said:
Thanks, though I've got it working by just using SCREEN!
Click to expand...
Click to collapse
Awesome. Just remember, screen not on isn't the same as screen off, and screen unlocked isn't the same as screen on. I mean those are obvious, but unlocked is an instant event, and sometimes fails to register, especially on a screen off then user turns it right back on. Sometimes Tasker believes the screen is still off, especially if the screen wasn't unlocked, which it wouldn't need to be if it wasn't off for longer than half a second
---------- Post added at 07:09 AM ---------- Previous post was at 07:06 AM ----------
Sharan A. said:
Is there any battery efficient alternative to WAIT? I'd like to have a window of time before power saver activates.
Click to expand...
Click to collapse
Then set TIMERACTIVATE or some such variable to %TIMES+60 (ONE minute from now) and make it activate on a time context of %TIMERACTIVATE
then you're having zero impact on your battery because it's ticking the seconds already built-in, and monitored with %TIMES
Oh yeah, and then set your power saving profile, and your screen on profile to clear the TIMERACTIVATE variable, which in essence disables the profile (it can never activate without the variable set) and your screen off profile to set the variable. Bam. Zero impact
loogielv said:
Then set TIMERACTIVATE or some such variable to %TIMES+60 (ONE minute from now) and make it activate on a time context of %TIMERACTIVATE
then you're having zero impact on your battery because it's ticking the seconds already built-in, and monitored with %TIMES
Oh yeah, and then set your power saving profile, and your screen on profile to clear the TIMERACTIVATE variable, which in essence disables the profile (it can never activate without the variable set) and your screen off profile to set the variable. Bam. Zero impact
Click to expand...
Click to collapse
I'm sorry but is it possible to show this procedure in Tasker? I'm kinda confused since I'm still a newbie. ?
I'm going to guess loogielv may be talking about doing something similar to the following links. In there they use two profiles for their operation. They use one profile to set a time to a global user variable, and they have a second profile activate based on that global user variable.
http://www.pocketables.com/2016/08/tasker-timers.html
http://www.notenoughtech.com/tasker/tasker-timers/
Personally I got away from using global user variables, because the way I was using them required having Tasker running in the foreground. I prefer being able to leave that option off. I would guess Tasker could potentially miss the sort of event mentioned in the links above when not running in the foreground.
I'm not sure if there are ways to do what loogielv was talking about using a local (lowercase) user variable, or if there's another option that would allow me to not use "Wait" and continue to keep from running in the foreground. I figure a loop could potentially use more battery to perform than Tasker's wait. Based on the action descriptions, maybe "Wait Until" could be more battery efficient than "WAIT". It looks like there's also an AutoTools Wait, which the description compares to Tasker's "Wait Until". That's all I could come up with for trying to keep from running in the foreground.
alluringreality said:
I'm going to guess loogielv may be talking about doing something similar to the following links. In there they use two profiles for their operation. They use one profile to set a time to a global user variable, and they have a second profile activate based on that global user variable.
http://www.pocketables.com/2016/08/tasker-timers.html
http://www.notenoughtech.com/tasker/tasker-timers/
Personally I got away from using global user variables, because the way I was using them required having Tasker running in the foreground. I prefer being able to leave that option off. I would guess Tasker could potentially miss the sort of event mentioned in the links above when not running in the foreground.
I'm not sure if there are ways to do what loogielv was talking about using a local (lowercase) user variable, or if there's another option that would allow me to not use "Wait" and continue to keep from running in the foreground. I figure a loop could potentially use more battery to perform than Tasker's wait. Based on the action descriptions, maybe "Wait Until" could be more battery efficient than "WAIT". It looks like there's also an AutoTools Wait, which the description compares to Tasker's "Wait Until". That's all I could come up with for trying to keep from running in the foreground.
Click to expand...
Click to collapse
So, Wait>10 seconds>Until SCREEN ~ off
Correct?
For my waits that last a few minutes I was thinking of setting a local variable (lowercase) to %TIMES + X. Then I was going to use the "Wait Until" action to check if %TIMES was greater than my variable. That way there would always be an end to the "Wait Until" action.
My understanding, based on items like the following, is that if you were to just check for screen off at 10 seconds with "Wait Until" it would keep checking every 10 seconds if the screen was on. Personally that would seem like a potentially bigger issue than using "Wait".
https://www.reddit.com/r/tasker/comments/3cdtjz/can_someone_explain_the_wait_until_task_to_me_it/
EDIT: I see that checking on %qtime has been suggested as another way to keep "Wait Until" from going endlessly, yet %qtime could be interrupted by other tasks
https://www.reddit.com/r/tasker/com...it_until_action_wait/?st=izr2om1x&sh=42e0ae24
http://tasker.dinglisch.net/userguide/en/variables.html