V5.31 - Feedback

[MacroDroidDev]

For clear bugs, please use report a bug in troubleshooting section with a clear description.

For other issue and discussions, please leave all feedback here.

 

[Endercraft]

5 minutes after installing, my action block is complete !
It opens the executing macro's own system log.

 

[ClayBenson]

V5.31.5 fixed my issue with notifications not persisting input values. Thanks for the fix!

 

[Dimlos]

The Disable MacroDroid action is not working.
Toast and Toggle will work, but the macro loop will not stop.

 

[Snurre]

The Disable MacroDroid action is not working.
Toast and Toggle will work, but the macro loop will not stop.

I don't know if I'm right, but you are starting a loop that never stops, the var is always true
And I think you disable further MD actions but not the one that's running continuesly
Correct me if I'm wrong

 

[Dimlos]

I have made it a loop for clarity, but the macro does not stop when I turn off the toggle in the app.
Is this normal behavior?

 

[Dimlos]

Is it correct that the test action works even with the macro disabled, even with the toggle off, so it is not possible to stop the macro as an emergency stop?

 

[Endercraft]

The Disable MacroDroid action is not working.
Toast and Toggle will work, but the macro loop will not stop.

I know that bug, I reported it 2 times long ago already. It is caused both by loops and wait actions. But didn't @MacroDroidDev fix this ?
It seems to still be causing problems...

 

[Dimlos]

If it is a bug, I would like to see it fixed, and if it is a specification, I thought there should be a way to emergency stop all macros.

 

[Endercraft]

If it is a bug, I would like to see it fixed, and if it is a specification, I thought there should be a way to emergency stop all macros.

Force killing the app is the way to go. Except if you have a macro that always runs that lets you crash MacroDroid.
I have a macro like that, where using an exploit in MacroDroid I can keep a macro active (but triggers cannot trigger so workarounds must be used). If you need this macro, please let me know and I will share it with you because I do not see why you would use it in ay malicious way. I will not attach it here available to public of course because that would be very dangerous..

 

[Dimlos]

I think it is possible by force-quitting the app with the ADB command, but I am not that deeply worried about it.
I have filed a bug report and will wait for @MacroDroidDev's response.

 

[JA-Translator]

I don't know if I'm right, but you are starting a loop that never stops, the var is always true
And I think you disable further MD actions but not the one that's running continuesly
Correct me if I'm wrong

I am not sure, but I think so, too.
It's the same logic as "cancel a macro" action.

I heard from the developer:
Once an action starts running, while the action (not the whole macro itself) is still running, you can't stop the Action itself.
You have to wait until the end of the action.

For example, once "Speak text" action starts, you can't stop the "speaking" voice until its action is finished.
Any other actions will be stopped with "Cancel Action/Macro".

I wonder if it's the same as your case.

If I am wrong, give me the correction.

 

[Snurre]

Once an action starts running, while the action (not the whole macro itself) is still running, you can't stop the Action itself.

Exactly what I mean

 

[LpmitBenjamin]

5.31.7

- Missing translation in user blocking system language is set to German, but text is in Polish
- I haven't found anything to see who is blocked / to unblock that person
- many timeouts when reading the screen

 

[Endercraft]

- many timeouts when reading the screen

If your screen has too many elements, it is likely this will time out.

 

[Dimlos]

The loop stopped with v5.32.0.
Thanks for the fix.