Why is Android so bad at keeping accurate time?
My Linux machines, my iPhones, and my radio Casios are all perfectly in sync to a fraction of a second.
But my GrapheneOS Pixel is consistently +/- 2 seconds. And my other Androids drift even worse.
1 Like
How is this bad? It is two seconds! I’d love for you to explain to us why this is such a big issue for you…
1 Like
Prior to Android 12 it used a less reliable time provider (NITZ) in most cases, but the current version should prioritize NTP just like iOS and most other devices, so I’m not sure what the discrepancy would be.
I can’t say I’ve noticed this myself, but it’s interesting. I’ll have to check this out on my own Android phone 
Because it is 2025 and having a Internet connected computer clock be within 1/10th of a second is expected.
They’re all Android 15. Stock Android appears to only sync once per boot. I think GrapheneOS is once every few network connections/switches?
https://time.is makes it easy.
1 Like
I am using GOS (Pixel 7) and its only 0.8 ahead. +/- 2 seems like a pretty big deviation. Have you asked on the GOS forum?
My stock Pixel 9 Pro is 0.8s behind 
clock is 2 seconds ahead on my GrapheneOS Pixel 7 but the PC I’m using is exact.
with that being said I agree with @firedragon and @jonah, is it really a huge deal at this point? Even as a seconds kind of guy I’m mot batting an eye over those 2 seconds, when I see them it’s like “Alright minute passed already”.
Maybe it’s because GrapheneOS uses a “secure network time update implementation”. 2 seconds is definitely a pretty big delay though.
TOTP codes can be messed up if your time isn’t synced correctly.
2 Likes
oh well fair enough but for 2 seconds ahead? Come on.
never had a problem with TOTP
Time updates are usually hourly I think? Even if you have very bad luck in the Quartz lottery your on-device clock should not be off by 2 seconds in an hour. Something else has to be wrong and I agree it has to be fixed. On-device time can and should be accurate to less than 1 second.
1 Like