Open
Labels
bugSomething is not workingSomething is not workingdevice/software specificIssues concerning devices with some specific hardware/softwareIssues concerning devices with some specific hardware/software
Description
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.3.0
Affected Android/Custom ROM version
Android 15 / Xiaomi HyperOS 2.0.202.0
Affected device model
Poco F7 Pro
How did you install the app?
F-Droid / IzzyOnDroid
Steps to reproduce the bug
- Set phone to vibrate/silent mode
- Tap the "Create timer" (+) button
- Set a timer for 30 seconds and make sure a timer sound is selected
- Start the timer
- Send the app to the background (go to home screen) and turn off screen
- Wait for the timer to fire
Expected behavior
I expect the selected timer sound to be played even if my phone is in vibrate/silent mode.
Actual behavior
A "Timer expired" notification is displayed and, if configured for the timer, the phone vibrates but no sound is played.
Screenshots/Screen recordings
No response
Additional information
I think this is due to the way timers currently work in the app (I haven't looked at the code yet so I'm just guessing from what I can see in the app): Creating a local notification with the specified sound when the timer is up. However, notification sounds will not be played if the phone is in vibrate/silent mode.
Reacted by Luca Junge, rubenvilhelmsen, Kenneth Söderlund, dessert1, code-mha, xXNickznXx, NamelessGO, Nate Reinar Windwood, lumikrynd, Edwin Kofler and 4 more
Metadata
Metadata
Assignees
Labels
bugSomething is not workingSomething is not workingdevice/software specificIssues concerning devices with some specific hardware/softwareIssues concerning devices with some specific hardware/software
Activity
mtnbnz commentedon Jul 24, 2025
This might be of interest: https://github.com/surendar4/Critical-Alerts-Android-Demo/blob/1ffc50351225591d9a7c3980ccaf4a5f7246344f/app/src/main/java/com/surendar4/criticalnotifications/notifications/NotificationNotifier.kt#L62It usesAudioManagerto disable silent/vibrate mode just before showing the notification and then switches back to the original "ringer mode" after the notification sound is done playing.mtnbnz commentedon Jul 24, 2025
Ignore my previous comment.
It seems this line is actually the problem:
Clock/app/src/main/kotlin/org/fossify/clock/extensions/Context.kt
Line 470 in 3c1ff89
Changing it to
.setCategory(Notification.CATEGORY_ALARM)fixes the issue.CosmicBagel commentedon Jul 24, 2025
On a Pixel 7a, android 16, clock ver 1.3.0. Installed with F-Droid.
Timers never seem to go off unless I leave the phone unlocked and the clock app open. Do not disturb seems to kill the vibration as well.
Aga-C commentedon Jul 25, 2025
@CosmicBagel Do you have a custom ROM, or have you modified something in your OS (related to notifications or battery optimization)?
mtnbnz commentedon Jul 25, 2025
Nevermind. This only works on my emulator, not on my actual device. I think the only real solution is to use a foreground service and have it use
MediaPlayerto play the timer sound just like it is done for alarms.naveensingh commentedon Jul 25, 2025
It does use a foreground service, but yes, it still relies on the notification for playing sounds.
Issues like #40 and #156 also require that change. I'll be working on it.
CosmicBagel commentedon Jul 26, 2025
Vanilla google rom: what ever it came with in the box + updates from google.
I have do not disturb mode on (fossify clock is added as an exception aka "Apps that can interrupt")
I also usually run with battery saver "Extreme" on (fossify clock is added as an "essential app")
Built-in google clock works fine with similar configuration. ¯\_(ツ)_/¯
kmantel commentedon Sep 19, 2025
may be related to https://issuetracker.google.com/issues/384844015
as a temporary workaround, I rebuilt replacing STREAM_ALARM with STREAM_MUSIC, because I usually have that on. another stream might be more reliable
nlorc commentedon Oct 13, 2025
I've ran into an issue that might be related.
This happens even if the device isn't set to silent/do not disturb/vibrate only.
Device: OnePlus Nord with OxygenOS 12.1 (Android 12)
Version: 1.3.1 from F-Droid
th23x commentedon Nov 8, 2025
I have made the same observation - and figured out no way to adjust with Clock or Android settings.
I use a Samsung S10e with the latest stock Android, no custom one. Android 12 / Samsung One UI 4.1
naveensingh commentedon Nov 25, 2025
Yeah, I'll work on it soon. FWIW, I also burned my pancake a few days ago, and it was absolutely my fault.
mycroftmcmansions commentedon Nov 25, 2025
Not sure if this helps (as a reference for fixing the issue), but this app is the only one I could find in F-Droid that manages to make alarms work the same way the native does:
https://f-droid.org/en/packages/com.best.deskclock/
antoyo commentedon Jan 2, 2026
I don't know if this is related to this issue or if it should be a new issue, but when the Notification volume is at the minimum (off), it doesn't play the timer sound either.
theanita1 commentedon Feb 10, 2026
Am adding my name to the list of users that the alarm doesn't go off unless in the foreground on noisy mode
Google pixel 8a, android 16
Sytten commentedon Mar 9, 2026
Yeah this is kinda of annoying that the timers dont work
natewind commentedon Mar 24, 2026
Same, alarm sound does work, but the timer only vibrates.
BreakfastSerial commentedon Apr 9, 2026
Experiencing the same issue. Timer is vibrate only, if phone is set to vibrate. Timer sound works if the ringer is active.
GrapheneOS build 2026040300, Fossify Clock 1.6.0 from GitHub apk.
lumikrynd commentedon Apr 15, 2026
I have this problem too
I have somehow made it work by going into all the notifications settings for the app, but now my screen stays on all the time when locked instead (if I have a timer running anyway).
Nagisa7Shiota commentedon Aug 8, 2026
Heya,
Same here for me still. Android 16 / Nothing OS 4.1 with Clock 1.6.0 on Nothing Phone 2a.
I wanted to add a screenshot but it does not work:
For some reason, I see that the clock app creates a high amount of "Timer" notification channels. If a new one gets created, it is not recognised by "Do not disturb" and therefore no sound is played. Maybe only one channel for all timers?
aRav3n commentedon Aug 24, 2026
Same issue for me, Samsung S23, One UI 8.5, Android 16, Clock 1.6.0 installed via Google Play. Note that the alarm works just fine, it's only the timer that doesn't work.
alexandrulesi commentedon Sep 21, 2026
Is this ever going to get addressed? 1 year old issue for something so essential and so small... I find the timer is frankly unusable the way it is now and I'm going to have to migrate away if this continues to be the case.
OrionH commentedon Nov 4, 2026
Samsung S23, One UI 8.5, Android 16, Clock 1.6.0
Alarm is tied to notification volume instead of alarm volume