Re: [time-nuts] "Selective availability" af accurate time for Apple users?

On Tue, Oct 20, 2015 at 3:09 PM, Paul wrote: > Network connected iOS devices not paired with a watch use (s)ntp at large > intervals rather than the mobile network or GPS. > I expect iOS 9 still has the post-iOS 4 behavior of doing an (s)NTP poll to time.apple.com at

Re: [time-nuts] "Selective availability" af accurate time for Apple users?

I think it has to do more with battery life as the first release of iOS 9 drained battery faster than prior releases and the GPS is expensive from a power standpoint. I think the non watch devices sacrificed precision time for runtime Content by Scott Typos by Siri > On Oct 20, 2015, at

Re: [time-nuts] "Selective availability" af accurate time for Apple users?

garrettbrian1...@gmail.com said: > Has anybody else observed this with their iPhone since “upgrading” to iOS > 9? > Anyone know of any difference in the reference time ( e.g. GPS vs. network > time) that Apple is using to “dumb down’ their smartphones in favor of > Apple > Watch? Is

Re: [time-nuts] "Selective availability" af accurate time for Apple users?

On Tue, Oct 20, 2015 at 4:02 AM, Brian Garrett wrote: > ... As measured by NTP apps such as Emerald Time and Watchville, millisecond accuracy comparable to the soon-to-be-released Apple Watch was now commonplace, with typical offsets of 5 ms or less, rather than the

[time-nuts] "Selective availability" af accurate time for Apple users?

Last spring (late March/early April) it was noted on this list that iPhone clock accuracy had improved significantly with the release of iOS 8.2. As measured by NTP apps such as Emerald Time and Watchville, millisecond accuracy comparable to the soon-to-be-released Apple Watch was now