Slow down screen scan rate - optimize battery life

[sabrinucci2]

Is there a way to use timers to scan every 1 second?
Or to scan for 50 ms every 1 second.
The goal is to search for text and if found it makes a sound, but it is enough that it checks every 1-2 seconds (since it will have to stay open all day), so leaving it always active destroys my battery and heats up a lot.
Many Thanks!

[Nain57]

Hi,

You can easily control the execution rate of the ImageEvent list computation (iow, the "scan" rate) by using a Wait action placed strategically. As nothing is parallel in Klick'r processing, waiting for a Wait action will pause the processing until the wait time of this action is complete. You can read this if you want to learn more about the algorithm behaviour and lifecycle.

You want ot achieve this behaviour: 50ms image processing | 1s wait | 50ms image processing | 1s wait ...

The easiest way to achieve your behaviour is by using this simple TriggerEvent in your Scenario:

Condition: Timer Reached
|-- Duration: 1s50ms <- You want to scan for 50ms and wait for 1s, so this condition must be executed every 1s50ms
|-- Restart when reached: True <- Repeat the process

Action: Wait
|-- Duration: 1s <- Wait for 1s and do nothing

Hope this helps !

[sabrinucci2]

Thanks a lot, I tried it, it seems to work, even if through the test function on the image I see it scrolling continuously as if it never stops scanning, now if it works the phone should heat up much less (I set 1020 ms and 1000 of pause, I saw that it still manages to detect the image on the display.

[Nain57]

I think you can ensure a more stable behaviour using 2 Change Event state actions:

• One setting the detection events to false at the end of your detection event.
• One setting the detection events to true every X time, so basically after the wait action of the Trigger Event.

This way, you will both ensure lower scan rate AND ensure the detection is triggered only once.

[hatbrox]

I have a lot of scenarios where I klick'r push a button from time to time. Because I know the button (an ad to claim a reward in the game) is active every 5 minutes, I just put a wait step of 4:30.
In general I almost put 1-5s wait steps after all click actions, at least to give the target application (like the video game) enough time to refresh the screen.
When I no longer need the scenario, trigger scenarios is my preferred way to deactivate a scenario.

[vibhor1102]

The exact implementation you wanted has been added through v4.0.0 now. Currently in beta, but the Execution Limiter feature will suit you well.