Well, well the string of viruses and bugs doesn’t just go away for the unfortunate iPhone. First, it was the CrashSafari bug, then came the Apple manufactured Error 53, and now there is this ‘time bug.’
The latest in the string of attacks to hit our beloved iPhone, this bug here, hates the date January 1, 1970. Well in fact it hates it so much that it will permanently crash your iPhone’s if you change time settings to the mentioned date.
According to CNN, the reason behind the crash remains a mystery, but by the way, why would anyone want to set an iPhone’s clock back 46 years? However, the iPhone which was launched just 8 years back in 2007 has the option to change the date as far back as to the start of the 1970.
Some of the guesses that come around are, January 1, 1970 is the earliest date that you can set your iPhone to. That’s because Unix time which is use by iPhone as basis for its clocks, began at midnight GMT on January 1, 1970, Unix time has been counting every second since then.
But, why will it render iPhone useless? Well, the reason given is if your time zone isn’t GMT, your iPhone might interpret a time before January 1, 1970 or in other words, before zero. Though Unix time can be negative, possibility exist that something related to the time zones is crashing the iPhone.
According to The Telegraph, The bug renders useless any iOS device with a 64 bit processor including the iPhone 5s, 6, 6 Plus, 6s and 6s Plus, the iPad Air 2, the iPad Mini 3 and 4, and the sixth-generation iPod Touch.
It further added that users in America, with time zones behind GMT, were affected, but one user with the time zone set to Beijing did not.
A precautionary tip for all you iPhoners! just stay in the present, that way is better for your iPhone device.
Copyright Business Recorder, 2016
Courtesy : BRecorder