Autoinput keeps losing Accessibility

[Dan Muller]

I have an S24 running Android 15, everything is up-to-date, Tasker and Autoinput are set for unrestricted background use and Tasker is set to keep Accessibility running for itself and Autoinput. I've gone through the checklist of "Why don't Tasker or its plugins work in the background on my device." Once a day or so, I get the Accessibility notification that Autoinput service is running, so all seems to be OK.

But every few days, Accessibility stops for Autoinput and I have to turn it off and back on.

Any thoughts?

[Erik Carlin]

Same..

--
You received this message because you are subscribed to the Google Groups "Tasker" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tasker+un...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/tasker/70daeb0b-abc3-4a18-a42e-d217523007aan%40googlegroups.com.

[Dan Muller]

Oddly enough, this seems to work better if I disable Keep Accesibility Running for AutoInput in Tasker's preferences. I can't swear this is a reliable workaround, but it sure seems that way. I'm continuing to investigate. (Note that I do not have AutoInput's Accessibility section set to Enable Just When Needed.)

[Dan Muller]

This is definitely not a reliable fix. 

Can anyone help?

[aa6vh]

I think this is a definite Android OS bug, and I believe Google has no interest in fixing it.

Some people have had success by keeping the Accessibility service normally disabled, and just enabling it during the brief time they need that functionality.

[Dan Muller]

Thanks, that's an idea I might try. I also just found a suggestion to create a profile that triggers every hour to turn accessibility off and then on. I'm hoping one of those will do it.

In the same discussion, there was an indication that this is indeed an Android change, but that Tasker's developer can (possibly) deal with it. And there seems to be a version in beta to address it. Hope that works and gets released soon!

[aa6vh]

I found this on Reddit, and it looks like an interesting solution to the accessibility issue:

https://www.reddit.com/r/tasker/comments/1mdu1kw/tip_my_solution_to_solve_problem_about_one_ui_7/

I have not tried it yet though.

[Dan Muller]

That's interesting. I've already set up the "hourly reset" profile and that is working well, as workarounds go.

[Dan Muller]

Elsewhere,  João indicated that the issue is something that he can't do anything about, so it looks like we're stuck with workarounds. Fortunately, several have been suggested that appear to work well.