Contact Us
The fastest way to get a useful answer from us is to send a report we can actually reproduce. “My macro stopped working” gives us nothing to test; the details below turn your message into something we can load onto a bench phone and investigate.
Write to us at contact@apkpad.com for troubleshooting help, corrections to a guide, or questions about an article. We read everything, though replies can take a few days when the bench is busy.
What to Include in a Troubleshooting Report
- Phone model and OEM skin — for example, “Redmi Note 13, HyperOS 2” or “Pixel 8, stock Android.” The skin matters as much as the model: OEM battery policy is the single most common cause of dead macros.
- Android version — found under Settings → About phone. Permission behaviour changed significantly in Android 13, 14, and 15.
- MacroDroid version — shown at the bottom of the app’s home screen or in the drawer menu. Note also whether you run the free version or Pro.
- The trigger and action involved — name them as MacroDroid does (“Geofence Trigger,” “Send SMS action”). If the macro has constraints, list those too; a constraint that never evaluates true looks exactly like a broken trigger.
- The exact failure behaviour — does nothing happen at all, does it fire late, does it fire once and then never again, or does it fire when it should not? Include the time of day it failed, if you know it.
- Whether battery optimization is excluded — check Settings → Apps → MacroDroid → Battery and tell us if it is set to Unrestricted, and whether MacroDroid also appears in your OEM’s own sleeping-apps or autostart lists. This one detail resolves a large share of reports before we even reply.
If your macro involves the MacroDroid Helper app or ADB permissions, mention whether WRITE_SECURE_SETTINGS has been granted and whether the problem began after a reboot — grants and helper connections are frequently lost there.
What We Cannot Help With
We do not provide support for automations aimed at other people’s devices or accounts, bulk or unsolicited messaging, or bypassing another app’s terms of service. For bugs inside MacroDroid itself — crashes with a stack trace, licence problems — the in-app forum and ArloSoft’s support channels will reach the developer faster than we can.