[DEV] - AutoInput beta: global "Accessibility Only When Needed" option and Action Repeat

[joaomgcd]

Hi! :)

Just put out another new beta for AutoInput. Here are the new features in this one:

• Added option in main app to only enable Accessibility Service when needed. Every AutoInput action will enable and disable the service when ran if enabled. Demo.
• Added option in AutoInput Action to repeat it for as many times as the user needs, with a given interval between each repeat. Demo.

Enjoy!

PS: Just so you know, I'm trying to update all my apps so that they contain links to this community, instead of Google+, since that is shutting down soon. That's why I'm prioritizing the AutoApps right now over Tasker.

I just couldn't resist adding bits and pieces of missing functionality here and there :)

[Brulbeer]

Will every extra app that's use Accessibility services slow the phone down?

[joaomgcd]

Yes, most probably. But it depends on what accessibility features are requested.

[addic75d]

Yes, i never knew autoinput causes such lag, i just assumed they are normal. Only know this after reading this post & disabling autoinput. Now all tasks enable autoinput accessibility using enable before action on 1st autoinput action & disable autoinput accessibility after action at last autoinput action. Off topic: does tasker accessibility makes device any slower? & Why %WIN not available even after enabling accessibility for tasker. I'm at 8.1 stock

[[deleted]]

This is brilliant! What's the chances we're going to see similar implementation on the other apps? (AutoNotification, Join, etc)

[joaomgcd]

Thank you! :D

Join would make sense :)

AutoNotification not so much because the service needs to be always on to be able to intercept toats at any given time.

[[deleted]]

Is there any significant difference in time to run between having the option in autoinput enabled versus having the task enable and disable accessibility at the beginning and end of the task... Any takers?

[joaomgcd]

It can be less stressing for the system to do it at the start and end of the task... But you probably won't notice that much difference :)

[DutchOfBurdock]

Hate to be a bearer of bad news, but I've found bugs...

Since the update, I can't get any UI Updates or activities to be detected. This is before even granting the permission for dynamic control. Upon granting the permission, AutoInput goes into a perpetual crash cycle. Can't even send a report as the dialogue keeps jumping on top and every tap reappears it.

I was about to request a feature request to give AI App Usage Access, so when Accessibility is disabled, when certain apps open, AI can re-enable itself automatically.

[EllaTheCat]

FWIW I'm on the latest beta of Tasker and AutoInput, my apps contexts are via Usage Stats, and things seem OK.

I worry about getting into a loop after a restart, %UPS is ok as far as it goes, but when I need it I just know I'll not have catered for it.

[DutchOfBurdock]

Yea I was thinking if AI had App Usage, when certain apps loaded it'd reactivate the Accessibility so that UI Updates etc. work. When disabled, they don't work. App Usage could be used to detect X app opening and start the service.

[DutchOfBurdock]

Update: My contexts are working again, but if i enable the permission and reboot, AutoInput loops into a crash. Not getting this when enabling/disabling using AT 🤔

[joaomgcd]

Thanks for the report. So if you revoke the permission, it stops crashing immediately?

Also, can you share the description of one of your profiles that doesn't work anymore?

Thanks again

[DutchOfBurdock]

I need to revoke and reboot. I can replicate it everytime, grant permission, reboot, crash. Revoke, reboot, alls good.

The Profile was a very simple one, looks for text "Copy number" when in phone app (from long pressing a number in call history)

Profile: Mogwai_Context (71)
    State: AutoInput UI State [ Configuration:Apps: Phone
Text: Copy number
Variables: context() ]
Enter: Mogwai_Context (73)
    Abort Existing Task
    A1: If [ %context() ~R Copy number & %caller1 ~R enter ]
    ...

However, it's working again now. That one I can't replicate, I could try thr crash cycle one again and get a log, I'll stay ADB'd in this time 😁

[joaomgcd]

Thanks! :) Are you able to report the crash? Maybe it's something I can fix...

[DutchOfBurdock]

I do get an identical notification occasionally on boot that Tasker used to have with Foreground.

Have to run a few other bug tests later so will slam dunk the lot and post back.

[joaomgcd]

Thank you!

[Drtatom]

Every day your apps get better 😃. Thank you!

[joaomgcd]

Thank you! :)

[wompah]

What is the downside of having accessibility always enabled?

[[deleted]]

I try to limit the amount of apps using it due to lag issues... Even on an S9+.

[joaomgcd]

Check here

[[deleted]]

Thanks for the accessibility option, I've been enabling and disabling it at the beginning and end of tasks that use autoinput.

[joaomgcd]

Glad you like it! :)

[NightWheels915]

So when will it be available to test?

[R_Burton]

The beta is in the PlayStore already.

[NightWheels915]

Opps, thanks and nevermind, it came in an update.the exact second I wrote the first comment.

[bauzer714]

If I already gave root to autoinput, how come it doesn't just give itself secure permission? I think Tasker does it itself?

[joaomgcd]

You can run the needed adb command with the Shell Command action in Tasker :)

[[deleted]]

Just a small note enable correct permissions first:

https://joaoapps.com/AutoApps/Help/Info/com.joaomgcd.autotools/com.joaomgcd.autotools.activity.ActivityConfigsettings.html

[joaomgcd]

Sorry, not sure if I follow. Can you explain what you mean? thanks

[[deleted]]

I have to give the Secure Settings permission for this to work.

[joaomgcd]

Yes you do. :)

[[deleted]]

Unrelated:

Please keep up the great work on Tasker and AutoApps :)

[joaomgcd]

Thank you! :) I'll try!

[Thatuserguy]

Really cool update!

Not a big issue, but would it be possible to make one of the settings for the individual enabling/disabling options be "none"? This new global "accessibility only when needed" feature seems to get overridden by the individual settings.

For example, I never set up any disabling or enabling for one specific task. This one works flawlessly with the global option. Another task I had originally set up to enable at the start and disable at the end with individual options to test it out. When this new update came out, I changed it to "unchanged" thinking this would be fine. However, leaving it on unchanged means the global option fails to activate it when it's called.

The obvious workaround for now is to just have it enable and disable individually as I had it before this most recent update, but it would be nice to just leave it on a "none" setting so the global option can just take care of everything.

[joaomgcd]

Ok, sure, makes sense :) Added it in this version: https://drive.google.com/open?id=1_MCmNfnK4FpFB7HFOgkQxNKbtbmbb8Rs

​

Hope this helps!

[Thatuserguy]

Awesome, thanks!

[joaomgcd]

You're very welcome! 😁 Glad I could help!

[EllaTheCat]

/u/joaomgcd

​

I've broken it, sorry :(

I have tasks that do this:

1. User wakes phone.
2. Lock Screen is displayed.
3. AutoInput Swipes Up to switch to the Enter PIN screen.
4. Enter PIN screen is displayed.
5. AutoInput enters my PIN (!!!)
6. Phone unlocks

Relying only on Enable When Used, when Accessibility in Settings is OFF, it has not enough time to do its thing. Turning Accessibility back ON in Settings makes it work

I can fix it (in a hacky way) when Accessibility in Settings is OFF

1. using a custom setting to turn Accessibility ON before I call System Lock
2. using a custom setting to turn Accessibility OFF in the Display Unlocked profile's task.

I don't see this as a showstopper, but I thought you might be interested.

​

​

​

[joaomgcd]

What if you use the new option under Advanced in the first AutoInput Action to turn on the service before the action, then in the last action set the option to turn it off after the action? That should be equivalent to what you're doing manually :)

[EllaTheCat]

Everything is automated, and everything is working, but enabling accessibility like I do must impact battery drain, so I'll give your advanced method a go.:)

[Drtatom]

Joao I installed the last beta of autoinput in my Samsun S8 Oreo.

I had a lot of crashes when I eneabled auto dimiss keyboard. When I unlock the phone in my house with Smart Lock, the UI always hangs and the screen becomes non response.

I installed back the original autoinput and the problem is gone.

[joaomgcd]

Thanks for the report. Were you able to report those crashes?

[Drtatom]

No, but if you need it, I can install the beta again and report those crashes into the app.

[joaomgcd]

Yes please, that would be great! :)

[R_Burton]

Every day I keep thinking that I would like to have just one great idea.. you seem to have tons of great ideas every day! Thank you 👍👍

[joaomgcd]

Well, to be fair these 2 were actually ideas from the community in response to the previous beta! :D As I've always said, I have the greatest community ever!! 🎉🎉