QUOTE(Alan @ 11-6-10, 8:32am) [snapback]1126986[/snapback]
I think it's the alarm app that doesn't recognize the time change. So, if the phone's time is automatically set back 1 hour and the app doesn't recognize it then the alarm will go off an hour late.
But if the alarm app doesn't recognize the time set back, then (if it is set to 8:00AM) tomorrow morning it will go off at 8:00AM alarm time, which will actually be 7:00AM phone time. The only way it could be an hour late would be 1.) during the Spring ahead time change. Or 2.) if the alarm thinks that the phone's set back time is still DST ON and sets itself back another hour. So at 8:00AM Sunday morning on the phone the alarm thinks it is really 7:00AM and so doesn't sound the alarm until 9:00AM phone time. But that would mean that each time app had to set itself back individually as opposed to setting themselves to the main phone's clock time. And for 2.) to happen the alarm would have to be looking at the phone's time and then setting itself back another hour from what it finds there meaning a 2 hour adjustment.
This news comes after iPhone users in Australia and Europe reported problems with their alarms ringing late after time changes on those continents earlier this year.
That quote seems to refer to the Spring time change "earlier this year". It still seems to me that this time they would be 1 hour early.