19-02-2025 02:41 PM - last edited 23-02-2025 07:17 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Highlight
- Report Inappropriate Content
Solved! Go to Solution.
1 Solution
Accepted Solutions
19-02-2025 02:56 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Highlight
- Report Inappropriate Content
19-02-2025 02:47 PM - last edited 19-02-2025 03:01 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Highlight
- Report Inappropriate Content
Go to Settings > Apps > Clock, then force stop and clear cache. In the same menu, ensure notifications are allowed and that the "appear on top" setting is enabled.
19-02-2025 02:56 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Highlight
- Report Inappropriate Content
22-02-2025 07:39 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Highlight
- Report Inappropriate Content
27-02-2025 03:19 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Highlight
- Report Inappropriate Content
I have the same problem. Have followed the instructions above and cleared the cache. Still no luck. Also, alarm will not sound at correct time after snoozing for 10 minutes; it will sound at 15 minutes. These issues need a fix from Samsung ASAP as I rely on my timer and alarm several times a day.
a month ago - last edited a month ago
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Highlight
- Report Inappropriate Content
Having also followed the same steps to clear cache and force stop I'm still able to reproduce it fairly consistently. I've also restarted my device. My alarms work, fortunately, but the timers just go negative.
Here's how to reproduce:
1. Set a timer for two minutes.
2. Background the clock application. Make sure you see it counting down.
3. Play any video with unmuted audio in a browser or YouTube. (Correction: play any audio at all.)
Observe the timer as it goes negative but never sounds.
Update: If you happen to have the mini timer overlay enabled you can see some bizarre behavior:
In the uncropped screenshot above the timer had been not triggering for eight minutes and fifty one seconds, shown as "-8:-5-1".
3 weeks ago
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Highlight
- Report Inappropriate Content
I have the same issue. Clearing cache and restarting the phone didn't help either. My alarm is fine, but the timer doesn't work at all.
3 weeks ago
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Highlight
- Report Inappropriate Content
I've done a little more digging with ADB.
When a timer fails to trigger I see these messages in ADB (filtered to just the clockpackage):
04-14 09:52:45.976 2200 2844 D ActivityManager: Received BROADCAST intent 0x2abbd61 Key{broadcastIntent pkg=com.sec.android.app.clockpackage intent=act=com.sec.android.app.clockpackage.timer.playsound pkg=com.sec.android.app.clockpackage cmp=com.sec.android.app.clockpackage/.timer.receiver.TimerSecurityReceiver flags=0x2000000 u=0} requestCode=0 sent=0 from uid 1000
04-14 09:53:00.012 3113 3113 D QSClockIndicatorView: Home Indicator status_bar_clock 9:53 notifyTimeChanged(QSClockBellSound - TimeText:9:53, TimeContentDescription:9:53 AM, DateText:Mon, April 14, ShortDateText:Mon, Apr 14, Demo:false, QuickStar-Second(false|12:34:56)) ClockVisibleByPolicy:true, ClockVisibleByUser:true, visible?true, parent:android.widget.LinearLayout{9917d32 V.E...... ......ID 0,0-65,63 #7f0b04f0 app:id/left_clock_container}
I tried a few times.
04-14 09:55:37.705 2200 6125 D CoreBackPreview: Window{302d590 u0 com.sec.android.app.clockpackage}: Setting back callback OnBackInvokedCallbackInfo{mCallback=android.window.IOnBackInvokedCallback$Stub$Proxy@42ae6af, mPriority=0}
04-14 09:55:37.707 31787 31787 W System.err: at com.sec.android.app.clockpackage.timer.service.PipTimerService.onStartCommand(SourceFile:8)
04-14 09:55:37.709 2200 6049 E WindowManager: win=Window{6603354 u0 com.sec.android.app.clockpackage/com.sec.android.app.clockpackage.ClockPackage} destroySurfaces: appStopped=true cleanupOnResume=false win.mWindowRemovalAllowed=false win.mRemoveOnExit=false win.mViewVisibility=8 caller=com.android.server.wm.ActivityRecord.destroySurfaces:6529 com.android.server.wm.ActivityRecord.destroySurfaces:6510 com.android.server.wm.ActivityRecord.notifyAppStopped:6574 com.android.server.wm.ActivityRecord.activityStopped:7162 com.android.server.wm.ActivityClientController.activityStopped:258 android.app.IActivityClientController$Stub.onTransact:613 com.android.server.wm.ActivityClientController.onTransact:136
04-14 09:55:37.709 2200 6049 I WindowManager: Destroying surface Surface(name=com.sec.android.app.clockpackage/com.sec.android.app.clockpackage.ClockPackage$_31787)/@0x2e7babc called by com.android.server.wm.WindowStateAnimator.destroySurface:942 com.android.server.wm.WindowStateAnimator.destroySurfaceLocked:536 com.android.server.wm.WindowState.destroySurfaceUnchecked:4303 com.android.server.wm.WindowState.destroySurface:4277 com.android.server.wm.ActivityRecord.destroySurfaces:6529 com.android.server.wm.ActivityRecord.destroySurfaces:6510 com.android.server.wm.ActivityRecord.notifyAppStopped:6574 com.android.server.wm.ActivityRecord.activityStopped:7162
04-14 09:55:37.710 2200 6049 D ActivityTaskManager: mStartingWindow and mStartingData is null for token=ActivityRecord{9d8de15 u0 com.sec.android.app.clockpackage/.ClockPackage} t17719}
04-14 09:55:37.716 1536 1536 I Layer : id=7346 removedFromDrawingState com.sec.android.app.clockpackage/com.sec.android.app.clockpackage.ClockPackage$_31787#7346 (192)
04-14 09:55:37.716 1536 1536 I SurfaceFlinger: id=7346 Removed com.sec.android.app.clockpackage/com.sec.android.app.clockpackage.ClockPackage$_31787#7346 (192)
04-14 09:55:37.716 1536 1536 I Layer : id=7346 Destroyed com.sec.android.app.clockpackage/com.sec.android.app.clockpackage.ClockPackage$_31787#7346
04-14 09:55:37.716 2200 6125 V WindowManager: Relayout Window{302d590 u0 com.sec.android.app.clockpackage}: viewVisibility=0 req=525x394 d0
04-14 09:55:37.727 2200 6125 D WindowManager: finishDrawingWindow: Window{302d590 u0 com.sec.android.app.clockpackage} mDrawState=DRAW_PENDING seqId=0
04-14 09:55:37.728 2200 2309 V WindowManager: performShowLocked: mDrawState=HAS_DRAWN in Window{302d590 u0 com.sec.android.app.clockpackage}
04-14 09:55:37.870 31787 31787 I TimerNotificationService: onCreate() : com.sec.android.app.clockpackage.timer.service.TimerNotificationService@2d23d06
04-14 09:55:37.886 2200 6049 D ApplicationPolicy: isStatusBarNotificationAllowedAsUser: packageName = com.sec.android.app.clockpackage,userId = 0
04-14 09:55:37.886 2200 6049 D ApplicationPolicy: isStatusBarNotificationAllowedAsUser: packageName = com.sec.android.app.clockpackage,userId = 0
04-14 09:55:37.887 3113 3153 D SecFgsManagerControllerImpl: onForegroundStateChanged: dialogShown:false, isForeground:true, packageName:com.sec.android.app.clockpackage , token:android.os.BinderProxy@d2b4276, userId:0
04-14 09:55:37.888 2200 2330 D ApplicationPolicy: isStatusBarNotificationAllowedAsUser: packageName = com.sec.android.app.clockpackage,userId = 0
04-14 09:55:37.888 2200 2330 D ApplicationPolicy: isStatusBarNotificationAllowedAsUser: packageName = com.sec.android.app.clockpackage,userId = 0
04-14 09:55:37.890 2200 2200 D NotificationReminder: addNotificationRecord record com.sec.android.app.clockpackage
04-14 09:55:37.893 3583 3583 I Launcher.NotificationListener: onNotificationPosted : com.sec.android.app.clockpackage number : 0
04-14 09:55:37.896 2200 4166 D ApplicationPolicy: isStatusBarNotificationAllowedAsUser: packageName = com.sec.android.app.clockpackage,userId = 0
04-14 09:55:37.896 2200 4166 D ApplicationPolicy: isStatusBarNotificationAllowedAsUser: packageName = com.sec.android.app.clockpackage,userId = 0
04-14 09:55:38.095 3583 3583 I Launcher.NotificationListener: onNotificationPosted : com.sec.android.app.clockpackage number : 0
04-14 09:55:38.099 3583 3583 I Launcher.NotificationListener: onNotificationPosted : com.sec.android.app.clockpackage number : 0
04-14 09:55:38.101 3113 3113 D InterruptionStateProvider: no Heads up : edgelighting enabled app. 0|com.sec.android.app.clockpackage|2147483610|null|10181
04-14 09:55:38.101 3583 3583 I Launcher.NotificationListener: onNotificationPosted : com.sec.android.app.clockpackage number : 0
04-14 09:55:38.104 3113 3113 D BubblesManager: onEntryUpdated : shouldBubbleUp=false ,key=0|com.sec.android.app.clockpackage|2147483610|null|10181
04-14 09:55:38.104 3113 3113 D InterruptionStateProvider: no Heads up : edgelighting enabled app. 0|com.sec.android.app.clockpackage|2147483610|null|10181
04-14 09:55:38.114 3113 3113 D BubblesManager: onEntryUpdated : shouldBubbleUp=false ,key=0|com.sec.android.app.clockpackage|2147483610|null|10181
04-14 09:55:38.114 3113 3113 D InterruptionStateProvider: no Heads up : edgelighting enabled app. 0|com.sec.android.app.clockpackage|2147483610|null|10181
04-14 09:55:38.316 3113 3113 D BubblesManager: onEntryUpdated : shouldBubbleUp=false ,key=0|com.sec.android.app.clockpackage|2147483610|null|10181
04-14 09:55:38.316 3113 3113 D InterruptionStateProvider: no Heads up : edgelighting enabled app. 0|com.sec.android.app.clockpackage|2147483610|null|10181
04-14 09:55:40.968 1071 1071 D io_stats: !@ Read_top(KB): loop45(4271) 128 android.youtube(32236) 56 pp.clockpackage(31787) 12
04-14 09:55:42.739 2200 2218 V WindowManager: Relayout Window{302d590 u0 com.sec.android.app.clockpackage}: viewVisibility=0 req=420x95 d0
04-14 09:55:42.742 2200 2218 I WindowManager: Reparenting to leash, surface=Surface(name=302d590 com.sec.android.app.clockpackage)/@0xe1084d, leashParent=Surface(name=WindowToken{99e4e8e type=2038 android.os.BinderProxy@e9c2b24})/@0x8e62f02
04-14 09:55:42.743 1536 1713 I SurfaceFlinger: id=7364 createSurf, flag=24000, Surface(name=302d590 com.sec.android.app.clockpackage)/@0xe1084d - animation-leash of window_animation#7364
04-14 09:55:42.744 2200 2218 D WindowManager: makeSurface duration=1 leash=Surface(name=Surface(name=302d590 com.sec.android.app.clockpackage)/@0xe1084d - animation-leash of window_animation)/@0x9e0d013
04-14 09:55:43.155 2200 2309 I WindowManager: Reparenting to original parent: Surface(name=WindowToken{99e4e8e type=2038 android.os.BinderProxy@e9c2b24})/@0x8e62f02, destroy=true, surface=Surface(name=302d590 com.sec.android.app.clockpackage)/@0xe1084d
04-14 09:55:43.163 1536 1536 I Layer : id=7364 removedFromDrawingState Surface(name=302d590 com.sec.android.app.clockpackage)/@0xe1084d - animation-leash of window_animation#7364 (191)
04-14 09:55:43.163 1536 1536 I SurfaceFlinger: id=7364 Removed Surface(name=302d590 com.sec.android.app.clockpackage)/@0xe1084d - animation-leash of window_animation#7364 (191)
04-14 09:55:43.164 1536 1536 I Layer : id=7364 Destroyed Surface(name=302d590 com.sec.android.app.clockpackage)/@0xe1084d - animation-leash of window_animation#7364
04-14 09:55:49.917 31787 31787 I TimerSecurityReceiver: onReceive() / action = com.sec.android.app.clockpackage.timer.SHOW_PIP
04-14 09:55:49.998 31787 31787 I TimerSecurityReceiver: onReceive() / action = com.sec.android.app.clockpackage.timer.playsound
04-14 09:55:50.232 31787 31787 I TimerSecurityReceiver: onReceive() / action = com.sec.android.app.clockpackage.timer.SHOW_PIP
04-14 09:56:00.057 3113 3113 D QSClockIndicatorView: Home Indicator status_bar_clock 9:56 notifyTimeChanged(QSClockBellSound - TimeText:9:56, TimeContentDescription:9:56 AM, DateText:Mon, April 14, ShortDateText:Mon, Apr 14, Demo:false, QuickStar-Second(false|12:34:56)) ClockVisibleByPolicy:true, ClockVisibleByUser:true, visible?true, parent:android.widget.LinearLayout{9917d32 V.E...... ......ID 0,0-65,63 #7f0b04f0 app:id/left_clock_container}
04-14 09:56:00.075 3113 3113 D QSClockIndicatorView: Home Indicator status_bar_clock 9:56 notifyTimeChanged(QSClockBellSound - TimeText:9:56, TimeContentDescription:9:56 AM, DateText:Mon, April 14, ShortDateText:Mon, Apr 14, Demo:false, QuickStar-Second(false|12:34:56)) ClockVisibleByPolicy:true, ClockVisibleByUser:true, visible?true, parent:android.widget.LinearLayout{9917d32 V.E...... ......ID 0,0-65,63 #7f0b04f0 app:id/left_clock_container}
04-14 09:56:29.680 2200 2305 W NotifHistoryProto: notification package name (com.sec.android.app.clockpackage) not found in string cache
04-14 09:56:29.680 2200 2305 W NotifHistoryProto: notification package name (com.sec.android.app.clockpackage) not found in string cache
04-14 09:56:29.682 2200 2305 W NotifHistoryProto: notification package name (com.sec.android.app.clockpackage) not found in string cache
04-14 09:56:29.683 2200 2305 W NotifHistoryProto: notification package name (com.sec.android.app.clockpackage) not found in string cache
04-14 09:56:29.684 2200 2305 W NotifHistoryProto: notification package name (com.sec.android.app.clockpackage) not found in string cache
04-14 09:56:29.685 2200 2305 W NotifHistoryProto: notification package name (com.sec.android.app.clockpackage) not found in string cache
04-14 09:56:36.680 2200 2844 D ActivityManager: Received BROADCAST intent 0x2abbd61 Key{broadcastIntent pkg=com.sec.android.app.clockpackage intent=act=com.sec.android.app.clockpackage.timer.playsound pkg=com.sec.android.app.clockpackage cmp=com.sec.android.app.clockpackage/.timer.receiver.TimerSecurityReceiver flags=0x2000000 u=0} requestCode=0 sent=0 from uid 1000
04-14 09:56:57.040 1071 1071 D io_stats: !@ Read_top(KB): pp.clockpackage(31787) 36
04-14 09:57:00.032 3113 3113 D QSClockIndicatorView: Home Indicator status_bar_clock 9:57 notifyTimeChanged(QSClockBellSound - TimeText:9:57, TimeContentDescription:9:57 AM, DateText:Mon, April 14, ShortDateText:Mon, Apr 14, Demo:false, QuickStar-Second(false|12:34:56)) ClockVisibleByPolicy:true, ClockVisibleByUser:true, visible?true, parent:android.widget.LinearLayout{9917d32 V.E...... ......ID 0,0-65,63 #7f0b04f0 app:id/left_clock_container}
One of the things that really stands out is the "04-14 09:55:37.707 31787 31787 W System.err: at com.sec.android.app.clockpackage.timer.service.PipTimerService.onStartCommand(SourceFile:8)" a system error in onStartCommand in SourceFile on line 8. The NotifHistoryProto is also interesting but might be a red herring.
3 weeks ago
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Highlight
- Report Inappropriate Content
Sounds like I've been having the same issue, and it looks like it started around the same time as the Bluetooth audio issue, which I'm also having.
https://eu.community.samsung.com/t5/galaxy-s25-series/bluetooth-issues/td-p/12020468/page/2
I wonder if the 2 are related.
