This is not the first time we’ve reported on problems that iOS devices seem to have with the Daylight Saving Time clock shift. Indeed it seems to be a recurring theme and we might have imagined that Apple could have sorted these issues out by now. However we have news that iPhone users have had clock problems again, this time with Daylight Savings 2012.
As we said previously this seems to be a habitual problem every time clock changes need to be made and indeed we’ve previously referred to the issue as Apples’ Achilles heel. No doubt many people were hoping that the same problems wouldn’t occur this time around but alas it seems that plenty of people have had problems. Twice a year when the clocks change, strange things start happening to iOS devices and there have been previous reports of frustrating alarm blunders and also Siri seems to have been confused about when exactly Daylight Savings was occurring this year.
Athough you may have imagined that these sort of bugs would have been ironed out by now with regular iOS updates, the problems it seem still go on. TUAW reports that some of its readers said their clocks went back an hour instead of forwards at the weekend. Meanwhile there seems to be another problem with picking up user locations as one reader’s iPhone thinks they’re on Mountain Time even though they live in Nashville while another user’s phone thinks it’s in Chicago when they live in Florida.
As TUAW says, these glitches are probably easily solved by simply restarting the device or switching the timezone automation on and off but that’s really not the point as Apple should have sorted out these issues by now and to be frank we’re surprised it hasn’t. We’d like to get an idea of how widespread the problems are so would like hear from any of you out there who have been affected by the clock iOS glitch. What irregularity occurred with your iOS device and what is your location? Do you feel that Apple should have smoothed this out by now?