Your favorite Apple, iPhone, iPad, iOS, Jailbreak, and Cydia site.
iPhone Newsforums, a part of the
An iOS 4.1 bug that causes alarms to be one hour off after the "Summer" or "Daylight Savings" time switch hit European users this weekend . The same bug affected...
11-01-2010, 10:58 AM #1
No Daylight Savings Fix This Year?
An iOS 4.1 bug that causes alarms to be one hour off after the "Summer" or "Daylight Savings" time switch hit European users this weekend. The same bug affected New Zealand and Australian iOS users last month, as those countries went on Daylight Savings for the austral summer. At the time, Apple Australia indicated that the bug fix would be released soon, but it appears that we'll be waiting for iOS 4.2 in November... after the entire world has changed its clocks.
Specifically, the bug affects alarms set using the iOS 4.1 Clock app: recurring alarms set to repeat for anything other than "every day" will fail to make the shift between summer and regular time. For New Zealand (which made the shift to Daylight Savings Time on September 27) and most of Australia (which followed on October 3), this was a nuisance for people who use their iDevices as alarm clocks, as they were awakened an hour early. For users in the Northern Hemisphere, whose clocks "Fall back" in autumn, this means that alarms will be an hour late, which is potentially a more serious problem.
Apple has indicated that it's aware of the problem and has a fix in the queue, but it's surprising that they chose not to get the patch out for the millions of iPhone users in Europe, and it'll even more surprising if they are waiting until after the many more millions of US users set their clocks back. It's still possible that we'll see an interim release to fix the alarm bug and the lockscreen issue this week, but anyone in the US who relies on their iPhone to wake them up should have a backup in place next Monday.
11-01-2010, 11:39 AM #2
- Join Date
- Aug 2010
- Thanked 2 Times in 1 Post
Since the time change occurs on a Saturday night (technically Sunday morning), couldn't you just delete and recreate all your repeating alarms on Sunday and not have to worry about it?
11-01-2010, 11:56 AM #3
this happen to me too
this happen to me too on sunday morning, i had my alarm set for 6am to get up for work next thing you know i looked at the time and it was 5am i was like wtf! i live in the states so is not just over there that its happen to...
11-01-2010, 12:08 PM #4
11-01-2010, 12:08 PM #5
Maybe i'm just having a stupid moment, but how did this happen?
I had my iPhone alarm set for 10am, the time change (in Ireland anywho) happened around 2am, I noticed my Macbook & iPhone change back an hour automatically as I was still up at that time. My iPhone alarm went off at 10am like it was supposed to....am I missing something?
11-01-2010, 12:11 PM #6
So this doesn't apply to one-time alarms? I wake up at different times each day as I work random shifts, so my alarms are constantly changing.
11-01-2010, 12:13 PM #7
That's funny as all my alarms were 1 hr off all weekend and I live in California.
11-01-2010, 12:16 PM #8
I'm from the UK and I started back to college after a week off for Halloween. I set my alarm for 6:30, but today it went off at 7:30 lol. Lucky enough I woke magically around 7 which was just enough time for me to get ready. Now I have the alarm set for 5:30 so that it actually works!
iPad 2 16GB Wifi iOS 5.0.1 - Absinthe
iPhone 4S 16GB iOS 5.0.1 - Absinthe
11-01-2010, 12:27 PM #9
I am in the US Army in Germany and was an hour late getting up this am because of this. That miscue cost me 10 miles on the bike this afternoon. Apple = FAIL on this one. Steve Jobs, that person outside throwing eggs at your house is me. LMAO
11-01-2010, 12:33 PM #10
This def affected me also I had my alarm set for 6:30 AM CST and it went off at 5:30 am CST it cost me a half hour of sleep trying to figure out wtf had happened. = ANGRY!! At least I know i'm not the only one I was about to restore my idevice.
3GS on 4.1
The Following User Says Thank You to nkgneto For This Useful Post:
11-01-2010, 12:50 PM #11
My alarms went off an hour early this morning too (Alaska). The time on the phone was (4:20), the time in the alarm app was (5:20). My wifes however did not have this problem. Took a while to figure out what was going on. Weird!
11-01-2010, 01:04 PM #12
This is why I use an alarm app, and not the built in alarm. No worries that way!
11-01-2010, 01:07 PM #13
my alarm woke me up an hour early and i started freaking out thinking my clocks were all messed up. nothing better then being half asleep and trying to make sense of the situation
11-01-2010, 01:51 PM #14
iPhone 4 on 4.1, my scheduled alarm that should go off at 7.15am went off at 8.15 am today (UK) - fortunately for me I don't get to sleep past 6am at present because mini me wakes me to feed him - but you would be peeved if this coding cock up made you late for work. And what sort of sense can be made of alarms going off an hour early in the US when they haven't even had a time change yet!
11-01-2010, 01:58 PM #15
Does doing a hard reboot do anything to solve the problem?
11-01-2010, 02:37 PM #16
11-01-2010, 02:38 PM #17
Those effected by this, can you please confirm, if you create a new alarm, does that work fine or the whole alarm app itself is 1 hour off until the next patch?
11-01-2010, 03:26 PM #18Let's go Red Wings!
11-01-2010, 03:58 PM #19
The issue is that the time change WAS the last Sunday in Oct but this year has been changed to the first Sunday in Nov. Thus the iPhone set itself back 1 hour for some people. I live in the US and mine did not.
11-01-2010, 04:36 PM #20
I found a quick easy fix for this for people in the UK.
settings, general, date and time, change timezone to Cupertino, then soft reset.
iPhone 4 resets back to London timezone automatically and alarm works fine.
iPhone 3g needs a little help and needs reset back to London timezone manually but works fine after that!
hope this helps folks.