Clock
Clock copied to clipboard
FossifyOrg
[bug] alarms/timers don't have sound/vibration if phone's on silent mode
Checklist
- [X] I can reproduce the bug with the latest version given here.
- [X] I made sure that there are no existing issues - open or closed - to which I could contribute my information.
- [X] I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
- [X] I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
- [X] I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
- [X] This issue contains only one bug.
- [X] I have read and understood the contribution guidelines.
Affected app version
1.0.0
Affected Android/Custom ROM version
Android 9
Affected device model
Samsung Galaxy A10
How did you install the app?
GitHub releases
Steps to reproduce the bug
- put your phone on silent mode.
- set up alarms/timers with sound and vibration enabled.
- wait for the alarms/timers to ring: they'll have no sound at all (neither vibration).
Expected behavior
they should still deliver sound, just like other clock apps do.
Actual behavior
they won't sound at all.
Screenshots/Screen recordings
No response
Additional information
I've reported the same bug in the old repository: https://github.com/SimpleMobileTools/Simple-Clock/issues/453
What exactly do you mean?
- The screen turns on, you can turn off or snooze the alarm, but there's no sound and no vibration.
- At the time the alarm should fire, there's no sound, no vibration and also the screen doesn't turn on. After unlocking the phone, there's a full-screen notification with sound and vibration.
- Similar as above, but after unlocking the screen, there's a full-screen notification without sound and vibration.
you get a notification, but the sound/vibration doesn't come at all.
I've actually been testing this issue with timers and with the screen on, so this is not related to the screen being turned off or anything like that.
EDIT: okay, I edited all my comment.
Please try with the screen turned off.
only alarms have sound/vibration when the screen's turned off.
with the screen on, both of them lack sound/vibration.
I've tested on three phones (Android 10, 13 and 14, all non-rooted, on silent mode), and here are my findings.
For timers:
- On Android 13 and 14, no matter whether the screen is turned on or off, timers have sound and vibration.
- On Android 10 I can reproduce the same behavior as you have.
For alarms:
- On all three phones, sometimes, when the screen was turned off, alarms didn't have sound and haven't turned on the screen. I was mostly able to reproduce it with alarms set for a very short period of time (like two minutes from now). After turning on the screen, the full-screen notification appeared along with sound and vibration.
- On Android 13 and 14, when the screen is turned on, there's an alarm's notification, but there's no sound and no vibration.
- On Android 10, when the screen is turned on, there's an alarm's notification with vibration, but without a sound.
if you're able to reproduce this bug on Android 14 then we're doomed, lol.
perhaps the easiest way to fix this bug would be looking at the source code of other FOSS clock apps, and check exactly what they do to trigger the alarms?
https://f-droid.org/packages/com.best.deskclock/
this one works well for me.
I can confirm this is an issue for me as well. Showed up late to work one day, because it just didn't ring.
I would like to chime in with some additional details as well. I wasn't really up to date with the whole SMT debacle when it happened and I just caught up a week ago and replaced all the SMT I used with fossifyorg instead. I am really glad it got forked, make no mistake. But I am not fond of the alarm not waking me and totally ruining my day.
With the SMT clock I could put my mobile on mute/silenced and sleep soundly and the alarm would go off as expected. So, something must have changed code-wise since the fork.
I'm on Android 11 on a motorola one phone. I have checked all the settings, thrice, and the alarm should go off. But it won't. I DO get an notification though. A silent one (since the phone is muted). That when I pull it down and click on it WILL sound the alarm. WHEN I look at the notification. Alarm will work as expected if the phone is unmuted. Screen locked or not. Doesn't matter.
As it is now the alarm is totally useless since you most often than not set it at night. Timer is fine since you're usually awake and unmuted when you time something.
So my suggestion would be to cross check the SMT one and see diffs regarding muted phone (dys)function.
I have this issue on LineageOS 20 (Android 13):
At the time the alarm should fire, there's no sound, no vibration and also the screen doesn't turn on. After unlocking the phone, there's a full-screen notification with sound and vibration.
The phone wasn't in silent / muted mode. Default clock on LineageOS 20 works fine.
was your phone on silent/vibration mode?
if it wasn't, then I should probably change the title of this issue. 🥴
My alarm is not working either. I am using android 14 on a motorolla edge (2022). I tried with the screen on/off. and repeatedly setting 1 minute alarms. I am not in do not disturb.
I tried forcibly giving it permission to ignore DND. but it won't let me do so, seemingly as the app does not list those as desired.
I managed to figure it out. By default notification permissions were off and the app does not request them. Only when I manually enabled notification permissions for the fossify clock app did the alarm go off.
If notification permissions is disabled for the app, it should say as much on the alarm page. with a "click here to enable" that takes you to the relevant settings page.
@throwaway242685 Do you have this problem also without silent mode? Because you've edited the issue after Naveen's comment, while Naveen encountered it on silent mode.
hi, I changed it because of this comment: https://github.com/FossifyOrg/Clock/issues/89#issuecomment-2428896451
I have this issue on LineageOS 20 (Android 13). The phone wasn't in silent / muted mode.
Using Android 11 and the fdroid Version, same Problem and more
- to be sure alarms work, i activate and deactivate and then i activate it again, otherwise alarm work or dont.
- when deactivating an alarm, somtimes the gui shows deactivated but it isnt. Nice to wakeup at sunday at 7 AM.
My feeling is, that the alram state is not set properly at the first command. I suggest some function catches it and the clock application does not read the real state after. I dont use silent/mute or some other supression mode
Another, i guess related problem. When setting up an alarm, lets say in an hour, somtimes it sets the alarm to the next day, then deactivate and activate, now the alarm is set to today.
I've had this problem for three days in a row now : telephone (on last version provided by F-Droid) is not on mute nor whatever, and I get a notification but no sound and no vibration (though I have voluntarily selected the "no vibration" option, so that part is probably not a mystery).
I had the same problem on Simple Mobile Tools too : the clock worked well for a while then suddenly it decided to just send notifications, never to ring. No idea why, nor do I have an idea why the Fossify Clock doesn't ring anymore these three days.
Not sure if it's related, but it (Fossify clock) also sometimes (four occasions in the couple months I've used it) decides to ring at a moment when I did not set an alarm - when it's at 4 am, it's not ideal.
I've had this problem for three days in a row now : telephone (on last version provided by F-Droid) is not on mute nor whatever, and I get a notification but no sound and no vibration (though I have voluntarily selected the "no vibration" option, so that part is probably not a mystery).
I had the same problem on Simple Mobile Tools too : the clock worked well for a while then suddenly it decided to just send notifications, never to ring. No idea why, nor do I have an idea why the Fossify Clock doesn't ring anymore these three days.
Not sure if it's related, but it (Fossify clock) also sometimes (four occasions in the couple months I've used it) decides to ring at a moment when I did not set an alarm - when it's at 4 am, it's not ideal.
And recently, it ringed at 3 am by itself (no alarm is set at this time, even off ones). Not ideal.
The system must be delaying the alarm somehow.
- What device do you have?
- Can you try changing the battery settings to Unrestricted for Fossify Clock?
"What device do you have?" Is there a way to send you this information privately ? (I checked whether you have a fediverse account so I could DM you, but coudn't find one)
"Can you try changing the battery settings to Unrestricted for Fossify Clock?" Where do I find this setting ? In the battery manager, there are two applications that are limited and Fossify isn't one of them.
Thanks for your work, anyway !
Also, today I got the "alarm" notification through KDE connect while I was on my computer, but the alarm didn't ring.
Is there a way to send you this information privately ?
Where do I find this setting ?
On most devices, it's at Settings => Apps => Fossify Clock => App battery usage.
Also, today I got the "alarm" notification through KDE connect while I was on my computer, but the alarm didn't ring.
Was the alarm on time? Sometimes KDE notifications are delayed (for me, could be app or system issue) so it's not exactly a reliable way to test this app.
It was on time, yes.
Today I had an even weirder occurrence : first alarm ringed on time, then half an hour late another alarm ringed at the wrong time and then stopped ringing by itself after a few seconds.
I had not been able to stop the ringing of the first alarm by toggling it to "off"; I had to press the "sleep" button on the phone itself for the first alarm to stop. Which allowed me to check that no other alarm was set, by the way.
I was able to check the battery optimization as per your indications, it was indeed optimized and I removed this optimization. Will it drain my battery ?
What do I need to report now ? This bug (actually, both bugs : alarm not ringing and alarm ringing at the wrong time) are random...
I was able to check the battery optimization as per your indications, it was indeed optimized and I removed this optimization. Will it drain my battery ?
Unlikely. The app doesn't do anything it shouldn't be doing, the alarms are triggered by the system.
Do you still observe this delayed alarm behavior even after disabling optimization? I have a device with similar setup as yours, I'll try to reproduce this there.
This does sound like a different issue than OP but more investigation is due.
As I wrote, this delayed alarm behavior (as well as the alarm not ringing when it should have, which is the problem that is close to the OP) occurs at random. So it didn't happen since I changed the parameter to "not optimized" (today), but it doesn't prove anything. I guess that if it never happens until the end of February, that may (insist on "may") be an indication that it's solved...
Curiouser and curiouser... What happened yesterday is that the first alarm ringed at the time it was supposed to ring (so far so good), then a bit more than one hour after that the second alarm ringed at the time it was set. But the problem is that the second alarm wasn't supposed to ring at all (toggle was on "off")...
That is after I set the battery parameter to "not optimized", for information.
Today, so still with the battery on "not optimized", the alarm didn't ring.