If you are concerned about the failure that can turn your iPhone into a paperweight when configuring one dated 1970You have to know that this problem has its days numbered. The latest beta of iOS 9.3, whose public version was released yesterday Tuesday and the version for developers last Monday, prevents a 64-bit iOS device (those affected) from being brickee setting the fateful date. If there are no surprises, the final version will be released in the week of March 15.
The '1970 ruling' was discovered in the middle of this month and, as we mentioned earlier, brick any iPhone, iPod Touch or iPad from 64-bit preventing it from restarting once shutdown, although it is not actually a brick, since this does have a solution. The problem seems to be that the capacity of the device is overwhelmed when the iPhone resets the date to the maximum value, a very high number that iOS devices are not able to process.
The 1970 bug will be fixed in the next version of iOS
The solution that Apple has chosen is very simple: as of the fourth beta of iOS 9.3, the oldest date that can be configured is the December 31th 2.000 at 7am or on January 1, 2001 at 12pm, depending on the area. In any case, if not for making some kind of joke, right now I can't think of any case in which I would set a date of 16 years ago.
On the other hand, the fourth beta of iOS 9.3 also solves a problem for devices that would have been affected by the 1970 crash. If an iPhone has been left on the block for this bugs, can be restored with beta released this week, something like the case of devices affected by the infamous Error 53. Have you experienced the 1970 crash and are you happy with this news?
That is very good.
But how bad they cover one error and another comes out ...
I know; They are beta (public) but my Apple Watch (2.1 that previously worked normal) since this public beta 4 stops receiving notifications,
Today it is a simple expensive watch without being smart.
Hopefully the 2 weeks for a new beta pass quickly and solve it
Some on reddit say to update the Apple Watch to 2.2, then desynchronize and synchronize again but (there another knot) although I already download the beta profile on the Watch, it does not throw me the update (and the truth is that scary because there is no step back)
Any ideas? What do you think you read to me?
Thanks for giving me a cable and greetings to each reader.
The same thing happened to me, and doing what it says on reddit it was solved.
The same thing has happened to me, I have stopped receiving notifications from the watch and a number of apps has stopped working.
Never update, it's that simple !!! It's not worth it, if something works, don't touch it! If your icacharro comes with a version x of ios, leave it like that since that version is the one that will work perfectly with it. I have my 4s with ios 5 and it goes smoothly, working as from the first day and without problems or hangs or lag or anything at all
But there are apps that need iOS 8 onwards to be able to use it on mobile 🙂
OS 5 Forever and without being able to install new applications, say the good and also the bad, I have an iPhone 4 to IOS 6 enchanted with life with its finesse, as a phone it works perfectly, telegram, whatsapp, calendar, luck that I installed those apps when it was still compatible with IOS 6.0.
But all the ones that need at least IOS8 screw you without being able to test them
It is true, some time ago I had an iPhone 4s with IOS6 and it was very fluid, I was on par with the basics (music, photos, camera, calendar, notes) with the iPhone 6, just for the applications that many were no longer 100 % compatible and those that were, had very limited functionality