iPhone Alarms Hit By New Year's Bug

An anonymous reader writes "Non-recurring iPhone alarms stopped working on January 1 for devices running iOS 4.02, 4.1, and 4.2.1. Apparently, it will fix itself by January 3, and the current workaround is to set the alarm to repeat. My girlfriend wasn't impressed, sleeping in, and I wasn't either, having to race her to work!"

No alarm? Thank god!

[PolygamousRanchKid]

I bought my girlfriend an iPhone, and the damn thing seems to set off the alarm at random times.

However, when I look at that thing, my Nokia N95 looks like crap in comparison. I'm no Apple fanboy, but I am really impressed with that thing.

Re:What's with apple and alarms in phones?

[drolli]

My Girlfriend also has an iphone. I mean lets forget about fucked up blue tooth support, not being able to send vcards (as i have done from small device to small device since my first palm/mobile phone), and lets just accept that automatic configuration (which worked for me in all courntries i have been in recently) is a little bit complicated for a phone for approx. 500Euro). Lets also forget that video calls follow just apples standard.

But what really disappointed me in this incredibly immature device is that under certain conditions EDGE support from the mobile cell tower prevents making calls on the iphone (my nokia works fine at the same conditions). As long a a device call itself a phone thats an epic fail. (Oh yes, dear Steve, we tried to use an legally unlocked iphone with some provider who is not one of the customer-sucking premium provider you chose. We will ask you forgiveness when you present in the next keynote 'it took us a littl bit longer to get it right, but you you can place calls in all EDGE networks'.)

Re:unreliable

[scdeimos]

I am sure you can give us an example where the iOS time routines don't work as advertised.

Here's a well-travelled and documented bug, which still hasn't been fixed: try editing a Contact entry to add a birth date for someone 77 years (I think) or older - good luck finding it in the calendar!

The three outcomes I've seen for this include:

1. Contact appears in the birthday calendar, but with the wrong birth date.
2. The correct birth date appears in the birthday calendar, but with some other contact's name against it (wtf?).
3. Neither the contact nor their birth date appear in the birthday calendar at all.

Apple's date and time code needs review and TFA just demonstrates another example.