Avoid the iPhone daylight savings time bug
Apple will almost certainly not get a fix out in time for the daylight savings bug currently afflicting the iPhone around the world, but there is a way that you can save yourself a lot of trouble when it’s your turn.
We’re sure you were paying attention as the iPhone failed to wake up millions of people when the time change for Daylight Savings Time came to their country. Users in Australia were the first to be hit as their alarms went off an hour late after the time changed there but the settings for their morning alarms did not. The same problem occurred in Europe a few weeks later. Again, iPhone alarms all over the continent failed to wake up their owners on time, never a wonderful occurrence but even worse on Monday morning. The problem is with the iPhone software and it has not yet been fixed.
That means, of course, that the problem will rear its ugly head in the United States this coming Sunday, leaving people lying in bed for an extra hour to start the work week, with the result that a lot of people will not be at work on time on Monday. There is no real fix, but you can save yourself some trouble by being prepared for the problem before it strikes. The problem lies in alarm synchronization; the iPhone itself figures out that it should change the time, and it does. However, it does not automatically extend that change to the alarms already set in Clock. So you need to give it a little help.
The phone only has the error on repeating alarms that are set to something besides every day, so an alarm set for just weekdays, or just Monday, as examples, will not work properly, according to a CultOfMac story. The answer is not to use those setting for the day after the end of daylight savings time, i.e. Monday, Nov. 8. Instead, set all of your alarms to “Never” repeat before you go to bed on the seventh. The alarms will then work once, specifically at the right time on Monday morning. Then you can go back and reset your alarm repeats to where they were before the time change. Hopefully, Apple will fix the problem before Spring.
Related posts:
