After update 5.21.3 MD ask permission for overlay

Nolan

Member
Hi
The app keep asking for this, but only after the latest update, before this, it was not needed. This is a problem because if I allow that, Google authentication don't work, it disabled orders for security reasons.
I am not aware of any of my macros not working if I don't allow overlay

Any solution and why she's MD out of the blue require this ?

Using Android 12

Best
Nolan
 

Jacob L

Moderator (Lawsonator)
What you can do is disable the permission and then head to the troubleshooting section and it will tell you which macros it wants the permissions for
 

Nolan

Member
What you can do is disable the permission and then head to the troubleshooting section and it will tell you which macros it wants the permissions for
Thanks, it was turn screen on when I receive a notification. But why is that needed? It was not needed before the update.

If that is by design there is an app aodNotify that can turn the screen on when receiving a notification, but that does not require overlay.

I would prefer to do that via MD instead of having to install new apps.

Is this possible to solve?

Thanks
Nolan
 

Jacob L

Moderator (Lawsonator)
I was under the impression it just needed accessibility services. Every android device is different so maybe it is needed. I've seen implementations that don't even need accessibility services. This is one for @MacroDroidDev to answer
 

Nolan

Member
But the strange thing here is that it worked before the said update, without the need to enable overlay. I hope this can be revoked again
 

Pseudocyclic

Well-known member
I don't know if this is the case here, but sometimes updates (which negatively impact MacroDroid) have to be made because of updates to Android. Another possibility is that something wasn't working well on a significant number of devices and changes are made to improve the situation.
 

MacroDroidDev

Administrator
Staff member
The overlay should only be required if you are using the screen on alternative option. This works by creating a temporary foreground activity which is used to cause the screen to turn on. This permission is required on Android 10+ to do this. If it was working for you previously then it may be because you have device admin access enabled for MacroDroid which also lets this happen.

I'm surprised to hear you say Google authentication doesn't work just because you have granted that permission. As I understand it, it will not work if you have an active overlay (for example you are using the dim screen action or have a floating button visible) but if you have no active overlay it should not interfere.

Strictly speaking I could mark this permission as not needed if device admin is already enabled I guess, but this would apply in many places and I don't have the bandwidth to look at all this right now.
 
Top