Hello,
So here’s the context (i.e. how to reproduce), let’s say I have two alarms, they’re 10 minutes apart, for example:
alarm #1 is 3:00, snooze is enabled and set to 10 minutes, CAPTCHA is disabled.
alarm #2 is 3:10, snooze is disabled, CAPTCHA is enabled (because it’s more important).
So when alarm #1 rings and is snoozed once, as expected it rings again slightly after 3:10, and that time overlaps with alarm #2, now the problem is: when you dismiss alarm #1 now after 3:10, alarm #2 somehow also got dismissed together and never triggered the CAPTCHA.
In other words, one touch of “Dismiss” would actually dismiss both alarms if they happen to be ringing at the same time, this becomes problematic if alarm #2 is supposed for something more important (that’s why it had CAPTCHA enabled, which never got triggered).
Is this the intended behavior or a bug? I feel like a single touch of “Dismiss” should not turn off all of the alarms if they happen to be ringing at the same time, especially if one of them had CAPTCHA enabled (and the CAPTCHA also might not trigger because of this behavior).
Would it be possible to let each alarm have their own dismiss behavior that’s independent from other alarms? (it feels unreliable when your alarm might not work if there’s another alarm that’s already ringing)
Your response is greatly appreciated.
Hi @hisleeper, what is the use case of having two wake-up alarms so close to each other?
If you wish to have the flexibility to snooze, but not after a certain time, you can limit the snoozing time in the settings. After this limit, only dismiss is available, and you can configure the CAPTCHA to protect this alarm from oversleeping.
Dismiss cancels the alarm, that is currently in the progress. But if there is one alarm in the progress, the other one cannot go off at the same time.
1 Like
Hi @lenka-urbandroid , it’s actually for working around the current limitation of the snooze feature (I also suggested a feature to make the snooze more customizable), I’m aware of all the features you’ve explained in your first paragraph, but unfortunately there currently seems to be no way to set a decreasing snooze time for individual alarms (only a global “Halve the Snooze” setting is available)
Besides that, since this is an alarm app, I also use it to set alarms for other things during my day (cooking, laundry, other needed reminders for the day, etc.), and those alarms also have snoozes enabled, thus it’s possible that two/more of the alarms might be going off near each other (simply by coincidence).
If only one alarm can go off at a time (and be shown on screen), it feels inconsistent that I’m dismissing one alarm that I’m seeing on the “Dismiss” screen but I might also be dismissing a different alarm that’s not shown there. (If you have two alarms going off simultaneously due to snooze, you probably still want to be notified and informed for both of them instead of just one, and due to how it currently behaves, you could potentially dismiss the other one without realizing it, making it unreliable.)
Therefore, could it be possible to only dismiss the alarm that’s shown to you on the screen? (or have an option to)
You are not dismissing both alarms. You are dismissing the alarm that is in progress, the one that is on the screen.
The problem is that the other alarm cannot go off if there is already one alarm in progress.
Does it mean the alarms are not wake-up alarms related to sleep?
Sorry could you elaborate on “The problem is that the other alarm cannot go off if there is already one alarm in progress.”? In other words, if there’s no longer “already one alarm in progress” (after you dismissed it), the “other alarm” should then be able to go off, did I understand it correctly?
In the case I described above, when I press “Dismiss”, as I’m only “dismissing the alarm that is in progress” (only one), after that I should then see the other alarm to go off and be shown on screen, right? But that’s not what’s happening, instead the other alarm just also got turned off without ever going off at any point, that’s why I think it’s a bug.
Snooze = I want to sleep uninterrupted for x more minutes. I will still need to be woken up later, so I need an alarm in x minutes.
Dismiss = I am done sleeping. I am awake and ready to get up, and I no longer need to be woken up by an alarm.
Chaining alarms for one time might be needed for reminders, or it makes sense to chain notifications. What is a use case for chaining sleep/wake-up alarms?
If you wish sleep longer (= you still need another alarm), you snooze the alarm.
And the alarm will go off after the snooze period.
If you are worried about over-snoozing for too long, you can limit the alarm snooze count, the alarm snooze time, or disable snoozing for the alarm completely.
Yes I understand the intended use of the snooze feature, like I mentioned I used two alarms because I’m only able to set a unchanging/fixed amount of snooze duration (e.g. 10 minutes for all of the snooze), but not a changing/decreasing snooze duration (e.g. 1st snooze 15 minutes, 2nd snooze 10 minutes, 3rd snooze 5 minutes, etc.), and the “Halve the Snooze” global setting is not configurable for each individual alarm, that’s why I had to find workarounds.
Also, let’s just say I’m using the alarms for reminders/notifications instead of wake-ups, could you please let me know regarding my last comment?:
Sorry could you elaborate on “The problem is that the other alarm cannot go off if there is already one alarm in progress.”? In other words, if there’s no longer “already one alarm in progress” (after you dismissed it), the “other alarm” should then be able to go off, did I understand it correctly?
In the case I described above, when I press “Dismiss”, as I’m only “dismissing the alarm that is in progress” (only one), after that I should then see the other alarm going off and be shown on screen, right? But that’s not what’s happening, instead the other alarm just also got turned off without ever going off at any point, that’s why I think it’s a bug (could you confirm please?)
What is a use case for chaining sleep/wake-up alarms?
We can reconsider our design, if it will benefit our wake-up alarms.
Our focus is solely on sleep.
It would be a great idea for a new app (Plan as Android?) that would work as a reminder.
The second alarm cannot start while there is the first alarm still in progress. After you dismiss this first alarm, the second alarm cannot start - it is already past its schedule, and also, you just confirm you no longer need alarms (by tapping the dismiss). Chaining alarms for the same time makes sense for reminders, but not for wake-up alarms.
What is a use case for chaining sleep/wake-up alarms?
Currently I’m only doing it to achieve a decreasing “snooze” duration, the idea is basically:
assuming I always snooze until the limit I set,
and I have the first alarm with longer snooze duration, snooze until its limit and treat the final dismiss (without CAPTCHA) as a pseudo-“snooze” for myself (I understand it’s not how it’s designed),
and then a second alarm with shorter snooze duration, snooze until its limit and treat the final dismiss (with CAPTCHA) as the real dismiss for myself,
but sometimes the second alarm’s CAPTCHA gets skipped if I planned their timings (alarm time, snooze duration, snooze limit) without careful calculations (which may cause alarms #1 to ring (without CAPTCHA) when alarm #2 is also supposed to ring (with CAPTCHA), causing alarm #2’s CAPTCHA skipped upon dismissing alarm #1).
So in other words, I’m doing all of the above just so that I can get decreasing “snooze” duration, there is no need to reconsider the design, but perhaps consider allowing “Halve the Snooze” to be set for each individual alarm and/or consider my “snooze list” idea?
The second alarm cannot start while there is the first alarm still in progress. After you dismiss this first alarm, the second alarm cannot start - it is already past its schedule, and also, you just confirm you no longer need alarms (by tapping the dismiss). Chaining alarms for the same time makes sense for reminders, but not for wake-up alarms.
Ok, so in the case of reminders, even if I tapped dismiss (e.g. for reminder alarm #1), that doesn’t mean I also no longer need to be reminded for reminder alarm #2, right? I understand “the second alarm cannot start - it is already past its schedule” from a mechanics point of view, but why not have a queue system so that alarms can ring one at a time? (instead of getting completely skipped if it happens to conflict with another alarm)
Instead of creating two alarms (where one alarm starts snoozing and the second alarm ends it), we have snooze limits for alarms. Every alarm can have different periods allowed, so you can for example have long snoozing allowed for your free days and no snooze/short snooze period allowed for work days.
The suggestion will be considered, we saw the suggestions on the suggestion forum.
In this Bug report thread, I am trying to explain that the app does not queue alarms. Dismiss = no more alarms, I am awake.
Creating queued alarms would confuse users. Why another alarm screen after just dealing with one?
We have terrible experience with the wake-up check feature. It was optional and by default OFF. Thousands of unhappy and angry users, hundreds of emails daily, thousands of 1* reviews even from long-term users. I can only imagine the rage and confusion after dealing with multiple alarm screens right after they are woken up.
This is too risky. Dismiss meaning cannot be changed.
Fair enough, I undertand why you consider it to be risky.
For snoozing, I understand I can set different periods for different alarms, but what I actually want is a variable/decreasing snooze duration for one single alarm like mentioned from earlier (“Halve the Snooze” is okay, but unfortunately it isn’t configurable for individual alarms)
Thanks for your reponses and for considering my suggestions.