Interval 1 minute fails to trigger at 1 minute, but sometimes not....

[MartinNL123]

Is this a known problem?

Running a get every minute (use alarm set, reference start 00:00), 3 macro's.
Randomly it runs at the expected time for a while, but then triggers at almost random moment, missing 3 or 4 minutes sometimes.
Returns to regular 1 minute triggers sometimes.

Using 5.42, battery management manual, Huawei LYA-L29 (also seen this behavior on other phones)
See attached screenshot from System Log, going from random moments to correct triggers.

 

[Endercraft]

Are you using the 'use alarm' option (located in trigger configuration screen)?

 

[MartinNL123]

Are you using the 'use alarm' option (located in trigger configuration screen)?

Yes, use alarm is set.

 

[Dev777]

Try using a stopwatch instead

 

[MartinNL123]

I've done that earlier but since I am collecting more data from the different devices in the house I would like to have those at the same time.
The stopwatch drifts in time because it adds the time spent on the get, which sometimes takes a few seconds.

I am running this on two phones, on those I had this as well. They are on 5.41 now and so far no problems.
Screenshot is from a third phone with 5.42, used for testing.

 

[Dev777]

You could reset the stopwatch first then action

 

[MartinNL123]

You could reset the stopwatch first then action

That would work, but I rather have 5.42 behave as 5.41 so I don't need to retrofit "bad" code?
5.41 works fine.

 

[MacroDroidDev]

I do not believe there is any reason that 5.42 should behave any differently to 5.41 as I've not changed anything related to this (to the best of my knowledge).

If you can recreate it in 5.42 please use "Report a bug" in the troubleshooting section and I will take a look at the logs to see if I can spot anything.

 

[MartinNL123]

I do not believe there is any reason that 5.42 should behave any differently to 5.41 as I've not changed anything related to this (to the best of my knowledge).

If you can recreate it in 5.42 please use "Report a bug" in the troubleshooting section and I will take a look at the logs to see if I can spot anything.

Done. It is also quite clearly visible in the screenshot in the op.
It is also fun to look at the switch of the day, before 00:00 random triggers, after 00:00 again 1 minute for a few runs, but then suddenly a 5 minute interval when no triggers are executed. This then alternates a bit during the day.
The data that is fetched is saved in a file which has the current datetime stamp, those concurr with the times in the System Log.

 

[MartinNL123]

Oh, I thought the log was sent with the app, attached a zipped version here.

 

[MartinNL123]

And the macro.

 

[MartinNL123]

Small Update.
I've tested some more and now know this is not version related.
And I am able to re-produce the problem on a Huawei Mate 20 Pro phone, Android 12.

Setup the tasks, 15 or so API calls in parallel on the same interval, every minute.
What works: Setup an extra macro which keeps the screen alive, clicking it every 3 minutes.
When the screen is turned off, the interval of 1 minute does not work anymore and becomes random between 1 to 5 or even more minutes.

To be certain the MacroDroid app is configured correctly (manual, and all three options checked) also verified with dontkillmyapp with the same settings. First without and then it reported 29% in a 1 hour test. Then correct, same as MacroDroid, then it reported 100%.
So there seems, according to dontkillmyapp, no problems with the phone.

Which leaves:
- still a problem with the phone (and also another phone which reported the problem first)
- MacroDroid application problem? Why would the interval not be triggered every minute?

For now I keep the screen on, telephone on the charger, and tap the UI every three minutes. So it works.
But I am still curious if it can be prevented....

 

[MacroDroidDev]

I am fairly confident the regular interval trigger does everything it can to wake up the device at the required time, I don't think there is anything I can change with this respect.

I am also aware that Huawei are the number one most hateful device when it comes to breaking the Android OS and I'm glad that these devices have pretty much gone away because a few years ago a large percentage of bug reports where Huawei related issues. This may seem like a cop out but I am working under the assumption that your phone is just not respecting standard Android functionality when it comes to waking up the device.