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


wow)) viagra prescriptions

buy viagra online

viagra generic

girl viagra

viagra 100mg ’
viagra 100mg
viagra generic

generic cialis ’
cialis for sale
cialis cost
cialis 5mg

cialis levitr

cialis pills

cialis online

compare generic cialis price

generic cialis ’
online cialis
online cialis
cheap cialis

viagra online ’
viagra online
viagra pills
viagra generic

viagra et impuissanc

viagra coupon

buy viagra

viagra you can buy at walmart

viagra price ’
viagra online

cialis ’
cialis price

forum cialis generi

cialis tadalafil

cialis coupons

generic drug for cialis

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 116.25 ms. Executed 215 queries in 38.08 milliseconds.

Memory usage:

Memory used at: devel_init()=0.37 MB, devel_shutdown()=8.83 MB.