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
Related
Hi:
I am looking for an app to filter calls. I would like to allow only certain numbers, and block or silence the rest. All the apps I have found do the opposite, they block only the numbers you ask them to, and it would be very impractical to have to add all numbers except for the 2 I want to allow.
The latest one I tried was call filter, which was great, and easy to use, but the same as the others, you could only block individual numbers, rather than allow only specific numbers.
Thanks!
You can use Tasker to do that. I had a Tasker profile that ran at night when my phone was on silent. It would ring only if calls came in from my children or my parents. You could use the same type of profile but have it active all the time.
Tasker is more complicated than your typical android app. But there are example profiles that you can download and modify.
Sent from my Captivate
Hi Redger:
Thanks so much for your reply. I downloaded and installed tasker. You are right, it is complicated. I installed the sample profiles for Auto Sleep Mode with Exceptions (sounds like what you mentioned).
I made it as far as adding the numbers I do want to ring. I am wondering is there any way to activate it manually (maybe a one click home screen type thing), rather than right now it is set to start automatically at a certain time?
Basically what I would like to do, is have only 2 phone numbers able to reach me (for both voice and sms calls) while I am sleeping, and all other numbers to be completely silenced.. I don't really want it to start and stop at a certain time, because my bedtime varies greatly from one day to the next.
Any help would be appreciated.
Thanks again!
cincy1020 said:
Hi Redger:
Thanks so much for your reply. I downloaded and installed tasker. You are right, it is complicated. I installed the sample profiles for Auto Sleep Mode with Exceptions (sounds like what you mentioned).
I made it as far as adding the numbers I do want to ring. I am wondering is there any way to activate it manually (maybe a one click home screen type thing), rather than right now it is set to start automatically at a certain time?
Basically what I would like to do, is have only 2 phone numbers able to reach me (for both voice and sms calls) while I am sleeping, and all other numbers to be completely silenced.. I don't really want it to start and stop at a certain time, because my bedtime varies greatly from one day to the next.
Any help would be appreciated.
Thanks again!
Click to expand...
Click to collapse
You can put a shortcut on the screen to tasker, and it will open to the tasks. Click on the real to turn off. 2 clicks I know.
I think the tasker forums can tell you how to make the task into a "program" like you want.
Edit. Try long pressing on the screen and go to task. It might be there.
Download the generic toggle widget. You can put the widget on your home screen and program it to toggle your sleep mode profile. Remove the time constraints from the sleep profile and set it up to work with the toggle widget.
Sent from my Captivate
Edited original post as now getting. a collection of tasker tasks i have going on and easier to keep them in the first post but Will help below if anybody wants to copy them, also if anyone else wants to post there's that will be good.
1st) have tasker to toggle settings like wifi brightness etc when i get to work. Reverts settings back when i get home. Produces notifications on watch.
2nd) sends a message to my wife when i say launch task 1 that tells her im on my way home.
3) launches a autowear location menu on the watch. In the menu i can select wether i want high accuracy or low and wether i want location services on or off atall.
4) when i charge my phone between 2230hrs and 0625hrs the watch is switched to screen off, Bluetooth off and phone set to vibrate. When its unplugged or after 0625 the watch is switched to always on and phone is muted.
5) mobile data on and off options via autowear.
6) detects when i have lost connection to the watch and immediately turns on GPS to record the location. Then notifies me on my phone with a map view. I fix generators for a living so i need to take my watch of sometimes or when i have a shower in the gym etc. If for whatever reason i forget it which is unlikely i will know where i last had it.
7) every morning when i take my phone and watch off charge it selects a different watchface every morning at random from a predefined list. (needs watchmaker to be installed)
8) using autowear so that when i start My Tracks on the watch it automatically starts my gps task for me.
9) little on screen widget that i can control my Xbox/sky/tv changing channels, volume, play and pause, go to Fifa 15, record that, turn everything off. Accomplished using autowear, autoremote, autoinput, and a redundant tablet.
I have only just began with tasker so my methods won't be the most efficient but they work. If anyone has better ways as i mainly using auto input then please get in touch.
Could you describe which apps you used to pull this off? Thank you
Yeah sure, was a app called Tasker that i used on my phone to create it all and then a tasker plugin called tasker wear i think.
I have since been tinkering with it.
The updated version now has the following options;
1) text the wife I'm on my way home.
2) turns Wi-Fi of, auto brightness on, sync off
3) opposite of 2.
4) closes and returns back to watch face.
With option 2 and 3 i get a notification of what has beebeen switched on/ off.
With option 1 it also activates option 3 ready for when i get home.
Also if i forget to do the above especially switch evereverything on it detects when I'm nearly home and does it for me.
check AutoWear tasker plugin from joao, you can do anything with it in combination with the other Autoapps.
TheKaser said:
check AutoWear tasker plugin from joao, you can do anything with it in combination with the other Autoapps.
Click to expand...
Click to collapse
I'll have a look at that thanks, currently going to create a task that switches between gps and battery saving location as you can't turn location of anymore. So will have it switch to gps when needed and back to battery saving when not.
Also going to see if i can switch to cinema mode when charging and lost connection to the phone together and to revert back to previous or new watch face when undocked and regains connection to phone.
Hi Phil, would love to hear how you get on with that.
Hi rusty,
Just finished putting something together.
I have tasker detect when it's on charge and if between 2230 and 0625, and if so it switches the watch screen to off, and Bluetooth of.
using a profile manger, that detects that the watch it's no longer connected so switches notifications on the phone back on.
The opposite is when it's unplugged it switches Bluetooth back on, turns the watch screen to always on and the profile manager then detects the watch so turns the phone to mute but watch still vibrates.
I can now sleep at night with no lights keeping me awake and the only thing i have to do is plug my phone in.
Just to note it was pretty simple to set up with tasker and autoinput.
TheKaser said:
check AutoWear tasker plugin from joao, you can do anything with it in combination with the other Autoapps.
Click to expand...
Click to collapse
Hi kaser, as you recommended autowear do you have any experience with it as i can't get my head round it and there isn't much on YouTube or Google to help out.
phil gpx said:
Hi kaser, as you recommended autowear do you have any experience with it as i can't get my head round it and there isn't much on YouTube or Google to help out.
Click to expand...
Click to collapse
Hi, sorry for the late reply, I was on holidays.
I do have some experience. You need to download AutoApps from Google Play and suscribe to the alpha testing. Then you can download AutoWear. For this you also need to joing the Google+ community where the developer is always nice and reactive when posting bugs, questions or guidelines. Posting at the community is the best thing you can do since AutoWear is still in Alpha and it improves every day and it is not too straight forward to understand, especially how it communicates with AutoVoice and how commands and parameters are passed to Tasker.
By the way, I have a similar profile telling my girlfriend when I get to work, when I leave work and when I have parked at home coming from work, which automatically trigger depending on my location and connection to my car's bluetooth or work's WiFi. You don't really need your watch for that
Cheers for replying.
I have already downloaded it and played around but can't get my head around the processes of the app.
I followed the guide for the voice screen but cant get new screens up or start tasks etc.
I'm usually pretty good at working things out but cant with autowear.
what is it you are trying to do? Do you have the latest version of tasker?
Yeah i have the updated tasker but just can't work out how to get from the voice screen too say a "4 menu screen" that has tasks i have set up. Not sure what i want to accomplish with tasker next but i know if i can understand autowear it would help.
Have you done anything with autowear.
I have done the above tasks in the first post with autoinput and taskerwear but that is just a series of notifications that you can select to start tasks.
my main use for autowear is to send whatsapp messages from scratch (whatsapp currently only allows to reply to messages).
To achieve this I open an AutoWear Voice Screen by shaking the watch, and say "write to XXXX and say YYYY". This triggers an AutoVoice profile configured to react to "write to (?<contact>.+) and say (?<message>.+) (using Regex)
Inside the task, I do an WhatsTasker plugin contact search of the variable %contact generated by the regex command. Once found, I text the %message to this contact using whatstasker.
The best thing to do is to read the variable descriptions in the task. For example, you create your profile of AutoVoice Recognized. Inside it, before clicking configuration, you can see all the local variables available and their description. These are usable within the task. Same thing goes for any autowear task, they are usable after calling the task.
For example, in my task, after finding the contact, I have an AutoWear confirmation screen with the picture of my contact, his name, and the message I dictated. And following that I have an if %awmessage (the output of this confirmation screen) is different to cancel, then send the message.
Hope this helps a bit!
Thanks buddy, i will try and emulate this tonight once the kids are in bed. Whatsapp was one of the things i have been thinking of doing, just wish there was a way of bringing up a previous conversation without waiting for a new message.
well maybe you can capture the messages as they come, along with the sender's name, and save them in a temp file. Then create an autowear screen that shows the content of this file when requested... but I guess it would be very difficult to make it work perfectly (especially with groups).
I have managed to create and implement a mobile data on and off switch into my interactive notification popup for system settings using tasker, taskerwear and autoinput.
I now have the ability to switch wifi, mobile data, gps on and off as well as high and low accuracy location services and change profiles from one notifaction popping up.
left watch behind
Currently trying to set up a tasker profile that when i get disconnected from my watch will activate gps, stores the location, notifies you where it is and shows you on the map.
Hopefully will never need it but you never know. I.e you leave it in the gym, at work etc
Is there already something that does something similar as struggling at the moment but will crack on if there isn't.
Any one let me know about how to get nearby cell tower ID in a single variable.
Otherwise, how to convert the context in profile as a task.
Ty
Sent from my Micromax A58 using XDA Free mobile app
I'm sorrlearning tasker but i think if you create a new profile that activates when you connect to that cell tower. Then create a task and set variable %whateveryouwantto to %CellID.
You should only have to do that profile once and the variable will be set and you can use it in your profiles and tasks.
On another note i got my lost watch profile working like a charm.
Great Job
TheKaser said:
my main use for autowear is to send whatsapp messages from scratch (whatsapp currently only allows to reply to messages).
To achieve this I open an AutoWear Voice Screen by shaking the watch, and say "write to XXXX and say YYYY". This triggers an AutoVoice profile configured to react to "write to (?<contact>.+) and say (?<message>.+) (using Regex)
Inside the task, I do an WhatsTasker plugin contact search of the variable %contact generated by the regex command. Once found, I text the %message to this contact using whatstasker.
The best thing to do is to read the variable descriptions in the task. For example, you create your profile of AutoVoice Recognized. Inside it, before clicking configuration, you can see all the local variables available and their description. These are usable within the task. Same thing goes for any autowear task, they are usable after calling the task.
For example, in my task, after finding the contact, I have an AutoWear confirmation screen with the picture of my contact, his name, and the message I dictated. And following that I have an if %awmessage (the output of this confirmation screen) is different to cancel, then send the message.
Hope this helps a bit!
Click to expand...
Click to collapse
It sounds great :good:
May you please share your work with screenshots or something else so I can make it work for me?
Thanks in advance and best regards
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.
Does anyone know if theres a way to send sms 1 minute earlier each day so day 1 its 9:56 day 2 9:55 day 3 9:54.
anthony001 said:
Does anyone know if theres a way to send sms 1 minute earlier each day so day 1 its 9:56 day 2 9:55 day 3 9:54.
Click to expand...
Click to collapse
Use a variable for the profile's time context. In the task, send the sms then decrease the variable by a minute.
ktmom said:
Use a variable for the profile's time context. In the task, send the sms then decrease the variable by a minute.
Click to expand...
Click to collapse
Is there a way to convert string to date or time? my initial variable is a string
anthony001 said:
Is there a way to convert string to date or time? my initial variable is a string
Click to expand...
Click to collapse
You don't need to convert the variable, just use the correct format. To send initial text at 09:56 am, then 1 minute earlier every day;
Initial value %SMSTime =9.56
Set variable %SMSTime-0.01 (check do maths)
tasker time context
If you want to send only on certain day(s), your profile needs a day context as well.
ktmom said:
You don't need to convert the variable, just use the correct format. To send initial text at 09:56 am, then 1 minute earlier every day;
Initial value %SMSTime =9.56
Set variable %SMSTime-0.01 (check do maths)
tasker time context
If you want to send only on certain day(s), your profile needs a day context as well.
Click to expand...
Click to collapse
i already disabled beginner mode but i cant see the field to set the variable on the time context. is this a bug or something?
anthony001 said:
i already disabled beginner mode but i cant see the field to set the variable on the time context. is this a bug or something?
Click to expand...
Click to collapse
Click on the double arrows...
anthony001 said:
i already disabled beginner mode but i cant see the field to set the variable on the time context. is this a bug or something?
Click to expand...
Click to collapse
When not in Beginner Mode, it's possible to specify a global user variable as the source of the From Time or To Time by clicking on one of the rotating-arrow icons
thanks guys. my only problem is that the next day it doesnt trigger. it only triggered once then after the succeding days it doesnt trigger
i have a var %CHECKBAL with value 8.42 and i use that on the time profile like you guys suggested. i put that var on the to and from. Do you guys know what is wrong?
In the profile properties (select the profile then hit the gear icon at top right), is limit repeats checked?
If you go to the variables tab, it's your variable shown and set as you expect?
There's always using tasker's logging to see if there's an error.
ktmom said:
In the profile properties (select the profile then hit the gear icon at top right), is limit repeats checked?
If you go to the variables tab, it's your variable shown and set as you expect?
There's always using tasker's logging to see if there's an error.
Click to expand...
Click to collapse
cant find the gear icon which contains the limit repeats option. i can only see the three dot. the three dot only has "help:this screen" and "userguide" option. Do you mean the repeat checkbox inbetween from and to?
anthony001 said:
cant find the gear icon which contains the limit repeats option. i can only see the three dot. the three dot only has "help:this screen" and "userguide" option. Do you mean the repeat checkbox inbetween from and to?
Click to expand...
Click to collapse
It sounds like you are inside the context setting. You need to access the profile settings. The profile is the contexts that trigger the task and the task to be triggered.
I'm on the latest beta so I guess maybe it's differing in the "stable" version (I don't remember). The user guide for profiles says "Long-click on the profile name to get profile options".
I've been running this profile for a week. It's been sending an SMS daily, 1 minute earlier each day. I'm posting it here going it will help you. For example, if you don't have "do maths" checked in the set variable action, the variable might get goofed.
Profile: Recurring SMS (37)
Time: From %CHECKBAL Till %CHECKBAL
Enter: SMStest (53)
A1: Send SMS
[*
Number:1234567890
Message:Testing repeating sms*
Store In Messaging Appff*
Continue Task After Errorn
]*
A2: Variable Set
[*
Name:%CHECKBAL To:%CHECKBAL-.01*
Recurse Variablesff*
Do Mathsn*
Appendff
]*
If it still isn't working, you need to check the tasker log.
Hi
I have installed on my phone the app audio profiles with a tasker plugin
I've created a tasker profile that turn my phone on vibration mode when I'm in a particular location, but now how can I disable vibration when I leave this particular location? Which kind of profile I must create?
If you profile is GPS or cell location then surely you just need to create an exit task. So once the profile isn't true it'll run the exit task, which you can determine what is in there.
Thanks.
So, if I understand, I have to simply long press on my profile (vibration mode) and choose "Add exit activity".
Then after choosen the exit activity my phone will run this activity when I will be not anymore in the profile's location?
copeppe said:
Thanks.
So, if I understand, I have to simply long press on my profile (vibration mode) and choose "Add exit activity".
Then after choosen the exit activity my phone will run this activity when I will be not anymore in the profile's location?
Click to expand...
Click to collapse
Hold on the current entry task and this will give you an option to add in the exit task, so either create new or choose an existing one. Hope you get it sorted out [emoji106]
mgdorbit said:
Hold on the current entry task and this will give you an option to add in the exit task, so either create new or choose an existing one. Hope you get it sorted out [emoji106]
Click to expand...
Click to collapse
hello, i am trying to make a tasker profile that opens a specific application (apk) when the speed drops below 4 kmh only with the GPS because i do not have any sensors. Unfortunately I am still not able to set the variables in the Speed well and if I need a secure setting plugin for the GPS. Can you lead me towards success or advise me how to get started? Thank you
bettuccio said:
hello, i am trying to make a tasker profile that opens a specific application (apk) when the speed drops below 4 kmh only with the GPS because i do not have any sensors. Unfortunately I am still not able to set the variables in the Speed well and if I need a secure setting plugin for the GPS. Can you lead me towards success or advise me how to get started? Thank you
Click to expand...
Click to collapse
I'm afraid I've not looked at any of the GPS settings or functionality. Try a search on the internet, you might find something.
Sent from my SM-G950F using Tapatalk
mgdorbit said:
I'm afraid I've not looked at any of the GPS settings or functionality. Try a search on the internet, you might find something.
Sent from my SM-G950F using Tapatalk
Click to expand...
Click to collapse
something I found but it does not work in practice.