Search results

It is so that macros can be constrained depending on whether they have run since Macrodroid last started. If the counter is incremented after a macro is enabled then that macro may be triggered without being properly constrained (because the counter has the wrong value). Thus the counter needs...

That is NOT {Macrodroid Start Time}. On this device {system_time}-{uptime_secs} is a moment approximately 6 days and 7 hours ago wheras {Macrodroid Start Time} is approximately 22 hours ago. Quite a bit different. {Macrodroid Start Count} is not a time. It is merely a count of how many times...

I have already considered doing things the way you suggested. In my system log, the first macro enabled is not the first macro I created and the last macro I created is enabled somewhere in the middle. The order can, most definitely, change. I would rather not depend on something that is...

Which macro will always be enabled first?

No. I am talking about the time at which Macrodroid starts. Both Device Boot and Macrodroid Initialised fire after the macro enabling stage. Incrementing a global variable on those triggers is too late.

A magic integer that is incremented each time Macrodroid starts (it should be incremented before the macro enabling stage). It might also be nice to have {Macrodroid Start Time}.

Excellent! Now, why did I not think of that? :/

Macro Enabled is not quite right for my needs since it also fires when the macro is edited. It is good enough for now. A specialised trigger will be much better.

I'll check it out. I did not think to try it because the last time I used it it caused serious problems.

Can we, please, have a trigger that is gauranteed to be the first trigger to fire after Macrodroid starts? I ask because I have some initialisation stuff that needs to be done before anything else. I suggest that the first trigger be Macrodroid Initialised. At present other triggers may fire...

Try turning notification access off and then on again. Doing so fixes notification access issues on my device.

That is because the NFC adapter actually has 4 states: ON changing from ON to OFF OFF changing from OFF to ON That is why I suggested checking the state using the constraint and setting a variable and using the variable changes as triggers elsewhere.

For NFC on/off... Listen for intent: android.nfc.action.ADAPTER_STATE_CHANGED Use constraint: NFC State (Enabled/disabled) to check NFC status and set a variable to true or false accordingly. Elsewhere, you can use changes in your variable as a trigger.

Thanks mate.

Thanks Jacob. Not going to root my devices and doing ADB hacks on one of my devices is anoyingly difficult (no PC and device is too old for wireless and I don't have appropriate cabling for device-to-device method :( )

Please add some means of getting the version number of Macrodroid. A magic text item would be nice. Thankyou.

I am seeing the same thing on an Android 11 device and an Android 12 device.

Thanks but requires root or adb hack. Not useful to me.

Can we please have magic text for the current version number? Thankyou.

Irrelevant. If I add a wait action of 5 or more seconds and enable use-alarm then the icon appears when the action is executed and persists until the wait period has elapsed. This happens on my Pixel 4XL. It does not happen on my Galaxy Tab S5e. If I recall correctly, it was happening on my...