3 ms·
I recently turned on a first gen iPad mini that had been off for maybe a year and its battery had run down. I unlocked it but got repeated prompts to sign into
by js2 8y ago
I recently turned on a first gen iPad mini that had been off for maybe a year and its battery had run down. I unlocked it but got repeated prompts to sign into iCloud with an error when I attempted to do so.
I finally thought to check the time and it was set to 2017. Apparently if its too far from the current date, automatic time setting does not work. I had to manually set it to the current date/time, wait a minute or two, then I could toggle on automatic time setting.
It’s been a while but I seem to recall ntpd behaving the same way on Unix/Linux and having to manually use ntpdate if the system clock is too far off.
- hug 8y ago1000 seconds, I believe, is the max that ntpd will correct without manual intervention. It also usually corrects by slewing time, so that the time correction doesn’t upset timers so much. I believe it can take several weeks to correct for a large offset. That information is true for most linuxes, and may not have any direct bearing on iOS.