I noticed when daylight savings came in the phone had updated the time to an hour forward as it should. But this morning my alarm woke me an hour early at 5:15am instead of 6:15am. I checked the setting and it WAS set for 6:15am! Now yesterday I also updated from I think 4.0.1 to 4.1 so unsure if it was the daylight savings change or the update that has made my alarm change as this is the first working day since both.
So, any ideas or others with the same trouble?
Toshiba Satellite A100,
Windows 7,
iPhone 3G - OS 4.1
Yeah, same again this morning after trying a reset yesterday :S
Kinda glad to see I'm not the only person here that has this problem!! 😀
I've sent feedback now so added to the pressure.
I read an article about this yesterday, and wanted to share it so you can read it if you'd like. I hope they get this fixed for you guys soon! The U.S. goes back to standard time in November, and I'm wondering if this bug will affect our phones. I guess we'll see!
So far I have tested this on my iphone 4 ios 4.1,
Using the clock app if I set an alarm with no repeats, it goes off on time.
If I set it to repeat even one day it goes off an hour early.
This occurs regardless if I have time set automatically or not.
And with restarts between.
I live in Auckland New Zealand, and have the time zone set to this.
I changed my time zone to Detroit (random city).
Turned off automatic setting.
Changed the date and time to my home town time.
Restarted.
And set an alarm, recurring, and it goes off fine!
Changed time zone back to Auckland,
Set time and date back to my current time.
restart.
So far I have tested this on my iphone 4 ios 4.1,
Using the clock app if I set an alarm with no repeats, it goes off on time.
If I set it to repeat even one day it goes off an hour early.
This occurs regardless if I have time set automatically or not.
And with restarts between.
I live in Auckland New Zealand, and have the time zone set to this.
I changed my time zone to Detroit (random city).
Turned off automatic setting.
Changed the date and time to my home town time.
Restarted.
And set an alarm, recurring, andit does not go.
So I set an alarm to an hour from now (with a minute to spare).
And it goes off an hour early.
It's an odd bug indeed.
And did just start with daylight savings.
This looks to be some weird line of code error that deals with alarms and DST.
Those who say they have not found this problem I would be keen to hear from you.
Have you set your home timezone, are you using the clock app for alarms.
My solution now is to set important alarms in calendar.
Though then my computer will no doubt give me alarms when I wake it at work (the one sync'd to my iphone).
I’m sure most NZ’ers with IOS4.1 will be experiencing the issue as long as they have the device set to NZ times and the alarm is the repeat kind.
I've talked with apple and they can repeat the bug. It’s too early to expect Apple to announce that they are working on a fix but I’m sure that will happen soon.
At least we know they know so now you know they know (sorry for that)
Do use the email address from one of the threads above to email a bug feedback form to Apple. It’s easy to fill in. The more feedback they receive the more attention they will give to the bug.
I live in Queensland, Australia. My state does not observe daylight savings, but the rest of the east coast does. My iPhone 4 (4.1) alarm went off an hour earlier this morning (beginning of daylight savings). Time was correct, alarm was early, and after slide-to-stop, the alarm was still showing as set in Clock/Alarms. An iPhone 4 synced to a WinPC did not have this problem.
It was not a recurring alarm. Turning off Set Automatically in Date & Time seems to have solved the problem, but I would prefer Set Automatically working.
I live in Queensland, Australia. My state does not observe daylight savings, but the rest of the east coast does. My iPhone 4 (4.1) alarm went off an hour earlier this morning (beginning of daylight savings). Time was correct, alarm was early, and after slide-to-stop, the alarm was still showing as set in Clock/Alarms. An iPhone 4 synced to a WinPC did not have this problem.
It was not a recurring alarm. Turning off Set Automatically in Date & Time seems to have solved the problem, but I would prefer Set Automatically working.
Recurring alarms that were set prior to the Daylight Saving switch went off an hour later than intended.
Recurring alarms that have been set since Daylight Saving began, go off one hour earlier than the time they are set for.
Therefore, any recurring alarms have to be set one hour later than the required alarm until the software update arrives. e.g. to wake at 5:15 on weekdays, I set my recurring alarm for 6:15. etc.
Yeah my alarm woke me at 5am instead of 6am.
Another poster said that it won't trip at the real time.
Apparently workaround is to turn off the repeat function and turn back on.
Interesting that it might be tied to the start and finish of DST in different years.
Canberra has the same problem. If I don't set the repeat it will go off at the right time; if I do it is an hour early and deleting and resetting all of the alarms does not make any difference.
Yup, my iPhone 3GS running 4.1 woke me up an early this morning too!
I had it set for 6.30am, and it stupidly sang at 5.30!
I have had nothing but pain with iOS 4, which seems to break more existing features that provide new ones!
This is the last straw for me, I'm switching to an android phone after my contract finishes. I
t's not that I expect an android phone to be flawless, I'm done giving my money to apple.
Another here in Brisbane, QLD where we don't observe Daylight Savings. on 3GS running latest iOS.
Yesterday (03/10/10) My clock skipped ahead 1 hour at around midday. It then woke me up at 4:30 am (Clock said 5:30, alarm was set for 6:30). I then turned the phone on and off and the time reset to 4:30am. The alarm then went off again at 5:30, did the same deal, the alarm didn't go off at 6:30.
Just had a workmate walk in and he's described the same problem on his 3G.
He's also saying that he switched his alarms off and on and it seemed to fix the problem. I'll give it a go today and see what happens.
Apple, please fix ASAP. I'm a little wary of setting my alarm an hour later as this problem could fix itself and then I'm up the creek again...
