Galaxy Watch 7 inaccurate pool length tracking with One UI 8

[TheRabbi]

I need some ideas.

I had a Watch 7 Ultra which became EXTREMELY inaccurate in pool length tracking after receiving OneUI8 Beta, and then OneUI8 Stable. I always swim 110 lengths in a 25-yd pool, and while it used to track them perfectly, that all changed with the new software. It started counting between 140 and 155 lengths. I could even feel the watch notify I'd completed two lengths IN THE MIDDLE of a length; sometimes even twice in one length.

Thinking I might have better luck with fresh hardware and factory fresh software, I traded it in for the Watch Ultra 2025.

I took my first pool swim since receiving the new watch two days ago, and I'm getting the same result: over-counted pool lengths. I swam my usual 110 lengths, and the watch counted 156.

Two watches, same problem, leads me to believe there's a bug in OneUI8. I've been working with Tech Support, but see no need in keeping the new watch when it's as much a paper weight as the old one.

So before I go through the return process and hopefully get my old watch back (I shouldn't have sent it in so fast), do any SWIMMERS have any ideas about anything I can try?

[TheRabbi]

It's been three months since I reported this problem to them (during the OneUI8 BETA), and still nothing. I'm still using my Garmin and Health Sync app to replace the junk data my Watch Ultra is providing.

[TheRabbi]

My Watch 8 Classic got an update last night. Thinking the lap-counting fix might be included, I wore it during my 110 length swim this morning. I also wore my Garmin Venue.

The Galaxy Watch counted 160 lengths. That's almost THREE QUARTERS OF A MILE more than I actually swam. The Garmin counted perfectly.

It's been FOUR MONTHS. This is pathetic.

[realaud]

Have you made sure that the pool length was not changed somehow in the settings?  Readjust the pool length to make sure it's in yards, not meters.  Even if it's correct, just change it to one and change it back to reset it.  See if that helps with the accuracy.  

[TheRabbi]

Already tried that. It's not an error on my part; Samsung Support has already acknowledged it's an issue. They're just apparently taking their sweet time to fix it. There is ZERO chance I'll be "upgrading" (?) to the 9 series next year if this mess doesn't get fixed. Lap lengths being off impacts almost every aspect of Samsung Health. Laps are off. Calories are off. Nutrition is off. Body Battery is off. Everything is impacted by a little thing.

My fix so far has been to use the Garmin and an app called Health Sync to save the correct 2750 yds and Calories to Samsung Health, and delete any workout measured by my Galaxy Watch Ultra 2025 or 8 Classic.

Of course, at this point, I'm wondering what the point of even using Samsung Health is, so I'll probably just uninstall it.

[usereywUl69nO7]

This has been irritating me for months.  I was thinking the same thing every time I looks at Samsung Health now.  Samsung watch is a bit less appealing if i have to jump through hoops to make the health app correct.  That's primarily what I use it for, tracking workouts and health features.  I've never had an issue like this from Samsung after many years telling people how great they were.  

[TheRabbi]

The long delay on a fix makes me believe they're not really interested in offering one.

I swim one length, and the dumb thing says I've done FIVE. 😂 At least I had an old Garmin sitting in a drawer, but not everyone does.

[TheRabbi]

Well, my Watch Ultra 2025 just received an update to BYK1. There's no listing of a fix for the swim tracking bug, so I'm assuming that after four months, Samsung hasn't bothered. I'll take it on a swim Monday, but I'm pretty sure the data from the Ultra will be worthless, so I'm going to wear my Garmin as well.

I'll report my findings then.

[TheRabbi]

Welp, same trash with the latest software update. Samsung obviously doesn't care.

[usercgm2tBm3uM]

Having same issues with watch 7 and ui8. Used to be very accurate!😡

[TheRabbi]

OneUI8 ruins every watch it gets downloaded on.

It's going on seven months since I made them aware of this issue during the Beta, and they still haven't done anything about it. Let's just say: I've gone back to wearing my Garmin Venu for now; it hasn't missed a lap. Right now, I'm syncing the Garmin activity to Samsung Health, but since bad tracking ruins everything else in Samsung Health, I'm probably just going to uninstall it and stick with Garmin Connect.