Home / News / Mobile Phone News / iPhone Alarms Fail Again

iPhone Alarms Fail Again

David Gilbert


iPhone Alarms Fail Again

It’s a story we could have written on Friday evening before the weekend even began. With the switch to British Summer Time taking place on Saturday night/Sunday morning, as sure as night follows day, iPhone owners around the country were going to be late for work this morning.

Last November we saw a similar problem when we switched to Daylight Savings Time and almost six months later we are seeing identical problems. Irate workers took to Twitter and other social networking sites this morning following their alarms failing to go off, going off an hour early or going off an hour late. “Bloody iPhone alarm again!! Did I learn nothing from last time the clocks went back?” one frustrated Twitterer said this morning.

Others though were less angry with the situation: "Thanks iPhone. I didn't really want that alarm to go off anyway." The problem seems to have affected non-recurring alarms set within iPhone’s calendar application rather in its dedicated alarm clock. The issue has been seen across the globe in recent months with iPhone owners in Australia and the United States also hit with the problem. Apple had promised to fix the glitch but it seems as if there are still some issues to be ironed out.

Plans by the UK government to get rid of Daylight Savings Time altogether could be the solution Apple are looking for but it seems to us as if it should be a relatively easy problem to solve for the computer giant. Have you had any issues with your iPhone alarm this morning?

Source: Twitter


March 28, 2011, 3:07 pm

My Zte blade, made that pesky old summer time transition flawlessly. Boo Ya Thanks again Trusted Reviews.
My T-shirt size is medium.;)


March 28, 2011, 3:16 pm

This is just too funny. At least the iPhone isn't an expensive premium handset, marketed for its ease of use. Oh hang on...

Meanwhile the alarms and clock in my HTC Tattoo adjusted automatically and work just fine.


March 28, 2011, 3:24 pm

Yup, I was utterly bamboozled when my alarm went off at 6am despite the alarm clearly saying 7am. Of course it didn't help that I'd forgotten the clocks were going back anyway.

Martin Daler

March 28, 2011, 3:38 pm

@Ed you are all messed up man, the clocks went forward!

Michael G

March 28, 2011, 3:42 pm

Well if you're going to insist on using an iPhone to wake you up every morning then in my opinion you kinda deserve it..


March 28, 2011, 3:44 pm

@Martin Daler: Of course I meant 'going back to being forward'. ¬_¬

Arctic Fox

March 28, 2011, 4:38 pm

I shall manfully restrain myself from exercising my wit and wisdom and I shall not mention that my Desire Z (costing approx. 40% less than an iPhone) worked perfectly. There I haven't mentioned it. However, on a more serious note (!) I am very puzzled. One would have thought that Cupertino would have managed to sort out this glitch by now if only to spare their very loyal customers from having the urine extracted by the rest of us. Has anyone any idea why this is proving to be so problematical?


March 28, 2011, 5:55 pm

In fairness, the same product existed in three major revisions of Symantec's Enterprise backup solution, Backup Exec - what hope have Apple got? :-) http://bit.ly/ibfomi

Arctic Fox

March 28, 2011, 7:18 pm


Is it really? Apple incorporated the same product in their iOS? Given what your informative link shows one has to wonder why. I am not assuming Apple are dumb (that would be foolish) so one has to assume they had what they thought was a good reason - it would be interesting to know what that reason was. It is scarcely a critical malfunction (if one is aware of the problem in advance) but it is certainly an embarrassment for them.

Nav Garayal

March 28, 2011, 7:30 pm

dont worry, iphone5 will put it right. they will call it something like "summertime recognition". just like facetime it will be ground breaking


March 28, 2011, 10:05 pm

Clearly there's a bug here but do many people really set wake-up calls in their calendar, rather than in the more usual clock app (which can after all handle multiple alarms for different kinds of day, shift patterns, etc)?


March 28, 2011, 10:28 pm

I'm not sure why some Android people seem so smug, reading around the forums their platform also had a fair share of problems coping with the time change. Even Windows Phone 7 had problems.

The problem is due to how computers store time, it's based on an offset (usually seconds) from a reference time point (in UTC).
So when you set an alarm is gets stored as this offset.

However with changing timezones, or daylight saving changes, etc It becomes necessary to recalculate this offset and then it all becomes complicated. Even for users, imagine you set a meeting for 4pm but then move timezone. Should the meeting time change?

I'm not trying to excuse Apple from not having done their homework fully, but it's wrong to assume it is a simple thing or that just Apple gets it wrong.

Timbo 1

March 28, 2011, 10:37 pm

Mine worked fine this morning. I was definately using the same repeat alarm that was being used last week!!


March 29, 2011, 1:02 am

Yet another reason to get rid of daylight savings time. It never really made sense in the first place.


March 29, 2011, 4:09 am

@Fishscene - Unless you're a farmer in Scotland... but then again, they have a devolved Government now, so shouldn't England's do what's right for us and leave those north of the border to make their own decisions on this matter?


March 29, 2011, 11:02 am

Another example of how Apple cannot develop sensible / secure software.

Once you go past the glitzy front-end, their software is truly dreadful.

comments powered by Disqus