I had recently updated from 7.6 to 7.8 (now with ioDroid). Not sure if it has anything to do with the system update or with a possible update of the clock app.
I set an alam today on my phone, as I have done hundreds of times before. About fifteen minutes before the set alarm time, I got a notification of an upcoming alarm.
Annoying! (I imagine I would use the alarm in the morning, just to get woken up 15 minutes earlier to inform me that, soon, the alarm would go off …)
So I withdrew notifications.
The alarm went off, but then I did not get the interface which is used to turn the alarm off or snooze for 10 minutes.
There seems to be only the option to allow all notifications or none.
This “feature” seems to be new - I cannot recall that I changed anything with general notifications.
I admit I had many years experience with Apple/Macintosh and their clean intuitive approach to User Interface, so after only 4 months with my Brax3 I’m still finding “hidden” features …
Now that I turned off the notification, things got even worse: when the alarm rings it does not appear on my screen anymore. And it does not wake up my screen. To stop it, I need to unlock my phone first and then open the clock app.
So, I returned all notification “on” again, to be able to observe timers to give their finalisation signal. I got the undesired notifications back as well.
That is what happened to me when I turned notifications off. I then did what droidwiki offered and now it works as intended/as it used to in the good old times.
FWIW I have been having all the same issues, but not just with Clock. Especially infuriating is with the clock app is setting off the general notification sound every time you minimise or close the app (if the timer or an alarm is active)!!! But also other apps randomly setting off notifications too (again sometimes just when you minimise them). I’m also gettign random notification sounds, in the middle of the night ,while in do not disturb mode, for notifications I can’t even find or identify… All started since the last major update.
I am about to test setting from droidkiwi for the clock (thanks @rik for pointing it out).
Nope.
Yep - I went down the same road and had the same nightmare…
Yep. I appreciate iodé and the work the devs do, but can’t understand why Android (in general) always seems to take the obscure obtuse approach to how settings and menus are organised (and especially the names/description of function which are often counter intuitive).
Anyway I just wanted to add to this thread I have the same issue and that unfortunately droidkiwi’s solution does not eliminate the general notification sound when I minimise the clock. As this thread is marked solved I’ll continue with it in the existing thread I linked above. But thought I’d post it here in case anyone is looking at this (clock specific) thread and has a similar issue.
I could “unsolve” it. For me, the alarm notification issue has been solved, but the sound is still there for timers. Really annoying, especially since it had worked perfectly well before - never change a running system!
I did not look into it, since to my knowledge the clock will override any do-not-disturb-settings (which is okay to wake me up during not-disturb-times). Does anybody know if the app developers did realise that this was a bad idea and will maybe fix it? Then I would not fumble with any settings …
(what is a firing alarm? Perhaps it’s an alarm that is alarming. Does anybody at all want to be notified when it fires? I presume one wants to be alarmed by whichever alarm sound that is chosen, that’s all. Therefore I am afraid that I utterly misunderstand what a firing alarm IS)
Why does my phone beep if I snooze an alarm? Is that because by snoozing it I sort of set a new alarm? That is probably the case (given the bad experiences reported here), but it is pure nonsense )
Because you have Notification for Snoozed alarm toggled ON
From that screen you posted - Tap on the little right-facing button just to the left of any of those active toggles
and you will be given a whole 'nother screen full of confusing options
The thing I tried to illustrate is the weird notion in the mind of an app developer imagining it to be a sensible idea to provide the option of making a phone beep if one is silencing (snoozing) it. And yet more weird: to make that default.
Sorry if my communication was unclear.
Meanwhile, could anybody confirm to me that a firing alarm = an alarming alarm?
I’m okay with you leaving it solved. As I had already started the other thread before this one due to it being more than just the clock.
The Firing Alarms & Timers is the one I played around with a bit, but it caused chaos, alarms/timers went off but no notification visible, no visible active app, no way to stop it, etc (had to reboot the phone on two occasions - out of desperation - because I couldn’t turn the notification sound, alarm one morning, timer on another occasion, off - and I had one of my other issues at the same time where it ignored volume control and was blaring at full volume and I couldn’t turn the volume down)!
Yes exactly. I’ve assumed that’s an AOSP (so Android) developer initiative. But some of it could be iodé team due to being GUI related? @rik may know?
But yeah, some of these functions it’s like why add these when basics like setting a default ring tone for each SIM, a basic and significant function IMO, is still lacking when iOS has had this for 10+ years… (pretty sure that’s an AOSP thing - iodé team can’t enable something that isn’t supported in the base system).
Gotcha right there - a notification to tell you that there’s a notification… it’s why I am not a programmer/developer
But I can see a vague reason for the snooze case:
The alarm goes off
you grope in the dark and snooze it (say for 10 minutes)
you wake up 5 minutes later, panic, what’s the time?
grope in the dark for the phone, 5 past 6, why didn’t the alarm go off?
Oh. there on the lock screen is the notice: Alarm snoozed.
But IMNSHO people who need such a notification, more importantly need a life.
Well my experience with this is disabling or changing it meant when (for example) an alarm or timer went off, you:
didn’t get any notification on lock screen you could tap to access the alarm or similar; or to show the alarm was making an audio notification/was active,
When you unlocked your phone there was no active widget or notification to tap to silence or manipulate the alarm/notification either,
If you went into the app there was nothing showing (at least in the case of an alarm) that it was active, so couldn’t be silenced or halted from in the app itself (e.g. clock),
And basically in most other instances the app concerned was active or ‘doing something’ you had no way to access what it was doing and pause/stop/cancel that activity…
Now I was just playing around and trying different combinations of settings to resolve my other issues (with more than just the Clock app), but my general conclusion is this controls what happens when an event, alarm, timer, or other action ‘triggers’ from an app - and gives you the ability to vary or suppress what appears ‘on screen’ (e.g. what notifications) for that event - e.g. it’s not the event or notification’s “notification” (e.g. an audio alarm), it’s the enabler of the generation of the alert to show the notification that shows the actual notification’s text or audible alert of the actual notification event (i.e. it’s a precursor of some kind, that makes the event actually visible - and actionable? - when it triggers) - … if that makes sense.
