Hello,
I would like to exit my coyote application when I leave the Bluetooth.
I've already tried some tricks but I don't manage to get something that works every time.
Have you an idea how I can manage to exit coyote without root required?
Thanks,
Kevin
Use AutoInput then you could use the exit app task.
What if the app requires a Back followed by click on an OK prompt to exit? Can you help with the AutoInput task for that scenario?
JWadle said:
What if the app requires a Back followed by click on an OK prompt to exit? Can you help with the AutoInput task for that scenario?
Click to expand...
Click to collapse
The AutoApps forum I linked to earlier (exit task link) is a great place to get educated about those apps. Basically you need to do a:
plugin -> Auto input -> Global Action -> Back
followed by a:
plugin -> Auto input -> Action
Which needs to be configured with:
Action -> Click
Field type -> text
Field text -> OK
** that configuration is based on your example. YMMV
A1: AutoInput Global Action [ Configuration:Action: Back Timeout (Seconds):20 ]
A2: AutoInput Action [ Configuration:Type: Text
Value: ok
Action : Click Timeout (Seconds):20 ]
ktmom said:
The AutoApps forum I linked to earlier (exit task link) is a great place to get educated about those apps. Basically you need to do a:
plugin -> Auto input -> Global Action -> Back
followed by a:
plugin -> Auto input -> Action
Which needs to be configured with:
Action -> Click
Field type -> text
Field text -> OK
** that configuration is based on your example. YMMV
A1: AutoInput Global Action [ Configuration:Action: Back Timeout (Seconds):20 ]
A2: AutoInput Action [ Configuration:Type: Text
Value: ok
Action : Click Timeout (Seconds):20 ]
Click to expand...
Click to collapse
I've searched in this way but my phone is locked with a pin code so I need another solution. Or maybe an improved one.
I've tried with AutoNotifications to use the exit button that sit in the "open coyote" notification. But it's not really stable and I need to quit coyote manually about 1 time on 2.
Thanks for your help.
Kevin
Hi, I want to do something with tasker and I can't how to do
I want to disable call vibration + disable pin lock security when I go out from my wifi range
And enable it when I am in range
Please help
Please help
This approach requires your device to be rooted to work around the Android limitations for secure lock screens.
Start with a profile that is triggered by the presence of your wifi network.
Create a new profile:
State -> Net -> WiFi Connected
Configure to your specific WiFi network. If you do this while actually connected to the network it will be easier.
Now create an enter task to enable vibration and secure lock screen (sets the secure lock screen to engage 1 minute after screen off = 3600 seconds).
Audio -> Vibrate Mode [
Mode:Vibrate
]
Code -> Run Shell [
Command:Settings put secure lock_screen_lock_after_timeout 3600
Timeout (Seconds):0
Use Root: on
Store Output In:
Store Errors In:%LockScreenError
Store Result In:
Continue Task After Error: on
]
Create an exit task to disable vibration and secure lock screen (sets the secure lock screen to engage 1 day after screen off = 86400 seconds).
Audio -> Vibrate Mode [
Mode: off
]
Code -> Run Shell [
Command:settings put secure lock_screen_lock_after_timeout 86400
Timeout (Seconds):30
Use Root: on
Store Output In:
Store Errors In:%UnLockScreenError
Store Result In:
Continue Task After Error: on
]
To better understand using root shells to modify secure settings see Replace Secure Settings with Shell Commands
Hi guys, I'm trying to reply something I had done with another task app (llama), but idk why, isn't working properly. Basically, I wanna airplane mode set on or off under not 1 but 2 conditions:
if time is between x and y (first condition)
and
if screen is on (second condition)
then
do nothing
but if screen is off, turn on airplane mode
this imply that when, between x and y, I will turn on the phone (for example during night, to check something), it will turn automatically plane mode off, and again on when screen turns off.
Any ideas to get this working? Thank you!
I think the most reliable way to do this is with three simple profiles.
The first is for the time context. The enter task would set a variable (e.g. %SleepTime) to "true".
The second profile has 2 contexts. The first is to check the previous variable (%SleepTime) is set to "true". The second context is screen off. The task would set a different variable (e.g. %ScreenOff) to true.
The third context checks for (%ScreenOff) is true. The enter task turns on airplane mode. The exit task turns off airplane mode.
The exit task for the first 2 profiles clears the variables.
This could be all handled in one profile using loops and tests for state. IMHO, using 3 profiles is more responsive.
hello,
i use a variable %Night, which is set to "yes" with a profile with the time condition and screen off condition ("if %SCREEN is off") without exit task.
%Night is set to "no" with other profile and all conditions you like. In your case i think it's only the time condition.
The airplane mode profile has as a condition "if %Night is true". Enter task: airplane on. Exit task: airplane off.
ktmom said:
I think the most reliable way to do this is with three simple profiles.
The first is for the time context. The enter task would set a variable (e.g. %SleepTime) to "true".
The second profile has 2 contexts. The first is to check the previous variable (%SleepTime) is set to "true". The second context is screen off. The task would set a different variable (e.g. %ScreenOff) to true.
The third context checks for (%ScreenOff) is true. The enter task turns on airplane mode. The exit task turns off airplane mode.
The exit task for the first 2 profiles clears the variables.
This could be all handled in one profile using loops and tests for state. IMHO, using 3 profiles is more responsive.
Click to expand...
Click to collapse
Hi guys, first thank you in Advance. Im trying this method, every condition seems ok but screen check, which remain black even if I test it on, and so airplane isnt set. I wonder why? Screenshot attached (notice Ive tried screen on just to check and it was still black as I guess means not working properly...)
Ty
There are things to remember.
The non-active state (black as you are saying) for screen off is always going to be the case when the screen is on.
When setting up and testing tasks that include variables, it is very easy to get into a non-defined state with the variables not setting/unsetting correctly. This subtle issue can cause all sorts of headaches because the variable isn't cleared (or set).
Here is the description of a working set of profiles. This variant sets a notification on screen off and screen on to affirm the task ran. The screen off task also vibrates as a tactile assurance the screen off task ran.
Code:
Profile: Airplane Mode Time (86)
Time: From 2:30PM Till 4:30PM
Enter: Airplane Mode Time Variable (87)
A1: Variable Set [
Name:%AirplaneModeSleepTime
To: true
Recurse Variables: Off
Do Maths: Off
Append: Off ]
Exit: Airplane Mode Time Exit (126)
A1: Variable Clear [
Name:%AirplaneModeSleepTime
Pattern Matching:eek:ff
Local Variables Only: Off ]
Profile: Airplane Mode Screen Off (88)
Priority: 1
State: Variable Value [ %AirplaneModeSleepTime ~ true ]
State: Display State [ Is: Off ]
Enter: Airplane Mode Screen Off (94)
A1: Variable Set [
Name: %AirplaneModeScreenOff
To: true
Recurse Variables: Off
Do Maths: Off
Append: Off ]
Exit: Airplane Mode Display On (11)
A1: Variable Clear [
Name:%AirplaneModeScreenOff
Pattern Matching:eek:ff
Local Variables Only: Off ]
Profile: Airplane Mode Set (118)
Priority: 1
State: Variable Value [ %AirplaneModeScreenOff ~ true ]
Enter: Airplane Mode Action (120)
A1: Notify [
Title:Airplane Mode On
Text:
Icon:
Number: 0
Permanent: Off
Priority: 3 ]
A2: Airplane Mode [ Set: On ]
A3: Vibrate Pattern [
Pattern: 0,500,100,500,100,500,100,500,100,500,100,500,100,500 ]
Exit: Airplane Mode Exit (125)
A1: Notify [
Title:Airplane Mode Off
Text:
Icon:
Number: 0
Permanent: Off
Priority: 3 ]
A2: Airplane Mode [
Set: Off ]
A3: Variable Clear [
Name:%AirplaneModeScreenOff
Pattern Matching: Off
Local Variables Only: Off ]
Hmm thx but Im confused a little, is possible to past this text somewhere?
No. But it sounds like you are really new to tasker. Maybe you should work through some tutorials to get some practice.
I used tasker long time ago, but what Im trying to do is quite simple, yet it doesnt work....for example Ive tried this simpler way:
Profile 1) Display on -> var set %Screenon to true
Profile 2) Display off -> var set %Screenon to false
Profile 3) from x to y -> 2 conditions) airplane mode set on if %Screenon is false; 2nd condition: airplane mode set off if %Screen on is true
I wanted to try like this to see but it works only when I press the play button under the actions. Otherwise if i turn on or off the screen nothing change...
takui said:
I used tasker long time ago, but what Im trying to do is quite simple, yet it doesnt work....for example Ive tried this simpler way:
Profile 1) Display on -> var set %Screenon to true
Profile 2) Display off -> var set %Screenon to false
Profile 3) from x to y -> 2 conditions) airplane mode set on if %Screenon is false; 2nd condition: airplane mode set off if %Screen on is true
I wanted to try like this to see but it works only when I press the play button under the actions. Otherwise if i turn on or off the screen nothing change...
Click to expand...
Click to collapse
I would suggest trying to turn screen on and off, check the Tasker log to see if the variable is set properly.
- If it does, trying manually set it to false, and then true in your time range x-y to see if 2nd profile reacts to that.
- If it does not, check 1st profile again, maybe you are using screen on and unlocked? or whatever... anyways, that should narrow down the possibilities at least
Ty, Reading the log Ive noticed that the variable is set correctly (see attach) but the 3rd profile doesnt set airplane...hmm
takui said:
Ty, Reading the log Ive noticed that the variable is set correctly (see attach) but the 3rd profile doesnt set airplane...hmm
Click to expand...
Click to collapse
so what does the log say when you manually run 3rd profile? just so we know the profile does not correctly start or not correctly run...
If I run it manually it works in both ways (on and off) otherwise no. Logs attacched. Its just that it doesnt check alone the variable and doesnt start alone
ok to clear things up:
- your display profiles can be combined into 1 with exit task
- have you tried to manually set %ScreenOn to each value to see if the profiles reacts to that - I doubt it would
- try using equal instead of match for the variable
- maybe post your profiles and tasks
Hello. I had them combined before, ive tried splitting but mothing changed... Log show that the variable is set correctly, what doesnt change is the airplane mode, as it doesnt care the variables at all (time frame condition btw works, as it is showed green...)
takui said:
Hello. I had them combined before, ive tried splitting but mothing changed... Log show that the variable is set correctly, what doesnt change is the airplane mode, as it doesnt care the variables at all (time frame condition btw works, as it is showed green...)
Click to expand...
Click to collapse
ok I think I know what the problem is: your timed profile is triggered by state and not event, which means during the time frame, profile is triggered and finishes, it will test your variable during this time only, and will not recheck if this variable changes, when task is finished.
I hope I made it somehow clear....
anyways, try this, put the variable in the condition part as well.
Hm ok maybe Ive understood what you mean but so, what kind of profile Ive to make? Everyone is triggered from something, state, event, app, UI...isnt "free", so Ive choosed time...
add condition variable set
Hmm Im closer to a solution, still I cant get the timeframe works. In this new adapation, airplane is set correctly on and off when I turn on and off the screem but, it doesnt consider the timeframe so, if I turn off the screen in the morning, it sets airplane mode on anyway. In attach the new setup...
Edit: if Im not wrong, the red bar on the right means that the conditions are not reached, right? So why even if the bar is red in the airplane on mode, it turns on when the display turns off? ....
here you go, try this on your device at night time. if you have a heart attack, I'm not responsible...
ktmom said:
I think the most reliable way to do this is with three simple profiles.
The first is for the time context. The enter task would set a variable (e.g. %SleepTime) to "true".
The second profile has 2 contexts. The first is to check the previous variable (%SleepTime) is set to "true". The second context is screen off. The task would set a different variable (e.g. %ScreenOff) to true.
The third context checks for (%ScreenOff) is true. The enter task turns on airplane mode. The exit task turns off airplane mode.
The exit task for the first 2 profiles clears the variables.
This could be all handled in one profile using loops and tests for state. IMHO, using 3 profiles is more responsive.
Click to expand...
Click to collapse
alienyd said:
here you go, try this on your device at night time. if you have a heart attack, I'm not responsible...
Click to expand...
Click to collapse
? This just speech... I dont need it Im confused
Hi,
lets say i want that every time my smartphone connects with the wlan at home bluetooth should be enabled and disabled when i leave the wlan. this is easy to do with tasker.
but when i enable bt manually when i'm not at home, then tasker has nothing to do when i connect to the wlan. but whe i leave it bluetooth will be disabled.
is there any way to prevent bluetooth disable when i've enabled it manually? maybe there is a solution using variables? set a variable from 0 to 1 when bluetooth is enabled manually and not when it enabled automatically via tasker?
Restore settings being enabled in your profile will automatically restore the configuration based on the entry task. Deselect restore settings (long press profile, with it selected tap the cog/gear icon) and expressly restore the settings in your exit task.
In the entry task add a variable set %BTon to "true". Include an "if statement" in the variable set action "if %BLUE does not match on".
Then in the exit task, when you expressly turn off Bluetooth, add an "if statement" to the BT off action so it only runs if the variable "%BTon matches true".
Make sure to add a variable clear for the %BTon variable at the end of your exit task.
Tips
Thanks
I'm on a Galaxy S10 Plus and have over 15 increments in all my sound controls. Tasker only has 15 increments. I've got Tasker set to lower my notification volume at work but Tasker's "1" step isn't low enough. My phone sound has the ability to go many steps lower than Tasker's "1".
How can I address this in Tasker to get the volume lower than 1 or to increase the sound increments in Tasker? Thank you!
A couple of thoughts...
If you use a variable entry set to 0, does it go lower? If you're not yet aware, tap the double arrow button to get to an input field.
Or, see if a custom settings action will give you fine grained control.
I'm not sure how to use a variable entry to adjust the sound. Can you please elaborate?
Thank you!
ktmom said:
A couple of thoughts...
If you use a variable entry set to 0, does it go lower? If you're not yet aware, tap the double arrow button to get to an input field.
Or, see if a custom settings action will give you fine grained control.
Click to expand...
Click to collapse
https://www.pocketables.com/2012/08/beginners-guide-to-tasker-part-2-variables.html
I'm sorry but I don't see how to use a variable to set sound increments. Can you help? Thank you!
ktmom said:
https://www.pocketables.com/2012/08/beginners-guide-to-tasker-part-2-variables.html
Click to expand...
Click to collapse
I don't know what more to tell you. Create a variable, set it to a value (see the link that was posted) and use that variable in the action you are using to control the notification volume (tapping the crossed arrows to get the input field as mentioned in my first reply)
Hi - I tried using a variable with settings of 0.5 and it just takes the volume down to zero. I also tried setting the media volume to the lowest setting and recording what value that was in a variable and it just came up as "1" despite a value of 1 not getting me the lowest volume level. Has anyone figured out how to do this?
I have not figured out how to do this through Tasker.
It's clanky, but what I've done for the moment is to use Tasker to set Media Volume to zero, then in a simple loop I mimic pressing the "Volume Up" hardware button as many times as requested.
Task: Adjust Volume
A1: Media Volume [
Level: 0 ]
A2: Variable Set [
Name: %max
To: 17
Max Rounding Digits: 3
Structure Output (JSON, etc): On ]
A3: Variable Set [
Name: %num
To: 1
Max Rounding Digits: 3
Structure Output (JSON, etc): On ]
<loop>
A4: If [ %num < %max | %num = %max ]
A5: Button [
Button: Volume Up ]
A6: Variable Set [
Name: %num
To: %num + 1
Do Maths: On
Max Rounding Digits: 3
Structure Output (JSON, etc): On ]
A7: Goto [
Type: Action Label
Label: loop ]
A8: End If
A9: Flash [
Text: %VOLM
Continue Task Immediately: On
Dismiss On Click: On ]
I have the final Flash in there just to check out what Tasker is calling my required volume; I'll clearly be taking it out when I put the task into implementation, if I decide it works at least well enough for me.
For the record, I have a Samsung Galaxy S10e, on which I have used Sound Assistant to increase my volume rocker steps to 30.