Even after updating to Android 10 on my S9, the native clock still has a bug where it is incorrectly reporting the next alarm to third-party apps like my weather app widget. For example, if my next alarm is set for 7:00, the widget displays 6:55 (always 5 minutes off). I've tried installing the Google clock app and this problem does not exist when setting an alarm in that clock app (i.e. next alarm is shown correctly in the weather widget). The weather app developer has also confirmed this is a Samsung issue. This problem has existed for some time now. What is Samsung doing about this?
To be clear, this problem exists only for the native clock app. When using another clock app, like Google Clock, there is no problem. In the attached screen shots, you can see that the alarm is set for 3:00, but the alarm time reported to the widget and displayed is 2:55. The app maker even built a workaround for this known issue to allow users to add a five minute pad to the time to correct it. However, this then makes all other alarms and reminders coming from apps other than the native clock incorrect by five minutes in the other direction (i.e. 2:00 would be displayed as 2:05 due to adding the five minute pad). I have switched to using Google Clock and have no issues.
This doesn't help. As I indicated earlier, the app developer knows this an issue with some Samsung phones and added a "fix" to compensate for this. They have said that the clock API is reporting the wrong time.
This is definitely an issue with Samsung Clock, and it is well known to developers of clock apps. Samsung unfortunately either doesn't understand, or doesn't believe there is an issue. It wouldn't take them long to see for themselves by conducting a test or two but for some reason they are unwilling to do this. The solution is to not use Samsung Clock to set alarms, but use Google Clock instead, which doesn't suffer from the bug.