Add comment

Apple iPhones hit by summer time alarm glitch

2011-04-01 15:34
Some iPhone owners were heading in to work late on Monday after a glitch caused their alarms to malfunction.

Users found their wake-up alert coming one hour late, one hour early or not at all.

The problem, related to the clocks going forward for British Summer Time, does not appear to have affected everyone.

Apple has yet to comment on what caused it, but similar problems have previously hit iPhones in the US.

Many of those whose alarms went wrong turned to social networking sites to vent their fury. One Twitter user wrote: "iPhone alarm failed twice. 1) went off at 5.45 instead of 6.45. 2) Didn't go off at all when I reset it. Time to update software."

Another unimpressed owner wrote: "Thanks iPhone. I didn't really want that alarm to go off anyway."

According to user reports, the glitch has affected non-recurring alarms set within the iPhone's calendar application, rather than its dedicated alarm clock.

The problem first came to light in the United States last November during the switch from Daylight Savings Time.

Despite promises from Apple to correct it, a similar issue hit iPhones on 1 January 2011.

Printer-friendly version


which is better tadalafil or sildenafil [url=]cialis online[/url] when does tadalafil patent expiry buy cialis online tadalafil chewable tablet tadalafil mode d'emploi tadalafil fluconazole

Feel free to surf to my homepage - generic cialis

o que significa tadalafil [url=]cialis online[/url]
tadalafil other drugs in same class generic cialis online cialis tadalafil
precio mexico cuando tomar tadalafil tadalafil equivalente

tadalafil ricetta medica [url=]buy cialis online[/url]
how does tadalafil tablets work cheap cialis online does tadalafil
work as well as cialis www tadalafil tablets tadalafil ilaç etkileşimleri

Post new comment

More information about formatting options

This question is for testing whether you are a human visitor and to prevent automated spam submissions.
Enter the characters shown in the image.
Page execution time was 115.31 ms. Executed 173 queries in 22.71 milliseconds.

Memory usage:

Memory used at: devel_init()=0.29 MB, devel_shutdown()=8.96 MB.