Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
If folks only rely on a PHONE for their PRIMARY alarm, and then miss flights/work/etc., that's on them. People should know that an electronic device that does more than be an alarm clock might mess up that feature. Why people don't just spring for a $10 travel clock that works perfectly 100% of the time (save for battery death/changing) is beyond me.

Or why spend hundreds on a phone that doesn't even have working alarm clock. You never travel? You mean a clock radio can't be trusted? What about a digital watch? Get over it.
 
Is this what you've become on trying to defend Apple? Pathetic.

I don't think the idea of relying on 2 alarm clocks is so far out there. I think the idea of using a phone as a sole means of waking you up is stupid. Batteries die, people sleep through their first alarm, etc. Two is one, One is none.

I'm not apologizing for Apple either; I think they make some of the dumbest mistakes I have ever heard, but come on? One alarm clock and it's a cell phone with a short battery life?

I think Apple's "fix" is BS and their software developers should be shot for this oversight.
 
Just tested it for 16:59 (maybe it depends on the format, 12 vs 24 hrs) - and no problem here either...

Or someone is full of urban legend. I use 12 here and no problem 4 different alarms at different times and have not seen the issue. Are these phones that are jailed braked or just some phones. :confused:
 
So it's only on alarms that are set after 12/31/10? My partner set an alarm on 12/31 for 1/1 and it worked fine... I told her about the issue and actually expected it not to happen, but it did... :-(

Weird...

I guess the problem is fixed because I just did it with different times and still no problem, urban legend bull. :rolleyes:
 
Apple's new alarm programmer.
He's showing you how to hold it right.
Stay tuned.
One more thing.
Magic.

flava-flav-clock.jpg
 
I don't think the idea of relying on 2 alarm clocks is so far out there. I think the idea of using a phone as a sole means of waking you up is stupid. Batteries die, people sleep through their first alarm, etc. Two is one, One is none.

I'm not apologizing for Apple either; I think they make some of the dumbest mistakes I have ever heard, but come on? One alarm clock and it's a cell phone with a short battery life?

I think Apple's "fix" is BS and their software developers should be shot for this oversight.

I think you should stop trolling :mad: and on 2 phones at my house one iphone 4 and an iphone 3G no problems. So question is who exactly is having these problems.
Is the IOS perfect no, but this is a no big deal since I say its not happening at all and more of a troll society at large bitching about everything. Same as the antenna no problem at all with hand, yes with metal key but not hand. :rolleyes:
 
What's weird is...

First I must confess that I don't use the iPhone alarms at all - I have a battery backed up Sony Cube on the night stand that "just works" and if I go away on business, I always get the hotel to give me a wake up call.

That said, I understand that other people DO rely on their phones to do this kinda thing and that it obviously shouldn't fail to work on "specific" days as this could have serious consequences for the user.

But what's weird is... why is it happening at all on these "specific" days? The alarm setting doesn't even have a day or date in it unless you repeat it automatically and then its only the day you're setting not the date? Why would the alarm clock need to store the whole date including the year in its alarms?

It seems to me that this "bug" has uncovered a more serious issue. Why is Apple making their software more complicated than it needs to be? What could the alarm also be doing so that it needs to know the date it was created or changed...
 
Last edited:
Well the bug could of been in their since iOS 1.0. Reason being is it was only looking at the 1 spot in the year. 1-0. 0= 10. So when it hit 2011 to the alarm clock it was 2001. Piss poor programing and it was basically the year 2000 bug which in todays age no real excuse to try to save memory but cutting 3 numbers. We have memory to burn and there are better ways to save memory than just cutting 3 numbers.

If this was the case how would it fix itself without new code on the 3rd, which it did for me and others. No clue as to why some users are still affected.
 
I'm going to make one point, and one point only: iOS bugs is news worth reporting. Penny for your thoughts.

Absolutely! Millions of people around the world use iOS, probably more than any other specific mobile OS.

Don't forget iPod Touch and iPads. They have the same clock app.
 
Absolutely! Millions of people around the world use iOS, probably more than any other specific mobile OS.

Don't forget iPod Touch and iPads. They have the same clock app.
well... not the iPad, which doesn't have the clock app at all
 
If this was the case how would it fix itself without new code on the 3rd, which it did for me and others. No clue as to why some users are still affected.

I don't get it either. My wife's & my iPhone alarms didn't activate yesterday (the 3rd), but they worked fine today. Luckily for my wife, her first patient also got bit by the iPhone bug.
 
I still had problems on the 3rd. (luckily I didn't need my alarm that morning, woke up early) Last night I deleted the alarm and remade it, and it worked this morning.

What a ridiculous bug. At least the first and second were on a weekend, otherwise this could have been a lot worse. (still sucks for those who needed to wake up this weekend though)
 
I'm a CS graduate from one of the best universities in England, with 8 years experience in software engineering. So please don't insult my aptitude.

It *is* utterly unforgivable. This is an introduced bug in iOS4. If the phone can render the time and date without problem - which it can - then there is absolutely no excuse for the alarm to fail. All it has to do is check that.

It's totally basic.

It's not even as if this is the first time the alarm system has been shown to be buggy in iOS4. After the daylight savings problems - across the world, with multiple opportunities on multiple dates to issue a fix I might add - we've also had Apple's announcement of a couple of days ago that it was no longer an issue as of 3rd January.

Bugs happen, fine - of course they do. Bugs like this should get fixed much quicker by a 300 billion dollar company relying on this OS to drive future growth. Even if only for PR reasons.



Don't be silly. I've got plenty of brains, and an alternative, but it's sure as hell still worth complaining about.

This is one expensive piece of kit - and this is one freakin' basic piece of functionality that should never, ever fail.

Strangely, not everyone has been bitten by this bug. For example, I use my iPhone as my *only* alarm clock, and it has gone off as expected every day. In fact, I set it without thinking about it over the weekend and had to shut the thing off so I could sleep in. Obviously, there's something subtle and sporadic going on here.

Also, I'll assume that in your 8 years experience, you've probably never had to write a full-featured calendar/alarm application of any sort, so you don't actually know how many edge cases and corner conditions actually have to be handled. Oddly, I can't think of any off hand that would be triggered by 2011-01-01 through 2011-01-03, but the odd range of the issue speaks toward an odd problem.
 
Way to avoid the bug.

There is a way to avoid the alarm not activating, just set the clock to repeat on several days. For example on monday, saturday and sunday.

This way the alarm will go off and does not cause you to be late!
 
Ok, I had a weird alarm experience this morning (1/4).

Yesterday, I remade my main alarms after I found out you had to delete the old ones and make new ones for the bug to go away. I have two: One non-recurring one for medication that's generally set for 2am and one recurring one for waking up at 7:30am on weekdays. I had them both activated last night before bed. They were both set to play the default Marimba.

I woke up on my own around 2:50am this morning a realized I never was woken up by the alarm tone. I'm a light sleeper so it's not like I could have slept through it. The pop-up notification for the alarm was on the phone when I pressed the home button, but the actual Marimba alarm tone never played. I was a little frustrated as I missed my target time for the medication, but it's not the end of the world.

Since it was close to the time, I then adjusted the same alarm for 3:00am to see if it would do the same thing (pop-up, no tone). A few minutes later when 3 rolled around, the alarm functioned 100% normally. Weird.

The recurring 7:30am alarm worked just fine.

I can't tell if this is the same bug as everyone has been complaining about or something new. The situation seemed unique but I can't tell.
 
100% agree! Sometimes my wife doesn't feel like sex, which is why I have a girlfriend on the side as backup. With all the other things my wife does I can't expect her sex drive to work 24/7.


:rolleyes:

nice....but what if the girlfriend is busy?.....see Tiger did understand redundancy....
 
Has anyone seen Steve Jobs's latest tweet?
"Until Apple issues an official fix for the iPhone alarm glitch, please do not open your iPhone's clock app. Doing so may void your warranty."
WHAT?:eek:

You know that's a parody Twitter account, right?

It worked for me... My wife has a library book due today, and my alarm went off (yes, I enter my wife's library book due dates as events into my phone -- whenever she is late, she sends me to get her next book out and I end up paying her fines).

Calendar events and alarms are not the same thing.

Well the bug could of been in their since iOS 1.0. Reason being is it was only looking at the 1 spot in the year. 1-0. 0= 10. So when it hit 2011 to the alarm clock it was 2001. Piss poor programing and it was basically the year 2000 bug which in todays age no real excuse to try to save memory but cutting 3 numbers. We have memory to burn and there are better ways to save memory than just cutting 3 numbers.

Since the alarm clock doesn't even care what year it is, that seems highly unlikely. Besides, I'm about 99.999% sure that's not how NSDate works.
 
Everclock Works For me

I have been using The App Everclock and it worked like a charm. :)
 
BigTRQ said:
If folks only rely on a PHONE for their PRIMARY alarm, and then miss flights/work/etc., that's on them. People should know that an electronic device that does more than be an alarm clock might mess up that feature. Why people don't just spring for a $10 travel clock that works perfectly 100% of the time (save for battery death/changing) is beyond me.

Apparently I didn't word this properly. I am not defending Apple. They have a bug, in a simple app. Should never have appeared, period.

What I am trying to say is that if one must wake up for something important, then only relying on a device who's primary function is NOT being an alarm clock is ridiculous. I based my previous post on the fact in the article that people mentioned missing flights. I guess I just play it safe when it comes to important stuff like air travel. Yes, I use a cheap, battery-powered alarm clock in these instances. If you want to rely on the iPhone/iPod touch, that's your prerogative.

And way to keep the comments about the post classy, post quoters. :rolleyes:
 
Dear Steve, please buy me an alarm clock...

Call me a victim of modern society, but I rely on my phone to wake me up in the morning. Given that it is marketed as so much more than a phone, I don't think it is unreasonable for me to rely on it to wake me up in the morn.

Twice in as many months it has let me down. Would I be unreasonable to request a nice little alarm clock from Stevo (probably analog, or at least without a date function might be best if coming from Apple)?
 
Apparently I didn't word this properly. I am not defending Apple. They have a bug, in a simple app. Should never have appeared, period.

What I am trying to say is that if one must wake up for something important, then only relying on a device who's primary function is NOT being an alarm clock is ridiculous. I based my previous post on the fact in the article that people mentioned missing flights. I guess I just play it safe when it comes to important stuff like air travel. Yes, I use a cheap, battery-powered alarm clock in these instances. If you want to rely on the iPhone/iPod touch, that's your prerogative.

And way to keep the comments about the post classy, post quoters. :rolleyes:
I don't think it's unreasonable to expect an iPhone's alarm to work properly. I mean, what scenario would ever cause it not to work? A programming error in the clock app relating to the new year? I think not.

Now I use a regular alarm too, just cus. Unfortunately I forgot to set it Sunday night, and woke up the next morning to a text from my boss asking if I was alive.
 
I use a backup alarm every day. I have my main Alarm and my iPhone as a backup. I never had to use either as my excuse for being late for work. go to walmart spend $10-$20 and we already have threads about the issue and complant. ;) Pretty sure SJ isnot active on the forum as well. and I saw this joke last night on Twitter.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.