/* Style Definitions */
mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
mso-fareast-font-family:”Times New Roman”;
If, like me, you rely pretty heavily on your iPhone alarm to get you out of bed in the morning then you might have been in for a rude awakening this morning. Despite automatically updating the handset’s clock to GMT from BST on Sunday morning, some users have found that their alarms have been going off as though the clocks never went back – so an alarm that was meant to go off at 7am went off at 8am instead.
Not all iPhone users have been affected; looks like just iOS 4 users are having troubles – reports on Twitter have suggested that those running iOS 3.x or anything over iOS 4.1 had no issues.UPDATE: Looks like we were wrong about iOS 4.1 users being unaffected – commenters Casper and Grant have both experienced the bug and are running iOS 4.1.
So, how do you fix this annoying little bug? One option is to delete all your alarms and set a daily, non-repetitive alarm, it worked for us. [we previously stated that simply deleting and resetting your alarm would work but Engadget has pointed out that resetting repetitve alarms doesn’t work]
The other option is to update your iPhone software by plugging into iTunes. Australia and New Zealand suffered the same issue when their clocks changed in early October and Apple promised a software fix was imminent – we’ve been awaiting the release of iOS 4.1.1 ever since. Although upgrading to iOS 4.1 won’t necessarily fix the bug, at least you’ll be up to date.
The final option is to indulge in a spot of time-based maths and set alarms an hour earlier than you would otherwise. Just don’t blame us if your iPhone starts getting you up at 5am…
UPDATE: Apple has added the issue to its support website, stating that it should be resolved on November 7th when American clocks change. We shall see… Read more here.