Am I the only who misses no longer seeing new notifications displayed immediately on their watch by simply turning their wrist to turn on the display? I received both a phone update (S24+) and a Watch 7 update in September, so I am uncertain which may have caused the problem, but I can't imagine this feature being removed intentionally. Now when I get a notification tone from my phone (which is in my pocket or elsewhere), I must free up my right hand to swipe left on my watch to see the new notification. In the past, the new notification would be the default screen displayed for five or more seconds after the notification arrived. If this is still working on your Galaxy watch 7, please respond to let me know what settings you have in the Wear app under Notifications. I have tried several combinations to "turn it back on" again, but no joy yet.
Samsung team, if this is a known defect in the recent version, can you let us know?
Have you checked the notification settings in the Wear app on your phone? I have notifications set to always show on both my phone and my watch, which has been working fine with all of the phone and watch updates. In the Advanced settings, there's an option to turn the watch screen on when notifications received. There's also settings available to choose which phone and watch apps can send notifications to your watch. You need to check these settings in the Wear app.
Yes, I have. (I tried to communicate that in my original post.) Right now, I must free up my right hand and swipe right to see the new notification. If I already have existing notifications on my watch, I may have to swipe right many times to see the newest notification.
If anyone out there has Notifications showing immediately on their watch screen as they arrive, please let me know what your watch settings are under Notifications. Did this stop working for anyone else, or do most people not use this method? Very frustrating to have "drop everything" to read a new notification when I have been just twisting my left wrist to do so for many years. (My Tizen Galaxy Active 2 watch also worked this way.)
Samsung support, if you're out there, is this a known defect in a recent release, or did somehow change my settings without realizing it?
FYI - A factory reset fixed this problem. Fortunately for a Galaxy watch, that is not a big deal since it is primarily a slave to the phone. (I don't store music or other audio on my watch.) So, all fixed. Now about those problems with the new release of OneUI for Galaxy watch..... (but that's for another thread.)
