iPhone 4 alarm not working since 01.01.2011

thanx Spruik, glad it actually worked to FIX the problem 🙂 icarma... read my previous post... set ONE alarm to repeat as EVERYDAY, let it go off ONCE and it will be fixed... remove that alarm and you can now set a single alarm and it will WORK! it fixed mine, it worked for Spruik... i'm sure it will work for you

I too have a defunct alarm. Not only did it not go off but I missed two meetings as a result. But what gets me is that apple KNEW about the glitch and did not warm it's users. A simple text would have helped but instead they allowed all of us to us our alarms as usuAl And then over sleep. I love apple but this situation makes me rather upset. Please let us know about these problems when you know of them!

UKCats77 wrote:

What you want from a company is for them to fix the mistakes, and Apple has a great record of doing that.

Hmm Which Apple do you know of? The one I know are far from quick to fix stuff. Took too long to 'admit' to antenna gate, they knew about the PDF exploit for quite a while before only fixing it once someone exploited it in such a huge way. Other fixes hackers have had to release to the public due to Apple not even acknoledging the issues.

Wallsey wrote:

. +set ONE alarm to repeat as EVERYDAY, let it go off ONCE and it will be fixed... remove that alarm and you can now set a single alarm and it will WORK!+

Nope - no go on this idea above described - tried it twice - when single alarm is again set (with no repeats) it does not sound. I'll soon be able in 45 mins to test the Jan 3 operation.

I'm on 4.1 and the alarm didn't go off either. Seems to be a New Year's clock problem with the phone.

compwiz1202 wrote:
+If the logic about it having to do with dates from different years being in the same week is correct, failures should be:+

>
+> 2012: 1+
+> 2013: 1-6 - etc.+

Could someone expand on the above, please ?

UKCats77 wrote:
What you want from a company is for them to fix the mistakes, and Apple has a great record of doing that.

Yeah, they do fix stuff, eventually. After they crumble to millions of users complaining on forums like this and the work fixing the bugs has been done for free for them by some annoyed user who has decided to fix the problem themselves. But.... this process takes time.

How long did it take them to even admit to the issues present in iOS4? I had a a 16Gb 3G which thanks to the update was basically an unusable phone for nearly 3 months!!! I couldn't answer calls, 80% of my apps would crash within 3-5 mins of use... the list goes on. But eventually after millions of posts and complaints, user released fixes and hacks to allow a rollback to the previous operating system (which is an option that Apple could have easily offered and was also the solution that was being advised to customers by Apple store employees), it got fixed.

This alarm problem (lucky for Apple) seems to fix itself. I'm lucky too, I didn't have to work on the 1st or 2nd but I did have to work today, the 3rd, and the alram is working.

What a horrible bug. Does anyone actually know why it didn't work on the 1st and 2nd?

I just love the way apple deletes the posts they do not like. I think is ** and this post will be deleted as well. Shame! Any appogies yet somewhere?

It will be released as statement somewhere when they get around to working out a way to 'spin' it.

Apple and Steve Jobs owes me $100.00 for making me late for work yesterday. Yes, I do realize that others have posted and complained too but, I will not feel better until this is posted.

iuniadinu wrote:

+Shame! Any appogies yet somewhere?+
*
Companies do not, as a rule, publically admit mistakes and especially avoid public apologies - it gets them sued in class-action prone USA.
*

Do you feel better?

At 6 minutes past midnight GMT my iPhone 4 now correctly sounds an alarm, without repeat having been set. So it seems the problem is solved/gone-away for now.

I had to get up at 5am for a flight this morning. Thank goodness for my Dad and his old school alarm. I'm totally shaking my fist at Apple and hugging my dear father!! This problem is not the best way to ring in a new year. It could have been worse in my case, though.

I would no longer call myself an expert, but I have over 30 years experience in IT, doing coding, testing, project management, systems analysis, etc. This looks like a case of shoddy testing. Every programmer makes mistakes and it's the tester's responsibility to find them. There are (or should be) multiple levels of testing. I suspect that someone proposed a test plan that included a special case (to cut time spent testing), and that special case left 1/1/11 and 1/2/11 untested. Let's hope it's really just 1/1 and 1/2 and not all Saturdays and Sundays!