I've been using pool.ntp.org for syncing time on my Android devices, but I've noticed that after a few days, my clocks fall behind by 2-3 seconds. Is this a common issue? Should I be waiting longer for the clocks to sync, or is my obsession with being precise just causing unnecessary stress? I know a delay of about a second is generally acceptable, but I'm considering looking for alternative time sources, maybe even ones that sync with atomic time signals. Additionally, I plan on redirecting pool.ntp.org to time.nist.gov in the future—would that help?
3 Answers
It's not likely that pool.ntp.org itself is slow. Actually, many Android devices default to using Google's time servers at time.android.com, which might be the cause of your issue. Just for reference, my Samsung phone uses "0.pool.ntp.org" as its NTP server. You might want to check which server your device is actually syncing with to see if that's the culprit.
You could be experiencing a syncing problem with your Lenovo Smart Clock 2s. It happens sometimes that devices don’t sync properly over time. It might be worth playing around with the network settings or resetting the clocks to see if they improve sync performance.
I encountered a cert issue with Chrome when I tried to access pool.ntp.org. But keep in mind, the site itself doesn’t offer a secure connection for HTTP, since it's used primarily for NTP. You usually won't have issues using it for time syncing. Although, if you're looking for more reliable time updates, maybe explore NTP providers that do offer TLS.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures