Alarm Clock stopped working

I had this issue yesterday morning.. the alarm failed to sound. The screen lit up and the buttons on the screen for Snooze and Dismiss came up, but there was no audio coming from the speaker. It sat there for 5 minutes making no sound, and after i dismissed the alarm and then went to test the sounds, they were sounding properly. I got the RC29 update this morning, so we'll see if it happens again. Rebooting seemed to have fixed the alarm as it sounded this morning after a reboot last night.

The only thing I can think of is, that the installation of SOME app messed up the alarm clock--  and than powering the phone completely off and on "resets" it, so it's ok.

We're ALL madly downloading and installing probably 80% of the apps that come from the market-- so I'm guessing we all installed the same thing at one point.

Just a theory that I cannot substantiate in any way--  but seems logical.

No RC29 (or any other) update for me yet.  *grrr*.

My alarm worked on day 1 (no applications installed) but did not work on day 2 (again, no application installed) as I posted on page 1 of this thread so I don't know about Market (or other) applications messing with the alarm.

It's worked on and off since then (mostly HAS worked, which is good) but I now DO have a few apps installed, etc.

Bah.  You blew my theory.   Even more annoying, because that confirms the clock is really unreliable.....

I'm *hoping* something in rc29 addresses it?    No way to tell, since I still don't even HAVE that update

Well, I got the RC29 update and I STILL have this problem. I absolutely love this phone, but some of these problems are simply unacceptable. Does Goggle want Android to fail?

EDIT: Well, once again this morning I got the alarm clock visually claiming it was going off, but NOTHING played.  This is getting old.  I know all about the brand new OS/first Android phone ever/early adopter risk arguments, but isn't a working alarm clock a pretty basic feature?  Where's the fix?

This morning my alarm stopped working.  It goes off, the phone vibrates, but no sound.  I was using an out of the box alarm.

Now when I go into alarm, it says unknown ringtone.  wtf.  if i click it, i get a force close error.  i even deleted the alarm and made a new one.  It also won't change from the default time of 8am, no matter what i try setting it to.

i think it's related to me listening to music yesterday.  i noticed my SMS and email alerts were set to random songs I HAD NOT LISTENED TO and had to be changed back.

W.  T.  F.  google.  Do we leave grievances with T-Mobile to forward on to Google?  Or have they setup a G1 feedback/your crap sucks email address?

Hello all.  I'm the developer responsible for the AlarmClock.  There is indeed a problem with alarms.  It is intermittent, and hence hard to track down.  It looks like there are cases where either the system fails to launch the clock's AlarmAlert activity, or fails to play the audio, or maybe both.  We are working on a fix.  I'm not sure yet when we'll get it into an OTA, but I will let you know when it is going in.

Also note that alarms are canceled five minutes after they start playing.  This is to avoid running down the battery (and bothering the neighbors) when a phone is left unattended.  We are increasing this timeout to 10 minutes, for the heavy sleepers.  There will also be a message on the alert screen when the alarm is canceled, so it won't be mistaken for a bug.

Thanks for your help tracking this problem down, and sorry for the hassle.  I'm very aware how much people depend on this app.

Alan

Try the NightClock app in the Market. Works great.

Hello all.  I'm the developer responsible for the AlarmClock.  There is indeed a problem with alarms.  It is intermittent, and hence hard to track down.  It looks like there are cases where either the system fails to launch the clock's AlarmAlert activity, or fails to play the audio, or maybe both.  We are working on a fix.  I'm not sure yet when we'll get it into an OTA, but I will let you know when it is going in.

Also note that alarms are canceled five minutes after they start playing.  This is to avoid running down the battery (and bothering the neighbors) when a phone is left unattended.  We are increasing this timeout to 10 minutes, for the heavy sleepers.  There will also be a message on the alert screen when the alarm is canceled, so it won't be mistaken for a bug.

Thanks for your help tracking this problem down, and sorry for the hassle.  I'm very aware how much people depend on this app.

Alan

It's nice to hear that the issue is being worked on.  Hopefully it's fixed soon.

Mine went off this morning but now i know not to trust it. What ringer you guys use? I like the rooster sound lol!

Thanks for letting us know it's being worked on alan.
Btw, this problem is happening every day for me.

Question, is the alarm supposed to wake the phone when it's completely off? If not, it should

Can any1 else verify that nightclock works fine?

I am also having this problem - the alarm worked NO PROBLEM until this morning, when I woke up and saw the snooze or dismiss screen on the phone. No audio!  Only a few apps, standard alarm tones, standard charger.  Please do let us know when this is fixed!

I HAVE MY ALARM GOIN OFF AT 6:30AM MON. THRU FRI. AND SINCE OCT.31 (THE DAY I GOT MY PHONE) I HAVE HAD NO PROBLEMS AT ALL! I CHECKED ALL THE LITTLE BOXES FOR MON-FRI.

I've been having this same issue with the alarm and also now any msgs.  I have my phone on vibrate pretty much all the time, and notifications set for txt's, gtalk, email, an phone yet when I get anything coming in on the phone all that happens is the screen lights up and thats it till I miss the call.  Then the little green light comes on.  I wonder if I need to reset to fix this.

argh .. the alarm was working fine for me the last few days, until I gotten the RC30, today I missed classes thanks to the G1 alarm failing on me !! argh!!

There will be a fix in the next OTA.  Or at least an attempted fix... The AlarmClock will play its audio/vibe directly, rather than through the platform's AlarmManager.  We also doubled the unattended-alarm timeout from 5 minutes to 10, and fixed a few other minor problems.

mine actually did this the other day finally. lucky i woke up before it was supposed to go off or i would have missed work! i do have RC30 as well

There will be a fix in the next OTA.  Or at least an attempted fix... The AlarmClock will play its audio/vibe directly, rather than through the platform's AlarmManager.  We also doubled the unattended-alarm timeout from 5 minutes to 10, and fixed a few other minor problems.

Welcome to TmoNews and thanks for sharing this information.  It's great to see some of those working on Android coming here to enlighten us!

Morning Everyone!

I know this is an old post, but I had this issue recently and managed to find out how to rectify it.
For some reason, the Alarm Volume on my phone had been turned to mute - this is not the same as the ringer volume (which is where I was getting confused). I'm not sure whether this was due to an update or an app,  but here's how I fixed it (Courtesy of T-Mobile tech support)

Go to Alarm Clock ------> Ringtone -----> Android System - when the list of sounds comes up, press the volume keys to turn the Alarm Volume up and down.

Hope this helps!!