No, January 1st is NOT when the i Phone alarm problem hit -- Apple has known about this problem since it first showed up on iPhones in New Zealand in October. see this Apple Insider report from last November:
"The new support document [<http://support.apple.com/kb/TS3542>]*, published on Wednesday [11/03/10], comes days after Apple made headlines with an iPhone bug that caused repeating alarm clocks to go off late across Europe. The issue occurred because of a change from daylight saving time, and could repeat itself in the U.S. on Sunday when America concludes daylight saving.
Apple's documentation notes that users can resolve the issue by setting the repeat interval on an alarm to "Never." If users reset their alarm every day, the daylight saving bug will not affect them.
The support note says that after daylight saving ends in the U.S. on Nov. 7, users will be able to set their alarms to repeat again. The iOS issue affects the iPhone 4, iPhone 3GS, and iPhone 3G, as well as the fourth-, third- and second-generation iPod touch models.
In October, the same bug caused alarm clocks in New Zealand to go off an hour early. Apple said it was aware of the issue and had already developed a software fix, but it has not yet been released.
This week, Apple released the golden master of iOS 4.2, the next software update for the iPhone, iPod touch and iPad, to developers. Golden master status suggests that the software is finalized and a release to the public is imminent. It's possible that Apple could release the software update before this Sunday, allowing users who update their iPhone to iOS 4.2 to avoid the daylight saving bug."
*Apple Support doc: <http://support.apple.com/kb/TS3542> posted November 3, 2010, which said:
"Symptoms
In some regions, shortly before or after the daylight saving time (DST) change, repeating alarms created in the Clock app may work incorrectly.
Products Affected
iPod touch (2nd generation), iPod touch (3rd generation), iPhone 4, iPhone 3G, iPod touch (4th generation), iPhone 3GS
Resolution
To resolve this behavior for existing alarms, set the repeat interval to Never. You will need to reset these alarms for each day you need them.
After November 7th, 2010, you can set your alarms to repeat again"
NB: This Apple Support doc was posted 11/03/10, and has not been updated since.
----------------------------------------
But the problem didn't "fix itself" on 11/07/10, after the DST change, and it didn't fix itself today, January 3, 2011 -- Apple's next promised date that the iPhones would "fix themselves," -- as both my daughter in CT, and my son-in-law in KC, KS can attest: their iPhone "wake-up" alarms both went off an hour late, in different time zones.
----------------------------------------
Want more on "No kidding, Jan. 1 is when the problem hit. Jan. 3 it goes away?" Try these:
Computerworld IT Watch
iPhone alarm clock glitch: Still not working; iOS bug FAIL
By Richi Jennings. January 3, 2011
Despite Apple's promise that it would fix itself by today, the iOS alarm clock glitch is still making pomaceous owners oversleep. iPhone and iPod Touch alarms stubbornly persist in not working due to yet another bug with alarms. In IT Blogwatch, bloggers rub their eyes in disbelief.
From SkyNews, 01/03/11
An Apple spokeswoman released a statement to Macworld on Jan. 2 saying it was aware of the problem and that the alarm on the £499 ($773) handset would begin functioning normally again Monday.
However, the firm has yet to release a further statement on the problem.
Read more:
http://news.sky.com/skynews/Home/Technology/iPhone-Users-Say-Alarm-Clocks-Yet-to -Be-Fixed/Article/201101115878764
from CNNTech, 01/03/11 ,
http://www.cnn.com/2011/TECH/mobile/01/03/iphone.alarms.mashable/index.html?hpt= Sbin>:
"Apple said yesterday that the failure of its clock app only happens when you set a one-time alarm, and it will somehow fix itself on January 3.
"We have made a call and sent an e-mail into Apple asking why this happened."
----------------------------------------
From PC Magazine: <http://www.pcmag.com/article2/0,2817,2374971,00.asp>:
"iPhone Alarms Still Silent On January 3 "Self-Fix" Date"
"Just two days ago, we reported about a frustrating glitch for those using various permutations of iOS 4 on Apple's iPhones—specifically, an annoying bug that was preventing one's mobile alarm from ringing on either day.
"The bug allegedly only affected single alarms set for either January 1 or January 2. According to Apple itself, the company was aware of the issue and was advising users of a crafty workaround—setting recurring alarms for either day, which would bypass the issue for whatever reason. And according to said Apple spokesperson, the bug would allegedly go away on its own come January 3.
Or so we all thought.
"Reuters is now reporting that some iPhone users are indicating that the alarm issue persists, a claim that's being slowly backed up by affected users' Twitter posts."
----------------------------------------
Washington Post 01/013/11:
<http://voices.washingtonpost.com/fasterforward/2011/01/iphone
alarm_problemspersist.html?wprss=fasterforward>
"iPhone alarm problems persist
By Hayley Tsukayama
Call it Y2K-11. When a bug kept iPhone and iPod touch alarms from sounding on Jan. 1 and Jan. 2, Apple suggested that those having trouble should set recurring alarms, and that the alarms would fix themselves by Jan. 3, the first work day of 2011."
----------------------------------------
Yahoo News, UK & Ireland, 01/03/11: <http://uk.news.yahoo.com/22/20110103/ttc-uk-apple-asia-fe50bdd.html>
"Some iPhone users in Asia and Europe complained of malfunctioning alarms on the first working day of 2011, even after Apple reassured users that its phones' built-in clocks will work from Monday.
"Bloggers, Facebook and Twitter users complained they missed flights or were late to arrive at work, as the alarm built into Apple's iPhone failed to go off for a third straight day for some users."
----------------------------------------
BBC: <http://www.bbc.co.uk/news/technology-12104890> 10/02/11, updated 09:14 ET 01/03/11:
iPhone alarms hit by New Year glitch
Setting New Year single alarms was to no avail
A glitch on Apple's iPhone has stopped its built-in alarm clock going off, leaving many people oversleeping on the first two days of the New Year.
Angry bloggers and tweeters complained that they had been late for work, and were risking missing planes and trains.
Apple has acknowledged the problem and says it will be fixed by 3 January.
The reason has not been given but the glitch appears to affect single alarm settings on the iPhone 4 and earlier models with software updates.
“According to the company, the problem will resolve itself on 3 January, but that is two days late for many people”
Jonathan Fildes
BBC Technology reporter
A similar problem hit the iPhone alarm when the clocks went back in November, again causing many users to be late for work or for transport arrangements.
"We're aware of an issue related to non-repeating alarms set for January 1 or 2," Apple spokeswoman Natalie Harrison said in a statement quoted by Macworld.
"Customers can set recurring alarms for those dates and all alarms will work properly beginning January 3."
'Two days too late'
"BBC Technology reporter Jonathan Fildes says the problem is embarrassing for Apple, not only because of previous problems that came to light when the clocks changed, but because the company prides itself on the simplicity of use of its products.
"This seems like another simple error, but it cannot afford to have too many before its reputation becomes tarnished, he says.
"Apple should have learnt from that example and seen this one coming, he adds. According to the company, the problem will resolve itself on 3 January, but that is two days late for many people.
"More than 1.7m people around the world had bought iPhone 4 handsets by June 2010, in what was the company's most successful product launch."
DEAR APPLE DISCUSSION GROUP MODERATORS:
This is not a rant, I'm simply reporting the news regarding the situation with the iPhone Alarm function as it stands this morning, 01/03/11. People claiming that this was a new problem as of 01/01/11 are simply wrong, as your own TS doc <http://support.apple.com/kb/TS3542> of November 03, 2010 clearly attests.
It would certainly be helpful to know the latest Apple timetable for the iPhone alarm problem to "fix itself," or if Apple has managed to come up with any workarounds, other than the third-party alarm clock apps that are available for the iPhone.
Best of luck.
Bart Brown
