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. 😡

[kimberleigh]

Remove life 360 app and see if that stops

[realaud]

I understand they are working on a patch, but submitting an error report might hurry them up. They did recommend to delete or disable the app, but most don't want to do that since they have the app for a reason.

[king_james17]

It happened to me on my s23 ultra paired with my watch ultra

[Blu-Ray]

8th time now.

[Dusk46]

I am starting to hate my watch because of the reset request! This is like the 5th time. My whole entire running workout lost! Pisses me off so much! Then I have to redo everything AGAIN!! Samsung, fix this! NOW!!

[user8821]

I'm going through this right now. It's extremely annoying. Every month it resets. What's the point of having it

[Spike1814]

Every 7:00 to 10 days I have to do this factory reset. Unfortunately it does not back up my watch face. Therefore I have to reconfigure my watch face every time. This is getting very old

[Members_BRqZmXA]

Right there with!!! Getting very very old!!

[Tiffany04]

I upgraded my phone AND watch at the same time. I literally just had to reset it again for the 6th time since the day before Christmas. It's annoying. I had the watch 4 and it never did that. Not once. And it was paired to my 22 ultra. I got the 25 ultra and watch 7 the same day. Very annoying.

[GreatDrivr]

Forgive me, you're saying you've experienced your Watch Ultra disconnecting from your phone (and requiring a factory reset in order to reconnect) since Christmas??

If so, this is the first I've heard of this issue occurring prior to the Watch Update, released ~Jan. 22nd, 2025.

Everything I've seen & experienced from this community indicates this issue did not exist until end of January, particularly after the January, 2025 update, released on ~Jan. 22nd, 2025.

Thanks,