timing is unreliable

The cycles do not take as long as it is set up to, and even with the same setting, the length of the cycles varies from time to time.

My guess is that it is not timed with "real" time, but user or system time or how much cpu time the process itself gets or something.. (I did not have time to look into the code yet).

First, I noticed that if the work cycle was set up for 25 mins, it finished a little bit sooner, so I set it to 26. After that, it usually(!) finished around 25 mins and 20-something seconds. Then I still had the feeling sometimes that it finished very soon, so I ran a timer on my phone, too, and sometimes the ubuntu timer would finish as soon as 12-13 minutes before the phone timer (at the 26min setting).