[Last5Digits]

I only have access to Android devices, so my claim likely won't extend to Apple. In fact, I've been told by a friend that Apple watches do in fact use the GPS signal to sync the clock. But as far as I know, they are the only ones doing that.

[mikequinlan]

A brief google search find this information on maintaining time accuracy on Windows. https://learn.microsoft.com/en-us/troubleshoot/windows-serve...

In general though, you need to look in more detail at what your exact configuration is and find out what you have misconfigured.

[Last5Digits]

I never made the claim that there were no solutions to the problems outlined above. In fact, I implemented exactly what you've linked long ago. This doesn't, of course, change the fact that no such easy procedure exists on unrooted Android devices and that Windows, by default, has inaccurate timekeeping. Requiring extensive configuration for something as simple as accurate time is what irks me. Time sync is neither expensive nor complicated, so why is Windows so reluctant to do it often enough to keep the time?

Having to set registry values to get sane syncing behavior is just nuts when, again, my cheap Casio watch - which possesses a miniscule fraction of the features of a modern computing device - can deliver sub 500ms accuracy with absolutely zero fuss.