It doesn't work even on January 3rd! F...... stupid Apple. If you need a good programmer to fix your stupid iOS bugs... I'm available!
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
iPhone Clock Bug Prevents Alarm Triggers after New Year's
- Thread starter MacRumors
- Start date
- Sort by reaction score
Today is Jan 3rd already (Lithuania, Eastern Europe) and I have missed time to wakeup.
Yesterday I was planning to charge and use my old Nokia 3310 for alarm, but I have read an "official" Apple response here, that alarm will work on 3rd Jan... !@#$%^&*( you Apple
Yesterday I was planning to charge and use my old Nokia 3310 for alarm, but I have read an "official" Apple response here, that alarm will work on 3rd Jan... !@#$%^&*( you Apple
the question is why did each of them fail. It is safe to say it was not a software bug for any of them and a stupid software bug at that.
I know only time my cell phone has failed is if they were off or the battery died in them.
Alarm clocks and computers were both effected by power going out. Hence the reason why I would have 2 for anything I was paranoid about. Lately my cell phone has been my primary alarm. Only time I worry about it is if I try to charge it when it is low on juice. I have a flaky charger and sometimes does not work right and I have not wanted to flip the charger around to my good one because it is a huge pain for me to rerun the wire.
According to my own testing, the alarm (non-recurring) has to be created on the third. I had one created yesterday, at around 11:30pm for 12:01 am that failed. But, the one I set at 12:07am for 12:09am worked fine.
To sum up: One that was created on the second, but set for the next time to be on the third won't work. It looks as if the alarm itself is corrupt, so the time just being set for the third doesn't matter - it has to also have been created on the third.
To sum up: One that was created on the second, but set for the next time to be on the third won't work. It looks as if the alarm itself is corrupt, so the time just being set for the third doesn't matter - it has to also have been created on the third.
Wirelessly posted (Mozilla/5.0 (iPhone; U; CPU iPhone OS 4_1 like Mac OS X; en-us) AppleWebKit/532.9 (KHTML, like Gecko) Version/4.0.5 Mobile/8B117 Safari/6531.22.7)
Although I use an alarm clock (Today Programme on BBC Radio 4 as I'm so young and hip), I set my iPhone too out of curiosity. Didn't go off, as others have said you seem to have to create the alarm on the 3rd.
I know this is not the mist serious problem in the world, but it should have been simple to fix and Apple knew there were problems thanks to daylight saving time. Poor show, what if I had been away and depending on my phone alarm today?
Although I use an alarm clock (Today Programme on BBC Radio 4 as I'm so young and hip), I set my iPhone too out of curiosity. Didn't go off, as others have said you seem to have to create the alarm on the 3rd.
I know this is not the mist serious problem in the world, but it should have been simple to fix and Apple knew there were problems thanks to daylight saving time. Poor show, what if I had been away and depending on my phone alarm today?
Yeah missed my doctors appointment this morning since I had no idea a problem like this will occur. Thanks apple.
To all the people who say I shouldn't use my iPhone as my alarm, why the hell shouldn't I? I've been using my iPhone as an alarm since the DAY IT LAUNCHED, and it didn't have any problems until iOS4, first with the DST bug, then this. For 3 1/2 years it worked, now suddenly I need to buy a new clock because Apple changed their code? Nothing changed in the clock app since day 1, at least on the front end, just change it back!!
It worked for 2008, 2009, and 2010, what's different about 2011?
It worked for 2008, 2009, and 2010, what's different about 2011?
That's right. Then we can ALL get four dollars. Victory.
I suppose one of these decades computer "engineers" will finally figure out how to tell time and do math.
With lawyers it's easy. Their Number > Your Number.
Bug still persists...
Set three alarms this morning (1/3/2011) and the non-repeating alarm didn't sound. Not sure if it matters, but it was set for 0430. The repeating alarms were set at 0420 and 0445 and both sounded normally. (Note that the 0430 alarm was one that was originally set so I'm going to delete it and try again... hope this keeps someone from being late!)
Set three alarms this morning (1/3/2011) and the non-repeating alarm didn't sound. Not sure if it matters, but it was set for 0430. The repeating alarms were set at 0420 and 0445 and both sounded normally. (Note that the 0430 alarm was one that was originally set so I'm going to delete it and try again... hope this keeps someone from being late!)
Well, because you don't want to miss appointments. You can live based on what you believe you should do, but living on what everything else should be is an exercise in frustration.
I can confirm that the Alarm didn't work on my iPhone 3Gs, iOS 4.2.1, this morning too. I have set an alarm on 08:35 and it didn't start. After I set another alarm for testing purposes for 08:45, it worked... well, doesn't matter, I will not use my iPhone for reliable alarms anymore. My Samsung mobile is working great, too... no customizable sound, but who cares... :-D
Great work, Apple!
Great work, Apple!
Alarm starting working for me. Pretty sure you had to create the alarm on the 3rd (for example, you couldn't create it on the 2nd at 11pm for this morning).
Problem now is the alarm notification in the upper right corner remains on although I have no alarms set.
Problem now is the alarm notification in the upper right corner remains on although I have no alarms set.
Saying you should not use iOS for its alarm function makes as much sense as saying you should not use it for its phone function. In other words, its complete nonsense direct from the Kool-Aid drinkers that see no fault from Apple CONsumer Electronics.
That way you can sweet-talk every problem in the world. Fact remains that if people shouldn't be using the iPhone as an alarm, then Apple should remove it from its device. There is no excuse for this sloppy programming (and sloppy communication - what do you mean it works on Jan 3?)
It's January 3rd and my wife's alarm did not go off this morning at 7am. What ever happened to It Just Works? And I guess we really can't believe anything Apple says anymore. Usually the first words to come out of Cupertino is usually a lie. But, They usually do correct themselves after the media pours on the pressure.
Oh man, I had about 5 friends who slept in for a meeting we had yesterday. All of them running 4.1. Pretty funny.
The scary part is that Iphone users are accustomed for the phone part not working. From a BGR review of a phone of another brand:
So Iphone users blindly assume that the error must be somewhere else - not on their Iphone. It seems that now many Iphone users are ready to accept that the expected functionality of alarm clock is to randomly not work. And they'll be shocked if they someday try another model and the alarm actually works reliably.