- Credits
- 51,755
The bells weren't ringing for many iPhone users this New Year's weekend, when thanks to a glitch the alarms on Apple's iconic mobile phones failed to go off, causing many to oversleep.
It was the second time in just a few months that the alarm function on the phone failed to activate correctly, prompting an avalanche of complaints on the social networking micro-blog Twitter.
"Dear iPhone, why didn't your alarm go off this morning? I set six of them. I've now missed church. Thanks for nothing," said one user Sunday morning.
"Some sort of digital iPhone pandemic is going on. Alarm clock failure reports are pouring in from all sources around the globe," said another Twitter user.
Apple said in a message sent to Macworld magazine that the California-based company was aware of the problem. "We're aware of an issue related to non-repeating alarms set for January 1 or 2," spokeswoman Natalie Harrison said.
"Customers can set recurring alarms for those dates and all alarms will work properly beginning January 3."
The problem seemed to be affecting Apple's most recent versions of iPhones and iPods launched in November, but website Engadget suggested that it may also have hit earlier versions.
The problem first occurred when the clocks went back at the end of October and early November when Australian and British iPhone owners complained of being late for work because their alarms had not switched over to the new time.
Apple did not immediately respond to a query from AFP on Sunday.
source
though I don't have one, I would only rely on a alarm clock timer.
It was the second time in just a few months that the alarm function on the phone failed to activate correctly, prompting an avalanche of complaints on the social networking micro-blog Twitter.
"Dear iPhone, why didn't your alarm go off this morning? I set six of them. I've now missed church. Thanks for nothing," said one user Sunday morning.
"Some sort of digital iPhone pandemic is going on. Alarm clock failure reports are pouring in from all sources around the globe," said another Twitter user.
Apple said in a message sent to Macworld magazine that the California-based company was aware of the problem. "We're aware of an issue related to non-repeating alarms set for January 1 or 2," spokeswoman Natalie Harrison said.
"Customers can set recurring alarms for those dates and all alarms will work properly beginning January 3."
The problem seemed to be affecting Apple's most recent versions of iPhones and iPods launched in November, but website Engadget suggested that it may also have hit earlier versions.
The problem first occurred when the clocks went back at the end of October and early November when Australian and British iPhone owners complained of being late for work because their alarms had not switched over to the new time.
Apple did not immediately respond to a query from AFP on Sunday.
source
though I don't have one, I would only rely on a alarm clock timer.
