Good that it's working again with that change...
As to what might have caused the issue: my setup requires MacroDroid to be the default assistant (so as to control Airplane mode) and I've noticed in the past week or two that I've had to remove and re-apply MacroDroid as default assistant every couple days to get Airplane mode actions to work. Maybe a glitch got introduced in either a recent MD or Android update affecting this general area of MD being the device assistant and/or admin...
That doesn't make sense still.
a) I never had to use Device Admin OR Device Assistant just to control Screen Off action. I have root and this worked perfectly fine before. If you're not using root to perform actions and you rely on either Device Assistant, Accessibility or even MacroDroid Helper, then yes you may run into issues, where either the permissions for them are removed, OR perhaps they're not running in the background (e.g. MacroDroid Helper not running would mean it can't intercept calls from MacroDroid). As another example, if you force close MacroDroid on MIUI devices, Accessibility services need to be re-configured. Of course, the new ADB workaround/hack in the MacroDroid settings can help with this, but you get my point.
Device Admin however, does not lose its permission regardless of the situation.
The problem is NOT that I had MD set as Device Admin and the permission got reset. The problem is that I never had to set MD as Device Admin to make Screen Off work and now I have to. Even with Screen Off (no lock with root), it didn't work. If you're using Screen Off (no lock with root), then it shouldn't even care about Device Admin. If you then say OH but maybe MacroDroid somehow can't detect root, then no that's not the case either. Other actions that require root work just fine. It's not a loss of permission issue.
b) You can set MD as the default assistant in the systems (or maybe it's global?) table easily. I can easily use MacroDroid to set this and so this is never an issue for me.
