Issue with listener and accessibility services

[Mauro]

Yesterday an Interruption set block gave error because "Notification listener service not running", and it's a couple of days that there seem to be an issue with the Privileged service or something linked with it: the Get clipboard change gave an error "Accessibility service not running" and I had to restart again ADB in TCP/IP mode: after that it worked for some hours, but then I get again the same error and I had to restart again ADB, and so on.

Until some day ago it all worked without issue, and there were no update to Automate or the system.

[Henrik "The Developer" Lindqvist]

The Clipboard get block doesn't rely on the accessibility service, but if that or the notification listener service is stopped it's usually cause by some non-standard "power save" feature killing them, please read: 

https://llamalab.com/automate/doc/faq.html#automate_not_running

The Privileged service should be kept running until device reboot. For way to make it more reliable, please read:

https://llamalab.com/automate/doc/adb.html#privileged_service

Android version?

Device brand & model?

[Mauro]

Sorry, Xiaomi Mi 11 Lite with Android 13; in the past I never those issue and I already checked that page, so I'm not sure it depends on the phone or on power save options (since I didn't change them), but I'll check them again just to be sure.

I  noticed the "Disable adb authorization timeout" was turned on, not sure why: I turned it off again, and already did all of the things to make it more reliable. I'll see if it happens again and update your, thanks.

[Mauro]

I noticed "access screen content and observe your action" was deactivated in the flow with the Clipboard get block, not sure why; I reactivated it, I'll see if the issue happens again.

[Henrik "The Developer" Lindqvist]

That's the Automate accessibility service, as said, it's not used by the Clipboard get block.

[Mauro]

It stopped happening, no idea why, there were no change in the phone (I also turned on again "Disable adb authorization timeout", and it still didn't happen again); there was a couple of days in which it happened, then it stopped and I wasn't able to replicate it.