iPhone Alarm Bug Leads To Mass European Sleep-in
nk497 writes "A flaw in the alarm clock in iPhone 4s gave Europeans a bit of a lie-in this morning. While the Apple handsets automatically adjusted to daylight savings time, a bug in the alarm system meant many were woken up an hour later than they should have been, after clocks rolled back over the weekend. Annoyingly, Australia was hit by a similar problem last month, but Apple failed to fix the problem or even warn users. American Apple fans, consider yourselves warned. The iOS4 bug can apparently be avoided by using one-off alarms, rather than pre-set regular wake-up calls."
What a bunch of whiners. Apple tries to do something nice for you, give you a little more time in the morning, and this is how you thank them?
Dislike the Electoral College? Lobby your state to join the National Popular Vote Interstate Compact.
my girlfriends 3gs (running iOS 4.x) had the same bug this morning.
Fortunately, my $99 android phone woke us up at the right time
I am sure that Apple will fix it shortly, then patent alarm clock apps for mobile phones that adjust automatically for daylight savings.
The real bug is that we change the time at all, considering all the problems it brings.
Not one comment yet about the real culprit here: daylight savings time. If we didn't have it anywhere in the world, then programmers wouldn't have to worry about when DST happens in different timezones (or which places have DST and which don't), or worry about what to do with log files or anything else when time jumps an hour.
Someone remind me please what we're saving? It's not electricity, because we use lightbulbs before sunrise and after sunset in summer and winter.
I don't know anybody under the age of thirty who doesn't use their phone as an alarm clock.
I support the Slashcott and will not be reading or commenting from 2/10/14 to 2/17/14. Beta is steaming pile of dog shit
I see a lot of posts with hate for DST.. that's fine, I'd be happy if it were abolished as well.
But now back to there being a bug in how the alarm thing is handled on the iPhone. How does that bug even exist?
If the alarm is set for a particular time, say "7am".. then what does it matter whether or not the clock went back an hour at 3am?
I can understand the alarm app going a bit batty if the clock went back at 8am (essentially the alarm going off -twice- that day), but given the actual circumstances... how did the alarm decide that it should instead be going off at 8am? The clock, presumably, does give the correct time.. so it's not like its internal time functions don't know what time it actually is. I'm confused. Is this just some manner of shoddy coding going on?
What's worse is how Apple is handling it... i.e. 'not'. Most of America (some states ignore DST already) is up for its DST change next week. I guess most people are now warned by the media attention (where was that when it was NZ / AU?).