31-12-2024 09:43 AM
Hi all,
Up until very recently, my Galaxy Watch 6 Classic would display a summary of a notication on the screen, eg from WhatsApp or BBC news. This is how I want it, it's very useful at work.
This has now stopped in the last few days, I just get the notification dot on the right hand side of my watch face and have to swipe right to see what it is.
I've been though every setting for notifications I can find, on the watch and the phone (S24 Ultra) and everything seems spot on, it SHOULD work. Restarted the phone, restarted the watch, both running latest software, turned off wrist detection (no change), turned it back on...
Before I reset the watch to factory and start again setting it up, has anyone else found the same recently, and did you solve it?
Thanks
Solved! Go to Solution.
01-01-2025 08:48 AM - last edited 01-01-2025 08:48 AM
Thanks, I found the answer! Ringtone volume on the watch was set to 0. This greys out the notification sound level - I turned up ringtone volume and that sorted it.
No idea how ringtone volume ended up as 0 but hey, it’s fixed and maybe this will help someone else..
Thanks for the replies, and happy new year!
31-12-2024 10:02 AM
@DB551: On you Watch6 Classic, please try heading to Settings > Notifications > Show phone notifications on watch > Show alerts even when phone in use.
You can also try heading to Settings > Notifications > Advanced settings > New notification indicator on watch face, and toggle this option off to see if this helps.
Please note that if more than 2 notifications are received, you will be required to swipe left or right on the screen to check for more notifications. In this instance, I recommend leaving the notification indicator in place.
31-12-2024 01:39 PM
31-12-2024 07:04 PM
01-01-2025 08:48 AM - last edited 01-01-2025 08:48 AM
Thanks, I found the answer! Ringtone volume on the watch was set to 0. This greys out the notification sound level - I turned up ringtone volume and that sorted it.
No idea how ringtone volume ended up as 0 but hey, it’s fixed and maybe this will help someone else..
Thanks for the replies, and happy new year!