My constantly-updated-with-nightly-builds Geeksphone Peak has developed a nasty habit of not ringing any of the alarms I've set. At this point I only have two alarms set to go off, one in the morning and one in the afternoon to pick up my kid from school on weekdays. Things started to deteriorate a couple of days ago, when my afternoon alarm wouldn't go off and then today I didn't get a wake up ring on time from the morning alarm. The phone was in sleep mode every time the alarm was supposed to go off. I don't see anything related in the attached logcat, besides a CSS error. I should add a couple of observation that might be relevant. I've set the phone to automatically adjust the time. Last week I was traveling abroad and the device clock changed timezones. Once or twice that week I had to set the time manually, because the device wouldn't pick the correct time (right time was shown in the 'Date & Time' setting, wrong time in the status bar on top), but always returned to automatic time management afterwards. Alarms continued to go off as expected, but this week I updated the afternoon alarm (changed the recurring days) the day before it stopped going off. I don't remember updating the morning alarm yesterday though at all (there is a small chance that I might have toggled it on and off though). Hope this is somewhat useful, because it looks like the alarm clock is back to last year's state again. I'll be happy to provide any more information as needed.

Here is a screenshot of the alarms for completeness.

When I add an alarm it works the first time but it does not works on 'snooze' and if it's recurent it doesn't ring either the next times

Ouch, that sounds like a nasty bug. You mention your issues started a couple of days ago; do you happen to know when you last flashed it with a nightly build? (Or was it newly flashed that day?)

I've been updating daily, but since the beginning of this week I'm doing it by using the update check from the settings app, not flashing from the nightly tarball like I used to. I don't think my change of updating practice coincided with the appearance of the symptoms.

In my case I think it started 1 or 2 weeks ago, and if it's any help, that's on a Geekphone Keon

The nightly I installed over the weekend (20140307064238) seems to have fixed the issue. Both of my alarms now ring and I can also see the alarm icon in the status bar on top of the screen. This wasn't displayed previously as can be seen in attachment 8383528 [details] (not sure why I missed that). I have no idea what fixed it, but I'll be monitoring it for a couple more days and then resolve this bug as WORKSFORME.

There were a few regressions identified and fixed last week that probably contributed to the fix. Hopefully they also fixed this one. :)

The problem made a comeback of sorts today. I didn't get a wake up ring in the morning, and when I got up from the alarm of my other phone (running 1.1; always have backups they said!) I noticed when I resumed the screen from standby that the clock app was in the foreground, but without making any sound or vibrating (the alarm is configured for both). Furthermore as can be seen in the screenshot the window was not properly rendered (alarm label and time missing in the middle). Other interesting observations are: - I couldn't dismiss the alarm app with any button (on-screen or device buttons like home/power). - adb wouldn't attach to the device (presumably because it was still locked). - The time in the status bar on top stopped updating after 19 minutes (I noticed it because I only managed to hook the device to my laptop about an hour after the alarm was supposed to ring, and I have another screenshot from that time that shows the time as 7:34). - The device didn't hang completely, I could grab screenshots by pressing Power & Home buttons, I could see the WiFi and GSM indicators, and I could even hear the sound Loqui makes when it connects to the chat servers. One thing I regret not trying is to blindly try the swipe gesture for unlocking, but I'm not confident that the event would actually go to the lockscreen beneath the clock (assuming it was there, I'm not that familiar with gaia architecture). I'm not sure if this is the same bug or a different one, but that's all the information I can provide.

With the alarm label missing, it looks like there was a JS error while trying to display the alarm. I recently landed refactoring that was intended to improve the reliability of this screen; if you see this happen again, please let me know (and grab a logcat if you can). Would be curious to know if this happens any more on master.

My alarms have been working without issues for the past week at least.

I could confirm that bug with Firefox OS 1.0.0.1, 1.1, 1.2 and 1.3 on an Alcatel one touch (hamachi). It is very annoying when i need to use an other mobile phone to wake me up. If the alarm doesn't work, i could restart my phone and the alarm is fired after the restart. I am not sure how to reproduce that behavior.

Duping to bug 1052245 in the interest of tracking this in an actionable place.