# Pixel 5a clock off by 2 sec fix

**URL:** <https://www.twit.community/t/pixel-5a-clock-off-by-2-sec-fix/15285>\
**Category:** Android\
**Created:** [September 20, 2023, 1:13am UTC](https://www.twit.community/t/pixel-5a-clock-off-by-2-sec-fix/15285 "2023-09-20T01:13:17Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![nickapos](https://sea2.discourse-cdn.com/flex020/user_avatar/www.twit.community/nickapos/32/4074_2.png) [@nickapos](https://www.twit.community/u/nickapos)\
**Post date:** [September 20, 2023, 1:13am UTC](https://www.twit.community/t/pixel-5a-clock-off-by-2-sec-fix/15285/1 "2023-09-20T01:13:17Z")

</div>

Hey everyone I have a Pixel 5a and it seems that its clock is off by 2 sec.  
I tried disabling and re enabling automatic time updates but did not make any difference.  
Has anyone seen this before?

---

<div class="post-metadata">

**Author:** ![nickapos](https://sea2.discourse-cdn.com/flex020/user_avatar/www.twit.community/nickapos/32/4074_2.png) [@nickapos](https://www.twit.community/u/nickapos)\
**Post date:** [September 20, 2023, 1:20am UTC](https://www.twit.community/t/pixel-5a-clock-off-by-2-sec-fix/15285/2 "2023-09-20T01:20:40Z")

</div>

Oh it seems a reboot fixed the issue.

---

<div class="post-metadata">

**Author:** ![LycheeMcPie](https://sea2.discourse-cdn.com/flex020/user_avatar/www.twit.community/lycheemcpie/32/2140_2.png) [@LycheeMcPie](https://www.twit.community/u/LycheeMcPie)\
**Post date:** [September 21, 2023, 6:41pm UTC](https://www.twit.community/t/pixel-5a-clock-off-by-2-sec-fix/15285/3 "2023-09-21T18:41:22Z")

</div>

Curious as to what use you have for your phone to need such time accuracy?

---

<div class="post-metadata">

**Author:** ![nickapos](https://sea2.discourse-cdn.com/flex020/user_avatar/www.twit.community/nickapos/32/4074_2.png) [@nickapos](https://www.twit.community/u/nickapos)\
**Post date:** [September 21, 2023, 7:01pm UTC](https://www.twit.community/t/pixel-5a-clock-off-by-2-sec-fix/15285/4 "2023-09-21T19:01:44Z")

</div>

It’s something I discovered a while back, that sometimes phones or computers are not accurate.  
It has happened with another Android a while back, and with a MacBook Pro 2015.  
In that second case the clock was off by several minutes and caused me a lot of grief with meeting scheduling.

Since then I have been using radio controlled watches, as reference.  
Apart from those radio controlled watches I also have Bluetooth ones and one of them is using this particular phone for its sync.  
The interesting thing is that the watch is accurate even when the phone was not. Which means that the app used for the sync has a separate ntp server it’s using.

---

<div class="post-metadata">

**Author:** ![big\_D](https://sea2.discourse-cdn.com/flex020/user_avatar/www.twit.community/big_d/32/1023_2.png) [@big\_D](https://www.twit.community/u/big_D)\
**Post date:** [September 22, 2023, 4:10am UTC](https://www.twit.community/t/pixel-5a-clock-off-by-2-sec-fix/15285/5 "2023-09-22T04:10:35Z")

</div>

Windows has been using the time in SSL header packets to set the clock, which has caused fun, as there is no requirement for the time field to be filled at all, and it is often filled with junk, people have ended up with their computer clocks being off by over a century!

---

<div class="post-metadata">

**Author:** ![nickapos](https://sea2.discourse-cdn.com/flex020/user_avatar/www.twit.community/nickapos/32/4074_2.png) [@nickapos](https://www.twit.community/u/nickapos)\
**Post date:** [September 22, 2023, 4:31am UTC](https://www.twit.community/t/pixel-5a-clock-off-by-2-sec-fix/15285/6 "2023-09-22T04:31:19Z")

</div>

Wow, I didn’t know this. I knew that computers are using the ac frequency as a poor man’s oscillator and used an external ntp source for periodic calibration, which is bad enough but depending on ssl headers for this?  
That is really daft.  
In any case the issues I noticed in the past were bugs and there was no way to solve them so since then i have been using atomic watches as reference. You can also use [http://time.is](http://time.is) to check clock deviation in a more visual manner

---

<div class="post-metadata">

**Author:** ![big\_D](https://sea2.discourse-cdn.com/flex020/user_avatar/www.twit.community/big_d/32/1023_2.png) [@big\_D](https://www.twit.community/u/big_D)\
**Post date:** [September 22, 2023, 6:48am UTC](https://www.twit.community/t/pixel-5a-clock-off-by-2-sec-fix/15285/7 "2023-09-22T06:48:34Z")

</div>

My Apple Watch was within a fraction of a second of time.is.

---

<div class="post-metadata">

**Author:** ![nickapos](https://sea2.discourse-cdn.com/flex020/user_avatar/www.twit.community/nickapos/32/4074_2.png) [@nickapos](https://www.twit.community/u/nickapos)\
**Post date:** [September 22, 2023, 7:13am UTC](https://www.twit.community/t/pixel-5a-clock-off-by-2-sec-fix/15285/8 "2023-09-22T07:13:29Z")

</div>

Yeah, same here my android is now exact after a reboot too. My ipad was also exact for a few days but since yesterday it has deviated by 0.2 sec.  
Obviously 0.2 sec deviation is not important but it is quite interesting.
