“Users of Apple’s iPhone 4 mobile phone could be forgiven for arriving late in to work this morning – an apparent bug in the phone’s software prevented the handset’s alarm function from working correctly,” Claudine Beaumont reports for The Telegraph.
“Although the time on the iPhone 4 automatically updated when the clocks went back at the weekend, it seems the alarm function didn’t, resulting in scores of people being woken an hour later than they had intended today,” Beaumont reports. “A similar bug affected iPhone 4 users in Australia and New Zealand when clocks switched from Daylight Saving Time last month”
Beaumont warns, “The glitch could strike again next week when the United States adjusts its clocks to mark the start of winter.”
Full article here.
MacDailyNews Note: Daylight Savings Time in the U.S. (except for Arizona and Hawaii which do not observe it) ends on the first Sunday of November (Nov. 7th, this year). Winter officially begins on December 21, 2010. The United States does not adjust its clocks to mark the start of winter.
Flew from San Francisco to London one day. Had switch from Daylight Savings Time the next day. Headed to Paris with the time zone change the next day.
For some reason, my iPhone switched flawlessly and the alarms went off on time. My girlfriend never even noticed the time changes.
Flew from San Francisco to London one day. Had switch from Daylight Savings Time the next day. Headed to Paris with the time zone change the next day.
For some reason, my iPhone switched flawlessly and the alarms went off on time. My girlfriend never even noticed the time changes.
What’s the problem?
I live in London everything worked just fine. No problem with time updating.
iOs 4.1 (8B117)
Am I just lucky or what is everybody else doing wrong!
What’s the problem?
I live in London everything worked just fine. No problem with time updating.
iOs 4.1 (8B117)
Am I just lucky or what is everybody else doing wrong!
First, Apple needs to catch this kind of software bug in functional testing.
Second, I vote to end daylight savings time. Arizona and Hawaii get by fine without it. The rest of us could, too.
First, Apple needs to catch this kind of software bug in functional testing.
Second, I vote to end daylight savings time. Arizona and Hawaii get by fine without it. The rest of us could, too.
This morning in Redmond WA I all my daily iPhone 4 reoccurring alarm that read 5:30am woke me up an hour early at 4:30am! Can I rely on my my iPhone alarms working correctly tomorrow morning? Is there a fix?
This morning in Redmond WA I all my daily iPhone 4 reoccurring alarm that read 5:30am woke me up an hour early at 4:30am! Can I rely on my my iPhone alarms working correctly tomorrow morning? Is there a fix?
@cclements: No one’s complaining about “time updating”. They’re complaining about previously-set alarms not operating at the (new) correct time.
@cclements: No one’s complaining about “time updating”. They’re complaining about previously-set alarms not operating at the (new) correct time.
There is only one daylight saving, not multiple savings:
http://en.wikipedia.org/wiki/Daylight_saving_time
There is only one daylight saving, not multiple savings:
http://en.wikipedia.org/wiki/Daylight_saving_time
This is a puzzle. When you switch from daylite saving to standard time you gain an hour. The alarms would have woken everyone up early not late.
As you go to daylite savings you lose the hour so Australia and NZ most certainly had alarms go off 1 hour late.
So how is it that users in Europe would be late?
Strange article. Sure the bug exists but at least get the detail right way round. For whatever reason it did not effect me in the slightest while i was in NZ for the change and back in australia the week after. No fuss. No pain…
This is a puzzle. When you switch from daylite saving to standard time you gain an hour. The alarms would have woken everyone up early not late.
As you go to daylite savings you lose the hour so Australia and NZ most certainly had alarms go off 1 hour late.
So how is it that users in Europe would be late?
Strange article. Sure the bug exists but at least get the detail right way round. For whatever reason it did not effect me in the slightest while i was in NZ for the change and back in australia the week after. No fuss. No pain…
Does this mean iOS 4.2 this week?
Hmmmmmm……
Does this mean iOS 4.2 this week?
Hmmmmmm……
@Michael Dickson, please think before you type.
Think about Australia and New Zealand. The day before, real time, phone time and alarm time are the same. Perhaps the alarm is set to go off at 0700 each morning.
Jump forward a day. At 0300 real time and phone time suddenly jump to 0400 but the bug does not shift alarm time which still thinks it’s 0300.
A few hours later, real time and phone time show 0700 but the alarm is set to go off at yesterday’s 0700 which, today, occurs when the phone says 0800
@Michael Dickson
Ooops…I should take my own advice.
I just thought more about what you typed and you’re absolutely right.
Of course Aussies and Kiwis would have been woken an hour late. The Telegraph is wrong in telling us that Europeans were woken an hour late, they would’ve been woken an hour early!