AlarmBug
Latest
iPhone alarms still not working, worlds crashing left and right
Hey, you -- it's January 3rd. You know, the day you're supposed to return to work / school / life. And the day you're supposed to catch a flight you've had booked for three months. And probably a day that you're supposed to accomplish lots of other tasks. Unfortunately for you, you actually believed that your iPhone alarm would fix itself when today rolled around, but based on hordes of complaints seen on Twitter and Facebook, said fix is still hibernating. And thus, you're still sleeping. Even here at Engadget HQ, we've seen iPhone 4 handsets not wake us as promised (on non-recurring alarms), so who knows when Apple will step up to the plate and address the issue. In the meantime, go ahead and set up a recurring alarm while gently crossing your fingers and toes. Or, you know, buy a battery-powered alarm clock off of your grandmother. [Thanks to everyone who sent this in]
PSA: iPhone alarms not working come New Year's Day 2011
We're not exactly sure of the cause of this fancy new issue affecting Apple's super cool iPhone line of cellphones, but apparently you've got trouble come 1/1/2011. According to an explosive stream of frustration-filled tweets on the Twitter microblogging service, when the clock strikes midnight, one off alarms will cease to sing out. The issue sounds eerily similar to recent Daylight Savings Time trouble we witnessed back in November, although we saw both repeating alarm and single alarm failures. So how can you fix this potentially life-ruining problem? Well until Apple patches its OS -- and it's currently unclear if this is just iOS 4.2.1 or earlier versions as well -- you can simply create a recurring alarm at the time you need to be woken up, and then disable it once your dreams are completely ruined. We're taking a deeper look into the issue and have contacted Apple -- if we get more news, you guys will be the first to know. In the meantime, feel free to commiserate in comments, and... happy new year? Update: 9to5 Mac says that the bug will get fixed all by itself once the calendar hits January 3rd. We haven't confirmed this, but if it turns out to be the case, that's pretty good news. In less good news, the issue seems to be affecting iOS 4.1 and 4.0.2 as well. Update 2: Apple responded to us on the issue, though they didn't offer any surprises: We're aware of an issue related to non repeating alarms set for January 1 or 2. Customers can set recurring alarms for those dates and all alarms will work properly beginning January 3. [Thanks to everyone who sent this in]
