Skip to main content

iPhone Alarm Glitch Sees Users Oversleep AGAIN

You might remember back in November when daylight savings kicked in and the iPhone clock started malfunctioning. Despite the fact that the phone’s own internal clock automatically readjusted to reflect DST, the clock app did not and users with repeat or recurring alarms woke up an hour late. We watched as Australia and then Europe were hit by the glitch and hoped Apple would release a fix before U.S. DST. Unfortunately, Apple didn’t release a fix, preferring instead to advise users to set a non-recurring alarm for the Monday morning immediately following DST. Not too long after the DST debacle, Apple released iOS 4.2, which was supposed to have permanently fixed the issue.

Sadly, iPhone users who found themselves in the unfortunate position of having to work (or even just be awake at a specific time) on January 1 were hit by the same issue that plagued users after DST. On Sunday Apple acknowledged that alarms were malfunctioning, detailing that this time, it was non-recurring alarms that were affected. The company insisted that everything would be running normally come Monday, as the app would right itself by January 3. 

Despite this, it seems the problem is persisting for users across the world.The Twittersphere is alive with people complaining about their alarms not going off this morning. 



No official word from Apple at the moment. We’ll update once we know more. For now, might we suggest a recurring alarm? Those are still working. You could always try holding it differently, too, though we can't guarantee that will work.

  • molo9000
    Let the Apple hate commence :)

    Some poor programmer is going to be hanged, drawn and quartered for this by Steve Jobs himself... There is an App for that, too. :)
    Reply
  • millerm84
    All the sudden I am reminded why my $6 alarm clock (and its lack of 3am text messages from my drunk siblings) was such a good idea.
    Reply
  • Parrdacc
    Apple at its finest
    Reply
  • sunflier
    Whoopty-doo!! I bet there's another app for that.
    Reply
  • sunflier
    Dang! sry molo, didn't see your post.
    Reply
  • joebob2000
    Two items: first up "There's a nap for that"

    And "if it didnt work the first two times why did you think it would work on try 3?"

    I blame the over-inflated apple-heads who didnt just use a traditional alarm clock after witnessing the problem repeat itself the first time.
    Reply
  • HA! stupid phone.. and i have one....
    Reply
  • ik242
    no problems if you use phone as phone, clock as clock... but when someone put's on market phone with clock, alarms etc. they better make sure it works. Apple -> fails (again)
    Reply
  • sidestep
    I have to say, My EVO, on Saturday 1/1 morning thought that it was actually Sunday (1/2) and an hour ahead.. it corrected itself by mid-day. Somewhat interesting thought is that I normally have an alarm set for Sunday mornings (only day I have one set) and it didn't go off, even thought the phone thought it was Sunday.

    So at least my android had time issues..
    Reply
  • rad666
    It's not a bug. They're holding it wrong.
    Reply