Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
I can just see the curt reply.

Steve: it's no big deal.

Thanks, Steve. Helps a lot.

I was thinking the same. Or, he might give some BS excuse that the Kool-Aid drinkers will quote like it is an unquestionable fact; as they did a few months ago with the iPhone issue.

For example, Steve Jobs may say something like

All alarm clocks sometimes get it wrong

This will be followed forum post and YouTube music videos made be slightly mentally delayed people. For example...

All alarms clocks make errors, this is no different

Can anyone say they have had an alarm clock that has never made an error. Don't Blame Apple

I have 10 iPhones and non have given me this error, I even tested 20 in the Apple store... all were fine
 
Wirelessly posted (Mozilla/5.0 (iPhone; U; CPU iPhone OS 4_1 like Mac OS X; en-gb) AppleWebKit/532.9 (KHTML, like Gecko) Version/4.0.5 Mobile/8B117 Safari/6531.22.7)

Hour late for work this morning. Thanks apple for that! I can't believe they didn't fix this in time if they knew it existed. Just plain outrageous
 
I initially set the clock on my iPod Touch back because I wasn't sure if it was going to set it back or not automatically. Then I woke up sometime after 3AM because I was stressed whether I will be 1h late to work or not. So I noticed that it HAD set the clock back automatically, so it was now 1 hour early. So I set it back and thought it was going to be fine, but just in case, I used my trusty 20 year old CASIO watch. Obviously, my iPod failed to ring in the morning, despite it knowing the time.

What I have learned: Stop trusting "intelligent" technology for important things and just use good old fail-proof equipment.

Now my iPod Touch alarms keep ringing 1 hour late despite it knowing the right time. There is nothing I can do because everything is set correctly.

Stupid annoying bug.
 
My alarm went off an hour late in the UK. I was only ten minutes late for work but it's ten minutes later than I should have been. What a ridiculous situation this is.

Not sure how I'm going to get around it tomorrow. I might set a few different alarms for different times just to be safe.

iPhone 4 running iOS 4.1.
 
Yep. Happened to me this morning. I live in the US and my alarm went off 1 hour early. I thought I was going crazy...I guess I understand their being a bug but DST doesn't happen until Nov 7. So why did it hit this morning?:confused:

Same here. Got up, was nearly out the door - and realized I had an hour to wait.... grr. :mad::mad::mad::mad:
 
I set a second device to go off at 5am and I'm pleased I did that because the iPhone didn't sound the alarm until 6am!
 
get a real alarm clock and don't rely on a phone.

:rolleyes: My iPhone has the function of an Alarm Clock. It should fulfill that function...

Besides the point, but my iPhone all suits my life style. It will wake me up on if Im at home or in a hotel. I have got used to not worrying about it.
 
Bug happens in Mexico too

So daylight savings time started yesterday. I was almost late for work today because of the bug. This should be corrected ASAP :(
 
Wirelessly posted (Mozilla/5.0 (iPhone; U; CPU iPhone OS 4_1 like Mac OS X; en-gb) AppleWebKit/532.9 (KHTML, like Gecko) Version/4.0.5 Mobile/8B117 Safari/6531.22.7)

This only seems to be recurring alarms. I just set a brand new on off alarm and it worked. A brand new recurring alarm didn't. Looks like I will have to either set a one off alarm each day or move my alarm back an hour.

Luckily I'm not the only one at work with an iPhone, so it happened to a few people. Being on flexi time helps, but it totally screwed my day up.

Cheers Steve, now you even dictate what time I get up
 
This is doubly worse from my perspective as a developer of a popular clock app. Not only does the bug affect my own wake up time, but Apple's app approval policies make it practically impossible to fix this for my customers. If I submitted a fix, it would take about a week and a half for Apple to approve it. Then once Apple's fix comes out I would have to submit yet another version of my app and wait another week and a half. All thanks to the curated app store, and Apple's typical uncommunicative stance.
 
Yet another failure for Apple related to the iPhone 4. Ordering systems go down during the opening days of the iPhone 4 launch. Antenna issue. Proximity sensor. White iPhone 4 gets delayed and then basically cancelled. iOS 4 can't handle a simple time change.

It's all adding up to a company that has peaked. Stock is a sell.
 
Wirelessly posted (Mozilla/5.0 (iPhone; U; CPU iPhone OS 4_1 like Mac OS X; en-gb) AppleWebKit/532.9 (KHTML, like Gecko) Version/4.0.5 Mobile/8B117 Safari/6531.22.7)

Alosii

Daylight saving finished yesterday :). Now it's GMT
 
So alarms in the alarm section of the clock.app is what has a bug in it? If so, then I must have dodged a bullet cause I have been using it (iphone) to wake up for a while now and no problems so far...
 
This is doubly worse from my perspective as a developer of a popular clock app. Not only does the bug affect my own wake up time, but Apple's app approval policies make it practically impossible to fix this for my customers. If I submitted a fix, it would take about a week and a half for Apple to approve it. Then once Apple's fix comes out I would have to submit yet another version of my app and wait another week and a half. All thanks to the curated app store, and Apple's typical uncommunicative stance.

This is kind of comical in a way. If Apple applied their own guidelines for apps, then clock.app on the iPhone would be rejected, because it did not work correctly. However, Apple is A-OK including defective software and at the same time delaying fixes to others software that could correct the issue for other affected apps.

I thought the whole app store concept was to help users; not saddle them with a defective OS and then prevent/delay updates that could correct the poor coding on the part of Apple.

Way to go :apple:
 
My solution. The alarm label is an important part of the fix
 

Attachments

  • IMG_0632.PNG
    IMG_0632.PNG
    50.4 KB · Views: 95
You didn't have to wait very long. :D

The day SJ and/or :apple: advocates Daylight Savings Time is the day I call them idiots too. But they won't cuz they're smart. DST is an idiotic idea with idiotic consequences and this DST bug is just an obvious one. When the world was rural and having a certain time on your pocketwatch be during daylight hours made you feel warm and fuzzy inside maybe it was no big deal but now it is ridiculous. It will end and people will laugh at those silly folk from our decades that thought it made sense.
 
I am still trying to figure out how Apple screwed this one up.
I see sloppy coding all over the place in 100% apple fault. The Alarm code should be linked to clock. Which means that when the clock changes for DST the alarm should move with it.
Instead Apple has it linked up to something else which clearly is not system clock.

I can understand glitches in lets say your calendar events happening at the correct time and not updating correctly to account for DST but the alarm there is ZERO and I repeat ZERO excuse. The calendar excuse is a small one at best and really not a good one. This should be a simple fix and sad that Apple has not fixed it.
 
Wirelessly posted (Mozilla/5.0 (iPhone; U; CPU iPhone OS 4_1 like Mac OS X; en-gb) AppleWebKit/532.9 (KHTML, like Gecko) Version/4.0.5 Mobile/8B117 Safari/6531.22.7)

This only seems to be recurring alarms. I just set a brand new on off alarm and it worked. A brand new recurring alarm didn't. Looks like I will have to either set a one off alarm each day or move my alarm back an hour.

You're correct. I'm in the US eastern time zone. My reoccurring alarm went off one hour early while my wife's non-reoccurring alarm went off at the correct time.

There's no reasonable excuse for Apple allowing this to happen if they knew about it in advance. Lazy buttholes.
 
Nope:

http://www.***********/?q=XP+DST+bug

EDIT:eek:k, seems I can't post a link: just google for "XP DST bug"

Not really comparable as this was due to an unforeseen change in DST. Even then, they had a fix in place.

For those running XP, there will be a patch available that will be sent out as an automatic update on Tuesday. You will need to have Service Pack 2 in order to receive this update.

Vista users are immune, as that operating system was created after 2005 and doesn't have this bug.

Apple is in the position of Vista users here. It should be bug free.
 
Nope:

http://www.***********/?q=XP+DST+bug

EDIT:eek:k, seems I can't post a link: just google for "XP DST bug"

LOL - the top search result (http://support.microsoft.com/gp/cp_dst) is a Microsoft link advising people if they aren't running automatic update, they need to manually install the DST patches before DST approaches.

And, the base issue was that in 2007 the DST dates were changed in North America (note that XP first shipped in 2001 ;) ).

It looks like Microsoft was on top of the situation to update users for legal changes 6 years after the OS is released, but Apple doesn't care about a bug that they just shipped.

PS: My Windows phone has alarms for an upcoming trip - leave MNL 17:55 Sat 6 Nov, arrive HKG 20:00 Sat 6 Nov. Leave HKG 00:30 Sun 7 Nov, arrive SFO 22:00 Sat 6 Nov. No worries about the phone messing up even though I arrive a day before I departed....
 
You're correct. I'm in the US eastern time zone. My reoccurring alarm went off one hour early while my wife's non-reoccurring alarm went off at the correct time.

There's no reasonable excuse for Apple allowing this to happen if they knew about it in advance. Lazy buttholes.

That is ODD! I have a weekly alarm to wake me up for the gym at 445am and it went off this morning as it should. I also live in EST
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.