I set timers often - for cooking mostly. With OneUI 6, the timer does not sound the alert when it hits zero (0). Instead, it starts to count into the negatives. As soon as I bring the Clock app to the foreground, the alarm sounds. Can others verify that? I did file a bug.
I tried both Samsung Clock and Google Clock, and their timers worked correctly. On both, I: Set the timer. Put the app in the background. Turned off the screen to lock my phone and bring up AOD.
For both apps, the screen turned on, they played their alert sound and started to count into the negatives, and they gave me their usual timer options.
Working fine here. Have you tried wiping the cache partition of your device using recovery mode and then rebooting? Also wipe the cache of the clock app and make sure permissions are enabled.
Thank you all for the suggestions. I have wiped cache and verified permissions for the app - Google Clock - and it still doesn't chime until I bring it to foreground. The Samsung Clock app does not have this issue; it chimes as expected.
Honestly I didn't realize Google had a clock app. It's possible it's just an app issue since this is a beta OS, Google tends to screw things up on "unofficial" Android builds
Please use the latest Samsung Members app to submit an error report (Samusng Members One UI Beta Program Beta Feedback Error Report.
Note: To ensure relevant log information is included in the error report, submit the report within 3 minutes of encountering the bug or error, and do not terminate (swipe away) the Samsung Members application until you are notified that the report has been sent. This can take up to 5 minutes.
- To provide UX or UI-related feedback, such as usability or feature suggestions, select "Beta community Suggestions" in the Beta recruitment notice of Samsung Members app.
We appreciate your contribution to the Beta Program.
So, I got this working correctly now by adding permissions to music and notifications. This is very odd because I verified permissions before, included removing and re-adding them. Maybe the upgrade to the final version os One UI 6 reset something.
