You are reading a single comment by @Gordon and its replies.
Click here to read the full conversation.
-
That's a neat idea putting it in the App Loader, it'd just require writing a file after we set the time. The only issue is that watch reboots between App Loader runs would knock out the timings, and so if it was automatic it's possible it could end up configuring the PPM difference wrong.
I thought about that. Maybe a sanity check could be performed that makes sure the watch's reported time isn't too far off from actual time, and if it is, the recalculation of the drift could be skipped for that occasion (perhaps with a warning message printed on the console, if desired). Or else have a way to just let the user manually request when the drift should be calculated and the time be adjusted, perhaps.
tev
@Gordon
That's a neat idea putting it in the App Loader, it'd just require writing a file after we set the time. The only issue is that watch reboots between App Loader runs would knock out the timings, and so if it was automatic it's possible it could end up configuring the PPM difference wrong.
Thinking about how the timekeeping broke in 2v22 made me realise it wouldn't be the end of the world to actually add an optional adjustment inside the Bangle.js firmware (in the
jshGetSystemTimefunction) so I guess that could be an option to make it even more seamless...