- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday in
Galaxy Watch- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday in
Galaxy Watch- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday in
Galaxy Watch- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday in
Galaxy WatchAnyway, this is from the other thread posting what the development team said:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday in
Galaxy Watch- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday in
Galaxy Watch- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday in
Galaxy Watch- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday (Last edited yesterday ) in
Galaxy WatchI haven't experienced this situation myself.
I went from the S24U to the S25U both paired to my Watch Ultra and my Watch 6 Classic. I am not using LTE on either device.
I used Samsung Smart Switch to set up my S25U and it worked flawlessly for both watches when I transfered to new phone.
Is your watch using LTE ?
Have you tried setting up as new?
I would try going into Accounts and Backups and deleting all backups that are stored on Samsung Cloud and start fresh.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday in
Galaxy Watch- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday in
Galaxy WatchAre you by any chance using Life360? There is another discussion on this matter going on here and the answer to feedback was that Life360 was somehow interfering with something and the suggestion from the developers was to temporarily stop using Life360 while they worked on a patch. Those who paid for this service don't want to disable it for any length of time, so I posit that perhaps just either not allowing it to send notifications to the watch or disabling the watch companion app (if there is one). If you are not using Life360, I don't have an answer for you, but do make sure to put in your own error report trough the feedback link in the support tab of the members app.

