Considering that the Final GM build of OS 4.2 has been released, Apple is really stupid for not actually distributing it--then they wouldn't have to fumble around with "workarounds" for this bug.
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.
Apple Support Acknowledges iOS 4.1 Daylight Saving Time Bug
- Thread starter MacRumors
- Start date
- Sort by reaction score
It's hilarious that a simple algorithm that doesn't tax the digital watch given away if you express an interest in the latest pension plan is too much for a smartphone (i.e. very powerful mobile computer). Thank God Apple software isn't used to run run anything important like nuclear industry, or bus timetables. I do give them credit for their solution though. Balls of steel at Apple... Balls of steel...
Apple really need a way to push out minor software updates without having to use iTunes/go through the whole process of downloading the whole .ipsw file.
Kind of like the small security updates you get on Mac OS X - the iPhone could have an over-the-air minor updates feature as an app on the device itself? That way minor things could be patched straight away, rather than wait for the next release...
Kind of like the small security updates you get on Mac OS X - the iPhone could have an over-the-air minor updates feature as an app on the device itself? That way minor things could be patched straight away, rather than wait for the next release...
I think it'll be out next Monday, one week on, and they've released updates on a Monday before haven't they? So seems sensible...
Absolutely - it's around 600MB for the iPhone 4 or iPad, that's huge, especially when you're downloading both (or is it universal?), anyway, it's ridiculous, I know they do it so that people don't need to download the latest software all the time, but presumable, iTunes could detect what software version the phone's on, and then choose what it needs to download, a series of smaller files if the devices OS is only a couple of minor versions old, or a big ipsw if its a big update (eg. 4.0) or iTunes detects the ipsw is smaller than the series of smaller updates.
These small updates would also enable able to plug silly bugs like this, or block a jailbreak etc without having to download a huge file just to fix something so small.
Absolutely - it's around 600MB for the iPhone 4 or iPad, that's huge, especially when you're downloading both (or is it universal?), anyway, it's ridiculous, I know they do it so that people don't need to download the latest software all the time, but presumable, iTunes could detect what software version the phone's on, and then choose what it needs to download, a series of smaller files if the devices OS is only a couple of minor versions old, or a big ipsw if its a big update (eg. 4.0) or iTunes detects the ipsw is smaller than the series of smaller updates.
These small updates would also enable able to plug silly bugs like this, or block a jailbreak etc without having to download a huge file just to fix something so small.
Last edited:
Each type of device has a different file - iPad, iPhone 4 and iPhone 3G (all of which I have) all need a different version. That said 4.2 is somewhat less than 600 MB... though I'd need to open my mac to check.
True patches are extremely difficult to manage.
For big releases, this big one for the iPad, they like to have a large amount of the apps updated first. Developers are submitting their apps now.
I'm thinking the same. Apple are saying this is fixed on the 7th - because the US switch to day light savings - so everyone (Europe, Oz, NZ etc) will have working repeating alarms.
4.2 (can ship whenever) will (hopefully) have a fix to resolve the actual bug so that when the clocks change next spring repeating alarms will not be affected.
Interestingly (IMHO) the US change first next year - March 13th, so the issue is unlikely to occur until the Ozzies and the Kiwis test it again on October 2nd...you guys might want to set a calendar alarm now
Well according to this Crunchgear,
(http://www.crunchgear.com/2010/11/03/how-to-try-4-2-on-your-ipad-right-now/)
Which is HUGE! And they may be difficult, but if there's any company that can make something difficult, easy - it's Apple.
Likely from the same department that came up with the idea of telling users to hold their iPhone 4's differently or put a case on it, to mitigate an obvious design flaw.
Not really a big deal!!
My alarm was the same after DST
BUT you don't have to do the alarm manually (well i didn't) to get it working again.
The problem is/was my iphone alarm was set for 7am and it goes off at 8am so i just set the alarm for 6 and its back to going off at 7!
Easy
Then when apple bring out a fix I'll change it back to 7.
My alarm was the same after DST
BUT you don't have to do the alarm manually (well i didn't) to get it working again.
The problem is/was my iphone alarm was set for 7am and it goes off at 8am so i just set the alarm for 6 and its back to going off at 7!
Easy
Then when apple bring out a fix I'll change it back to 7.
So, that's why my new iPhone is waking me up an hour early, despite all times matching and correct. How annoying.
So apple basicly admits that it screws up but it still does not cover the fact that this is a mistake that should of NEVER of happen.
It is a huge example of sloppy and lazy ass coding. This would be really only 4-5 lines of code to fix but if you start having sloppy coding it makes it very hard to fix.
Apple cause other companies lazy. They might want to look at themselves because this bug is a great example of lazy.
It is a huge example of sloppy and lazy ass coding. This would be really only 4-5 lines of code to fix but if you start having sloppy coding it makes it very hard to fix.
Apple cause other companies lazy. They might want to look at themselves because this bug is a great example of lazy.
Bugs, like other things, happens. However, that is only a small part of the story. What is more at issue is that ACE did not release a patch to the issue, that was known WEEKS AGO. ACE was asleep at the wheel, and its users paid the price.
Bugs happen. This is a low priority issue - an annoyance - there is no loss of data and there are two simple workarounds. Personally I find it amusing that such a 'great' company as Apple can make mistakes like the rest of us. I also found it interesting that it was missed by both dev and test.
I have had issues with timezones etc in products that I have worked on. It is a complicated area, it is easy to make assumptions that are not true.
My only disappointment has been the time it appears to have taken Apple to acknowledge the problem. This first issue occurred weeks ago but it seems to have taken until the Europeans started complaining for it to be acknowledged. If true that sucks.
I am waiting for someone to loose their job for oversleeping and then sue Apple for loss of earnings for not waking them up correctly.
I would have thought the bug was low severity but high priority since it effects everyone that uses their phone to wake up in the morning. To me "After November 7th, 2010, you can set your alarms to repeat again." sounds like they are not bothering to release a fix at all this year but that it will start working on the 8th due to that nature of the bug. Basically giving the finger to everyone in effected countries.
After hearing about this I decided to do some tests. So yesterday I set three alarms: all for Sunday morning wanting them to go off at 7:45. 1) 7:45 no repeats, 2) 7:46 with repeats everyday, 3) 6:44 with repeats. This morning they all went off exactly as they were set. It appears maybe this issue might not affect all iPhones. I am iPhone 4 with 4.1.