Accessibility switches off (android 7)

[Robert Winkler]

Hi, switched the Accessibility Services of Automate 'On', but shortly after the setting is switched automatically back to 'Off'.
This also happens with all other applications that would require Accessibility.
I already switched off the 'Battery Optimization' and White-listed it. No success.
My operating system is Android 7, running on a Lanix LT520.
Since rooting does not work either, I suspect some security feature.
Any idea?
Thanks, Robert

[Henrik "The Developer" Lindqvist]

Android bugs. Just toggle the service off/on, or if that doesn't suffice reboot the device.

[EvrEn POSACI]

The same problem was happening on my android device (car multimedia device) with "px3 rom" installed. Accessibility also turned off, when I turn off the device by pressing the on/off button. Then I realized that there was no such problem when I turned off the car, before I turned off the device. This means that when I cut the electricity directly from the device, the permissions were not turned off in the accessibility service.

Maybe can help ...

6 Ekim 2017 Cuma 01:14:51 UTC+3 tarihinde Robert Winkler yazdı:

[Robert Winkler]

Hi, thanks for your feedback.
Obviously, it helps to keep a 'window' of automate open. Is there any way to 'lock' the running app? E.g. Jina uses the notifier ('J') to avoid a closing of the app.
Best regards,

Robert

[Robert Winkler]

Hi, the problem seems related to multitasking. "Inactive" apps are killed. I tried a lot of stuff: Battery optimization settings, Disable doze, Stay alive! etc. Background processes -> 4 (max). But no luck. Anyone running Automate on Android 7?

[Henrik "The Developer" Lindqvist]

It's known to occur during an app (Automate) update.
Sadly there's no known workaround since the accessibility services are started by the system, not the apps providing them.
If you have multiple accessibility services enabled, try disabling the others.

[dar...@gmail.com]

Hello,
are there any news on that?
I‘m having the exact same problem. Like @EvrEn POSACI, I also use a car unit (PX5). It stays enabled with a full reboot but gets disabled every time I switch off the display.
The Tasker app does not have this problem, Accessibility options for Tasker stay enabled always, so I‘m sure there is a way to fix it. Do they use some kind of notification to stay active? I have to check that.

A solution would be nice since I configured automate successfully to select my routes to work/home in car navi according to the time of day...

[Henrik "The Developer" Lindqvist]

It sound like an "power save" feature i the services stops working with just the screen off. Please read:
http://llamalab.com/automate/doc/faq.html#automate_not_running

Just checked, i can see Tasker doing much different, except only using a single process.
Automate uses two, one for UI and one for background, to minimize memory usage. However this has caused other issues on some devices, e.g. the SMS sending.
I'll do some test to see if that's the cause in the case too.

[dar...@gmail.com]

Hello Henrik,

thanks for fast reply.

I already checked for power save feature and of course, automate is already opted out.

But that car head units are tricky, they have more than the user-accessible power save feature. A build-in system app called "MTCManager" kills most applications when the screen turns off.

To clarify what I said about Tasker: Tasker uses some intransparent mulit-app plugin-architecture, and while accessibility services for Tasker main app does not get disabled, the accessibility service for the Tasker AutoInput-App gets disabled, too. The reason that the Tasker main app gets not disabled may be that I already use a custom Rom that may have Tasker main app already whitelisted.

So what can the user do?

As there is a vivid modding community for this devices, there are custom Roms like the one from "Malaysk" that already have a Xposed-requiring App "Graser Dasaita PX5 Hook" installed. That App tinkers with the MTCManager and enables a "white list" for Apps, that should not get disabled. Unfortunately, that requires to decompile the MTCManager and to find the right class and function names for the PX5 Hook in order to work, if the predefined settings do not work, and in my case, they don't.

To make things worse, all that is only documented in a russian board called 4pda and you should have a good coders background to understand what you are doing. If you want to, here is a good start (use google translator to translate in english): http://4pda.ru/forum/index.php?s=&showtopic=820460&view=findpost&p=69621721

But there is a slightly easier way: You can download a modded MTCManager.apk and, if your device is rooted (that is when you have a Malaysk-Rom), you can easily replace that app using root explorer, and no app will get killed when screen turns off any more: https://forum.xda-developers.com/android-auto/mtcd-software-development/rom-malaysk-roms-mtcd-device-t3598908/post72319193#post72319193

I'm currently testing that "no-kill"-version of MTCManager and since two days automate accessibility permission stays enabled! (Kudos to nico84!)

Thanks, I hope everything works fine now...

[Henrik "The Developer" Lindqvist]

The multiple process usage may be the cause, for next release i'll try a workaround.
It's so simple i can't understand why i didn't think of it earlier.
Instead of letting the background stuff run in a alternative process, e.g. named ":background", while the UI stuff run in the default (unnamed) process,
i'll run the UI stuff in the alternative process, e.g. named ":ui" while background run in the default process.
It's a simple workaround, worth a test on a larger scale.

[smart...@gmail.com]

Unfortunately, this problem did not fix on the PX3 device.

and PX5...

[nisalrox...@gmail.com]

No bro......i have same problem....that's shit

[Henrik "The Developer" Lindqvist]

It's an Android issue:

https://issuetracker.google.com/issues/75414169

[kkv...@gmail.com]

Пр