Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

iOS 4.1 Daylight Saving Time Bug Strikes Europe

flopticalcube said:
Even so, ios was developed after the changes. Apple should have tested this better. There simply is no other excuse.
Click to expand...

I think we all agree on that.

One trouble in today's economy is that companies have slimmed down their test teams.

Apple, while hoarding tons of cash that they could use to hire more people, insists instead upon "acting like a startup" and making their developers switch between multiple projects... good in some ways, but bad when it comes to people being able to devote time to make sure all their code is bug free.

Ah well. I'm sure that blame is going all around at Apple HQ today :)
 
I'm in the US (California), and my alarm just went off an hour LATE. So it doesn't seem consistent here in the US.
 
KindredMAC said:
get a real alarm clock and don't rely on a phone.
Click to expand...

I have a real alarm clock. There's a bug in it. If I set it for 6:59am, it rings on time. If I set it for 7:01am, it rings on time. If I set it for 7:00am, it rings at 8:00am.

I guess, the solution is buy an analogue alarm clock, if you can find one.
 
The reason this is happening to us in the USA is because DST ends on the first sunday of November. For some reason, the phone is thinking it's last year because DST ended in 2009 on November 1st. None the less I was woken up early. To avoid this snafu, the alarm seems to work if you set it to never repeat or to repeat only on weekdays. Lets see if this actually gets fixed this week since Steve was probably woken early from his slumber.
 
I'm assuming this bug only affects people who haven't changed their alarm?

I happened to reset mine on Sunday night and it worked fine for me Mondat morning.
 
flopticalcube said:
I could not disagree more. DST has been with us since the dawn of computing and it's a fairly trivial problem to solve. Y2K was a once only event with issues riddled throughout code bases with very little regularity and with many unknown results. The scale of the two problems does not even come close to being similar.
Click to expand...

A someone who had to do time zone testing in the past, I can tell you that the DST rules are an absolute nightmare. Not everyone follows the same rules, they do change (as happened here a couple of years ago), so it's not surprising there is a bug.

That's not to take away the blame from Apple, but it's not as easy as you think.

But seriously, DST is unnecessary - time to get rid of it.
 
DST Bug

OllyW said:
Single event alarms still work correctly.

As it says in the first line of the report, it's alarms that are set to repeat which are the ones going off one hour late (or one hour early in the Southern Hemisphere).
Click to expand...

I'm in Colorado and mine went off an hour early...
 
Rocketman said:
When 10.6 rolls around I hope they keep 10.5.x as the primary OS and let folks OPTIONALLY boot into 10.6 (or make 10.6 calls) for tasks specific to it while stability issues are worked out through 10.6.3 at least.

Can we agree 10.5 wasn't really stable till .4 or .5?
Click to expand...
Fortunately for all, 10.6 has been released, and most people are using it without problems. :) I've actually never had any problems upgrading with 10.4, 10.5, or 10.6--but, then again, I'm hardly an early adopter. If you constantly have problems, perhaps you should consider doing the same. Has Apple ever allowed dual-booting with anything besides OS 9?

OTOH, I was quite and early adopter with Windows 7 because my job involved testing on it, and even that worked fine--save for the few apps that weren't written with post-Windows-95 security (read: any) in mind.
 
Mine was going off an hour early too. Weird considering I'm in AZ and we don't change time... Just changed it from a re-occuring event and all is good.
 
iCal Bug As Well

Has anyone noted that there's a bug in iCal regarding Daylight Savings Time?

If I create an event in iCal that starts at 5 and ends at 11, the event actually says 5:00 to 11:00 in the details, but in the day view, it shows that it ends at 10 - an hour earlier.

It only starts on the day clocks get switched...
 
hayesk said:
I have a real alarm clock. There's a bug in it. If I set it for 6:59am, it rings on time. If I set it for 7:01am, it rings on time. If I set it for 7:00am, it rings at 8:00am.

I guess, the solution is buy an analogue alarm clock, if you can find one.
Click to expand...

No, the solution is to go to bed earlier so you can try waking up on time.
 
Also, if DST is such a problem, I can't imagine what will happen once the climate changes and the seasons flip which will happen in due time. Winters will be 90 degrees and Summers will be 12, at least in Jersey.
 
hayesk said:
A someone who had to do time zone testing in the past, I can tell you that the DST rules are an absolute nightmare. Not everyone follows the same rules, they do change (as happened here a couple of years ago), so it's not surprising there is a bug.

That's not to take away the blame from Apple, but it's not as easy as you think.

But seriously, DST is unnecessary - time to get rid of it.
Click to expand...
But it's all in one place. We have had 50 years to lick this problem. It works in OSX and ios pre 4. Apple has known about it for weeks.

I agree that dst is archaic and needs to go.
 
My iPhone clock doesn't even work. If it syncs with the Apple server it's always set 2 days and sum hours ahead of the actual time. I have to use the clock on manual until a fix comes out, the upside is the DST bug didn't effect me!
 
KindredMAC said:
get a real alarm clock and don't rely on a phone.
Click to expand...

That's what I ended up doing. I got burned with my Windows Mobile Palm Treo twice. Sometimes the stupidest technology is the best... An alarm clock is built to 'alarm' at a set time. That's usually its only function. Mine plays the radio (what's that?) if I want, but you set it and forget it. I use my iPhone to time things like stuff in the oven and my workouts.

Time is all relative anyway, right?
 
hayesk said:
As someone who had to do time zone testing in the past, I can tell you that the DST rules are an absolute nightmare. Not everyone follows the same rules, they do change (as happened here a couple of years ago), so it's not surprising there is a bug.

That's not to take away the blame from Apple, but it's not as easy as you think.

But seriously, DST is unnecessary - time to get rid of it.
Click to expand...

Then throw in the whole leap year nonsense... I crashed my Windows Mobile Palm Treo by entering an alarm on February 29th. Hung the damn thing up tight. I had to reset it and then every time I went to 2/29 the thing would hang again. I called Palm and they knew about the issue and helped me blow my entire calendar away to 'fix' it. Once, in an early version of the Palm Desktop, it would crash too on leap year appointments. Talk about sloppy...

I haven't tried to set anything in iCal just out of habit with all of the issues that I've had over the years. I put the appointments in 2/28, JIC...
 
I was awoken just before 5AM by the taxi driver knocking the door followed by my '4AM' alarm which went off at 5AM. I managed to catch my flight with only minutes to spare.

I'm absolutely livid that Apple haven't put out a fix for this even though it was first identified as a problem weeks ago and has the potential to cause serious inconvenience.

An alarm clock just has to let you down once and you'll forever distrust it.
 
iSamurai said:
I love your satire + pun :D :D


Steve: We'll be giving away free alarm clocks to those affected. This is all blown out of proportion. Apple users are probbaly holding the clock wrong anyway.

Plus here's a list of other devices suffering from similar problems
Click to expand...

Fixed.
 
Wirelessly posted (Mozilla/5.0 (iPhone; U; CPU iPhone OS 4_0_1 like Mac OS X; en-us) AppleWebKit/532.9 (KHTML, like Gecko) Version/4.0.5 Mobile/8A306 Safari/6531.22.7)

NATO said:
I'm absolutely livid that Apple haven't put out a fix for this even though it was first identified as a problem weeks ago and has the potential to cause serious inconvenience.

An alarm clock just has to let you down once and you'll forever distrust it.
Click to expand...

Amen. I use a regular alarm at home, but when I'm away from home (ie on call at the hospital, at a hotel), I'll use the iPhones clock to wake me. If I overslept because of this bug I'd never trust the iPhone alarm again.
 
UK - I can confirm bug

I live in UK and today my alarm went off an hour later.

iOS 4.1
 
Very strange related issue!

I live in the United States. I like many other users here in the forums use my iPhone as my alarm clock. This morning my alarm was set for 7:30, it sounded at 6:30. No joke. Odly enough it seems that since 12:00AM Today any alarm that I set sounds an hour early. I hope this gets fixed as an hour of sleep to me is greater than most things. Anyone else have this issue. (I live in KY)
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back