The new UI click trigger seems to be influenced by the screen reader refresh rate.

[LF0]

When only the UI click trigger is enabled, with a screen reader update frequency set to 5 seconds, the background CPU activity for MacroDroid is only around 0.4%..when set to 0.1 seconds, the CPU activity at least doubles, reaching around 1.0%.

I created a test macro before going to sleep, utilizing the UI click trigger and Empty Action. I set the screen reader update frequency to 0.1 seconds. When I woke up, my phone recorded a background power consumption of 210mAh for this macro, making it the most power-consuming background app on my phone currently.

So, if you use screen content or UI click triggers, make sure to enable macros only when necessary.

(Has anyone tested the power consumption of the screen reading trigger?)

 

[Endercraft]

I'm not sure how this trigger works but I assume it notices when you click on something specific.. Yeah I really have no idea.

I just tested it and triggers are instantaneous without using the screen reading function. So your battery drain is most likely caused by the update rate and not the trigger itself (I have it on 2 seconds at time of test).

 

[LF0]

I'm not sure how this trigger works but I assume it notices when you click on something specific.. Yeah I really have no idea.

I just tested it and triggers are instantaneous without using the screen reading function. So your battery drain is most likely caused by the update rate and not the trigger itself (I have it on 2 seconds at time of test).

But I did not turn on the screen content trigger. I only tried to change the reading screen update frequency when the UI trigger was turned on. I cannot explain why the background CPU activity of macrodroid changes. I think the UI click trigger will also read the screen content. Determine the keys on the screen?

 

[LF0]

I'm not sure how this trigger works but I assume it notices when you click on something specific.. Yeah I really have no idea.

I just tested it and triggers are instantaneous without using the screen reading function. So your battery drain is most likely caused by the update rate and not the trigger itself (I have it on 2 seconds at time of test).

What can be confirmed is that the UI click trigger does indeed undergo continuous monitoring in the background. When I activate it, MacroDroid's background activity increases, and deactivating it results in a decrease. This behavior is similar to the screen content trigger, which continuously reads the screen after activation. I have conducted repeated tests on this.