V5.53 - Feedback

[sooraj]

provide releases on git please then

 

[Jacob L]

Sorry I don't even know what this means. Can you show a screenshot of what you are referring to.

 

[nash]

When I test the "Open MacroDroid Log: System Log" action, I can see "Clear log" menu item. But that clears entire system log, not just this macro.
And the "Show log" menu item, when tap, is missing this menu item.

I was expecting to see the ability to erase a macro's log when viewing its log from the edit menu. But I didn't. Or I don't understand where to find it.

 

[Winny57]

Do you have any updates regarding the addition of the feature allowing a system log event to be recorded as a trigger? This would enable creating a macro that records the new system log event into a variable, so that the variable can be processed in actions.

 

[sooraj]

add clear log in menu in macro specific log
not system

 

[LK24]

For clear bugs, please use report a bug in troubleshooting section including the relevant macro (if relevant) with a clear description.

For other issue and discussions (related only to this beta), please leave all feedback here. Please keep discussion focused on this beta release and not general issues with MacroDroid as a whole.

Hi, I wanted to ask if the support of the new Modes of Android 15 is expected instead of the old Do Not Disturb, they would be extremely useful both as a trigger for macros and as actions (activate or deactivate a certain Mode)

 

[Winny57]

add clear log in menu in macro specific log
not system

I can be badly expressed. I had to ask for the addition of a feature to trigger a macro following an event in the system log (macrodroid). This would have made it possible to have notifications or use events in variables to process the data afterwards.

 

[sooraj]

I can be badly expressed. I had to ask for the addition of a feature to trigger a macro following an event in the system log (macrodroid). This would have made it possible to have notifications or use events in variables to process the data afterwards.

Wont that affect performance
every single actions from every single macro are logged to system log
means 100s of events triggered

 

[Winny57]

Wont that affect performance
every single actions from every single macro are logged to system log
means 100s of events triggered

I do not think that affects performance especially that entry into the log is already done from the event so no big impact

 

[sooraj]

I do not think that affects performance especially that entry into the log is already done from the event so no big impact

but its logged in background,
but when triggered continously and actions executed non stop

 

[md_sgf]

When editing scene, and create a new variable, the keyboard should be auto-invoked, like with creating a new variable normally using Set Variable action.

 

[LF0]

I encountered an issue when using dialog mode. When the scene in Macro 1 is not closed, the scene in Macro 2 cannot display properly. Additionally, if the "Block subsequent actions" option is enabled, Macro 2 will enter an infinite running state until the macro is disabled.

 

[sooraj]

I encountered an issue when using dialog mode. When the scene in Macro 1 is not closed, the scene in Macro 2 cannot display properly. Additionally, if the "Block subsequent actions" option is enabled, Macro 2 will enter an infinite running state until the macro is disabled.

already discussed
author says some people require scene to be displayed infiniteky with no means to remove like a layer that cannot be removed
so that behaviour is intentional

 

[timconstan]

When using a custom scene in an action block to update variables in the action block, the variables get saved but only for the duration of the action block's actions. The next time the action block is executed the values revert to their original values.

 

[timconstan]

When using a custom scene in an action block to update variables in the action block, the variables get saved but only for the duration of the action block's actions. The next time the action block is executed the values revert to their original values.

Never mind... I see that's the way action blocks work. I'll try using global variables.

 

[LF0]

Using the hidden scene action does not allow the macro that prevents subsequent actions to continue running; the macro will continue waiting for the scene to close, even though it has already been hidden.