iPad clock about 2 minutes fast

[BrettDS]

This has been driving me nuts for a couple of weeks now. I believe it started during one of the later iOS 9 betas, but I'm not sure which one. For some reason the clock on my iPad is about one minute and 47 seconds faster than the clock on my iPhone and laptop and pretty much everything else in the world that's synced to the atomic clock.

Both my iPhone and iPad are set to obtain the time automatically. On the iPad I've tried turning off the option to automatically sync the time and manually setting it correctly, but as soon as I turn auto sync back on it jumps forward by 1:47. I've tried restarting the iPad, turning auto sync off, then restarting, then turning it back on, and I even tried 'erase all settings' all to no avail.

Has anyone else seen this? Any ideas to get the clock back in sync?

 

[tokyotony]

Yep, I am having the same issue on my iPad mini.

 

[kmichalec]

Same issue here too. iPhone is running iOS 9.1 public beta 1. iPad mini is running iOS 9.0 public beta 5. iPad is 2 mins faster than iPhone.

 

[batting1000]

I have a bug on my iPhone where my clock goes back an hour and whenever I go to the Settings to fix it, it's on "Gmt +5" and I have to manually switch to an Eastern timezone location.

 

[sbailey4]

Had same issue on iOS 9 betas on iPhone 6. iOS 9.1 seems to resolve it.

 

[tokyotony]

I'm using iOS 9.1 beta - iPad Mini is experiencing 2 minutes fast.

 

[BrettDS]

Had same issue on iOS 9 betas on iPhone 6. iOS 9.1 seems to resolve it.

Unfortunately it didn't for me. My phone and iPad are both on 9.1

 

[C DM]

Had same issue on iOS 9 betas on iPhone 6. iOS 9.1 seems to resolve it.

Same here. Although I did have to reset all settings shortly after installing 9.1 beta, so maybe that contributed to it getting resolved.

 

[zorinlynx]

Yeah.. this is my iPhone 6 on iOS 9.0 GM running Emerald Clock, which shows the difference between device time and actual precise NTP time.

63 seconds. That's over a WHOLE MINUTE off! What the hell, Apple? In iOS 8 it was within 1-2 milliseconds. Someone really screwed up on this.

 

[tokyotony]

Yep, here's mine on my iPad Mini....

 

[Yun0]

i assumed it was my carrier's towers so i just turned off auto time & rolled it back 2 minutes, yet when i enable auto time again it jumps back 2 mins ahead..

 

[BrettDS]

Well, the good news is that I fixed this. The bad news is that I fixed it by erasing all content and settings and restoring from my iCloud backup. Just resetting all settings did not fix the problem.

 

[jetsam]

I first noticed this on my iPhone 6 Plus in PB2. It was not fixed in PB3 or 9.0 GM. By the time I switched to manual time setting, my iPhone was running five minutes fast. This is not just annoying - it screws up Google Authenticator, which allows a time error of no more than 60 seconds.

It was fixed in 9.1 beta. Here's Emerald Time now, after updating to 9.1 PB1 last week (and switching back to automatic time setting):

 

[sbailey4]

Same here. Although I did have to reset all settings shortly after installing 9.1 beta, so maybe that contributed to it getting resolved.

Hmm same here. I did a reset all settings myself since its been a while since I did. That also fixed an issue I was having with the latest version of Flickr crashing (4.0.5) Version 4.0.4 worked fine without resetting. Anyway point being the reset all may have very well fixed the time issue. Not sure I noticed it being fixed after 9.1 and before the reset so not sure which one fixed it.

 

[nightmare28]

I had the same issue on iOS 9.0 public beta, not for the normal beta (dev-account). After installing of the iOS 9 GM it still was not gone. Solution was... completely restore public beta device with the gm oder other full release and restore the backup from iTunes.... now everything is fine... but today the app store is really slow... after restore all apps had been installed over the air not via iTunes... so it take a lot of time :-(

 

[Broken Hope]

My iPad was out by over 100 seconds and my iPhone was a little out, doing a full erase and restore of my backup sorted the issue on both devices.

 

[PowerBook-G5]

Same here, iPad Air 2, iOS 9.1

My iPhone 5C on iOS 9.1 is fine though.

 

[zorinlynx]

I think iOS 9.0 is using the time provided by the carrier rather than NTP to set the clock.

I turned off cellular data on my iPad and toggled "set automatically" for the time. Suddenly the clock was EXACTLY right, at 0.000 offset from NTP clock as reported by Emerald Time.

I think Apple shouldn't be using carrier time at all, and should be using NTP all the time. It's far more precise.

 

[tokyotony]

I don't have a cellular connection on my iPad. It works through wifi only and I have this issue.

 

[BrettDS]

Yeah, mine is wifi only, although it's still fixed after wiping and restoring the backup

 

[tokyotony]

Yeah, mine is wifi only, although it's still fixed after wiping and restoring the backup

So, I am guessing by backup, you mean I would have to restore from an older backup? Or, are you saying I back up my iPad and then restore from that backup?

 

[BrettDS]

So, I am guessing by backup, you mean I would have to restore from an older backup? Or, are you saying I back up my iPad and then restore from that backup?

That's all I did. I updated my iCloud backup, erased all contents and settings, then restored the backup I just took.

 

[jetsam]

I think Apple shouldn't be using carrier time at all, and should be using NTP all the time. It's far more precise.

Carrier time is more accurate than NTP, not less. Carrier time must be accurate to within a few microseconds; to get there, they use GPS clocks accurate to about 100 nanoseconds. NTP can only do better than 10 milliseconds with special equipment. In fact, the NTP support site recommends using carrier time as an NTP reference clock:
http://support.ntp.org/bin/view/Support/ChoosingReferenceClocks

I believe the problem was that the iOS 9 betas (and GM) stopped retrieving the time. Doesn't matter how accurate your source is if you don't use it!

I think it was very clever of you to figure out that you could force a time update via NTP. Was your iPad able to maintain its accuracy, or was it a one time update, followed by renewed drift?

 

[LordQ]

Clockgate?

 

[solodogg]

9.1 beta 1 on my air 2...63 seconds fast.