Main menu

Pages

Fies: pranksters use iPhone-date bug out

A particularly nasty iPhone Prank promises currently the activation of a "Easter Eggs", the device data is being changed to 1 January 1970th Actually, however, this date ensures that the iPhone does not work anymore.

Just last week we reported at this point on an iPhone bug that reset the machine when changing the date to January 1, 1970 out of action. Now there are reportedly on Imgur the net obviously some pranksters that exploit the bug for a particularly nasty prank. Using an image they promise that on the iPhone a classic Macintosh Theme from the 1970s will be shown as "Easter Egg" as soon as the date is set to January 1, 1970th

A Macintosh Theme from 1970?
This is of course complete nonsense. So it was in the 1970s at all no Macintosh and therefore no Macintosh Theme. The first computer of this series was introduced only in early 1984th In addition, the change in date leading up to the fact that the iPhone freezes on reboot and no longer works. Affected are apparently all iOS devices with 64-bit processors from the A7 chip.

Changing the date destroys the iPhone
The user who has set his iPhone in this way incapacitated, then one is compelled to leave as repair the smartphone at the Apple Store. Alternatively, the bow should also be rectified by the battery is briefly removed from the iPhone and used again as a video on YouTube showing. However, this repair should be performed only with a special tool and always at your own risk. and will void the warranty on the device.

iOS apparently has problems with the Unix time
the bug in the iPhone is triggered apparently by a faulty adaptation of the devices to the Unix time. Unix is ​​a 1969 developed operating system that is the basis for iOS and many other modern operating systems. January 1st 1970, defined as the start time for Unix computer systems. Why this date calculated on iOS systems results in an error, in other current operating systems but not is unclear. Apple, however, has already announced plans to correct the error with an iOS update.
reactions

Comments