We have moved to a new Sailfish OS Forum. Please start new discussions there.

[Bug] Alarm sounds only once

asked 2014-03-19 11:06:00 +0300

JonS gravatar image

updated 2014-03-19 11:18:35 +0300

Prior to if an alarm was ignored it effectively "auto snoozed" and re-triggered later. Since it appears that if an alarm is missed it simply results in a "missed alarm" notification. A notice on the notification screen of a locked phone isn't going to wake me up...... Any chance of restoring the original functionality?

edit retag flag offensive close delete



hi. i just tried and if i ignore the alarm it goes to a 5mins snooze. it'd be nice if we could make it ring forever as an option for groundhogs like us.

Low ( 2014-03-19 12:16:38 +0300 )edit

Yep.. Was supposed to wake up at 6 am, but didn't hear the alarm go off (I'm a heavy snoozer). Woke up naturally at 11 am, picked up the phone and was rather frustrated to see the "missed alarm" -notification. As long as this issue is around, I can't use my Jolla as an alarm clock.

Milo ( 2014-03-19 12:45:47 +0300 )edit

An alarm clock that automatically silences after one (or two) alarms is almost as useless as no alarm at all.

ln ( 2014-03-19 18:41:26 +0300 )edit

1 Answer

Sort by » oldest newest most voted

answered 2014-03-19 13:54:51 +0300

PMG gravatar image

updated 2014-03-21 11:42:27 +0300

In clock alarms and calendar reminders are automatically snoozed two times if the user does not react to the alarm UI within 60 seconds. If the user does not react to the third time that the alarm is show, then it will be automatically dismissed, and a notification about the missed alarm will appear in the events view.

However, clock alarms created in versions prior to will be automatically dismissed (without snoozing) if the user does not react to them. You can re-create the alarms by disabling/enabling the alarms in the Clock application (or by modifying the alarms in any way), after which the alarms will be snoozed two times as described above.

edit flag offensive delete publish link more



Thanks for that hint. But I have to agree to previous comments: it should not be dismissed autmatically. Not even after 2 or three snoozes. It would be better to configure that.

naytsyrhc ( 2014-03-19 15:59:14 +0300 )edit

"An alarm clock that automatically silences after one (or two) alarms is almost as useless as no alarm at all." - @ln, so true :)

Milo ( 2014-03-20 12:32:29 +0300 )edit

Need to get this back on track. Just copy N9 alarm clock behaviour and it's usefull again. Now the alam clock is useless and in fact I have to go to buy real alarm clock, as I don't have my old N9 with me. :( Workaround for this at the moment is that you set several alarms.

hannuuki ( 2014-03-20 22:39:23 +0300 )edit

@hannuuki: the current automatical snoozing/dismissing of alarms works exactly as in the N9. @Milo: the alarm dialog is shown to the user three times, if the user does not react to them, not one or two.

  • Both and N9 show alarms to the user three times if the user does not react to them. After the first and second showing the alarm is automatically snoozed, and after the third it is automatically dismissed. In addition, adds a missed clock alarm notification if the user does not react to the three appearances of the alarm dialog.
  • If the user does snooze the alarm, then it will be again shown to the user three times if the user does not react to the alarm; the automatical-dismiss counter is reset if the user snoozes the alarm.
PMG ( 2014-03-21 11:36:52 +0300 )edit

For real, I want the alarm to ring again indefinitely if not explicitly dismissed. It became useless for me with the latest update.

epsilonijk ( 2014-03-26 22:10:32 +0300 )edit
Login/Signup to Answer

Question tools



Asked: 2014-03-19 11:06:00 +0300

Seen: 350 times

Last updated: Mar 21 '14