Strictly necessary cookies are on by default and cannot be turned off. Functional, Performance and Tracking/targeting/sharing cookies can be turned on below based on your preferences (this banner will remain available for you to accept cookies). You may change your cookie settings by deleting cookies from your browser. Then this banner will appear again. You can learn more details about cookies HERE.
Strictly necessary (always on)
Functional, Performance and Tracking/targeting/sharing (default off)
I've found that the callback will be fired only at certain specific points of the timeline (kind of when Clock%40==0) regardless of the time when I start timer.
As a result, when I start timer, I might have to wait just 1 time unit or it can be as long as 40 time units to reach the point the system can fire a timeout callback.
With this design, there is no way to make it consistent.
What I am doing is to synchronize multiple Bluetooth devices by broadcasting non-connectable advertisement (only 1 packet) to those devices. When they receive (I assume they will receive at the same time), they can use that point of time to start timer simultaneously. Therefore, they could reach each fine timeout callback at the same time.
However, that method doesn't work anymore.
but it might works if I can completely reset the clock. Is it possible?