"Macrodroid isn't responding"

[Janek Ebert]

Hi,
a few time per day MacroDroid stops working and there is an information, that "Macrodroid isn't responding".
It doesn't cause any other problems, it's just annoying.

I was trying a few things: uninstall the app, restart the phone, update the app, grant permissions again, etc. Nothing helped, so maybe you have any idea what to do?

Phone: Samsung Galaxy S21+5G.
Android 12.

 

[Jacob L]

What does MacroDroid's system log say? We need to be able to identify a specific macro. We may be able to rewrite your macros to be more efficient so they don't cause crashes

 

[Janek Ebert]

Here is the screenshot of system log. The crash happened exactly at 10.00 a clock. I don't think a macro could cause the problem, the crashes are too random.

 

[Jacob L]

Two things I can suggest. Fingerprint isn't compatible with your device it seems so the accessibility service doesn't need to be on for it. You'll need to evaluate macros that have fingerprint gesture triggers and change them.

Also what may help is to take out the hyphens (-) out of the phone number. Besides this it may help you to press in system log where it says standard, to set it to detailed or errors as it will show more.

 

[Janek Ebert]

Ok, thanks. I will try it.

 

[Janek Ebert]

Unfortunately it didn't help. The error happened again and there wasn't any trigger before. It kind of looks like the macrodroid process is kiling by system for some reason.

Sorry for the polish words in system log, I think the most important things are in English.

 

[Jacob L]

Fingerprint is still getting added by accessibility services. So by turning it off may help: settings>accessibility>fingerprint MacroDroid. Also it may help to set MacroDroid as device administrator. Settings>security>device administrators.

 

[Jacob L]

One way to find the actual crash is to disable all macros and enable them 1 by 1 and see which caused the crash

 

[MacroDroidDev]

The most likely culprit for these kind of freezes would be the read screen contents trigger and UI Interaction actions. Accessibility service functionality can sometimes cause these kind of hangs where the system seems to get stuck.

 

[sming]

One way to find the actual crash is to disable all macros and enable them 1 by 1 and see which caused the crash

I’m 30 years in the tech business and it saddens me that this is the way to go still in 2024 lol.

May I suggest perhaps one obvious enhancement to this approach? Basically do this :

1. Disable the first half of all your macros
2. test to see if crash happens.
   1. If it does, enable the first half of the disabled macros and disable the 3rd quarter of all macros
   2. If it doesn’t, it means the problem macro is in the second half so
      1. enable the first half and
      2. disable the 3rd quarter of all macros
3. test to see if crash happens.
4. … repeat 1-4 until you’ve identified the culprit !
   

I hope that makes sense? It’s a form (for which I cannot find a name!) of binary space partitioning but I just cannot find a reference to it ¯\_(ツ)_/¯

Also bear in mind that it might be 2 or more macros in combination that are causing the problem. If this is the case then… you’re in trouble - nah, it basically makes your analysis much harder is all.

HTH,
Pete

 

[MacroDroidDev]

I'm not quite sure why this 2 year old thread is resurrected but the best way initially is to use "Report a Bug" in the troubleshooting section as this will send me an anonymous device identifier that I can then use to try and fix the issue in my crash logs.