dhj49er
Well-known member
I like to have different screen timeouts for different modes and include a the scree Timeout action with values when the mode changes.
Unfortunately the screen Timeout doesn't change.
I have tried using the system setting with and without using helper, whilst the setting value changes, the actual timeout doesn't change.
I have tried invoking the macro with and without the screen on, it doesn't change the actual screen Timeout.
I am running these macros on an Oppo Find X3 Neo and thought it probably is the Oppo software preventing the change.
However, if I open the macro and run test action, the timeout changes. So I'm not sure it's the Oppo software.
So what is the difference between running the macro from a trigger (which never works) and manually running test action (which always works).
I've checked the system log and it correctly shows the actions executed without error in all the above cases.
Also I have used a simple test macro, that uses date time trigger (with alarm enabled) to one action to set a screen Timeout value, with no constraints.
I have tried running this macro with the screen off, screen on and screen on Macrodroid running with the macro displayed. Trying to see if Macrodroid in the background and foreground influenced the outcome. Unfortunately it didn't.
So I don't know why the action isn't working from a triggered macro.
Unfortunately the screen Timeout doesn't change.
I have tried using the system setting with and without using helper, whilst the setting value changes, the actual timeout doesn't change.
I have tried invoking the macro with and without the screen on, it doesn't change the actual screen Timeout.
I am running these macros on an Oppo Find X3 Neo and thought it probably is the Oppo software preventing the change.
However, if I open the macro and run test action, the timeout changes. So I'm not sure it's the Oppo software.
So what is the difference between running the macro from a trigger (which never works) and manually running test action (which always works).
I've checked the system log and it correctly shows the actions executed without error in all the above cases.
Also I have used a simple test macro, that uses date time trigger (with alarm enabled) to one action to set a screen Timeout value, with no constraints.
I have tried running this macro with the screen off, screen on and screen on Macrodroid running with the macro displayed. Trying to see if Macrodroid in the background and foreground influenced the outcome. Unfortunately it didn't.
So I don't know why the action isn't working from a triggered macro.