how to run a task after every one min

[Saad Thahim]

I want my phone to beep after an interval
how can I do this with tasker?

[lear peleg]

When I needed to run a task every minute I did a task every 2 minutes and a wait command that waits 1 minutes and a goto command that starts tge task from the beginning..
(if the 2 minute limitation wasn't your problem then it'll be nice if you could be more specific)

[Saad Thahim]

This way the task will always be running actually is there a way to execute or evoke it through a profile.

[Rich D]

> This way the task will always be running actually is there a way to execute or evoke it through a profile.

The way i understand the "every x min" context is if it set for every 3 min then it will fire in minutes multiples of 3 IE 1.03, 1.06 1.09 etc.     So... without the ability for a every 1 min context I believe ...

Without doing all the math I think the only way would be with 21 profiles linked to the same task.  With time contexts from every 2 min to every 9 min and then all the prime numbers up to 59. I am no mathematician but it would be something like that.. so I am not sure what would be more CPU friendly. 

[Rich D]

so I am not sure what would be more CPU friendly. 

Of course you will also have many task collisions for tasker to deal with as well so i would imagine the 1 minute wait approach would be the best

Just guessing.....

[Brandon Horwath]

Context event: Variable set: %TIME

Enter -> Beep!

[Rich D]

> Context event: Variable set: %TIME
>
> Enter -> Beep!

Does that work on your device??

AFAIK... you can not use %TIME in a context...

[Brandon Horwath]

Profile: Every Minute Test (320)
Time: Every 2m
Enter: Repeat Test (319)
A1: Music Play [ File:Ringtones/hangouts_message.ogg Start:0 Loop:Off Stream:2 ]
A2: For [ Variable:%wait Items:1:60 ]
A3: Wait [ MS:0 Seconds:1 Minutes:0 Hours:0 Days:0 ]
A4: End For
A5: Goto [ Type:Action Number Number:1 Label: ]

... oops.

[Brandon Horwath]

Oddly enough, this should work. But testing has proved inconsistent.

Profile: Time Test (133)
State: Variable Value [ Name:%Time Op:Doesn't Match Value:%TIME ]
Enter: Time Test (95)
A1: Variable Set [ Name:%Time To:%TIME Do Maths:Off Append:Off ]
A2: Write File [ File:Recorded/test.txt Text:%Time Append:On Add Newline:On ]

[Matt R]

You can do it with two profiles each with repeating 2 minute contexts. Just have one with no range specified (uncheck from and to) and the other range from 00:01 to midnight.

Matt

[Matt R]

The built-in %TIME variable isn't "dynamic" per the user guide, so it shouldn't be used in variable value contexts. In a task, it will be evaluated when the task runs, but when used as a context it won't necessarily be updated every minute, giving inconsistent results.

Matt

[Brandon Horwath]

The built-in %TIME variable isn't "dynamic" per the user guide, so it shouldn't be used in variable value contexts.

Thanks :-)

[Brandon Horwath]

From the user guide:

Set a repeat period of 2 minutes (the minumum allowed) and specify a task like this:

Perform Task, TaDa
Wait 1 Minute
Perform Task, TaDa

[Saad Thahim]

Hi brandon can u please explai that profile? How can I make it on tasker.

[Brandon Horwath]

Repeat Test (319)

Create a new task, in this example called repeat test.

A1: Music Play [ File:Ringtones/hangouts_message.ogg Start:0 Loop:Off Stream:2 ]

First action, media, music play (file path to desired media)

A2: For [ Variable:%wait Items:1:60 ]

I have been trying to use a for loop successfully for sometime now to be honest, and have yet to really play with them or understand them (feel free to jump in here Matt!) but I think this its basically setting a variable to values 1 through 60. I don't know exactly for sure myself, but I am just playing around with what others have suggested previously.

A3: Wait [ MS:0 Seconds:1 Minutes:0 Hours:0 Days:0 ]

I believe this action waits one second for each %wait variable. Again, just playing around and while testing it seemed to work.

A4: End For

Action, task, end for.

A5: Goto [ Type:Action Number Number:1 Label: ]

Action, task, Goto.

Profile: Every Minute Test (320)
Time: Every 2m

Create a new profile, context time. Deselect to, and from boxes, select repeat only, time 2 minutes. Profile name in this example, every minute test.

Enter: Repeat Test (319)

The task created before creating the profile is selected as the entry task.

[Rich D]

> You can do it with two profiles each with repeating 2 minute contexts. Just have one with no range specified (uncheck from and to) and the other range from 00:01 to midnight.

Nice Matt... I have not seen that approach before... I will give. It a try.. :)

Thanks,   Rich..

[Rich D]

> > You can do it with two profiles each with repeating 2 minute contexts. Just have one with no range specified (uncheck from and to) and the other range from 00:01 to midnight.
>
> Nice Matt... I have not seen that approach before... I will give. It a try.. :)

As I was expecting, It works perfectly ... I believe this is exactly what the OP was looking for, slightly less complicated than my suggestion :)

[Bob Hansen]

I was playing around with this same idea. I did some testing using two profiles each set to 2 minute repeats to see what the affect on battery drain would be. I found that there was no noticeable increase in battery usage. Also, I found that using the two profiles together was very reliable and that the timing was very accurate - the events occurred exactly 1 minute apart. I also tested using a 2 minute context plus a 1 minute wait, and found that the wait action (with default priority setting) was not very accurate ranging from 60 second to 66 seconds.

If you want to have a 1 minute event that occurs durring a certain time period, for example 8:00am to 9:45am, you can set the first time time context to start at 8:00 and end at 9:45. Then set the second profile's time context to start at 8:01 and end at 9:45. This will result in the associated task being triggered every minute between 8:00 and 9:45.  

[Brandon Horwath]

I did some testing using two profiles each set to 2 minute repeats to see what the affect on battery drain would be. I found that there was no noticeable increase in battery usage. Also, I found that using the two profiles together was very reliable and that the timing was very accurate - the events occurred exactly 1 minute apart.

I have found the timing more reliable than what I suggested, also decreased battery usage. It appears that repeating the same task and waiting is a bigger drain than just initiating the task without the wait.

... makes sense.

[Saad Thahim]

Brandon how to make profile for every minute I couldnt find any way.

[Brandon Horwath]

From the user guide:
Set a repeat period of 2 minutes (the minimum allowed for time based contexts) and specify a task like this:

Perform Task, TaDa
Wait 1 Minute
Perform Task, TaDa

So, Saad...

You must create a task that performs your desired action, what are you looking to do?

[Saad Thahim]

You mean to say I should create 2 tasks but where is the profile to run it?

[Brandon Horwath]

You mean to say I should create 2 tasks but where is the profile to run it?

Really?!? That's what you're going with?
Tell me what I mean to say again... because clearly you know.

... please.

If that was what I meant to have said, that is what I would have said.

However, I asked what are you looking to do so I can provide more information.

Create a new profile, context time, deselect to and from, select repeat, minimum two minutes.

1) NOW WRITE YOUR TASK ACTIONS YOU WANT IT TO DO.

2) NOW HAVE TASKER WAIT ONE MINUTE IN THE SAME TASK.

3) REPEAT STEP ONE IN THE SAME TASK!

WHAT ARE YOU LOOKING TO DO?!?