What is Reddit's opinion of AutoInput?

> I use Tasker to turn Wi-Fi off automatically when I connect to my car's Bluetooth

Yep. I feel your pain. I had the same issue when they removed the ability to programmatically turn mobile data on and off.

Fortunately there are some options that may help some people:

(1) Use the AutoInput Tasker plugin to do the actual screen tapping for you to turn off Wi-Fi. It's not an elegant solution, but it works.

https://play.google.com/store/apps/details?id=com.joaomgcd.autoinput

(2) If you use LineageOS, you can use Profile triggers (see Android Settings) to turn Wi-Fi on and off. You can also install the Profile Shortcuts for LineageOS app and let Tasker trigger the profile changes.

This can work with other settings that LineageOS profiles let you change. So you can turn mobile data on and off automatically, GPS, etc.

https://play.google.com/store/apps/details?id=net.battlemoose.cmprofileshortcuts.googleplay

There are obvious pros and cons to these solutions, but my take is that if I can avoid do those annoying, frequent manual tasks, the small downsides are fine with me.

Tasker's developer has also received this, apparently. This means app detection will be slower and based on polling rather than simply reacting to an event.

I wonder what will happen to the AutoInput plug-in since it relies completely on the accessibility service.

If you use Tasker, you can probably set up a task in conjunction with AutoInput that would simulate whatever inputs you need to perform this task, then add a shortcut to this task on your watch using AutoWear or whatever.

> HATE configuring it

There's a macro recorder Tasker plugin that can sometimes help some people.

AutoInput Tasker plugin

>You can use AutoInput to click on-screen buttons, or to write some text in text fields of any app.

>You can even retrieve text from other apps.

>You first record your input by actually touching and swiping your screen and then replay that input with AutoInput, which will faithfully reproduce everything you did.

>It allows you to create a series of input actions, including physical button presses and various taps and swipes, to emulate some sort of macro sequence that can be executed inside any app of your choosing.

>Androidpolice

With my usage patterns I'll probably not be able to give up root for some time; still, it's nice to see these rootless alternatives to power user stuff cropping up. AutoInput is another great example.

AutoInput plugin can do that. I'm using it on my GS9 and it seems to work pretty good. There is a free version, but you have to watch ads to get it to function.

Yes, with the plugin AutoInput you can use the Key Supress action to first remap/disable the volume button(s). Then use an AutoInput Key Press Profile to detect the key press, and link it to a Task that does the Track skip.

Agree with using AutoInput to automate the click sequence. You may want to have it happen at a time when you can observe it, or have the phone alert you when it's doing it, to make sure all is well.

Since if your banking app updates and the screens become different - you may end up with some un-intended results, like transferring all your money to /u/Spoghead haha.

It just may need the screen to be woken, so try starting your Task with an Alert > Popup Action, with a 1 second timeout so it then immediately moves on with the rest of the Task.

Or try a first action using the plugin AutoInput's "Wake/Unlock Screen" action.

Yes it can, using the plugin AutoInput with it's "Key Event" Profile.

There's a long list of keys it can detect that you'll find in there, and if you goto the log in the main AutoInput app (From the App Drawer) and press keys on your keyboard, it will show in the log what AutoInput sees them as.

You would use the Plugin AutoInput with it's Key Suppress Action, to disable the volume up/down buttons when YouTube is open, and re-enable them when YouTube is not open.

At the same time you'll have an AutoInput Profile for "Key Event" that intercepts the volume up/down key presses and link the Profile to a Task that simply sets media volume up and down. You would also add the YouTube app context to this Profile.

Will look pretty much like this:

PROFILE 1: App > YouTube

ENTER TASK: A1. Plugin > AutoInput > Modes > Key Suppress: Enable Keys: Volume Up + Volume Down

EXIT TASK: A1. Plugin > AutoInput > Modes > Key Suppress: Disable Keys: Volume Up + Volume Down

That takes care of disabling the default function of the keys when YouTube is open. Then this will remap them:

PROFILE 2: Event > AutoInput > Key Keys: Select - Volume Up + Volume Down Key Action: Key Down + App > YouTube

LINK TO TASK: A1. If %aikeycodename ~ Volume Up

A2. Set Media Volume > Level: %VOLM+1

A3. Else If %aikeycodename ~ Volume Down

A4. Set Media Volume > Level: %VOLM-1

A5. End If

And that should do it. Note that in the second Profile the actions to set the media volumes will indeed accept the +1 or -1 directly, without using any additional Variable Set actions.

The combination of AutoInput and Tasker allows you to do this.

Be aware that Tasker has a bit of a learning curve. Both apps offer a free trial, so you might want to try that first to see if everything is to your liking.

You can use AutoInput to open the Wear OS app on your phone and disable/enable tilt to wake from there. (Idea taken from here)

In Nova, long press on your app's icon, and select the "Pencil" to "Edit Shortcut".
Then choose "Swipe Action". That'll open the "Choose action" page.
If you go to the "Shortcuts" tab, you'll see an option for "Direct message" that'll let you pick a contact.
Also on the "Choose action" page, you'll find a "Task Shortcut" action (if you have Tasker installed). From there, you can choose to execute any task you've previously created in Tasker.
If you have AutoInput installed, you can automate the navigation of an app to get to where you want it to open to.

Basically you'll use the Event > UI > New Window Profile and set the "Window Type" to "Dialog", then in the "Label" field you'll likely have to enter the full text of the dialog popup as it appears on your device.

Then for the Task to click the "OK" you'll need the plugin AutoInput. Whole thing looks like this:

PROFILE: Event > UI > New Window Label: (full text of the popup as it appears on your device) Window Type: Dialog

TASK: A1. Wait: 500ms

A2. AutoInput > Click > Text: OK

The Wait action may or may not be needed depending on how fast your device is.

Check out the AutoInput plugin, it lets you control interface actions based on button text or recording touch input. As long as you can reliably get it to the correct starting screen in the app for the touches to work every step of the way, it should be good. I'm trying to do something similar with a cycling recording program, but I have difficulty with various splash screens popping up from time to time and throwing off the process. I'm looking into possible workarounds for this problem.

Get the %WIN label name.

Event>Variables> Set Variable> Type %WIN for variable & leave value filed empty.

Now create task Alart>Flash>Type %WIN for text field

Once that mobile data box appeared, note down window label. After that, you can delete above task & profile you created.

IF Window label appeared, click X, Y coordinates (root need & that is /u/ladfrombrad mentioned in the pic to get X.Y coordinates) or press the button using autoinput or touchtask ( no need root). Link https://play.google.com/store/apps/details?id=com.joaomgcd.autoinput / https://play.google.com/store/apps/details?id=com.balda.touchtask

Now create new profile Event>Variables> Set Variable> Type %WIN for variable field & Window Label that you noted in value filed.

Create a task to click the button location of mobile data popup. There are good guides on youtube to use autoinput / touchtask. Watch those. Tasker will automatically click the popup button using autoinput / touchtask

The plugin AutoInput can click on an Element on the screen based on its Text or on its Element ID, regardless of where on the screen's x/y it shows up.

Possibly. More than likely. The plugin AutoInput has its "UI Query" function that can read most data on any screen in an app. The display doesn't always have to be on for this to happen.

To display the text in a widget, a lot of people use Zooper Widget Pro to display information from Tasker if they want it anchored to a homescreen.

Yes AutoInput is what you'd use. Make a Profile for Event > AutoInput > Key and in the Config leave the "Key" field blank so the Profile will trigger on any key.

Then in the Task just need one Action to Flash %aikeycode

A few things can cause this. Main one being memory management your device does. Second is battery management. Mobile devices are designed to work hard and then idle.
You can try to turn off optimization for the application in your battery settings and/or try a different memory management scheme.
A bandaid solution is to fake screen touches. There are a few applications out there but Tasker+AutoInput seems to be the best.
- AutoInput – Android Apps on Google Play - https://play.google.com/store/apps/details?id=com.joaomgcd.autoinput

Does the "App has stopped working" dialog show up? In that case you could use AutoInput and its UI Update event that triggers when a specific text is visible on the screen :-}

It depends on your handwriting. If it's a messy disaster, no OCR will be able to read it. Heck I might not be able to read it lol.

If you write clearly and legibly then the AutoTools beta plugin mentioned here as OCR now, so you could try that.

You'd likely first use AutoInput's Screen Capture action to screenshot what you just wrote (or have Tasker open S-Note to it and then screenshot it etc). Then use the AutoTools OCR to read the image.

You'll have to experiment with it, and your success will likely depend more on adjusting your handwriting style rather than adjusting Tasker or the plugins.

Yes, with the plugin AutoInput you can do this. Basically you'd have a Profile with an AutoInput Key Event for the Recents key.

In the Task (or Profile) it can detect both key down and up; meaning whether you pressed or released it. With these you can calculate how long you held it down. You could use either %TIMES or %TIMEMS to log/calculate the differences.

Then when you release the key you would have AutoInput use a Global > Back action (to return to the screen you want to screenshot if long-pressing Recents changes the screen).

Then you can actually use AutoInput's Screen Capture action to do the screenshot'ing as well.

To get Tasker to open the Settings Screen for that particular setting category.

Either for convenience to then change those settings by hand, or to have them changed automatically by Tasker using a plugin like AutoInput since even though Tasker has direct access to some settings in a category, there's probably ten times as many in the actual Settings Screen for that category.

A tip might be but post this in the Alpha community since it's an alpha app.

But I might be able to help you now anyways. I just tried it and it worked for me.

Run a "playlists" action and set the filter to Discover Weekly to get the %asplaylisturi().
Run a "play media" action and set the query to %asplaylisturi(1).

If you check the "play in spotify" you need to run an AutoInput to actually start the playlist by pressing the "SHUFFLE PLAY". It will start playing directly if you don't check it using the external AutoSpotify player.

It's possible by using AutoInput.

New Task A1. Plus sign => Plugin => AutoInput => Modes => Gestures (Enable) => Key Supress (Enable) => Keys (Back,Home)

You do however need to create an exit task that disables supresses as you otherwise would have to restart your phone if you want to use it again. It might also be a good idea to implement a backup failsafe incase the exit task get's canceld for whatever reason.

Very welcome! Glad you got it working ;)

Regarding running a direct "Activity" within an app, it may be available in Tasker's "Launch App" action. When the window opens for you to choose the app to launch, long-click on the app name/icon to see a list of available activities in the app that Tasker can go directly to.

Sometimes the names are cryptic and you have to just try them out. And often times only a small subset of things is available and the one you want isn't on the list. The workaround for that is to find (likely by searching on the net) a direct intent to do it (in which case you would be using the Send Intent action)...

...or - use the plugin AutoInput to have Tasker auto-click it's way to the screen you want in that app.

Not sure if you've visited over to /r/Tasker but it's an excellent resource for Tasker :)

You would use the plugin AutoInput. It has Event Profiles for Tasker that can trigger on just about any key presses, including those coming from Bluetooth devices.

(To set it up you can check the AutoInput logs in the main app as it logs any key presses it detects and lets you know it's exact keycode/id).

By the same token AutoInput has Action(s) to disable/enable keys. So you can disable the default functions of those keys and 're-map' them to Tasker Tasks, etc.

Sure!

My setup consists of Z-wave wall switches for lights and outlets, Raspberry Pi with RaZberry Z-wave controller on the network, Arduino with Ethernet Shield for garage automation including reading a magnetic open/close switch on the mail slot and relays to trigger the garage door button, a Logitech Harmony Hub, an Amazon Echo, Nest thermostat, and a Linux server to do some other web API based calls and some scheduled tasks (Christmas lights).

The first scenario is triggered automatically with Tasker on my phone based on sensing my wifi router's signal. It fetches the latest timestamp of the mail slot delivery logged on the Linux server from the Arduino. My alarm system has an API that I use. The lights are on Z-wave so that's a web request for a scene to the Pi controller. The garage door trigger is a web request to my Linux server which then triggers the Arduino to switch the relays connected to the existing garage door button contacts. And finally, the music is a Tasker scene that prompts for input to trigger the Harmony Hub for music on my stereo.

The second scenario for YouTube casting is thanks to the AutoInput plugin for Tasker. My Tasker task for this is roughly:

Launch App: YouTube
Wait 450ms
AutoInput Action: Click "Cast" icon
Wait 450ms
AutoInput Action: Click "Chromecast" to select it
Wait 450ms
AutoInput Action: Click "Subscriptions"
Wait 450ms
AutoInput Action: Click top video based on screen coordinates to play

To find the name of the app you're currently in, use the AutoInput plugin's UI Query feature. It returns the name of the current app as well it's package in the variables %aiapp and %aipackage.

Then you can just use the plugin AutoLaunch to launch an app based on it's name or package name (which you've stored based on the above).

Also a question - what method are using / planning to use to detect when you're 'closing an app' to trigger the querying/storage of it package name, etc.

For all you Tasker users: The plug-in AutoInput can be used to replicate actions that would normally require root, such as toggling Airplane mode or Location, emulating key presses, etc. It takes some getting used to, but like all AutoApps it's an awesome utility.

You could also try AutoInput to simulate screen touches. It's more involved, but might be worth a try if you can't get WoL to work.

There's a macro recorder Tasker plugin that can sometimes help some people.

AutoInput Tasker plugin

>You can use AutoInput to click on-screen buttons, or to write some text in text fields of any app.

>You can even retrieve text from other apps.

>You first record your input by actually touching and swiping your screen and then replay that input with AutoInput, which will faithfully reproduce everything you did.

>It allows you to create a series of input actions, including physical button presses and various taps and swipes, to emulate some sort of macro sequence that can be executed inside any app of your choosing.

>Androidpolice

The plugin AutoInput can do this on most devices.

Sometimes system overlay/popups aren't accessible to AutoInput but the Wifi one appear to be doable.

First you set the clipboard with your password using Tasker Set Clipboard. You'd use AI and/or Tasker to then navigate to the Wifi settings and the popup/overlay/screen where you enter the Wifi password.

Use AI > Focus to put focus on the password field, i.e. - com.android.settings:id/password

Then use AI > Paste and it will paste in the password. After that perhaps another AI command to click "CONNECT" or whatever following that you'd like to do with Wifi.

Yes, please do your research before posting - this has been asked MANY times in this sub, and there's even a topic posted at about the same time as yours (3hrs ago) also asking for advice.

This is how you can call a specific playlist up in Spotify (by URI) and you can use AutoInput to hit the play button based on app elements. All of this can be done without root.

Ofcourse you can. Install Auto Input and you can automate the touch sequences. Watch some youtube videos from the developer if you need some tutorials.

Hi Steve,

Absolutely, I have adjusted my reply above to reflect this, should more people find this thread in the future.

As for the workaround. Yes, I had to do this as well with my watch.

There are two workarounds possible and both work.

1:

One involves writing an AutoWear input script to automate the watch to go to: Display Settings, scroll down a bit, and enable (toggle on/off) the Always-on screen toggle.

2:

The second workaround (this is actually the one I use), is to instead use AutoInput on your phone. What I coded AutoInput and Tasker on my phone to do is it is a script that will: Open Wear OS app on my phone, uses AutoInput to scroll to the bottom of the screen, clicks Advanced settings, and toggles on/off the Always-on screen setting there. It works the same way as if you used option #1 above.

Both work, but I like option #2 as it has the benefits of running a bit faster and being able to run it even if watch is offline or not connected. For both solutions, you can poll the toggle on the screen using a UI query and set it as a variable so that you can use that variable in other profiles and act on them. For example, maybe you want to turn off AOD if the battery of your watch gets below 25%. In this "low watch battery" profile, you can use an If statement to see if the variable %WATCHALWAYSON = 1 and if so, run the action command to turn it off automatically.

Will this description suffice, or do you need more details on how to accomplish this?

AutoInput plug-in (I don't use it) should be able to do it. Eg.:

Profile > Event > Plugin > AutoInput > UI Update
Select your internet browser app.
Text > desired Url.

Task > "Display AutoRotate" action.

To be sure, wait for other users that are actually using AutoInput plug-in.

Good luck.

The AutoInput plugin has a key event condition which you can use to react to certain keypresses, you'll need to create two profiles to handle long presses for the back button.

Profile: Volume Down Press (388) Event: AutoInput Key [ Configuration:Keys: Back Key Action: Key Down ] Enter: Down_ (294) A1: Variable Set [ Name:%DELAY To:%TIMEMS Recurse Variables:Off Do Maths:Off Append:Off Max Rounding Digits:0

Profile: Volume Down Release (389) Event: AutoInput Key [ Configuration:Keys: Back Key Action: Key Up ] Enter: Up_ (386) A1: Variable Set [ Name:%DELAY To:%TIMEMS - %DELAY Recurse Variables:Off Do Maths:On Append:Off Max Rounding Digits:0

A2: Flash [ Text:%DELAY Long:Off

And as for the action to show the browser history use the tasker keyboard action ( You'll have to grant this action write secure settings permission to use it ) with input Control+H Add this action to the end of the Volume Down Release profile.

Damn, the notification doesn't even update?

You may be able to use the %WIN variable - it's usually the title of the current window - as a State context.

If you aren't rooted, look at AutoInput.

Yes this likely can be done. Using either the Keyboard in the new Tasker beta or the plugin AutoInput.

You'd need to have some text or element id's from the pin screen so that Tasker knows when the pin screen is no longer showing, meaning i has succeeded. Here is an example of how the Task would look:

A1. App > Launch App: <your photo app>

A2. For: %pin Items: 0:9999

A3. AutoTools > Text > Padding: %pin Padding Character: 0 Padding Number: 4

A4. AutoInput > Write Text: %pin Field Type: Focus

A5. AutoInput > UI Query

A6. If %aitext() !~ <some text on the pin screen>

A7. Variable Set: %PIN To: %pin

A8. Alert > Popup: "FINISHED! PIN IS %PIN"

A9. Stop

A10. End If

A11. End For

And the successful code would be stored in the Tasker variable %PIN.

By 'text,' I'm guessing you mean SMS which would mean the audio is likely in a MMS. Haven't used either for many moons but in the old days, the audio would only download once clicked. Therefore, in order to have something like the Music Play action to work, you'll need to get the clip onto your device first.

Your messaging app may already do that but if it doesn't, you can simulate a human click with AutoInput whilst the screen is on or see if you have any luck with the screen off using an app like this.

As for Google Home and/or smart speakers, a simple route would be to use a casting app such as...

Linkme: AutoCast

AutoInput just got a lot more useful. But don't use it alone.

The accessibility service it uses is sort of a battery hog and was even causing scroll lag on my phone as it monitored input. I would strongly recommend installing Secure Settings so that Tasker can toggle the AutoInput accessibility service at the beginning and end of any task that needs it. There's really no reason to leave AutoInput's service running (and eating battery) when Tasker can toggle it with the right setup.

As /u/EllaTheCat stated, using AutoInput is the way to go. It has it's Event > UI Update but it also has a State > UI State.

I think the main difference between the two is if you need an Exit Task to do also something when the words no longer appear on the screen. If so then use the State context.

If you only want it to trigger something when the text first shows up - use the Event Context.

Hmm. There is no other way to get that permission that I know of.

Alternatively, you could probably toggle that setting in a less elegant way by using Autoinput to access the settings page that you require and tap on the setting. Autoinput uses the accessibility service though, if that is a problem. It also causes my phone to lag, so I don't use it, but that doesn't happen to everyone. There is a free trial, so you can give it a go.

There may be a different way to achieve your aim, but I'm only an amateur with Tasker. Maybe someone else can chime in and help.

You can likely use AutoInput's "Focus" Action to shift focus on the screen to any other element that's not a text field.

And/or - does your keyboard dismiss when you press your device's Back button? If so just use Tasker or AutoInput to issue the "Back" action.

And after the keyboard is dismissed if the cursor is still in the text field you can then use the Focus action to put the focus somewhere else, and thereby unfocus the text field.

Here is a Profile/Task that will detect both volume keys pressed at the same time. (note this needs AutoInput to be installed on the device).

Download and import into Tasker while in the Profiles Tab. Give it a try!

Download Profile XML

Yes, definitely possible exactly the way you want to do it, regarding turning the capacitive buttons off, and then re-enabling them by pressing one of the volume buttons.

You will need the plugin AutoInput to first suppress/disable those two keys ("Back" and "App Switch").

Then you would make a AutoInput profile that watches for the volume key press, and then re-enables those two keys. (Using the power button as the profile trigger may or may not work, but you can try that as well.)

So first turn the capacitive buttons default function off:

TASK: "Turn Off Buttons"

A1. AutoInput > Modes > Key Suppress Key Suppress: Enable Keys: Back,App Switch

A2. Profile Status: "Watch For Volume Keys" Status: on

A3. Flash: "Capacitve Buttons Disabled"

Put a shortcut to that Task on your desktop. This will disable those keys and enable the Profile you'll create below to watch for a volume key press to re-enable them.

PROFILE: "Watch For Volume Keys"

Event > Plugin > AutoInput > Key Keys: Volume Up, Volume Down Key Action: Press down

TASK: A1. AutoInput > Modes > Key Suppress Key Suppress: Disable Keys: Back,App Switch

A2. Profile Status: "Watch For Volume Keys" Status: off

A3. Flash: "Capacitive Buttons Restored"

> is there a way to fix that ?

Yes. What you need to do is just have Tasker emulate a swipe in the app when it detects the swipe in that bottom bar. In fact you could just as easily use a Tasker Scene with an invisible rectangle and put that at the bottom of the screen (or at the top) to detect the initial swipe and run a Tasker Task.

Then use AutoInput's "Gestures" action to swipe left in any other area of the screen where the bar/scene isn't. And/or if you're rooted you could alternatively use a shell command.

Unfortunately there's no Scene Elements that can work like that. It would be nice if they could though. For example right now if you wanted to 'time' how long an element was pressed on, there's no way to do it.

What you can do though is use a hardware key like volume down or up. By using AutoInput you could have Tasker disable the volume keys from their normal function when your Scene is showing, and remap them.

An AutoInput "Key Event" Profile would register the presses, and it registers down press separately from up press. So you could have a Task looping/repeating only while the key is held down, or measure how long a volume key is held down for before it's released, etc.

CC: /u/xyph5

You could use AutoInput to have Tasker click through the settings sequence, as if you were doing it by hand. Can be extremely fast too, but you would see a brief change of the screens within the app.

Yes, Tasker along with the plugin AutoInput can directly turn the screen off/on when power to the device is present or not.

Autoinput and tasker combo is the perfect solution for you.

MacroDroid has "launch and press" and "touch screen" but it requires root. If you aren't rooted, both Tasker and MacroDroid would require you to use the AutoInput plugin. AutoMagic ("control UI") and AutoMate ("interact") have this feature built-in.

As /u/UnkleMike mentioned - the plugin AutoInput can provide information about what app is currently in the foreground.

For example you could make the first Action of your Task be a "UI Query" action, which returns the name of the current app in the variable %aiapp and you can then use that in the rest of your Task.

Get the AutoInput plugin :) You can disconnect hardware buttons and reconnect their press and release events via profiles to tasks. Then do a calculation to measure the interval between press and release.

The plugin AutoInput has a screen capture feature that also includes a "compare" function. It can compare a full image to another,or compare a section of an image to a section of another image.

Just link the S-Pen Intent Profile to a Task that uses an AutoInput Action to do whatever simulated tap/scroll you want done.

One thing though - doesn't pressing the S-Pen button bring up the S-Pen menu? If it does you can always start the Task with a "Back" Action to back out of the menu, or perhaps you have the S-Pen menu disabled?

Possible surely.

With the tasker plugin AutoInput you definitely can, it can basically simulate manual actions amongst other things.

If you are rooted you might be able to use shell commands like 'input tap X Y' or 'input swipe X Y' to do the same without a plugin. Here's a guide to that on pocketables

Maybe there are other options like using intents or similar, somebody else should know more about that.

Without root the only option would be AutoInput or TouchTask.

Sorry I dont have that phone with me. But I did so tasker launcher google play then only made autoinput click the upper left corner then "my apps & games" and finally click "update all". With a few seconds sleep between them

You can use AutoInput to bring up the Recent Apps screen, then have AutoInput click on text "CLOSE ALL".

You'd probably have to get a bit creative to get the page title ;)

I think that in the Task that AutoShare triggers, if you begin the Task with an AutoInput "UI Query" Action, it could possibly grab the page title as long as the webpage is still showing on the screen.

Some of it will depend on which browser you're using as well. I know that in Chrome - AutoInput can 'see' the page title, and returns it as the first element in its %aitext() array. Other browsers you'd just have to test it.

Alright, I've got the answer for you :)

In my other reply I mentioned using Source > USB but I just saw your other reply about Tasker not recognizing USB charging on your device. So scratch that.

The solution exists with the plugin AutoInput and it's "UI Update" Event Profile. The key is that you mentioned your lock screen says "charging rapidly", and you can use that as the trigger. So - remove the Power: Any context and replace it with:

Event > AutoInput > UI Update Apps: System UI Texts: charging rapidly

And that should do it!

The AutoInput plugin has Profile Events for "UI Update" and "UI Action", in which you can specify an app, and some text to appear in the app which will trigger the Profile.

And the text you'd be looking for would be related to any unique elements on the app's screen that relate directly to multi-window. There's a Helper/Test Task to help show you what AutoInput "sees" when it looks at a screen.

Yes can do it with plugin AutoInput. Profile would look like this:

PROFILE: Event > Display > Display Off

TASK NAME: "Reboot Timer"

A1. Wait 30 Minutes

A2. AutoInput > Unlock Screen

A3. AutoInput > Global Action > Power Key Menu

A4. AutoInput > Action > Click > Text: Power Off

A5. (AutoInput Action to click whatever confirm text/button needed)

As was mentioned elsewhere here - once you get this part working you'll have to add some pieces to prevent an unintended reboot, but get this part working first. For testing you could change A1 to be just 1-minute, etc.

The plugin AutoInput has this ability. Just make a Task with the AutoInput Action to record video, then put a shortcut to it on your homescreen.

The main trigger for your Profile (if you're using the one I think you're using) is the Display being on/off correct? (i.e. there's nothing in the Profile about the Power Button itself).

There are plugins like AutoInput that can detect the press of hardware keys as the trigger for a Profile. The Power Button can be tricky though, it's sometimes device/OS dependent on whether Tasker/AutoInput can detect it at all, or with the screen off.

If it can detect the Power Button on your device, since AutoInput can detect whether a key was pressed down, or released, it will then be rather easy for Tasker to calculate how long the button was pressed for. You'd just have to try it and see.

Yes you can use AutoInput to accomplish this, using two aspects of the plugin. The first would be its "UI Update" Profile Event to detect when that button pops up in Shazam.

Then after that in the linked Task you'd have an AutoInput action to press the button. Something like:

PROFILE: App: Shazam + AutoInput UI Update > Text To Appear: "My Shazam Tracks"

LINK TO TASK: A1. AutoInput Action > Click > Text: "My Shazam Tracks"

And that should do it. In the Task in A1 you may need to designate something else to click based on exactly what it says on your screen. Or you may have to address the button using its "Id" field. Thankfully AutoInput has an "Easy Setup" mode to assist you :)

Yes, the plugin AutoInput has Write/Replace/Paste functionality, including the ability to specify which field on the screen.

It works to input text into most Android apps and input fields, with the main exception being able to 'type' text into a web page that's inside of a browser window (like in Chrome) as most mobile browsers don't allow outside Accessibility.

Other than that though I've seen it put text just about everywhere :)

No offense to your fine work sir, but - the plugin AutoInput already has this ability to return the color of a pixel at any coordinate, as well as the full pallette of colors in an entire image, without root needed.

Additionally, as shown in the above - it can compare any specified rectangular area of an image to another image of the same area that is stored on the device. So for example if you want to determine in any app if a checkbox is checked - you would store an image of that part of the screen with the box checked, and then AutoInput at any time can look at that part of the screen and compare the two to determine if they are the same or different. (in which case returning whether a checkbox is checked).

Can also be used to 'see' if a thumbs up icon has been highlighted in a music app, or anything where there's only a graphical visual indication on the screen, and not any text or other designator that could be compared otherwise.

I think this is a good interim solution if a more technical one can't be found. Using AutoInput and its UI Query Action to put the application name in the variable:

PROFILE: Application > Google Play Music, Pandora, 8Tracks

TASK: A1. AutoInput > UI Query [leave config blank]

A2. Variable Set: %MediaApp To: %aiapp

And that will at least save in that variable the last media app that was in the foreground each time. Then can using something like AutoLaunch to Launch that last used media app at anytime later, for example when connecting to car:

PROFILE: Bluetooth Connected: Car

TASK: A1. AutoLaunch > App Name: %MediaApp

/u/ehead if you give this a try it will/can potentially solve the issue.

Best way is to use the plugin AutoInput with its "UI Query" action. That basicallly takes a look at whatever's on the screen, and returns a lot of info about it, including the app name.

So add a first couple Actions in your "Process REDDIT Code" Task, that are:

A1. AutoInput > UI Query (leave Config blank)

A2. Stop If %aiapp !~ Tasker

And that'll do it!

I think there is a solution that will work. It will require the plugin AutoInput, as it has a Profile for Event > UI Action that will detect any interaction with the screen.

That coupled with an App Context, then linked to a timer Task, should do the trick. It would look like this, using Gmail as the example foreground app, and 5 minutes as the timeframe:

PROFILE: Event > AutoInput > UI Action + App > Gmail

TASK: "My Timer" A1. Wait 5 Minutes

A2. AutoInput > UI Query (leave config empty)

A3. If %aiapp ~ Gmail

A4. Launch App <whatever other app>

A5. End If

Collision Handling: Abort Existing Task

The key is really the Collision Handling setting in the Task's Properties. That way anytime anything in the app is clicked, it starts the timer Task over again. You can also see in A2/A3 that once the time period itself is up, the Task checks to make sure that Gmail is still the active app, and if so launches the other app.

Give this a try, should definitely work, and if so there is some icing on the cake for it to account for all possible circumstances :)

You can use AutoInput's "UI Query" action to query the Chrome Screen. Tasker would just have to open Chrome first. In the array that AutoInput returns named %aitext() there will be an element that says 3 open tabs or whatever number followed by the words "open tabs".

So Tasker would just have to parse that number out. The general Task outline would look like:

A1. Launch App > Chrome

A2. AutoInput > UI Query (leave config empty)

A3. Variable Set: %index To: %aitext(#?+open tabs)

A4. Variable Set: %words To: %aitext(%index)

A5. Variable Search: %words Search: ^[0-9]+ Store Matches In: %matches

A6. Variable Set: %num_tabs To: %matches(1)

And that will get you the number of open tabs. If you have AutoTools you can do it all in just 3 actions with the "AutoTools Regex" action.

Also if you want to run this Task at a certain time and the screen needs to be on - you can use AutoInput's "Wake/Unlock Screen" action.

It might be possible by using setting up a profile that reacts to the %WINvariable. Otherwise it's 100% possible by using AutoInput and its UI Update state to react to the text in the error popup.

Saw a guide here

You need to install the app first. Then go to tasker to create the necessary task, then create a profile to run that task. Instruction is in the attached screenshot from the xda post. It is pretty confusing to set up that task but you need to match what you've created with the first three lines:

Type: Text
Value: do it later
Action: click

I noticed you said that you also have Macrodroid. Macrodroid can run Tasker plugins, so you could probably use AutoInput. Also, I'd personally recommend using Tasker over Macrodroid or Automate. It has a huge community over at /r/Tasker and a ton of plugins are developed for it.

Also, if you can root, the shell command input tap x y is better and more reliable than AutoInput.

The plugin AutoInput can do this with its "UI Query" action. It will look at the Chrome screen and (hopefully) see the text that is in the URL bar/field.

It will return the url in its aitext() array, which you can then save to any Global variable you'd like.

You would use plugin AutoInput to both detect that the call has been answered as well as press the button. (you'd have to test the latter to make sure it can press a number pad button on your phone).

So you'd likely have AutoInput's UI Query look for the Timer to start on your call screen indicating the call has been answered (or anything unique to the call screen that changes when you actually answer the call).

Whole thing would look something like:

PROFILE: State > Call: Incoming Number: <choose phone number>

LINK TO TASK: A1. AutoInput > UI QUERY Text: 00:[\d]{2} Regex: true

A2. AutoInput > Click > Text: 9
<or use Text: WXYZ> <or maybe Element ID: com.android.contacts:id/nine>

And that should do it!

(Edit: May need an additional AI Click action to open the "Keypad").

When you say "idled" are you referring to the screen being off? Because neither TouchTask or AutoInput can operate while the screen is off.

Don't think that's possible directly.

The longer workaround you could do is set AutoInput's UI Query to trigger every time you open an app and then check if %aiappmatches any of the names on your list.

Don't think that's possible.

If you want a "clunky" solution you could make a UI Query loop with the help of AutoInput that continuously checks for the "@" symbol.

Feel free to send your credit card number to "".

As for the task, the easiest thing to do is to:

Open the UI query action.
Press the Variable Setup and go into the Chrome Dev app.
Search for a random website so that the url get's populated.
Click on the notifcation and go back into Tasker.
"Check" the field that contains the url.
Set the name of that field to url.

Try and run the task again to see if it works.

As for Youtube I don't know if it's possible. Try to run a UI Query on within to app to see if an url is visible. It's easiest done by using This task. It populates your clipboard with all the data you retrieve from running the action.

The only way to know if it works for reddit and other apps is to check if an url is visible anywhere. Otherwise most apps have a "share button" avalible somewhere. You could use AutoInput to click it for you, but it wouldn't be as clean.

If what you want to do is have your steering wheel controls trigger things in Tasker, the plugin AutoInput can likely do it.

The first thing you'd do is install it, open the AutoInput main app (from the app drawer) and go to the Log screen. The Log is live/realtime, and with your device connected to your car, start pressing the steering wheel controls.

If you can see them show up in the the AutoInput log, you can use them in Tasker AutoInput Profiles to trigger Tasker Tasks.

You can get the screen content using AutoInput's UI Query action. But it might be hard to get it properly formatted.

There's a few workarounds. One of the best ones is the combination of a Profile along with the AutoInput plugin in the linked Task:

PROFILE: Event > Variable Set > %WIN

LINK TO TASK: A1. AutoInput > UI Query (leave config empty)

A2. If %aiapp ~ Tasker

A3. Flash "Tasker is open!"

A4. End If

So basically when a new window is opened, if %aiapp is Tasker, then proceed with your Task. More realistically you just put this as A2:

A2. Stop If [%aiapp !~ Tasker]

And then put all the rest of your actions after that. Give it a whirl!

If there are no intents/activities avalible for the app to do that you could always use AutoInput to make the clicks for you.

Well the easiest thing would be to use AutoInput. It has a build in feature for unlocking the screen.

You can likely just use Tasker's "Call" Action to bring up the Call Window/Screen with the number pre-filled in. This might get around that popup showing up.

And even if it doesn't, the plugin AutoInput can take care of auto-clicking it without you having to see it or manually touch the screen (or wake up ;).

(In fact you'll likely need AutoInput to initiate the actually sending of the call either way).

It should be possible by using AutoInput yes. If you haven't used it before the easiest thing is to use the Easy Setup feature, you can't really go wrong with that one. :)

Haven't heard of anything like that, but as a last resort you could use AutoInput.

It requires the screen to be on and is allaround not the best solution, but it would be possible at least.

Could probably be done by using AutoInput but it would require the screen to be on and it's kind of clunky.

If it's a setting in the app you can configure by clicking it by hand (say if you need to navigate through some menus and then check a checkbox somewhere or something etc) then the plugin AutoInput can in all likelihood automate it for you.

The plugin AutoInput can likely click it. The best/simplest way to do it for starters would be to find the x/y coordinate of that button on the screen and give that to AutoInput for it's "Click" action.

To get the x/y coordinate you can enable Developer mode/options on your device, and then enable "Show pointer location". Load the screenshot you took, and then swipe to that point and it will give you the x/y in the status bar.

The Tasker plugin AutoInput can put just about any non-rooted phone into Airplane Mode.

Either by going to Quick Settings as suggested by /u/hay4bay, or, by using AutoInput to open the Power Menu Dialog and click on Airplane Mode that way.

Also as inquired, AutoInput can shut down or restart the device this way as well. No root needed.

(Regarding the determining of speed, the related plugin AutoLocation can detect when the device is moving and speed, etc. )

Basically I'm using AutoInput to simulate a tap on the "Add Transaction" button once Tasker launches YNAB. I've coupled this task with a Nova Launcher shortcut, so in effect, I swipe up on YNAB, and I get taken straight to the "Add Transaction" page.

A1: Launch App [ App:YNAB Data: Exclude From Recent Apps:Off Always Start New Copy:On ]

A2: AutoInput Action [ Configuration:Type: Id Value: com.youneedabudget.evergreen.app:id/add_transaction Action : Click Is Tasker Action: false Check Screen State: false Timeout (Seconds):20 ]

Autoinput would do the trick, i guess.

I think it's happening because the head unit does not have i backup battery, and some cars shut the power completely off when you stop it. I've heard of other workarounds for it too, but they are more mechanicy.

/u/TremendoSlap put forth a very interesting solution using Intents with straight Tasker.

Another solution (that would use a plugin) would be to use AutoInput to track whichever app was the most recent one opened by using it's UI Query feature to save that app's name or package to a Global Variable that Tasker will hang on to until needed.

Then, when Bluetooth connects, Tasker would launch that app using either the plugin AutoLaunch, or, a Java(script) method that is floating around here somewhere, if I have it I'll post it. But AutoLaunch will be used in the example:

PROFILE: App > Spotify,Pocket Casts

TASK: A1. Wait 1 Second

A2. Plugin > AutoInput > UI Query (leave config fields blank, it will return %aiapp and %aipackage)

A3. Variable Set: %MediaApp To: %aiapp

That will take care of saving the app's name to the variable for use anytime later. Then use this to Launch the app on Bluetooth connecting:

PROFILE: Bluetooth Connect > (your phone etc)

TASK: A1. Plugin > AutoLaunch > App Name: %MediaApp

And that should do it!! If you'd rather use the package name for any reason you could set a variable like %MediaPackage to value of %aipackage in that first Profile/Task, and then use that package in AutoLaunch in the second Task.  

I don't think there's a way to stop it from popping up without root, however, you can probably automatically close it when it does pop up. I did that with the high volume level pop-up using Tasker and AutoInput.

Edit: Here is the XML of the profile if anyone is interested. You should be able to import it into Tasker. It does require the AutoInput plugin.

Edit2: Here is a profile that works for the mobile data pop-up.

I'd rather not create a new post, but just want to share my Tasker rundown:

Default Profiles:

Turn on my Bluetooth before I get in my car in the morning
If headphones are connected, set appropriate Volumes/Settings

Location/Time/Calendar Based Profiles (my favorite use-case for Tasker):

At work: volumes down, BT off, Wifi On. Once I leave work, turn BT back on so it's ready to auto connect to my car.
At home or church: Wifi on, appropriate volumes
In my car: Wifi off, appropriate volumes, start podcast playback (only during certain days/times)
After work, show a notification with buttons that either text my wife pre-generated messages, or call her. Great for keeping her updated on whether I'll be working late or coming home on time.
If none of the above are active, set "Default" profile to true. Set appropriate volumes, wifi off...

Specific App Profiles:

If I'm in a game: set appropriate volumes
Pokemon GO: Crank the brightness (only if work or home profiles aren't enabled), increase display time-out, and pause [Gravity Screen]() .
Enable Auto-rotate for certain apps (youtube, photos, maps...). Once I leave that app, disable auto-rotate (this is an easy winner, no more fumbling with the auto-rotate toggle!)

Misc. & AutoInput Tasks (paired with Nova Gestures/Shortcuts):

Grab a random image from earthview.withgoogle, and set it as current wallpaper
Save the current earthview wallpaper to my gallery (otherwise, it'll disappear the next time I run the above task)
Begin playback of NPR One
Connect to my Google Cast audio speakers, set appropriate volume
Go directly to my Google Keep grocery list
Go directly to my gym membership card (in Android Pay)
Go directly to YNAB's "Add Transaction" page

Of course these are all over-simplifications of how my profiles actually work. Setting it all up has been no easy task. I've had my fair share of head scratching moments, and battery killing profiles. It takes time, patience, and the willingness to troubleshoot and refine it to your liking. Sometimes, you have to weigh whether or not a profile/task is work it, resource and battery-wise. Just take it one profile at a time, read the documentation, and ask around. You'll learn!

GEARTH RUNDOWN: To find out how I did this, read these comments.

Using the AutoInput app it's possible.

Action=>Plugin=>AutoInput=>Global action=>Power Dialog

You could use the AutoInput plugin to click the button for you automatically.

for easy setup: https://play.google.com/store/apps/details?id=com.joaomgcd.autoinput

with Tasker

You will most likely need AutoInput. I use that to open my August lock app and then "tap" the unlock button in the app for my door. It is from the same Dev as Tasker.

You would want to tie the task to a notification. I highly recommend AutoApps also from the same Dev. You can get AutoInput as well as AutoNotification that would make it easily to catch the push notification you are wanting to link to the task. As you may also might guess, it's from the same person.

You could automate the process using the AutoInput plugin

Try the screen on event and use the AutoInput plugin to automatically dismiss the lockscreen.

Maybe you could try the AutoInput plugin or TouchTask

I believe this app could do

https://play.google.com/store/apps/details?id=com.joaomgcd.autoinput

AutoInput has a direct Record Video action.

This should be possible with AutoInput. First in the profile that turned up the volume when Pocket casts is launched, add:

Profile: Application => Pocket Casts

Task: A1. Media Volume 15 A2. Plugin => AutoInput => Modes => Key Supress => Volume up

Exit task: A1. Plugin => AutoInput => Modes => Disable key Supress => Volume up

This will disable the volume up key so that it no longer controls the volume. It still works with AutoInput though.

The next profile is so that you can have Tasker react to when you click the volume button:

Profile: Event => Plugin => AutoInput => Key => Volume up

Task: A1. Plugin => AutoShare => intents => Pocket casts => play/pause

To control Pocket Casts the easiest way should be to use AutoShare and its intents that are avalible for download Here.

Let me know if this works for you or if it doesn't or there was something you didn't understand. :-}

Might be possible with a scene yes, but you'll still Need AutoInput if you want to supress the keys.

Plugin: https://play.google.com/store/apps/details?id=com.joaomgcd.autoinput

I don't know if this is acceptable but you can also automate tap inputs using tasker and AutoInput

(Most likely) AutoInput will help.

You can grab BT battery info through intents, as outlined here: https://www.reddit.com/r/tasker/comments/9h4hn2/help_grabbing_bluetooth_battery/

As for changing button functionality, /u/ZellZoy is right, I would use the AutoInput plugin. https://play.google.com/store/apps/details?id=com.joaomgcd.autoinput&hl=en_CA

Here is a reddit post running through how to use AutoInput to intercept Bluetooth button presses: https://www.reddit.com/r/tasker/comments/3f0ebb/how_to_using_a_bluetooth_remote_to_launch_tasker/

Plugin Link: AutoInput

https://play.google.com/store/apps/details?id=com.joaomgcd.autoinput

Use plug in action block, then choose screen capture option. This lets you return the pixel color to a string, it's in hex rgb

You can use the AutoInput plugin Keyguard event action to monitor when smart unlock is detected.

As someone who's had plenty of difficulties with %WIN being very inconsistent, I also personally recommend getting AutoInput for this purpose. In addition to being able to automatically perform gestures and inputs, it's also very good at detecting the current window, far better than I've found %WIN is. It can be a little more complicated to set up however.

If you're curious about it, I recommend you download AutoInput, the Snackbar Tasker Plugin, and this project for Tasker. The project allows you to go to any screen, and then have AutoInput query it. When it's done, it copies everything it sees to your clipboard. If you paste this into a notepad app, you can search through it to find Text that's unique to this screen and app.

If you then choose AutoInput as your State Context in Tasker, it gives you the option for a specific app you want to query, and some unique Text present on that screen to make it trigger when that specified app is open.

For example, my Overview Screen is listed as being part of the System UI app and there's unique text on it that's always present, "Application info". Plugging this info into the AutoInput State Context allows me to very consistently determine when the Overview Screen is open versus anything else. It's not as quick and dirty as %WIN, but again, I find it far more consistent and accurate if you're willing to go through the trouble to set it up with everything.

Yes you can using the tasker plugin AutoInput to click on the screen for you.

You can try the Key Suppress action in the AutoInput plugin.

AutoInput has a back button action which you can use maybe try it out and see if that works?

You can use the plugin autoinput to paste on a currently focused field or let it focus on a field first before posting

https://play.google.com/store/apps/details?id=com.joaomgcd.autoinput

Autoinput will do this for you. Not sure if there is a better way though.

https://play.google.com/store/apps/details?id=com.joaomgcd.autoinput

Yes, using a tasker plugin, AutoInput

You probably mean AutoInput.

Yes AutoInput plugin can help you do this.

AutoInput can detect hardware key presses and link them to Tasker Tasks, however the display must be on.

Since you are not rooted, the only way you can do this is with automated touches. Seeing as how you have Tasker, I'll use Tasker and the AutoInput plug-in. You can import these files in Tasker and use the tasks or edit them.

Here's comfort view high and comfort view low. Here's how to trigger them via a homescrenn shortcut and here's what one looks like in action (it just looks like someone is doing it). Your screen will be highjacked for 2 seconds while it completes, but, hey, one-touch switch.

You could alternatively trigger the tasks at certain times or whatever, but you'll need to add screen on and unlock steps—which would require something like Secure Settings or SecureTask.

You may also be interested in System UI Tuner, which can unlock Night Mode. It is a stronger blue light filter than comfort view, and can even be stacked with comfort view.

AutoInput

This is the AutoInput I have installled, which is part of the AutoApps suite. I notice that it has the same developer as AutoTools, so I'm not sure what exactly the difference is.

Off the top of my head, I would think this could be easily accomplished. I've never used either of these before, so you'll need to test it of course, but I would set it up like this:

PROFILE:

Event: Phone > Phone Ringing > Priority: Highest

TASK:

Phone: Take Call

I'm on a Note 4, so you might have this problem on the S4 too, but the 'Take Call' action isn't available on my phone. With root you might be able to use it, but if you can't we'll need to come up with another way to answer.

Now, to interact with the dial pad, I would recommend using AutoInput by Joao. This will be used to actually press the "1" button. I'm at work, so I don't have time to actually figure out the steps to do so, but once I'm home I'll edit this with directions if you aren't able to get it or someone else answers by then.

You'll need to make sure that when a call is taken, the dial pad is what appears, and not the blank caller profile page. I'm pretty sure there's a setting for that for Samsung phones under the call settings.

You should probably add a WAIT action of at least one second (test the time between the take call action and when the phone displays the dial pad) between the take call action and the button press action... that should help with pressing the button too soon.

**There's also a setting in AutoInput for Screen Query, so this could potentially be setup to wait until the 1 is actually displayed before the button press. This would avoid needing the dialogue all together because it will press at the right time (in theory) every time. Again, can't run through the steps for you yet.

I would also use AutoInput if the TAKE CALL action isn't available for your phone. When a call comes it, you would use it to select the answer call button or whatever.

I'm sure someone else here will have a cleaner setup, but this might work to start with! Let me know if I can help.

AutoInput is definitely what you're looking for.

/r/Tasker - Toggle Settings

I've done it with Play Store - AutoInput. I don't remember purchase price of the pro, but it does require a second 'servicer' app, Play Store - Auto Apps.

I'm not sure what functionality Trigger exposes (e.g. NFC id detected) in Tasker.

I think Auto Input can pick up some headphone buttons.

https://play.google.com/store/apps/details?id=com.joaomgcd.autoinput&hl=en_GB

It's possible by using AutoInput's UI Query.

Here's a task I use to send the current tab to another device using Join, but it should work for what want to achieve as well :-}

I'm not sure if it's possible to react to a 2 finger swipe. AutoInput can react to single swipes like, left,right, up-left,down-right etc. So that might be an option for you.

The AutoTools (Beta Link, Community link, Playstore link) plugin has a Gesture screen that let's you react to more complicated gestures. You will however have to activate that screen first so I don't think it would be of much help to you.

As for the webpage sharing. I don't know it it's possible with PB through Tasker. I do know it's possible by using Join since I have a similar task on my phone.

This would be easy to do in Tasker. The near dying part anyway, and for some shut downs. There are some shut downs (e.g. hold down Power button) where there wouldn't be time to get a location fix.

For the near dying, just a profile with a context of Battery between 0 and X, with a task: action of Get Location (network or GPS) then compose email with %LOCN or %LOC (depending on which Get Location you used) then use AutoInput to hit the send button.

Tasker does have a Shutdown event but it's largely inadequate: it just allows variables to be changed. You could email at Boot, though.

See my reply about using plugin AutoInput to open it. I posted a video too of how lightening fast it is too :)

I don't use Google Play Music, but maybe the Tasker plugin AutoInput can help with that. It seems that this plugin is good for Tasker-ing things on a non-rooted device.

I don't use it myself, so I can't give you any pointers, but AutoInput should work.

AutoInput can be an incredibly powerful plug-in to have. Among other things, without root, it can be used to simulate touches, enter text into a field, or capture text from an area of the screen. Many people find its ability to simulate touches without root to be immensely useful. Link to the Dev's website.A link to the FAQ ...Please Note: I am a Bot.. To report errors or request additions, message /u/letestaccount

Try this: Tasker AutoInput

Tasker is fantastic. I've done so much cool stuff with it, and some fun things as well. You can do a lot without being rooted,though some actions, like toggling battery saver mode, do require root.

However, there's a plugin by the amazing developer joaomgcd, AutoInput($1.35 USD IAP for full version), which can click on most buttons in apps without root. If you're planning on automating your phone's functions without rooting, this plugin is awesome. You could make Tasker open the Battery Saver screen and quickly click the toggle. However, it would be much more seamless if you were rooted.

I see there's a lot of the detail on how to do most of this explained here. I'll toss in a way to DELETE the SMS without needing root.

The plugin AutoInput can delete the thread/conversation (and maybe individual messages) but I assume the SMS's from your carrier all come from the same number/contact, and if there's more than one SMS from them - you want the whole bunch of them gone.

So you use Tasker to open Messages, then AutoInput to long-click on the SMS conversation with the messages in it, then use AutoInput to click whatever button/icon represents delete, usually the trash can, and confirm any 'DELETE' pop-up that may appear.

LOOKS LIKE THIS

The 'UI Query' Actions are there to wait until the next text appears on the screen. When it does, it proceed to next Action to click it. In this example I get message from my carrier via number 6772, so this deletes them.

This should do it. AND - it all works with the screen OFF. So I think that's pretty cool/convenient. At least on my Note 4 Lollipop. If the screen is locked though it may or may not, just got to test it on your device.

The only way that Tasker can "see" what's on the screen at any given moment is to download/use the plugin AutoInput from the Play Store / JoApps.

AutoInput has a future called "UI Query" that will look at the screen, and return all the text elements in an array called %aitext()

You would then use one of Tasker's IF/matching function to see if the text you're looking for exists on the screen.

Yes. Except for item 4, that will need a plugin like AutoInput

https://play.google.com/store/apps/details?id=com.joaomgcd.autoinput

Have you tried AutoInput?

I think it is possible with Autoinput. Have you tried?

https://play.google.com/store/apps/details?id=com.joaomgcd.autoinput

>I'm not sure if this app is made for what I need

No need to wait and ask if it works, just try the Tasker trial and AutoInput trial directly. Try it yourslef and if it works, buy it for real.

AutoInput

if the app does not have any 'open' intent you will need autoinput https://play.google.com/store/apps/details?id=com.joaomgcd.autoinput or touchtask https://play.google.com/store/apps/details?id=com.balda.touchtask or adb wifi or shell root to perform clicks and swipes. to perform clicks and swipes, device screen needs to be on and unlocked. remaining things are inbuilt in tasker. launch app action to open the app and a time context profile to perform actions when desired. best of luck

Auto input a plugin for tasker.

This resurrects an old thread 😊

>the heks auto imput

AutoInput is an add-on to Tasker that provides a way to automate interactions with the screen.

>why can't I find anything about it?

I can't answer that. It's right here in the Play Store. Maybe you misspelled it?

Well I didn't have to do anything to get my AirTurn working with my tablet, but I did investigate anyway, as it seemed like an interesting problem. I figured out a way to do what you want.

You're going to need the AutoInput plugin, although you should be able to get the keystrokes using the LogCat function, as keystrokes usually show up as ACCESSIBILITY entries

First thing I'd do is create a somewhat generic autoinput profile, that matches all keydown events. Then for the execution of the profile, do a flash that shows you which keycode name was pressed. Set that task up, run it, and press some buttons on your remote. You'll see which keys they send to the device.

Once you know what keys are sent, I'd go in and edit the autoinput settings to only fire on those keys, and then edit the execution to use an Input>Keyboard, and choose the appropriate keys.

You might have more success using AutoInput to tap/scroll the screen though.

https://play.google.com/store/apps/details?id=com.joaomgcd.autoinput has this feature

I've made it work via AutoInput. This Task

Shows the Devices button
Launches the Notifications panel
Clicks on the word "Devices" (you'll have to change this text if your phone isn't in English). This uses AutoInput.
Hides the button again.

There's a similar thing on Nova Launcher. I don't know of any way other than using the AutoInput plugin to press the buttons automatically. I'm happy with that.

https://play.google.com/store/apps/details?id=com.joaomgcd.autoinput&hl=en_GB&gl=US

The link shows the beta versionn.

I haven't used it myself but this might work:

https://play.google.com/store/apps/details?id=com.joaomgcd.autoinput

This is what I use:

https://taskernet.com/shares/?user=AS35m8kEqSNyoiYOogz8IcM5EXJi1BnhOZgjaT2dZtNentuq8I6Mgtgr7WVfdjmNolY%3D&id=Profile%3ASelect+Tasker+For+NFC

Requires AutoInput

Profile: Select Tasker For NFC Restore: no Notification: no

Event: AutoInput UI Update Apps: NFC Text: Tasker

Enter: A1: AutoInput Action Type: Text Value: Tasker Action : Click Timeout (Seconds): 23 Structure Output: Off

I haven't noticed a similar issue (Android 10), I think my Kiwi Browser is blocking that popup. If I did have that issue and couldn't find another way then I would use AutoInput + Tasker to click the cancel button on the popup.

After doing a short sub Search (intent Keep note) - always available on the very top of every page - I found this which should do the Keep job:

[HOW-TO] List your Google Keep notes and open a note directly in the Google Keep app (No root needed)

Add this to an app checking context - e.g. Event/UI/New Window or Event/Plugins/AutoInput (UI Update) - and integrate with any other preferred actions within the Enter task.

Further information can be found at the side bar to the right or, if you are on mobile, tap sub's menu ≡ then 🛈.

Valuable information for starting with Tasker: Tasker Wiki, User Guide

Profile for bt connected, you can specify the name of the Bluetooth in your car to avoid activating when connecting to any Bluetooth device.

In your entry task launch the app. You could also use Autoinput to press the button to turn on insurance.

In your exit task have autoinput turn off the insurance and then go to home screen or whatever

Use AutoInput.

>No way to tell tasker to click an element without it, right?

Using "ADB Wi-Fi"...but You know...a reboot and You will lose "ADB Wi-Fi".

I'd go AutoInput or TouchTask

Here I was reporting to Joao the issues with "End Call" and "Call Screened".

Try to contact Joao, because He told (above link) that on "pure" Android, "Call Screened" and "Call Screening" should work.

>i had this on s7, the workaround has been disabling "instantly lock on power button" or whatever the exact name of that setting was (i've used 5 seconds timeout instead).

Thanks, tried this, but on my devices the screen still turn off :/ so as workaround I'm using "Airplane Mode" on/off in conjunction with "Airplane Radios" "Cell".

You can use AutoInput, if you have root then you can use base Tasker, and if you want to use the ADB Wifi action then you can use that too.

You already did more than half the way, use AutoInput to finish the rest. ;-)

It will tap for you and switches the wanted light(s).

Yes you need to buy Tasker and then install AutoInput

You can always trial them both before though for 1 week.

Guarantee though you will not regret buying these 2 apps. I use Tasker since few years now and cannot imagine using my Phone without Tasker being the first app I install.

check AutoInput

I'm not too sure what are you trying to achieve but if it's to simulate a click or tap on your screen then you can use AutoInput.

If you want to do that from Tasker without any plugins then you can do it like this:

Tap (27) A1: Run Shell [ Command:input tap X Y Timeout (Seconds):0 Use Root:Off Store Output In: Store Errors In: Store Result In: ]

The X and Y in the command are your screen coordinates (e.g. 539 1857) for the click/tap.

https://play.google.com/store/apps/details?id=com.joaomgcd.autoinput

It's one of the many plugins made by the same developer as Tasker

That's because xdotool uses X11. It wouldn't work on your Android device itself.

But I'd try AutoInput to do what you want.

Download AutoInput:

https://play.google.com/store/apps/details?id=com.joaomgcd.autoinput

And we can AutoMate the closing of either of the recording cameras at the end of the Task with:

Stop Quick Video

A1) Status Bar Set: Expanded

A2) AutoInput Action Configuration: Type: Text Value: Click to stop Action: Click

A3) WAIT 500MS

A4) Status Bar Set: Collapsed

A5) Beep Freq: 4200 Duration: 200

A6) Flash Text: Recording stopped

You could probably try simulating a press the mute icon using the AutoInput plugin and see if that works?

I have a Task/Profile that auto pastes the clipboard whenever a text box gets focus, then closes the input window and hits "OK". It is rough around the edges... I turn it on manually when I'm going through scanning & renaming new catches, because it doesn't do any checking about what screen it's on or where it's pasting.

I never made it do any others steps, like going on to the next Pokemon... I was actually a bit concerned about automating too much, out of an excess of caution. It would in theory just take a couple steps (make a loop that drags a certain amount from L/R, then run this task) for a quick & dirty version.

One gotcha is that it uses AutoInput, which I believe is an extra $2 purchase on top Tasker.

Edit:

I've never shared from Tasker. Hope this works:

Task: PoGo AutoPaste

Profile: Paste on Focus

Hope this helps as a starting point.

You wouldn't use Flutter for this. Use an app like AutoInput to automate screen touches.

Try the AutoInput AutoInput Ui State state context (condition):

Create a profile > State > Plugin > AutoInput

Well, yes. AutoInput (AutoApps plugin) and also TouchTask, both allows you to record screen and take pictures too. In case you decide to go for AI:

+ > Plugin > AutoInput > Screen Capture

A1: AutoInput Screen Capture [ Configuration:Video Path: /storage/emulated/0/AutoInput/screencapture.mp4 Capture Audio: true Video Resolution: 1080p Duration: 0 Timeout (Seconds):200 ]

I just didn't mentioned it to you because I understood you didn't want shell code nor plugins. Seems I missundertood it, sorry.

>I wanted to see if anyone was able to do this (without running a shell script) with Tasker or Autoapps?

Btw, I have an old project to record screen, if you wanna try and look how to record video and take screenshots using AI:

https://www.reddit.com/r/tasker/comments/9bub37/project_screen_recorder_screenshots_draw_on_screen/

Do not know when I will update it, sorry.

Video Map Bixby button to anything

To perform the tap, try to play with AutoInput

Some suggestions for future help requests:

It's always better to search this sub before posting. There are good chances to find answers to your questions/needs.
Try to check out the sidebar too. It's populated with more than 1 hundred examples/tutorials.
You should post or at least describe what you have so far or what you have tried.
In your post, You could write/use...Thanks; Please; TIA or similar. It's a good habit and You will maximize the chances to not be ignored from users.

Good luck.

If you still don't find a suitable solution to your problem you could try the Compose Email action instead:

Add action > Net > Compose Email

Downside: doesn't send the email automatically (this could be somewhat circumvented by using either the Tasker Keyboard action or the AutoInput plugin).

Try the AutoInput plugin :)

Those are task descriptions :) The AutoInput plugin is what you're looking for btw.

it might be possible using autoinput

is it specific massage you want to react to or all of them?

Try using the Long Power Button action combined with an AutoInput click action.

Probably using intents, but if you're referring to using the AutoInput plugin in the background then no, it's not possible.

Checkout the AutoInput plugin.

Try using the AutoInput Ui Query action and the AutoTools Count Repeat Items option located in the Text action.

You could try using the AutoInput plugin AutoInput UI Update event condition :)

There are two ways for tasks to do things inside other apps.

The most used required the Autoinput plugin. The autoinput plugin can simulate taps on the screen.
Tasker can be used as a keyboard. You can use the keyboard to navigate through the line app. Using tab, up, down, left, right and enter.

Well there's the ADB method as you mentioned above or you could stimulate a few screen presses using the AutoInput plugin.

Here you go AutoInput ;)

https://www.dropbox.com/s/v4ihc8xdvzzkx0c/Sync_Calls_And_SMS_To_Cloud.tsk.xml?dl=0 A method in Tasker. Needs the https://play.google.com/store/apps/details?id=com.joaomgcd.autoinput Tasker plug in. It might need root did nt try it to non rooted phone

Also the ui query parts need changing to English

AutoInput is a tasker plugin https://play.google.com/store/apps/details?id=com.joaomgcd.autoinput

UI Query makes several lists, %aitext() is an array of strings, it defaults to everything but can be trimmed to be only visible ones or clickable ones. It also sets %aiapp, the name of the app.

All my idea is, is to use %aitext() to see if the display is changing.

(The narcolepsy is a side effect of medication for Parkinson's. I endure it.)

Checkout the AutoInput plugin :)

The Logcat Entry event can probably do what you need otherwise the AutoInput plugin is also an option.

Edit: also checkout the Secondary App Opened event as an alternative option to the Logcat Entry event context(condition)

You may have some success with the AutoInput plugin

You could stimulate turning on the feature using the AutoInput plugin.

You could try the AutoInput plugin and the AutoNotification plugin to accept the call for you.

Take a look into this plugin. https://play.google.com/store/apps/details?id=com.joaomgcd.autoinput

You could try the AutoInput UI Query action to capture the URL for you then open it in another browser.

Use the AutoInput plugin to automatically click the button for you.

Maybe this can be useful for you. Anyway, if you have AutoInput, it's easy. Just create profile which will have Event on Phone Ringing. On that, create task where you put AutoInput and set position where you want to click automatically.

You could try the AutoInput plugin if that what you really want

Try the Custom Setting action and see if that works if not you could try the AutoInput plugin instead.

Try using the AutoInput plugin :)

A sure way of doing this is to use the AutoInput plugin.

As u/SAM4191 suggested your best bet is to use the AutoInput plugin to confirm for you.

You could try the AutoInput plugin.

Try using the AutoInput plugin the gesture option should be able to do what you want.

Try the AutoInput plugin

You could combine the Shake event context with a AutoInput press on the device screen to emulate the behavior :)

You can use the tasker plugin AutoInput to perform the ui clicks for you :)

Maybe AutoInput is close to what you need? You can set it to automatically open apps and touch buttons for you etc. People use it to open games every n hours and collect awards for example without them actually having to do anything.

*Requires Tasker though.

You can use the Key Suppress function of AutoImput plugin. If you don't find it, just download AutoImput and this task and run it TASK

To do nothing when pressed just in some apps, create a profile>apps and select the apps you want to block home button, and assign to it the task I've sent above. Then, long press the task and clone it, edit the task to disable the Key Suppress function. Save and go back to the profile screen, expand it clicking it's name, and long click the task, a menu will appear, click the "add exit task" option and select the task you cloned to disable the Key Suppression. This will make when you open the selected apps, the home button will be disabled, but when you switch apps or close the selected ones the home button starts to work again.

Yep, This is totally on point. I was just gonna say the samething as well the only way I could thing of doing this is using the AutoInput plugin to simulate the swipes for you.

Maybe you could try emulating this using the AutoInput plugin?

I don't think that's possible but you could instead use the AutoInput plugin to wait until the text appears then click it

It's available on any of my app's play store listings.

I don't know how to have Ok Google active while the screen is off, but as an alternative, you could use AutoInput to maybe react to a long hold on a hardware button.

I did a similar thing when I wanted the torch to turn on by clicking the lock button twice.

Which version of android is your device on? The Window Label variable presumably stopped working after android 4.4 so if you're running anything after that this may be the issue.

As an alternative you could try using the AutoInput UI Query action to wait until you're in the app then perform the action.

As a workaround to this issue if you have the AutoInput plugin you could use the Keyguard Event and select the Smart Lock Detected option then in the task set the variable to false.

You could use the AutoInput plugin (works without root)

You could try creating a workaround using either the AutoInput plugin or TouchTask. Another alternative that has worked reliably for me over the past year I've been using it a simple solution created by u/Ratchet_Guy which works without using any plugins

Profile: Volume Key Track Change (299)

State: Display State [ Is:Off ]

Event: Variable Set [ Variable:%VOLM Value:* User Variables Only:Off ]

Enter: Volume Key Track Change (298)

<<h3>CLICK VOLUME KEYS QUICKLY:</h3>

UP then DOWN for Previous Track

OR

DOWN then UP for Next Track</h3>>

A1: Anchor

A2: Variable Set [ Name:%initial_vol To:%VOLM Recurse Variables:Off Do Maths:Off Append:Off Max Rounding Digits:0 ]

A3: Variable Set [ Name:%time_span To:300 Recurse Variables:Off Do Maths:Off Append:Off Max Rounding Digits:3 ]

A4: Wait [ MS:%time_span Seconds:0 Minutes:0 Hours:0 Days:0 ]

A5: Anchor

A6: Vibrate [ Time:60 ] If [ %initial_vol+1 = %VOLM | %initial_vol-1 = %VOLM ]

A7: Media Control [ Cmd:Previous Simulate Media Button:On App:Musicolet Use Notification If Available:On ] If [ %initial_vol-1 = %VOLM ]

A8: Media Control [ Cmd:Next Simulate Media Button:On App:Musicolet Use Notification If Available:On ] If [ %initial_vol+1 = %VOLM ]

>1gemma.. ok I've gotten the icon folder where it needs to be, I can press the play button in the task screen and it just copies the task to clipboard

Yep, that's the intended behaviour. It could input the copied emoticon automatically into the current focused app feild, but that would require you to at least know about tasker Keyboard action or the tasker plugin AutoInput. so you'll just have paste the emoticon into the currently focused app

>Where is this quick setting tile, and ultimately how do I even get to see these emoticons letaline use them in any kind of text message?

You can directly assign this task to a quick setting tile (provided you're on Android 7 or above) by going into the tasker Preferences setting and goto to the Action tab and choose the emoticon task in the Quick Settings Task option then simply add the tile to the list of available tiles in your notification bar.

Edit: also make sure to install the AutoTools plugin in order to see the list of icons

You could use the AutoInput key event action to react to "Back" keypresses and in the task use a Ui Query action to query the current screen everytime you press the back button and if the current screen matches the homepage of the app if you press the back key again suppress further key action.

Edit: Unfortunately yes this does require accessibility settings to work. Without root or accessibility settings, I'm afraid what you're after is impossible to do. The best chance you have is to suggest to the app developer of the app you're trying to prevent going home with the back key to implement something similar.

If you're rooted yes, but if not you can emulate the unlock using the AutoInput plugin.

Edit:also you could try AutoTools or the SecureTask plugin but you'd have to grant either of them write secure settings permission via adb.

You can try with AutoInput plugin

A1 - Launch app - Android Auto - Settings

A2 - AutoInput action -> Press the 3 dots

A3 - AutoInput action -> Press developper settings

A4 - AutoInput action -> Share Screenshot Now

EDIT : My phone is not in english, when i first wrote you i was thinking about the "Dump screenshot" dev options, but looks like its not working.

You could use the AutoInput plugin to switch if off for you.

Sorry I should have specified a bit more. I'm using the app AutoInput and the configuration for it is:

Type: Text
Value: SHUFFLE PLAY
Action: Click

Well I'm not familiar with the app but your best bet is to try using AutoInput or TouchTask.

Edit: forgot to mention it's not possible to interact with the screen while it's off. You could also look into intents and see if there's anything related to Toggling the app or try asking the 3rd party app developer about the available intents.

Well from what you've detailed I'd say your best bet is to try the tasker plugin AutoInput and see if it's possible.

Anything that can be done with a user interface can be done by calling the functions the a button is connected to. The hard part is figuring out which ones need to be called with what arguments in what order.

I think you're using an Android, but I'm not sure. Auto input can listen for UI events and simulate taps according to the description so you could use it to press the buttons very quickly. It's made by the same dev as r/tasker which is very high quality.

Making the app debuggable should give you more info with development tools. Besides that all I can say is to learn how to use Android Studio a lot.

https://gist.github.com/nstarke/615ca3603fdded8aee47fab6f4917826

https://developer.android.com/studio/debug/index.html

https://developer.android.com/studio/command-line/logcat

It would be nice if you could just paste it in. Released in the last 6 months or so is tasker net shares which make importing tasks a lot easier.

Here's autoinput https://play.google.com/store/apps/details?id=com.joaomgcd.autoinput

You can use AutoInput

Looks like the Google Voice API was recently killed but if you're up for a bit of coding, looks like there's a few alternatives on that page.

I don't really do much of this sort of stuff via Google but have you tried playing with Google Assistant?

Does the Google Voice app have quick replies via a notification button?

Do you have a root?

As a last Resort, you could likely get something working with Keyboard Actions or if needs must - AutoInput

Unfortunately since lollipop the "%WIN" variable has been deprecated instead you can use AutoInput

Familiarize yourself with the Autoinput plugin. Use the autoinput easy setup/configure option when building your task.

My crude way of going about it would be to launch app (openconnect) -> autoinput click connect. Launch app (firefox) [as a fresh copy] ***maybe just set that website as startup page*** autoinput click menu, autoinput click request desktop site, autoinput click connect.

There may be better ways of going about this, but this is my quick and dirty solution. You may be able to substitute some steps with intents [i'm not familiar with firefox intents] and/or Autoshare? [I haven't used it]. But Autoinput is still necessary I believe.

You can build this as a task, then drop a tasker shortcut widget on your homescreen that will run this task.

See if AutoInput will work for this.

Androibd version, rooted, xposed?

You could see if Profile: State - Keyboard Out works.

Else, when your keyboard is out and if you see a keyboard icon in the navbar, you should be able to react to that with AutoInput.

Else, when your keyboard is out and if you have a notification, you should be able to react to that with AutoNotification.

You could see if Action: Display - Immersive Mode - Off works.

Well I don't know of any native way to launch it but you could always use autoinput to simulate the press on the icon for you :)

https://play.google.com/store/apps/details?id=com.joaomgcd.autoinput

Welcome to the first day of the rest of your life.

When you open the AutoInput plugin from your app drawer, does it give you the option to unlock the full version or start a free trial, something similar to this?

Also, if you don't already have it, it's a good idea to also install AutoApps.

Are you rooted/xposed?

What brand (& chip if known) is your plug?

Does AutoInput find the button press?

If so, you could send that to a Assistant linked IFTTT Webhook via things like Join, AutoRemote or cUrl

Not so much automatically getting rid of the message, but I believe just getting the message means that a server is suspecting you of cheating.

That doesn't mean you'll be banned after 100 times or 1000 times, but if you get that message frequently and do things like not stopping at signal lights, walking through rivers/buildings in a straight line, etc. I think your account actually gets flagged somehow. Additionally, if you spin a Pokestop and then "teleport" halfway across the world (faster than a plane can carry you) to spin another Pokestop, your account can also be flagged as doing something physically impossible.

Your account can also be flagged if your character constantly "drifts" -- if you're using a joystick to control a "fake" GPS, every so often your phone's actual GPS will try to kick in. The real GPS fights with the fake GPS, leading to your character constantly "drifting" in the direction of your real physical location. It gets worse the further away your spoofed location gets from your real location. You can't disable your actual GPS without Pokemon Go noticing, so you have to constantly find a GPS "deadzone" so Niantic doesn't notice your GPS fighting with your spoofing app. As I mentioned earlier, if you "teleport" too fast you also can get banned, so you literally have to stay in that dead zone until your spoofed location matches your real location.

This is just a couple of the protections Niantic has against spoofers -- I'm sure there are more. Niantic is actually fairly forgiving when it comes to this sort of stuff, probably because there's a lot of room for false positives (mapping data incorrect, people running through dry creeks, people just running across the street without caring, bad GPS signal, general coincidences, etc.). But if there's a pattern (consistent speeds, consistently doing those things I mentioned earlier, lots of "drifting" and correction), I believe they'll send out those anti-cheat messages.

It's also possible that simply emulating touch inputs could also be tracked. I never messed with that sort of thing, but it should be possible to create an app which automatically detects a Pokemon, enters the capture screen, and throws a perfect catch every time by simulating touch inputs. All the user would have to do is walk around (and spoofers wouldn't even have to do that).

Again, I've never looked into it, but the tech exists that such a thing is possible (on Android, at least). I would imagine that Niantic also knows that it's possible to do something like that, and so anything which emulates a screen touch might also trigger their anti-cheat system. But that's all just speculation.

Might be worth checking out something like AutoInput or whatever to see if Niantic flags your account for using it, or if you get mysterious "errors." When you play with GPS Spoofing enabled in Developer Options, you get a mysterious "GPS Error," which is very vague but essentially means that Niantic has detected that you're possibly trying to spoof it. Another interesting thing is that Niantic also has a "shadowban" system where you only ever see common Pokemon -- you never find a rare Pokemon again. I never experienced it myself, but I certainly read about it a bit.

Mm

Try using autoinput!!!

https://play.google.com/store/apps/details?id=com.joaomgcd.autoinput

Is this it? https://play.google.com/store/apps/details?id=com.joaomgcd.autoinput

You can try using the plugin AutoInput's "UI Query" action to have Tasker 'see' what is showing on the screen. And as long as there is something unique to each homescreen, you can have Tasker determine it that way.

However depending on the Launcher - the "UI Query" action might always return all the text/icons on all the homescreens, rather than just the one showing. You'll just have to test it with your Launcher.

AutoInput has a "Screen off/on" Action. It doesn't say anywhere that it doesn't work with Android 9, so I'm assuming it does. You may have to try it of course.

And this is different that Screen Lock, in that it just turns the display off and doesn't effect whether it locks or not.

You can AutoInput's "Gestures" Mode. This places an invisible 'cover' over the whole display, rendering it basically unable to be interacted with. So you'd just toggle this on/off.

As a note, this feature is found under AutoInput > Modes > Gestures. It is not the regular "Gestures" action used to perform a gesture.

Look into AutoInput.

Hmmm....could be related to S8+. /u/joaomgcd would have to check it out when he returns.

As far as a workaround, I'm pretty sure AutoInput could fix the issue. Just put an AutoInput "UI Query" action in your Exit Task for that Profile (or for each app Profile that does this).

Don't put anything into the Config, just enter/exit the Action to add it. That AutoInput action will generate a variable named %anapp and that should contain the name of the app in the foreground, not the notification's app. You would then use this to compare and have Tasker not exit the Profile. Example:

PROFILE: App > Gmail

ENTER TASK: A1. <all your Gmail settings etc.>

EXIT TASK: A1. AutoInput > UI QUery

A2. Stop If %anapp ~ Gmail

A3. <all the rest of your Exit actions>

Interesting request!

Using the AutoInput plugin, if you use the State > AutoInput > UI Update Profile context, and put the website address in the "Text" field of the config - for example www.nbcnews.com - it should work.

(Also specify your web browsing app(s) in the "App" field of the AutoInput UI Update config.) You may find it works with Chrome and not with your device's browser, or vice versa. You'll just have to test to find out.

In your Enter Task put the auto-rotation action, and you shouldn't need an Exit Task as it should revert on its own.

Now, this is the most basic setup to do this. You may find it also triggers on pages/screens like the "Favorites" or "Bookmark" screens of your browser. This shouldn't be an issue though since once you leave that screen to some other website, the auto-rotation should revert to off.

However if that happens too often, there's probably some more logic that can be added to the Profile/Task to prevent that, but give this a go first and see how it works :)

> Hope that helps you help me.

Yes it does lol.

So - if you have to login, the "HTML Read" action in AutoTools would likely be the one to use. Or its Regex action. Both allow you to login to a website in the "Authenticate" section.

You may have to point it directly to the page you're looking for. The refresh part might be tricky. I think the website will see the request as a 'refresh' though and provide you with the most recent data.

You'd have to test it and see. Some sites logins work well with AutoTools, others sometimes not (like banking websites with heavy duty secure logins).

Another separate option is to use AutoInput in an actual browser window to mimic the clicks you'd normally make by hand.

Have it refresh the page, then open the browsers menu and select "Find", then have AutoInput put the text in the find field, then read the browser window (via "UI Query") to see any results are present.

AutoInput can detect an insane ton of key inputs in an Event Profile, and then link to a Task that does what you want.

The keycodes themselves are also available in the linked Task in the variable %aikeycode created by AutoInput.

The plugin AutoInput can detect clicks on the display, and return the coordinates, using it's Event > AutoInput > UI Action Profile trigger.

The coordinates will be available in the variable %aicoordinates in the Task linked to the Profile.

Don't think it can return drag coordinates though, just individual clicks.

i'm less famillar with tasker, but i have google-fu and the ability to make assumptions that may or may not be valid

setting the time: use this and add some sundown+[time] steps to finely control the slider

controlling the camera: if you're rooted tasker might be able to hook into the app to control it directly, otherwise use autoinput to do it through the UI

You can use AutoInput's "UI Update" Event context to trigger on Tasker. Might have to put some additional logic in the Task so that as someone mentioned - it doesn't get stuck in some weird loop, whereby you won't be able to use Tasker.

But if you do get some weird loop, at least the fix is rather easy - temporarily uninstall AutoInput.

If you don't have root, you must use a plugin such as AutoInput, that "presses buttons" for you.

The AutoInput plugin lets you disconnect a button from the system (and reconnect it later) plus it provides press and release events for said button that you can hook into.

If you're rooted:

A1: Run Shell [ Command:input keyevent 66 Timeout (Seconds):0 Use Root:On Store Output In: Store Errors In: Store Result In: ]

If you're not rooted, I'm 99% certain AutoInput can do it, but i don't have that one installed, so can't remember.

https://play.google.com/store/apps/details?id=com.joaomgcd.autoinput

Install and open that. It should be one of the first features there. Let me know of you get it working

> to their original positions

You mean it goes back to the default text? It will do that whenever the Scene is destroyed and re-created. Rather than using "Destroy Scene" this is where using "Hide Scene" comes in handy.

That way it still exists and when you use the "Show Scene" action again - it should still have all the same values in there that were typed.

The key here is to make a button specifically to Hide Scene. Otherwise if you use the back key, or the "Show Exit Button" option - it may not re-show with the user input values. If you want to disable the device's "Back" key while the Scene is in use - the plugin AutoInput can do this.

AutoInput can do this, and it has an Easy Setup Mode so you just click the point on the screen and AutoInput will remember where you clicked.

Use AutoInput and create a Profile for Event > AutoInput > Key Event > Keys: Back and link it to a Task that destroys the Scene, and also turns the Profile itself off (so it doesn't trigger everytime Back is pressed all day long).

Then in your main Task that shows the Scene, add an Action to turn the "Back Key" Profile status to "On".

Thanks for the quick response.

Good to know. I'll have to try something different.

Here's what I've tried so far with mixed results.

Using Tasker by configuring a Tasker Scene to open with a shake gesture. This is possible in Tasker, but you'll have to shake your phone to get the Scene to activate, plus if your phone happens to shake while in your pocket, the Scene will activate. So it's not ideal.
Tasker AutoInput Plugin.The Tasker plugin costs $2. So far I've got it to open my Tasker Scene by configuring AutoInput plugin to open my Scene on an Event when the Home button is pressed. If I press the Home button twice in quick succession, I can get the plugin to open my Tasker Scene without actually going to my home page. The quick succession button press action is typically reserved to open the camera on a Galaxy Note phone, but you can disable the camera from opening in settings. So far, this option is working best.
I was thinking about getting this NFC Button product to give me more dedicated buttons, but I'm not that carzy about mounting the button strip on the back of my phone.

AutoInput's "UI Query" Action may be able to help you.

It can "look" at any screen and return information about what it "sees" in terms of both text and element ID's. If when the widget is on the screen there is something specific that the "UI Query" action 'sees' - you can use that to detect the widget.

This Test Task/tool can help you out with configuring this as well.

Try making the first Action of your Task:

A1. Alert > Popup

And if that wakes the screen then the Task will run. You can have the screen turn off immediately again at the end of the Task using this code or you can use AutoInput's new "screen off" feature.

Give it a try.

You can download AutoInput from the Play Store and enable Auto Dismiss Keyguard for it to work like in the OnePlus 5T. No swipe needed.

That's where AutoInput comes in handy.

Hm. The best way I think this could work would be through autoinput (https://play.google.com/store/apps/details?id=com.joaomgcd.autoinput)

If you can use Tasker and Note buddy to show the input method, you should be able to also incorporate Autoinput to select the handwriting keyboard

AutoInput may be able to do this. The only question would be if there's something on the screen that can be clicked. If so AutoInput can likely do it.

However, if the "key press" has to be from the actual remote, there may not be an easy way to do it without root.

One possible way that mimics how you would do it manually - use Tasker's Display > Status Bar > Expanded to open the Notification Tray, then use AutoInput to click the QS Tile, and then have Tasker close the Tray.

It would happen very fast, the only potential caveat is that the screen may need to be on for this to happen. However even if the screen is locked, as long as it's on it may still work behind the Lockscreen. Would have to test it out :)

Might be possible. The plugin AutoInput has a "UI Query" Action which can read text on the screen, and many times beyond the screen if it requires scrolling.

If you use Tasker to download the PDF and then open it in an app that AutoInput can 'see' - you may be able to do this. The screen may have to be on for it to work, but AutoInput can wake it if needed.

You may have to experiment with a few different PDF viewers to find the one that works best with AutoInput as well.

AutoInput on an endless loop with a slight wait?

You can use AutoInput to unlock the screen. And if you'ed like you can use SecureTask to remove the keyguard :)

To disable / enable the "Recent Apps" and "Back" buttons, you'll need to use a plugin like AutoInput where you'd have a Task linked to the S-Pen profile, with an AutoInput Action based on the true/false that the %peninsert variable returns (see my other reply).

PROFILE: Event > Intent Received: com.samsung.pen.INSERT

TASK: A1. If %peninsert ~ false

A2. AutoInput > Modes > Key Supress: ENABLE Keys: Back,App Switch

A3. Else If %peninsert ~ true

A4. AutoInput > Modes > Key Supress: DISABLE Keys: Back,App Switch

A5. End If

You mention UI Query so assume you have AutoInput. If you notice in the UI Query Config, in the "Text" section - it says it will wait for the Text you specify to show up.

As far as how long of a time it waits, you can use the Timeout Slider at the bottom of the Config Summary screen to set the time.

If you want the Task to continue after the Timeout if the text never shows up - check "Continue Task After Error" and have Tasker check if %err is set.

You can use the AutoInput plugin to make it automatically tap things to achieve what you're after. You can also use the "input tap" shell command if you're rooted :-}

Am assuming that you'll be looking at the screen in your messaging app when the message is sent correct?

If so can you post an example of what it would look like?

It may be possible to do this with plugin AutoInput's "UI Update" Profile Event, if the screen is visible when you want it to trigger.

You can definitely emulate screen touches without root, although you're rooted anyway so it doesn't matter. AutoInput can emulate screen touches with Tasker.

AutoInput can likely do it. However it might get confusing if some of the numbers appear multiple times in multiple areas of the display.

For the Clock at least if you needed to you could make a "lookup table" of screen coordinates for where to click for hours and minutes.

So - it's not impossible but might no be the easiest thing either.

That's disable, not deactivate.

Perhaps you could use AutoInput to tap whatever disabling method is available. My KitKat Moto G doesn't have that feature, I've no idea what it looks like. Do you have a screenshot?

> How do I rebind my volume keys

Check out the AutoInput plugin.

Yes! In fact this a good idea to get an additional use out of that button. You could just use the plugin AutoInput with its "Key Event" Profile trigger, to watch for when the Back button is pressed down, and then when it is released.

Tasker would then calculate the difference between the two times and if it's at least a certain length (in seconds or milliseconds etc) - you can have Tasker do what you want.

Here you can see in the AutoInput Log where it detects the Back key being pressed, then released, and how it tracks the time down to thousandths of a second.

Yes AutoInput is a Tasker plugin. And regarding any screen lock, it typically doesn't have to be disabled, it really depends on what's being clicked.

If the screen is locked and the loud music dialog appears above it, I think AutoInput should be able to click it.

Thanks, I might try that for future projects. For now I've settled with using a tasker plugin on my phone that simulates user input to send my commands (AutoInput).

Oh, is that all? Then I suggest setting the whole thing to immersive mode, and have a couple of the navigation icons at the bottom that are maybe AutoInput Global actions for Back and Home and Recent Apps. You have flexibility of location with Lightning Launcher via freeform, although I suppose Nova Launcher's subgrid positioning is not bad.

You can probably find the icons in the System UI app; on my Moto G, they all start with "ic_sysbar_".

Some people have used AutoInput for this. It depends on how accessible your dialer is.

You can use the plugin AutoInput to click whichever option you want each time it comes up.

I'm pretty sure the Profile Event is "New Window > Dialog" and then you'd enter the title or text that appears inside the dialog to make it specific to that Dialog.

Then in your linked Task is where you'd use AutoInput > Action > Click > Text: Ok or "cancel" or whichever one you'd like. It would take an extra second or two for the Profile to detect the dialog but at least it would happen automatically and wouldn't have to deal with it by hand each time.

This sounds like a simliar situation as the "Danger: High Volume" popup that annoys people trying to crank up their headsets. After any reboot that message comes back everytime, and AutoInput deals with quite nicely.

So you want to find if a small image exists as part of a much bigger image? Not sure there's anything in Tasker or any plugin that can do that specifically, but if you know certain details there could be a way.

Basically if you know exactly where (from pixel/coordinate numbers) the small image would or would not occur in the bigger image, you can use the plugin AutoInput to do this. If has a compare function and you can specify cropped image areas to compare.

However if the small image could appear randomly in many different locations each time inside the bigger image, there may not be a way to do it.

Well as a temporary fix you could always use AutoInput to press the play button in the app :-}

Hi, I've ran into the exact same problem some weeks ago and have the solution for you. You need AutoInput by Jao and Tasker (don't know if it works with macrodroid).

What I did was in the task, I selected, "AutoInput Global Action" and then selected "Quick Settings". Then, for the next line, I put in an AutoInput action, type: Text, Value: Hotspot (Hotspot tile needs to be in Quick settings!), Action: Click. You can't create the AutoInput Action automatically with the Easy Setup because you can't pull down the Quick Settings with two fingers from the top while you are in that mode, so you can't get to the button to click it. (There is probably another way to get there so you could do it, but you can easily just do it manually.) To do it manually, click +, then select "Plugin", then "AutoInput", then "Action", click the pencil in the upper right, click on, "Field Type", and select, "Text", then click on, "Field Text" and type in, "Hotspot" (be sure to get the case correct), then click on, "Action" and select, "Click", then click on the checkmark, and you're done. To close the Quick Settings pull-down just make another step in Tasker: Status bar -> Collapsed. Hope this helps!

You may just need a visit over to /r/Appliances/

Aside from that though ;) I think that if you combine that app with the plugin AutoInput you will be able to accomplish what you want.

Basically you'd find the sensor in that multitool app that is able to reliably track motion vs. no motion when your phone is sitting on the dryer. Then you'd make a Profile that repeats every few minutes and runs a Task with AutoInput's UI Query action.

The UI Query can read information on the screen into Tasker, often times even when the screen is off (depending on the app). But even if the screen needs to be on, you can have Tasker control that as well. Anyways when the information on the screen says there's no more vibration, AutoInput will see that and make your phone ring. Something like:

PROFILE: Time > Repeat Every 3 Minutes

LINK TO TASK: A1. AutoInput > UI Query

A2. If %aitext(6) ~ 0.00

A3. Ring Phone

A4. End If

And that would do it. You'd just have to find the text value on the screen that represents when motion has stopped inside the %aitext() array. (The %aitext(6) was just an example). Thankfully a Test Task/tool has been created so you can easily find out what value in that array you'll need to check from AutoInput.

You can fake screen touches. https://play.google.com/store/apps/details?id=com.joaomgcd.autoinput

Do you have AutoInput?

If you go into the main AutoInput app (from the app drawer) and go into the "Logs" section - in the "Catergory: Key" section it logs all keypresses it detects in real time. So it could probably pick up whatever code that custom key you made is transmitting.

You can purchase AutoInput as an independent plugin (as you can most of the AutoApps actually). The subscription is a better deal if you want the whole lot of them ;)

In AutoInput, when you launch the main AutoInput app from the App Drawer (not from within Tasker) - go into the Log Listings screen, and in the "Key" section you can see in real time as any hardware key on the device (or connected to the device) is pressed, and in that process see as well if AutoInput can recognize it.

If it can, you can likely remap it. AutoInput has a "Key Suppress" Action to remove the default key action, but not sure if that will work with Bluetooth devices as well. Would have to try it. Either way though you could map the key to a Task.

Outside of that - I think there's some apps out there specifically to remap bluetooth headset buttons to do all kinds of things. Not sure of the names but you can likely search the Play Store, I'm sure I've seen one before.

> Is it also possible to make an android phone reboot after it is disconnected from power?

Yes. You can do it using the plugin AutoInput with or without root. Basically you use AutoInput to bring up the Power Key menu then it clicks the items necessary to reboot.

It's not as direct as a root-enabled reboot but it works:

A1. AutoInput > Unlock Screen

A2. AutoInput Global > Power Key Menu

A3. AutoInput Action > Click > Type > Text: Restart

A4. AutoInput Action > Click > Type > Text: RESTART

Depending on the device/OS this can even work when the lock screen is enabled. Also the text in the Power Key menu might not be the same as the above, so of course you can put in whatever is needed (i.e. click "OK" instead of the final "RESTART" etc)

For the Profile to trigger the Task you would just use:

PROFILE: State > Power > Any Invert: Checked

When you check the Invert box it means when a power source has dis-connected.

That's not true. Autoinput does touchscreen emulation no root.

If the popup has a button that says "Ok" for example you just use a Action:

Plugin > AutoInput > Action > Click Type: Text Text: Ok

And of course you'll need AutoInput to do this ;)

AutoInput would be a great place to start since you can select items on screen automatically and scroll if you need to to find a particular station.

If you just press the button briefly (instead of holding it down) - what happens in that case?

The plugin you'd want to use is AutoInput with its "Key Event" Profile. Once you install AutoInput, in the main app (from the app drawer) it has a "Logs" section.

You can see in real time the key(s) it logs as you press them whether that be from your device itself or a bluetooth device, etc. If it can detect the button that you press on your ShowerMate when you short-press it, then you should be all set to assign it to do something using Tasker :)

It would be possible by using AutoInput. It's very easy to set it up using the "Easy Setup" if you haven't used it before. :-}

Yes definitely possible.

Use the plugin AutoInput - it has a Key Event Profile. It can detect just about any key press coming from anywhere.

Once you install it, to find out what keycode AutoInput 'sees' that button as - open AutoInput main app from the App Drawer, go into the Logs section, and then just push that key on your device.

It will show you in real time what you just pressed. Then in Tasker all you have to do is make an Event Profile with AutoInput and specify that key.

As for the first "Stupid Question": I don't know if it's possible directly but a possible workaround is to use AutoInput's UI Update Trigger to react to when you click on the quicksetting.

It might be possible by using AutoInput's UI Update Event. You could set it up to react to clicking on the "Clear all apps" button.

I haven't tried it so I don't know if it works but it's somewhere to start :-}

Haven't used Tasker for more than messing around for a few minutes before uninstalling it... but there's a plugin for Tasker called AutoInput which might work: https://play.google.com/store/apps/details?id=com.joaomgcd.autoinput&hl=en

You may be able to use AutoInput's "Gestures Mode" to do this. That mode creates an invisible "cover" over the display that prevents any normal clicks. It covers even the power menu.

It's actual purpose is to let 'gestures' then be entered that Tasker can perform actions based on, but it's a great way to block access to the display as well.

Not sure if that is even possible :/

The other solution you have is to run a UI Query, use AutoInput to clear all of the "recent apps" and then re-launch %aiappwith AutoLaunch.

You can set a profile that reacts to outgoing calls:

Profile: State => Phone => Call => Outgoing

You can then have AutoInput do the rest for you. I believe the %CONUMvariable should contain the "last called" number.

Yeah, no problem. One caveat, this requires AutoInput. While not the most elegant way to do things, it gets the job done wherever Tasker can't.

Add YNAB Transaction (66)

A1: Launch App [ App:YNAB Data: Exclude From Recent Apps:Off Always Start New Copy:On ] A2: AutoInput Action [ Configuration:Type: Id Value: com.youneedabudget.evergreen.app:id/add_transaction Action : Click Is Tasker Action: false Check Screen State: false Timeout (Seconds):20 ]

I have never used TouchTask but yes it should.

I always use AutoInput's Unlock screen action to turn on the display but it can also be done by using Secure Settings for example, if it works on your OS version :-}

You can use the AutoInput Click Actions to click these 3 elements in this order. The first is type "ID" the other two are type "Text"

com.android.chrome:id/tab_switcher_button

More options

Close

HOWEVER - Chrome is notorious for having elements that are difficult to be clicked on by AutoInput. Just about any other browser would be better. I know on my device the "More options" part is where the sticking point is.

If NFC appears in your Quick Settings tiles - you can do it with the plugin AutoInput using just two Actions:

A1. AutoInput > Global Action > Quick Settings

A2. AutoInput > Action > Click Text: NFC

If AutoInput is allowed to click in that app then yes.

You can still have backups even on the free version of titanium if I recall correctly. I don't believe there's an intent, but I suppose he could use https://play.google.com/store/apps/details?id=com.joaomgcd.autoinput&hl=en

Yes - The plugin AutoInput is the best way. Here would be the basic Task outline:

A1. System > Intent: Action: android.settings.APPLICATION_DETAILS_SETTINGS Data: package:com.yourpackage.name Target: Activity

A2. AutoInput > Click > Text: Storage

A3. AutoInput > Click > Text: CLEAR CACHE

And that should do it. Just make sure in the Intent "Data" field you use that format of package: and then the package name.

If the screen is off when the Profile runs (if you're triggering it hourly) you can make a first action of AutoInput > Unlock Screen

To clarify on the proposed solution, yes likely you'll need AutoInput and then your Profile/Task will look like:

PROFILE: Event > Received Text (from contact)

LINK TO TASK: A1. Launch App > SURE Remote

A2. AutoInput Click > Element or text

A3. etc. etc.

And you'll need to work out the sequence of elements/buttons/things for AutoInput to click on. Could be two Actions, could be six. Basically whatever you'd click by hand is what you'll be configuring AutoInput to do.

Secure Settings won't even work anymore if you are using the newer systemless root. It doesn't recognize it and won't ask for root permissions properly. There are workarounds for updating some settings using a shell command but the one for changing location accuracy doesn't seem to work on newer Android versions.

I was playing around with using AutoInput to do it as the other commenter mentioned. I can report that it does work fine, but it essentially automates the process of doing it yourself - so yes, the settings screen will come up and select the desired location accuracy, for example. That wouldn't be so bad since you are wanting it to happen when you start and quit POGO.

The AutoInput app has triggers that reacts to both hardware key presses and presses on the touch screen.

Should be what you are looking for :)

The key would likely be to have the display come on and unlock, which can likely be accomplished with the plugin AutoInput as it has a Display Wake/Unlock Action specifically to do this.

AutoInput for Tasker. Note that Tasker does cost money, and AutoInput won't work without it.

If you are leaving the Media app during a task you can just run an AutoInput query exiting the app.

Then at the end of the task just set an:

If %aiapp ~ Phonograph Launch Phonograph Else If %aiapp ~ Pocket Casts Launch Pocketcast

I don't think that you can disable the Air Command menu from showing up, but what I do - is use the plugin AutoInput which has a lot of Global Actions (for Back, Home, etc.) and I use the "Back" Action to immediately cancel the Air Command Menu, then after that bring up my own.

So basically:

PROFILE: Event > Intent Received: com.sec.android.intent.action.AIR_BUTTON

TASK: A1. Wait 1 Second

A2. Plugin > AutoInput > Global Action: Back

A3. (put all the rest of your actions here for your custom menu)

A4. etc. etc.

AutoInput?

It's a macro recorder Tasker plugin.

AutoInput Tasker plugin

https://play.google.com/store/apps/details?id=com.joaomgcd.autoinput&hl=en

> You can use AutoInput to click on-screen buttons, or to write some text in text fields of any app. > > You can even retrieve text from other apps. > > You first record your input by actually touching and swiping your screen and then replay that input with AutoInput, which will faithfully reproduce everything you did.

> > It allows you to create a series of input actions, including physical button presses and various taps and swipes, to emulate some sort of macro sequence that can be executed inside any app of your choosing.

> Androidpolice

http://www.androidpolice.com/2014/10/15/autoinput-joaomgcd-tasker-plugin-automating-taps-swipes-text-entries/

Also check out an app called "AutoInput" https://play.google.com/store/apps/details?id=com.joaomgcd.autoinput

It's really useful for helping with tasker as well.

You could use AutoInput to have Tasker automatically delete the frequent contacts.

This AutoInput?

That looks sweet, and it~~'s free too!~~(does that lame free trial thing). Thanks. What do you use AutoNotification for?

Try the auto input plugin:

https://play.google.com/store/apps/details?id=com.joaomgcd.autoinput&hl=en&referrer=utm_source%3Dgoogle%26utm_medium%3Dorganic%26utm_term%3Dauto+input

You can set it to click certain coordinates or app elements. Not sure if it will work behind the lockscreen though.

I imagine, used in combination with the AutoInput and AutoVoice plugins, Tasker could get the job done!

There's a macro recorder Tasker plugin that can sometimes help some people.

AutoInput Tasker plugin (https://play.google.com/store/apps/details?id=com.joaomgcd.autoinput&hl=en)

> You can use AutoInput to click on-screen buttons, or to write some text in text fields of any app. > > You can even retrieve text from other apps.

>

> You first record your input by actually touching and swiping your screen and then replay that input with AutoInput, which will faithfully reproduce everything you did. > > It allows you to create a series of input actions, including physical button presses and various taps and swipes, to emulate some sort of macro sequence that can be executed inside any app of your choosing. >

Androidpolice (http://www.androidpolice.com/2014/10/15/autoinput-joaomgcd-tasker-plugin-automating-taps-swipes-text-entries/)

Then I think you're out of luck. I suppose you could delete messages "manually", using AutoInput to interact with your SMS app, but that might prove to be a clunky solution.

AutoInput is probably your best bet if you're not rooted. It might be a bit finicky to set up the actions, but it should work.

Keep in mind, though, that AutoInput most often needs the screen to be on. If I remember correctly there's an option to automatically unlock your device in the latest alpha or beta, but I think you'd have to be an AutoApps subscriber to access these. Perhaps someone else can chime in here.

If you don't have root and Tasker isn't allowing you to just use the GPS toggle in the tasker actions themselves, then you could try getting the AutoInput Plugin to automate opening your settings, going to location settings and toggling it there for you. But that would be kind of a pain and take about 15-30 seconds to execute every time and you might as well just do it manually yourself.

Ok, install that then go to the Playstore and try to download this https://play.google.com/store/apps/details?id=com.joaomgcd.autoinput

I do this type of thing and it works, here's how.

In your AutoVoice type command Action(s) you need to have an array somewhere that contains the names of the playlists you want to match to the word(s) spoken, paired up wtih the URI of the playlist. This is a whole other involved deal, so let's keep it simple for the time being - Use an IF/ELSE IF to basically say "IF <spoken keyword> EQ 'classical' SET VARIABLE %spotify_code TO <the uri hash value>
Create your Spotify Intent Action. This is how you set it up:

Action: android.intent.action.VIEW

Cat: Default

Mime Type: (empty)

Data: spotify:user:<your username>:playlist:%spotify_code

Target: Activity
To now click something on the screen (whether Shuffle Play or the first song on the list) you're going to need a Tasker Plugin named "AutoInput". It's well worth the investment, as it can focus, click, scroll, and do just about anything you can do by touching the screen, and you don't need root.
To click the first song on the playlist setup AutoInput Action to:

Type: List

Value: 3

Action: Click

<OR> to have it begin SHUFFLE PLAY set up AutoInput Action to:

Type: Text

Value: SHUFFLE PLAY

Action: Click
As far as directing the audio output to your 'Wifi Stereo System', it all depends on how you have that setup, how it is enabled (whether by screen clicks or whatever). Need more info on the technical aspects of that.

A few other notes - in order for AutoInput to go clicking things, the screen needs to be ON. So you'll need a plugin named Secure Settings to use turn the display on for a certain amount of time (a minute or whatever). This would probably be the first Action out of the whole list.

Lastly, if you're currently have to be using Google Now intercept, and say "note to self" I would just download AutoVoice and go with that. In fact the best deal is just to download the AutoApps suite and subscribe for about like a dollar a month. Best dollar I've ever spent lol.

(Note: You don't need root access for any of this stuff above)

AutoInput would probably be best for that, unless you have root.

I have got it working by a clever trick. If the system ui is restarted after every pin enabling or disabling then it works as before. For eg: A condition is met such as in home wifi and secure setting disables the pin. In the same profile i have added a task to launch this app http://forum.xda-developers.com/showthread.php?t=2235956 then using auto input plugin i click on system ui restart and volla the pin lock is disabled. Just bear in mind you have to restart system ui after every pin clear or set. I have used the above app to do so. Auto input is tasker plugin to record clicks, presses on different apps. Link to autoinput https://play.google.com/store/apps/details?id=com.joaomgcd.autoinput&hl=en I used this method you can use other methods too.

Also:

>Lightning Launcher Extreme updated and is now a Tasker plugin

http://www.reddit.com/r/tasker/comments/2hkugo/lightning_launcher_extreme_updated_and_is_now_a/

>Built-in Tasker support starts with LLX 10.5b1. This support consists in

>triggering Lightning actions (such as desktop navigation, script execution) from a Tasker task

>triggering Tasker tasks from Lightning, through scripting

> ]techno_babble_ 3 points 4 months ago > > As a long-term Nova user, what can this launcher do that Nova can't? > > > [–]p0ptarts 1 point 4 months ago > > From the quick look I had, more customization, and a steeper learning curve to use it. > > [–]UnmarkedDoor [S] 2 points 4 months ago > > Can confirm this is pretty much it. I've been with LLX for a year or so - I moved from Nova when when I was having space issues (LLX is tiny). > > Nova is definitely slicker and easier to set up, but there is literally nothing I haven't been able to do on LLX. > > LLX is to Nova, what Tasker is to Automateit (or Llama, or any of those other automation apps that look nice, but cater to people that can't get to grips with the Tasker). > > It's fiddly, but worth it. >

Combine with:

AutoInput Tasker plugin

>You can use AutoInput to click on-screen buttons, or to write some text in text fields of any app.

>You can even retrieve text from other apps.

>You first record your input by actually touching and swiping your screen and then replay that input with AutoInput, which will faithfully reproduce everything you did.

>It allows you to create a series of input actions, including physical button presses and various taps and swipes, to emulate some sort of macro sequence that can be executed inside any app of your choosing.

>Androidpolice

A macro recorder.

> auto plugins for tasker

AutoInput Tasker plugin

>You can use AutoInput to click on-screen buttons, or to write some text in text fields of any app.

>You can even retrieve text from other apps.

>You first record your input by actually touching and swiping your screen and then replay that input with AutoInput, which will faithfully reproduce everything you did.

>It allows you to create a series of input actions, including physical button presses and various taps and swipes, to emulate some sort of macro sequence that can be executed inside any app of your choosing.

>Androidpolice

A macro recorder.

"Autoinput" can automate taps, holds, swipes, etc on the screen without root. If you can tap and hold on the song name after it is recognized, copy it, and then go to Spotify and paste it and add the first result to a playlist this method should work. What matters is if Shazam always puts the song result in the same spot on the screen so your tap setting won't miss. For a starter action you could do [Using Shazam]+ [Shake phone up down] (These aren't the real names) to trigger it.

That's a quick answer off the top of my head let me know if you need more help.

Here's the app:https://play.google.com/store/apps/details?id=com.joaomgcd.autoinput

Getting started guide:http://joaoapps.com/autoinput/

There is- check out "Autoinput" for Tasker which can automate taps on the screen without root. It can also do softkey buttons and some other functions.

https://play.google.com/store/apps/details?id=com.joaomgcd.autoinput

Guide: http://joaoapps.com/autoinput/

Maybe try AutoInput, I'm not sure tasker can detect this natively.

You can use the AutoInput to detect hardware key presses on your device with it's Profile for "Key Event".

In the linked Task you can use Tasker's built-in "Torch" action to turn the flashlight on/off.

The question would be to figure out exactly which key(s) you want to use (and/or which keys are available to use).

What is Reddit's opinion of AutoInput?
From 3.5 billion Reddit comments

AutoInput

Popularity Score: 123

Best Comments

>

What is Reddit's opinion of AutoInput? From 3.5 billion Reddit comments

AutoInput

Popularity Score: 123

Best Comments

>

What is Reddit's opinion of AutoInput?
From 3.5 billion Reddit comments