by Michael S. Kaplan, published on 2010/11/07 07:01 -05:00, original URI: http://blogs.msdn.com/b/michkap/archive/2010/11/07/10087230.aspx
I didn't have any problems waking up at the time I thought I would be waking up.
You may not have been so lucky.
Though I had a few things in my favor:
But perhaps you were not as lucky.
I also had some celebrities warning me about the problem in case I did have an iPhone and it was my alarm clock and I forgot about that blog last week:
Thanks Alyssa! :-)
A part of me was hoping that Apple would get a hotfix out sooner since pulling in the iOS 4.2 update sooner would have been so much harder. But I guess they decide they would rather just take the hit and have a little widespread bit of trouble in their biggest (or at least their loudest!) market.
Perhaps this will get Apple into that same mode about taking these issues more seriously that they have largely been able to avoid, which I think would be good thing, for everyone. Even though they are technically the competition, I haven't ever really viewed them in exactly that way, and even if I did I'd rather generate interest on the merits of my products, not depending on the screwups or mistakes of others.
But that's just me, I know that opinions will vary.
Anyway, hope you didn't find yourself up an hour late, and hope you have removed your recurring alarm for tomorrow if you have one, like the instructions request.
And finally, I hope the iOS 4.2 update doesn't brick your phone (a friend of mine said the 4.1 update had that effect on her phone, a rather abrupt way to prove to her in light of these DST issues the truth of the old truism better late than never)....
Pavanaja U B on 7 Nov 2010 7:00 PM:
Steve Jobs himself got affected by the daylight savings bug in iPhone. read his tweet - twitter.com
Michael S. Kaplan on 7 Nov 2010 8:38 PM:
Well, one of his pretenders, at least. :-)
Random832 on 8 Nov 2010 6:52 AM:
Wait a minute...
It's fall. So the clocks got moved back an hour. So if a particular clock [whether an iphone or an ordinary alarm clock] _failed_ to be moved back, it will claim it's [e.g.] 7:00 when the time is actually [moved back to] 6:00. So wouldn't you actually be getting up an hour early?
Nicolas on 19 Nov 2010 8:22 PM:
Meh. This is newsworthy? Apple didn't *ever* update either iOS nor Mac OS X to all the DST mess in Argentina. I still have my iPod touch set to a different country that happens to have the correct UTC offset. And I got one hour late to somewhere twice (in different months, at the beginning and end of DST).