• by toast0 on 3/7/2024, 9:02:21 PM

    Quartz oscillators are sensitive to temperature. Modern computing involves varying power frequently, and therefore heat and temperature, so the real time clock varies a lot; even if we assume it sometimes gets calibrated / disciplined.

    I think most phones sync to the cellular network time, when available. GPS would allow for an alternate time source, but it's not always enabled and maybe nobody thought to feed it into the time source while the network isn't available.

    On Windows, I think the default settings for time sync are amazingly low; probably Microsoft didn't want to foot the bill, as they do run the servers windows syncs from, it's a large population, so increasing the sync volume would probably be meaningful. Microsoft also used to run a time server in Washington state somewhere with really bad asymmetric delay, leading to pretty poor sync performance. But it looks ok now.

  • by Leftium on 3/8/2024, 11:24:12 PM

    I experience time drift with devices not connected to NTP like cheap stopwatch/microwave clock/etc, but my all my devices connected to NTP stay synced on their own.

    For example:

    - Windows time settings says: "Last successful time synchronization: 3/7/2024..." (This was ~41 hours ago and not manually triggered.)

    - https://time.is/: "Your clock is 0.4 seconds ahead."

    I'm a little surprised there is a 0.4 second difference, but it doesn't seem to affect syncing via Dropbox/Google files.

    Perhaps the answer is that time that is accurate to within a second or so of precision is good enough for most consumers.

  • by DamonHD on 3/7/2024, 1:51:16 PM

    Have you explicitly told your phone etc to ignore sync or to use network time? My consumer stuff all works fine (Android and macOS), so I don't that think your sweeping claim in the headline is true. You may have simply gave a few troublesome devices with bugs or inappropriate settings/overrides.

    (Yes, I care - I have run NTP servers including some of the first in banking - since long before it was fashionable, and some of my code is probably still in ntpd.)

  • by giantg2 on 3/7/2024, 3:53:56 PM

    This sounds more like a syncing strategy issue. Maybe you just need to schedule delays into the sync. Or more likely, stop peer syncing. Instead of syncing from A to B then B to server, sync A to sever then server to B. A master sync strategy that uses the time on master is probably better then peer syncing strategies if you're having issues with time keeping between systems.

  • by mikequinlan on 3/7/2024, 2:06:25 PM

    This doesn't agree with my experience. If the time were consistently off by multiple seconds then the sweep second hand on my apple watch would stutter whenever the time was re-synchronized, but it does not.

  • by bell-cot on 3/7/2024, 2:15:01 PM

    Big picture - decades of cheaper-is-always-better design and BoM optimizations, and the perception that nobody cares about second-scale accuracy.