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

MacRumors

MacRumors

macrumors bot
Original poster
Apr 12, 2001
66,361
35,431



093441-ios_clock_icon.jpg


Several weeks ago, we noted that users in New Zealand and Australia had discovered a bug in iOS 4.1 that caused recurring alarms to go off an hour early after those countries switched to daylight saving time beginning in late September.

At the time, Apple representatives in Australia reported that the bug would be addressed in an upcoming software update, which many users had hoped would be a quick iOS 4.1.1 fix rather than having to wait until iOS 4.2 sometime this month. A fix has yet to appear, however, and with the UK and other European countries ending daylight saving time this weekend, the bug is striking a significant new population of users.

And with European users ending daylight saving time as opposed to the earlier groups in the Southern Hemisphere that were beginning daylight saving time, the bug means that European users are seeing their alarms go off an hour late.

Daylight saving time ends in the United States and Canada on November 7th, setting the stage for a fresh spate of oversleepers if Apple does not provide an iOS update this week.

Article Link: iOS 4.1 Daylight Saving Time Bug Strikes Europe
 
Article Link
https://www.macrumors.com/2010/11/01/ios-4-1-daylight-saving-time-bug-strikes-europe/
I was aware of the bug. However, I forgot to do anything about it. Luckily I woke up naturally before that time anyway. I can only imagine the amount of people who overslept.
 
Aww man.......Am I going to have re-jailbreak all because of a stupid DST bug? Screw it, I'll just be an hour off my appointments until spring rolls around.
 
I remember this being mentioned but didn't actually notice anything different on my phone. Although, I did set my alarm AFTER the clocks went back, not before.
 
I just tested this in the UK with my iPhone 4 running 4.1

Set the alarm for 1340 at 1339 and a minute later the alarm went off...

Sorry guys I misread the recurring alarm as recurring problem with the alarm. Shouldn't speed read!
 
jamojdm said:
I just tested this in the UK with my iPhone 4 running 4.1

Set the alarm for 1340 at 1339 and a minute later the alarm went off...
Click to expand...

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).
 
OllyW said:
I was already aware of the bug so I changed my alarm settings to go off one hour earlier. :)
Click to expand...

Smart Arse! :p


I figured it out on Sunday morning when the alarm didn't go off at the correct time, but didn't do anything about it for this morning.
Fortunately Tilly woke up only 5 mins after the alarm was meant to go off...
 
I have read that if you clear your alarms and set them up again it will be fixed.
 
Has anybody else had their phone randomly changing time when on "set automatically"? I turned it off becuase it kept going forward and then back one hour
 
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...

Ah I misread that as it being a recurring problem, not a problem with the recurring alarm. I'll continue to set my daily alarm then!
 
I had this problem this morning... I blamed it on myself thinking I'd mistakenly changed the time of the event.
 
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