Tasker...help "wait until"

[nettech_gt]

I have a profile that will disconnect my BT headset when I get home. (Wifi near) However if I'm on a call, I want to have the task wait until I'm no longer on a call or GrooveIP call. But I need some help with the wait until part. The task triggers regardless if I'm on a call or not. THANX!

[BossMan]

See this:

http://tasker.dinglisch.net/userguide/en/matching.html

Correct your condition for Wait action - I think it should be %PACTIVE matches *ProfileA*/*ProfileB*

Also, get rid of the if/else completely and use Wait Unitl only - after all, you want to execute all your actions once the call is over, right?

A.

[nettech_gt]

THANX! But now it doesn't work at all whether I'm on on a call or not...

[Brad Minion]

Don't know if this is the problem but don't you need asterisks around the profile names in the Wait "IF" statement?  "%PACTIVE ~ *Incoming Call*/*Groove Incoming Call*". I don't think the IF will ever be true without them.

--
You received this message because you are subscribed to the Google Groups "Tasker" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tasker+un...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[nettech_gt]

I added the * but I get the same results.

[Matt R]

Export the descriptions of the relevant task(s)/profile(s) by long-pressing the task or profile name and selecting export -> description to clipboard and paste it in a reply here.

Matt

[nettech_gt]

Profile: Disconnect BT Headset (22)
Event: K9 Email Received [ From:* Subject:test Receiving Account:* ]
Enter: Anon (23)
A1: Wait Until [ MS:0 Seconds:10 Minutes:0 Hours:0 Days:0 ] If [ %PACTIVE ~ *Incoming Call*/*Groove Incoming Call* ]
A2: Secure Settings [ Configuration:Keyguard Disabled/BG Package:com.intangibleobject.securesettings.plugin Name:Secure Settings ]
A3: Secure Settings [ Configuration:Screen & Keyboard Lights On
20 Seconds Package:com.intangibleobject.securesettings.plugin Name:Secure Settings ]
A4: Bluetooth Settings
A5: Dpad [ Button:Down Repeat Times:6 ]
A6: Dpad [ Button:Press Repeat Times:2 ]
A7: Go Home [ Page:0 ]
A8: Wait [ MS:0 Seconds:5 Minutes:0 Hours:0 Days:0 ]
A9: Secure Settings [ Configuration:Keyguard Enabled Package:com.intangibleobject.securesettings.plugin Name:Secure Settings ]

[bdanders]

Seems like you would want to wait until %PACTIVE does NOT match those profiles. The way you have it it is going to wait until you are on a call to run the rest of the task, instead of waiting for you to hang up.

[nettech_gt]

That makes sense! However I still get the same results...

[Matt R]

Look at the run log (menu button -> more -> run log) to see what's happening and to check if the incoming call profiles are activating and deactivating as you expect too.

Matt

[bdanders]

You do actually have profiles named "Incoming Call" and "Groove Incoming Call" that go active when they should, right? Have you tried flashing %PACTIVE  to verify that they are in fact in there? Check carefully for typos. You really shouldn't need to have both of them in there if they are named that since they both contain "Incoming Call".  Just wait until %PACTIVE !~ *Incoming Call*.

[nettech_gt]

Yes, my incoming call profile is activating and deactivating as expected.

[nettech_gt]

Removing the "Groove Incoming call" did it! THANX!

THANX to everyone who posted I really appreciate it.

PS: I posted this question on XDA Developers and no one responded.

[bdanders]

You could also try %PACTIVE ~ !*Incoming Call*/*Groove Incoming Call*
Possible that by doing "doesn't match" with the OR separator it was processing it such that PACTIVE must only not match one or the other and not both. Basically you would have to be on a call and on a groove call at the same time for that to be false. By changing it to "matches" !somestuff/someotherstuff you are forcing it to match niether somestuff nor someotherstuff.  And now I think I've confused myself.

[Michael Yeager]

I did this by monitoring the state of the phone (ringing, offhook or idle) and using the context of phone = idle to actually trigger the task. As long as I was home and not on a call, Bluetooth got disconnected.