Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
iOS 4.1 Daylight Saving Time Bug Strikes Europe
- Thread starter MacRumors
- Start date
- Sort by reaction score
. Think Different. Wake Up Early, even if you don't want to.
This has been happening to my girlfriend's iPhone for the past few days. We recently went on a trip from Mountain Time to Central Time so I wonder if that had anything to do with it. The trip correlated exactly to when the problem started.
I’ve suddenly had it start happening on my iphone, here in the US, and have been baffled about it.
I’m on a business trip in Arizona from Seattle, which are both on Pacific Time, so it didn’t make any sense.
Luckily it was an hour before I had to get up, rather than after.
I’m relieved that I’m not the only one that this is happening to.
.
I’m on a business trip in Arizona from Seattle, which are both on Pacific Time, so it didn’t make any sense.
Luckily it was an hour before I had to get up, rather than after.
I’m relieved that I’m not the only one that this is happening to.
.
Hmm. I don't know if this has been reported before, but apart from my alarm going off an hour late yesterday, today my alarm for a calendar event went off an hour early! This was a repeating event with a 15 minute warning, but I also noticed that the time of the event had moved too! Instead of 5-6pm as it has been for many years, through my Mac and previous iPhone, it has now been moved to 4-5pm. In fact all my calendar events have moved by an hour. For me, not too serious, I only use it to remind me when to leave work to go play football etc, but had it been a business meeting schedule, I wouldn't have been too happy. Anyone else notice anything similar?
The iPhone is becoming a joke
I have gradually upgraded through all the iPhone versions.
I now have a phone where the alarm goes off an hour late and emails display only in the list with their headers. No body.
Can't Apple fix the basic functions before going off designing some new sparkling bells and whistles???
Or perhaps I should just go back to my Palm Treo ... if Apple don't get their act together there will be a big market for little kits to convert your mini-sim-card into an ordinary sim.
I have gradually upgraded through all the iPhone versions.
I now have a phone where the alarm goes off an hour late and emails display only in the list with their headers. No body.
Can't Apple fix the basic functions before going off designing some new sparkling bells and whistles???
Or perhaps I should just go back to my Palm Treo ... if Apple don't get their act together there will be a big market for little kits to convert your mini-sim-card into an ordinary sim.
If you think I'm an Apple apologist, you haven't been paying any attention at all for the past few years
But I _am_ sympathetic to fellow overworked programmers.
You must not be a developer. It's one more coding path, due to different DST date calculations around the world.
The change in US DST didn't take effect until March 2007. I know from personal experience that a lot of places didn't update their code until the last second.
It was a mistake on the part of at least one person at Apple, sure. As I pointed out myself, this kind of thing happens because companies have downsized their test groups... and in Apple's case, they went cheap and constantly swap developers around between projects, which is not good for making bulletproof code.
I totally agree that they should've put out a fix immediately, once they knew about it. Can they even do small patches, or must they update the entire OS each time?
If you think I'm an Apple apologist, you haven't been paying any attention at all for the past few years
...
So sum it up apple is cheap.
My problem is the Alarm coding is lazy and piss poor coding on Apples part. It should be tied to the clock which from what I understand is updating just fine. Instead the Alarm needs its own DST with it. That is an example of lazy and crappy coding. It should of been updated with the rest of DST if it has to run on its own but in my mind the Alarm is going to be related direct to the local time and will have nothing to do with moving Time zones.
I would expect it if it was just errors with calendar events but this is the alarm clock. Needs to be with the system clock.
Besides it is really going to get screwed up in 4 months when we go from standard time back to DST. Also what about the people who do not follow DST. I can see them having issues with it in a week. What will apples excuse been then?
As I said lazy and piss poor coding is the cause of this.
Now I know why I have 3 alarms set in the morning just in case: 1st Gen iPod Touch on 3.1.3 set to go off first, iPhone 3GS on 4.1 set to go off 5 minutes later, and finally a Sony Alarm/Clock radio from 1989 that has a freakishly loud buzzer if the iProducts fail to ring
Gmt based time calculations
I'm not sure about the iOS but most mobile times and a great deal of enterprise systems store times based on GMT. For mobile devices this allows you to keep appointments when you move from time zone to time zone.
This complicates can complicate things a bit when checking scheduled events because these are not stored as absolute times based on the local time. Each check involves a calculation.
If there's a glitch in the calculation, like not having DST set properly, it will show up with each calc. The actual dates for DST are most likely implemented as calculations and not absolutes values.
It's still no excuse. These are well known exception events and should be part of an overall regression test suite. Have to go and check into the details n this one.
I'm not sure about the iOS but most mobile times and a great deal of enterprise systems store times based on GMT. For mobile devices this allows you to keep appointments when you move from time zone to time zone.
This complicates can complicate things a bit when checking scheduled events because these are not stored as absolute times based on the local time. Each check involves a calculation.
If there's a glitch in the calculation, like not having DST set properly, it will show up with each calc. The actual dates for DST are most likely implemented as calculations and not absolutes values.
It's still no excuse. These are well known exception events and should be part of an overall regression test suite. Have to go and check into the details n this one.
Does this glitch affect iCal at all? All my events in my iCal (MobileMe synced) are now an hour earlier than before. REALLY ANNOYING.
Anyone know when we can resume using our iPhones w/recurring alarms again? Like... Functionally working again?
Or is this unicorn 4.2 holding up the works.
Or is this unicorn 4.2 holding up the works.
the bug has been fixed since 7th November - it fixes itself.
Delete and recreate your alarms, thats all you need to do.
To clarify then, if I buy a new iPhone tomorrow and set up an alarm, will it go screwy next time the Daylight Saving switches? Or has the bug been fixed definitively?
I can't get too wound up about the bug itself, I think I mostly find it funny that Apple are incapable of setting an alarm clock. I gather it caused problems in Europe though.
