Galaxy Watch 7/Ultra resetting

[SKCrews2024]

The weirdest thing has happened a couple times and now I'm concerned. For no apparent reason, my watch keeps doin a forced reset. I then have to go through the whole process of setting it up again. This time around it completely changed the way my watch is set up. Face, settings and icon order. Can anyone help me understand why this is happening? This thing cost too much and is only 4 months old. 😡

[GrimII]

I've had my watch for a while now, no new phone or anything and almost everytime I charge it, it disconnects from my phone, it makes me have to reset and reconnect it everytime and it's getting really annoying. Has anyone else had this same reoccurring issue?

[Kjbeaver]

Yes ive had to reset mine 4 times and have never figured out why. I have the ultra paired to s24 ultra

[TxBikerBear]

I have had the same problem. Once or twice a week since I got it on January 20th. It loses its connection to my S24 Ultra. Then it takes several tries to get them to reconnect even after resets and reboots. I've reset all my wifi/Bluetooth connections on the phone, also. The backup helps, but I still have to uninstall apps that get reinstalled and reconfigure my watch face every time. About an hour of time a week.

[GreatDrivr]

Same!  Some boast to just use "Backup" to restore a reset watch.

Like you, I find the same issue.  While "most" of the configuration is restored, many settings, apps, & configurations are not restored.  Which means I have to not only wait for the backup to complete, I also have to install missed apps (ie. GBoard & some health add-ons) & then spot check all settings top to bottom.

So, just as you stated, even using "Backup" is still ~1 hour or more for each "Reset/Reconnect/Reconfiguration" process.

[GreatDrivr]

If you haven't already noticed, you're now part of a growing club of folks experiencing the exact same issue w/ their Watch Ultra, starting right after the last Software update ~Jan. 22nd or 23rd, 2025.  🙂

No known or long-term-confirmed solutions that I'm aware of, other than to continue factory resetting the watch to get it to reconnect to the phone.

It's also recommended to submit error reports via the Samsung Members App immediately after disconnection & again after failed reconnection attempts.  (Instructions can be found by simply googling "Samsung Error Report" or similar).

Some have reported they had to regularly reset their watch in order to reconnect up until ~10 days ago (~Feb. 10th), & haven't had to do so since.  Hopefully a secret fix is being rolled out, as clearing cache on both devices, removing bluetooth connections, removing/reinstalling Wear App, etc. have not yet been proven as reliable solutions.

If you find any solution, please keep us all updated!  🙂

[DevRuh]

My Galaxy Watch Ultra is harassing me to do a factory reset. I tried the clear cache method and it did not work for me, I think it made it angrier. Alerted me over and over again. I use the S25 Ultra but the first reset was when I was still using the S24 Ultra. This is the 2nd time it is forcing me to reset since the last watch update. This is frustrating and they need to find a fix for it ASAP. 

[GreatDrivr]

Hello, everybody.

At risk of jinxing myself, I wanted to post that I've not had the "Random/Unprovoked Disconnect" of my watch ultra & S23 Ultra since mid-day on February 12th.  Nor have I had to Factory Reset & re-set up the watch to get it to reconnect to my phone since February 12th.

Between ~Jan. 21st through Feb. 12th, my watch would lose connection to my phone & require a factory reset to reconnect.  This occurred as frequently as twice in one day, or as long as 1 week between disconnects.

There has been no software update to my phone that I'm aware of...  Beyond, of course, the usual App updates via Google Play & Samsung Apps.  There was a system update applied to my phone on Feb. 18th though.

I did nothing new or unique before, during, or after my last random disconnect & resulting Factory Reset on February 12th.  So I don't know what the tentative solution may have been.

Summary:  While I feel it's way too soon to consider this issue "Resolved", I have some solace in going this long w/o this issue manifesting.

I'd ask that this thread remain OPEN until several others confirm they, too, haven't experienced this issue for at least a month.

I encourage anybody still experiencing this (or no longer experiencing in over 10-14 days) to please chime in accordingly.

Thank you!

[userPgThPef8lF]

Same issue for me

[L1Wolf]

Well, clearing the cache did not solve my forced reset issue. After just over 2 weeks, I was forced to reset again this morning. Coincidentally, my S24U received an update yesterday. Every forced reset came after putting it on the charger and at some point while charging getting a watch disconnected notification. Then when I go to put the watch on, it shows a reset message. Nothing, and I mean nothing will get it to connect back to the phone. Watch thinks it's a new phone and will just fail to connect until I reset. This is the third time I've been forced to reset since the January update.

[GreatDrivr]

Sorry to hear that!  I was hoping there was an unannounced, secret, magical fix rolled out in the last 2 weeks!  My S23Ultra was last updated on Feb. 18th, 2025.  And the last unexpected disconnection was Wed., Feb. 12th, 2025.

I do agree, most of my unexpected disconnects occur while placing my watch on a charger, during charging, or immediately upon removing from charging.  But I also have experienced unprovoked disconnects while it was not on a charger.

I wonder if perhaps powering the watch OFF during charging may help mitigate the disconnects, at least temporarily?  Hard to say when we've already gone through 10-20+ charging cycles since our last disconnects w/o issue...  Only for the issue to then resurface ~2 weeks since the last disconnect.

Here's to Samsung taking ownership of the software issue & getting it fixed quickly & reliably...

In the meantime, if I see any more useless suggestions to "keep watch battery above 50%", "Keep devices near each other to avoid weak Bluetooth", "remove/Re-add Bluetooth", "restart", "remove/reinstall Wear", etc. it'll be too soon.  We all know none of those are solutions to this issue.

I'll keep you posted!