New year and classic glitch. That is the reading that emerges from an error that gave a lot to talk about in 2011, and more so in 2010, with the iPhone and the alarm clock function. You will remember that in 2010 the alarm system of the Apple phone clock registered failures at various times, since the internal chronograph of the terminal did not correspond to what reflected the one that is synchronized by software in iOS - the operating platform of iPhone, iPad and iPod Touch -. With the help of some updates, the problem was fixed.
But with the change of calendar, it seems that some terminals have returned to recall that incident, setting off the alarms - ironically - this year, given the added difficulty of adding a variable with the extra day of February, being as we are in leap cycle.
Through Engadget it has been found that many users have suffered this problem again, although it is not that Apple is the exclusive culprit of the error, since the answer to such an uncomfortable incident is in a system update that the affected ones themselves have not executed.
Specifically, the terminals whose alarm clocks did not ring between January 1 and 2, 2012 were those equipped with the iOS 4.2.1 system version, as well as the previous ones, which suffer from the synchronization problem between the system clock and the chronograph that the iPhone has hardware installed.
That is why the
