[bug] alarms/timers sometimes don't get triggered at all

[throwaway242685]

Checklist

• I can reproduce the bug with the latest version given here.
• I made sure that there are no existing issues - open or closed - to which I could contribute my information.
• I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
• I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
• I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
• This issue contains only one bug.
• 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

1. having alarms/timers is enough to reproduce this bug.

Expected behavior

they should work.

Actual behavior

there are times when they don't get triggered at all.

Screenshots/Screen recordings

No response

Additional information

SimpleMobileTools/Simple-Clock#453

[Aga-C]

What exactly do you mean?

1. The screen turns on, you can turn off or snooze the alarm, but there's no sound and no vibration.
2. 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.
3. Similar as above, but after unlocking the screen, there's a full-screen notification without sound and vibration.

[throwaway242685]

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.

[Aga-C]

Please try with the screen turned off.

[throwaway242685]

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.

[throwaway242685]

are you able to reproduce that on silent mode?

[Aga-C]

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.

[throwaway242685]

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 compare what each app exactly does to trigger the alarms.

https://f-droid.org/packages/com.best.deskclock/

this one works well for me.

[benstigsen]

I can confirm this is an issue for me as well.
Showed up late to work one day, because it just didn't ring.

[ThurahT]

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.

[omega3]

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.

[naveensingh]

Welp, I missed my alarm today.

[throwaway242685]

was your phone on silent/vibration mode?

if it wasn't, then I should probably change the title of this issue. 🥴

[naveensingh]

was your phone on silent/vibration mode?

Yes.

[taltamir]

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.

[Aga-C]

@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.

[throwaway242685]

hi, I changed it because of this comment: #89 (comment)

I have this issue on LineageOS 20 (Android 13).
The phone wasn't in silent / muted mode.