Galaxy Watch 7 Disconnection issues

[Jordan1515]

This is an issue that seems to be mainly with the LTE version of the watch, where it will randomly disconnect from your phone for no apparent reason. Today is the sixth time it has happened to me in the two months I have had my new phone (Galaxy S25 Ultra) and watch (GW7). A "reset your watch" message will pop up, and no amount of restarting the phone or watch will fix the issue. When you go to your phone's Bluetooth settings and look at connected devices, the watch is gone. However, it will show up in the visible devices area at the bottom. When you click on it to pair it, your phone pops up a message asking if you would like to transfer the watch to this device, like it has been erased and added to a different device without your knowing. A quick check on Reddit shows many others having the same issue. This is not a problem people should be experiencing with premium devices such as Samsung Galaxy products. Please look into this problem. 

[realaud]

Does everyone who is having this problem have the same phone?  I'm wondering because I have a watch 7 paired with an A54 and have not once disconnected or had to reset my watch.  It would appear this might be more a problem with the phone than the watch.  Just a guess.  From what I've seen it looks like the problem is happening with the higher end phones paired with the watch 7.  There may be something about the features of those phones that is not working properly with the watch.  Regardless, it needs to be fixed.  I'm just guessing it's the phones not the watches, though.

[JourneysADRIFT]

This has been happening for years. It's not just the phone models.

It affects multiple watches, not just the 7 series. Virtually any watch with WearOS is affected.

It affects numerous phone models, people with all sorts of phones on different versions of Android have encountered this issue.

[realaud]

I don't doubt it's happening to people, I'm just saying I have never had a forced disconnect/reset happen to me with any of my watches. The only common denominator I have seen is that they higher end phones. My highest end Samsung was an S10 lite. Now I have an A54. I might have missed it, but I didn't see any complaints for A series users.

[JourneysADRIFT]

It happens to all types of phones and has been happening for years. It happens to xaiomi, it happens to oppo, it happens to HTC, on and on. There are threads about this happening to all sorts of phones going back years. Even back to the watch 1/2 series.

*You* may not have seen it, but there are more commonly used sites for issues like these where it's been reported by a wide range of users. You may be biasing your knowledge due to most people with cheap phones aren't buying smart watches, but that doesn't mean the issue is exclusive to high end phones. Other phone brand users also won't be in here, rather, be on other websites.

[realaud]

Hey, don't shoot me.  I'm just looking for a common element.  There seems to be none, since it appears to be happening with all models (phones and watches), all brands, all Android and UI versions. Obviously, it is not happening to *every* Galaxy watch user. I am quite sure I am not the only one it's not happening to.  It is happening to enough users to warrant Samsung investigating the cause but they, too, might be looking for the common denominator.  If everyone sent in error reports, and those error reports included logs, it's a lot of code to go through, so unless something immediately jumps out as being the common element, they can't address it.  Just my 2 cents.

[JourneysADRIFT]

The only common thread is Google Play Service and WearOS.

This exact issue can be found in Pixel watch forums, in Fossile forums, etc. going back many years.

It likely isn't a Samsung issue.

[realaud]

Which is probably also why Samsung can't//won't fix it. I think, though, if they know what the problem is, they can program a fix in the wear app or the watches. But, I'm not a programmer, and Samsung is most likely looking at it as a Google problem. The two should work together to find a fix.

[Robin621k]

There seems to be a problem with the S25 series and watch 7 series. The majority seem to be those with LTE activated.

I have a Watch Ultra, Watch 6 classic, none using LTE and I have no problems.
There hasn't been any input from a moderator on how to fix this issue, which I suspect has no fix as of yet.
I gave checked Reddit and Google boards, there is no definitive fix that I can find. Which leaves me to to believe it is a Google Play System problem. The phones and watches get disconnected from Google accounts, not Samsung accounts.

[realaud]

Considering that there's a Google logo on the disconnect message shown on the OP's screen shot, I'd very much agree that it's a Google issue.