1970... What's the list of affected devices?

[adam9c1]

Looking for a solid list of iOS devices affected by January 1st 1970 bug.

Is this correct / complete?
Also not really sure where to stick it to.


iPhone 5S
iPhone 6
iPhone 6 Plus
iPhone 6S
iPhone 6S Plus
iPod Touch 5th Generation
iPod Touch 6th Generation
iPad Air
iPad Air2
iPad Mini2
iPad Mini3
iPad Mini4
iPad Pro

 

[Howard Ellacott]

Looking for a solid list of iOS devices affected by January 1st 1970 bug.

Is this correct / complete?
Also not really sure where to stick it to.

It's just 64 bit devices I think, so the 5th gen iPod touch isn't affected. Other than that that looks right! Any reason why you wanted a list?

 

[DeltaMac]

Just curious - Is that list so you can try to intentionally brick every device you presently have?

Also not really sure where to stick it to.

Not really sure what you mean?
Maybe a Post-it note, on the wall next to your wall charger, to remind yourself not to set the date for Jan 1 1970?
What else?

 

[adam9c1]

Because my network admin blocks NTP, and other ports and IPs we need.
Sometimes we can access MAS but not login, sometimes we can't download iOS updates, sometimes devices communicate with Cache and other times they do not.

If devices are not connected to the network for about a week they loose their time and need to manually set.
I need to present this need for time to the IT Dir providing list of affected devices.
[doublepost=1455657923][/doublepost]

Just curious - Is that list so you can try to intentionally brick every device you presently have?


Not really sure what you mean?
Maybe a Post-it note, on the wall next to your wall charger, to remind yourself not to set the date for Jan 1 1970?
What else?

Which forum to put this into.

 

[DeltaMac]

Hmmm, blocking a time server on a network makes no good sense.
There's too often that I have seen problems with a network when the network clock is not synced to correct time.
How can a competent IT even justify that?
(Guess I answered that question as soon as I typed it )

But if you have to manually set time and date, wouldn't you set the time for current time (not Jan 1 1970...)?

Just a thought, if you are losing the time settings completely in a week, then you have other problems, and the 1970 bug is not related.

 

[adam9c1]

The time issue is only one among many. But if we have clients not loosing their time then end users will not have a need to adjust time. I feel that if the device is working properly there is less chance for mischief. Indeed after about a week of no connection to the network, clients will loose track of date and time.

I am also facing other problems from properly connecting to MAS, and iTunes, see problems utilizing caching service, downloading updates, problems with MDM which stem from APN.

Many things are very inconsistent which makes huge problems deploying and supporting the end users.

I feel the network team is not on the same page as the tech support team and is working against us.

 

[Tech198]

Hmmm, blocking a time server on a network makes no good sense.
There's too often that I have seen problems with a network when the network clock is not synced to correct time.
How can a competent IT even justify that?
(Guess I answered that question as soon as I typed it )

But if you have to manually set time and date, wouldn't you set the time for current time (not Jan 1 1970...)?

Just a thought, if you are losing the time settings completely in a week, then you have other problems, and the 1970 bug is not related.

True, but it could share the same result as the the 1970 bug...

That is, open iphone, disconnect battery for few seconds and reconnect it, and ur ok

I bricked my phone 'testing' 1970 issue, because i foolishly didn't believe anyone else... and a restore did not work... so i opened the phone and is connected battery for a 30 seconds... all is fine..

If it saves a trip to the Apple store, u'r gonna do it