Galaxy watch ultra stopped working

[White_Rhino]

I've had the Galaxy watch hold you for a little over a month now and my phone notified me that the watch is no longer connected. 

I checked the watch and it shows it's not connected to my phone either, so when I get in the wearable app in the longer pops up that I even own a smartwatch. So it forced me to reset the watch and try to pair it again, which I did, just for it to not want to restore it with backup information. Pretty over Samsung at this point. 

[realaud]

The more people that put in actual error reports on an isse, the more likely and faster the issue will be addressed. A caveat, though, the logs get uploaded automatically, but you cannot close the members app until it's fully compiled and uploaded. Sometimes it takes a very long time. A notification appears on your phone when its done and a copy of the logs is saved to your device. Until the log appears on your device, the upload is not complete.

[GreatDrivr]

Sorry for another message about this.

I just realized there is no way to send error reports or "logs" or anything for your watch once this issue manifests...  Only the phone's error report & logs can be sent.

Reason being...  Submitting an error report for wearables is done through the connected phone's "Wear" app, which also requires that the wearable be successfully connected to the phone.

Therein lies the problem, since the entire underlying problem is that the watch cannot be reconnected to the phone until being reset...  And I'd imagine resetting the watch would also clear out the watch's logs & diagnostic data?

I suppose I can at least include the phone's diagnostic data & only hope that'd be enough diagnostic data for Samsung techs to investigate & develop a fix for the watch.

If I'm missing something & there is, in fact, a way to submit error reports & logs via the Watch while disconnected from a phone, please let me know!  Thanks!

[realaud]

The watch logs are contained deep inside the phone logs. There is no separate log for the watch. The logs currently contained on the phone should register the connection attempts snd the reason it disconnected.

[GreatDrivr]

Please forgive me for what may seem like a dumb question.  And I mean this sincerely w/ all due respect.

While I'm sure that's true, wouldn't the phone only include log activity for the watch while the connection was good & nothing during or after the connection severed?  Likewise, wouldn't any watch-related log activity related to the severed connection, (along w/ any watch activity from subsequent failed reconnection attempts), then be isolated to only the watch, itself, never making it to the phone?

I apologize.  It seems counterintuitive to me that the phone's logs would successfully contain the watch's critical log activity.  Particularly because the watch transmits said activity to the phone (when the connection is working), but obviously cannot transmit because the connection was severed & will not restore.

Akin to one person speaking on a wired phone, another listening far away, then cutting the wires while still expecting the listener to continue hearing what the speaker is saying?

Regardless, I'll still be submitting logs the next time this happens to me.  I'm mostly hoping for a reality check that I'm not missing something in the logic & that this effort is worthwhile.

Thanks, 

[realaud]

I can't answer that question since I cant understand the logs in the first place. If the developers cannot find what they are looking for they will let you know. You might try uploading a log immediately after a failed connection attempt.

[GreatDrivr]

Fair enough, thanks for talking through it.  I plan to submit an error report immediately after the next disconnect, along w/ another error report after one or two failed reconnection attempts.

I'm willing to help them (Samsung) play ball (to a certain extent) if it will help achieve a quick & successful fix.  I just hope it's worth it.

Thanks,