The trigger already exists and I use it macros to ensure interrupted actions such as stopwatch timers are resumed correctly.
Run macro before all other macros at startup
- Thread starter J70P
- Start date
Snurre
Well-known member
How about this trigger
Intent received
android.intent.action.ACTION_SHUTDOWN
It might work
I think it's common practice in software development or software in general to set default values for variables at startup, read configuration files, or check prerequisites in general. In software development, every object has a constructor for that purpose. No matter whether the program is started by a system restart or by Android. The stopwatches example of Abalsam is an example of why you should do it.
cwallen19803
Member
The macro I posted in my first response....
Snurre
Well-known member
My fault, Missed that
cwallen19803
Member
I think we're talking about two different problems.
How to handle restart and how to handle abnormal end. Abend, we called it...
Restart is easy. We've discussed it here with trapping shutdown and initialize triggers. Multiple ways of doing that. All good
Abnormal end, harder. The app may know the end was abnormal, I don't know. I know that my testing show that macrodroid is all screwed up when I force stop it, but I don't see any trappable triggers when I start it after force stop.
My experience is that an ungraceful app termination yields an ungraceful restart. Sometimes really ugly, like the loss of the next business day while databases are restored
I'm watching this thread for answers.
How to handle restart and how to handle abnormal end. Abend, we called it...
Restart is easy. We've discussed it here with trapping shutdown and initialize triggers. Multiple ways of doing that. All good
Abnormal end, harder. The app may know the end was abnormal, I don't know. I know that my testing show that macrodroid is all screwed up when I force stop it, but I don't see any trappable triggers when I start it after force stop.
My experience is that an ungraceful app termination yields an ungraceful restart. Sometimes really ugly, like the loss of the next business day while databases are restored
I'm watching this thread for answers.
cwallen19803
Member
But you were right on the moneyMy fault, Missed that
You could use the macro below to initiate a boolean variable at shutdown/reboot time. Don't add any other actions because MD won't have time to execute them before effective shutdown.
Then change its value to True at the end of your boot time macro (don't forget to tick Wait untill complete.. boxes whenever needed in the appropriate actions).
At last, add a simple global Constraint to every macro that needs to wait for boot completion (Constraint → global variable BootComplete=True)
Anyway, I'm wondering how/when your other macros fire? Don't forget that if you prevent them from firing at the time the triggering events occur, they won't fire again untill other similar events occur.
N B.: I used a local boolean variable in the example below to show its value but you must use a global one instead for every macro that needs it can acces it.
Attachments
Qarboz
Well-known member
No, your English is not bad (it's not my native language either) but I didn't have all the answers in memory as this thread has many posts (and not all of them are suitable to solve the guy's problem)...
