Alarm occasionally wont fire!?

[Golgo]

I've posted this on alldroid.org too but I though I'd ask here also:

Ok, this is really weird. I can't figure out whats going on here.
Problem: alarms sometimes just wont go off.

First let me say I never use any task killer apps so that's not it.
I'm 100% sure the alarms are enabled and silent mode is NOT on.

Last time it happened was this morning. Alarm was set to 06:45, I had a backup alarm clock (an old Palm device) wake me at 06:50 since I've learned the Milestone is not to be trusted anymore.
First thing I did was pick up the phone, and since I had it set to Media dock mode with DockConnector, it woke itself up with the g-sensor and THEN the alarm fired. I also had another alarm app set to go off 5 minutes later at 06:50 so that fired simultaneously.
I did a adb logcat to file and found something quite odd - between 00:13 and 07:03 (when i picked up the phone) there are no entries! It's like the phone has been dead most of the night only to be waken up by moving it.

I've attached the log file - if anyone would care to take a look Id be really grateful. I know there are some sharp minds on this forum

Thanks a lot!

 

[DAGr8]

since I had it set to Media dock mode with DockConnector, it woke itself up with the g-sensor and THEN the alarm fired. I also had another alarm app set to go off 5 minutes later at 06:50 so that fired simultaneously.

I may be wrong but right away this raises a red flag to me , have you tried not putting the phone in any mode ? iuse the moto dock myself and never had any issues with it , the 3rd party app you are using must be related to your problem ....

 

[hookbill]

The only time my alarm didn't go off for me is when I killed it with a task killer. And I did read your post, you don't have one.

 

[Golgo]

since I had it set to Media dock mode with DockConnector, it woke itself up with the g-sensor and THEN the alarm fired. I also had another alarm app set to go off 5 minutes later at 06:50 so that fired simultaneously.

I may be wrong but right away this raises a red flag to me , have you tried not putting the phone in any mode ? iuse the moto dock myself and never had any issues with it , the 3rd party app you are using must be related to your problem ....

Well, I've considered that but I've used that app for several weeks without any alarm problems and there are no comments in Market about alarm issues with DockConnector.

I'm thinking it might be related to 2.0.1, didn't have the problem before updating...

 

[natediddy1120]

Ive had MANY problems with my alarm clock not going off....trust me, Ive been late to school, work, etc., all because my Droid decided to not wake me up when I set it to! And I dont use task killers either...but recently I found an app that is perfect for me, in case I might sleep through the alarm also....its called ShakeToWakeUp or something along those lines.....but the only way you can disable the alarm once it goes off, is to shake it or it will continue to go off and not silence itself like the stock alarm clock. It has settings to adjust how many times you have to shake the phone to disable the alarm, and also, how hard you have to shake it, I have to set it on the highest setting (pretty damn heavy) to wake my ass up on those early mornings

 

[skribzy]

This has happened to me too. I have found by installing an app called CVolume that there are 7 sound settings in the phone (Ringer, Notification, Media, Alarm, Voice Call and System). On the occasions when the alarm hasnt gone off the specific alarm volume has been set to 0. I have no idea how this happened, however a quick check with CVolume before bed has eliminated this issue.

Hope this helps!

S

 

[Golgo]

Well thanks for trying to help, natediddy1120 and skribzy, but I don't think those solutions are applicable here since the phone seems to be in some weird zombie sleep state. Dont see that another alarm app would make a difference and since the alarm sounds as soon as I turn the phone on, it's not a volume issue either.

 

[gad]

Hi guys,
I have the same problem since yesterday when I upgraded myself to Android 2.1.

I happened to find a solution here.
Seems to work just fine for me.