Ringing alarm bells
Some iPhone owners apparently got an unwelcome lie-in today after their alarm failed to go off thanks to the start of British Summer Time.
The BBC reported that some people have dashed to work today after their phone alarm went off an hour late, an hour early or just didn't go off at all.
It is not the first time Apple's iPhone has suffered from an alarm clock glitch as the same problem affected some users on New Year's Day.
The popular smartphone's alarm application failed to work for the first 2 days of 2011 leaving owners asleep, with reports of missed appointments and work problems for users.
Apparently iPhone owners who set their alarm for ‘one-time use only' instead of relying on a recurring wake-up alarm were in trouble but it is thought problems only occurred over the New Year's holiday weekend.
This time round it appears the problem has not affected all iPhone owners although Apple has apparently not clarified what has caused the problem.
Much like last time, flustered users vented their frustration on social networks (presumably as they scrambled to make it to work on time).
One Twitter user reportedly wrote: "iPhone alarm failed twice. 1) went off at 5.45 instead of 6.45. 2) Didn't go off at all when I reset it. Time to update software," while another apparently Tweeted: "Thanks iPhone. I didn't really want that alarm to go off anyway."
It appears that the problem has affected ‘one-time use only' alarms once more; the non-recurring alarm that can be set within the handset's calendar app instead of its dedicated alarm clock.
Apparently the problem first reared its head in the US in November when the switch to Daylight Saving Time was made.
Apple had promised to investigate and fix the problem but it seems the glitch has reared its head again and users might have to watch out when the clocks go back again in Autumn.
