Comments on: iPhone Alarm Bug Prevents Alarm Clock Activating After New Years Eve

By: iPhone Daylight Savings Time Bug Strikes Again: iPhone Clock Falls Back Instead of Springing Forward

Sun, 13 Mar 2011 19:04:49 +0000

[...] iPhone has inexplicably been plagued by multiple daylight savings bugs over the past year, each time sending the iPhone-dependent internet into an uproar as alarms go off late or early. [...]

By: Ian

Ian — Fri, 07 Jan 2011 12:16:33 +0000

My question is always, when things like this happen, what else is not working?

I have a IPhone and am thinking i made a big mistake to move to apple. They are fast moving to market monopoly nonsense.

Controlling what i buy, watch, and how i used my device. There should be laws against this.

And now the thing is full of glitches. My message to Steve is get your priorities in order. Test your product and stop devising/implementing Market control gimmicks and spend your resources in making it work.
Your product should sell itself and do its own market domination, and not cause us to regret buying it.

By: Ra

Ra — Wed, 05 Jan 2011 22:01:34 +0000

No problem. This is because all alarms is set for year 2010.
Delete all old alarms and create new ones (for year 2011)

iPhone 4 iOS 4

By: conquestcommando

conquestcommando — Tue, 04 Jan 2011 03:16:14 +0000

Um…. Did everyone stop using old fashioned alarm clocks? I always plug in my iPhone beside my bed, yet sometimes the connection is lost and my phone goes dead when my phone has a low battery and end up being late for something (work/fun). Since then, I always have a backup old school alarm and it has served me well.

By: pellepimg

pellepimg — Mon, 03 Jan 2011 23:02:27 +0000

Insightful!

By: Preston

Preston — Mon, 03 Jan 2011 21:22:41 +0000

Man, folks. It’s a bug. It lasted a weekend. I mean come on… really? F Apple? They SUCK? Really??? Amazing how “deserving” some folks must be, to expect a sophisticated device like the iPhone 4 not to just be amazing, but bug-free.
Sorry, but bad news to those folks: if you’re expecting electronics to ever be perfect, you’re in for a lifetime of frustration.

By: Daniel Rubin

Daniel Rubin — Mon, 03 Jan 2011 12:05:56 +0000

For all it’s worth, the bug did NOT fix itself on January 3rd. I didn’t know about it, and now I’ve missed my flight this morning! What’s the chance Apple will reimburse me for the $391 change fee?!?!?! I say zero.

By: Laura

Laura — Mon, 03 Jan 2011 11:21:34 +0000

Well it’s 3 Jan and my alarm is still not working! Work tomorrow so who knows if my alarm will work then. Off to play around with repeating alarm but shouldn’t have to be doing this on my day off!!!!

By: iPhone Alarm Not Working in 2011? Here’s a Fix

iPhone Alarm Not Working in 2011? Here’s a Fix — Mon, 03 Jan 2011 09:42:27 +0000

[...] iPhone – January 3rd, 2011 – No Comments The New Years iPhone alarm bug is still effecting some people despite it being January 3rd, which is the date when things were [...]

By: New Years iPhone Alarm Clock Bug Continues to Effect Some Users

New Years iPhone Alarm Clock Bug Continues to Effect Some Users — Mon, 03 Jan 2011 09:29:46 +0000

[...] iPhone – January 3rd, 2011 – No Comments It looks like the New Years iPhone alarm bug is still causing a ruckus, as users from around the world complain their phone alarm failed to [...]

By: tzs

tzs — Mon, 03 Jan 2011 02:54:36 +0000

I doubt that it will resolve itself for “no apparent reason”. The reason it resolves on the 3rd, I suspect, is that January 3rd this year is the first day of week 1 of 2011 on the ISO week-based calendar. January 1st and 2nd are in week 52 of 2010.

Weeks in the week calendar start on Mondays, and week 1 is the week that contains the first Thursday of the year.

Next year, January 1 is part of the last week of 2011. Week 1 of 2012 starts on Monday, January 2nd. Thus, if Apple doesn’t issue an update, I’d expect alarms will fail on January 1 next year, and the problem will resolve on January 2nd.

By: Giampaolo

Giampaolo — Sun, 02 Jan 2011 23:41:44 +0000

Unfortunatly, the problem will repeat next year (verified on 4.2.1 iPhone 3gs manually shifting date to 1/1/2012) … The problem will NOT be auto-corrected by iOS (iPhone does not implement any AI engine and cannot learn from his mistakes). It’s just a bug requiring a fix… It’s not a shame to have a bug. It’s a shame to minimize its and to omit full details on that (I’m sure Apple engineers has already enough information to let us fully understand what’s happened). I hope Apple will clearly state the fix will be MANDATORY, so we will not incur in the problem in our future.
P.S. If I were Steve, i’d ask Quality Team to implement a full new set of unit tests on Clock apps and related api….

By: Jsmith

Jsmith — Sun, 02 Jan 2011 16:24:47 +0000

2 days in a row…

By: Jsmith

Jsmith — Sun, 02 Jan 2011 16:22:20 +0000

Not good to be late in power industry. “wah wah wah”?? Five years ago I wouldn’t pay the $$$ that I do for iphone. An automatic alert would have been all it took for customer appreciation. The operator I was supposed to relieve wasn’t impressed.

By: ben

ben — Sun, 02 Jan 2011 13:02:26 +0000

right after midnight on new years eve your phone wouldnt make a call? wow, that’s amazing. that’s definitely got to be apple’s fault then. nothing to do with the tens of millions of people overloading the phone networks calling round to say happy new year…