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]

I'll keep this thread posted. Yeah, it's comically bad; I have a couple of old Garmins that still count lengths correctly. I'd switched back to Samsung watches because the Watch 7 Ultra was DEAD ACCURATE. Soon as it got UI8, however, it took a total dump. Since the 2025 Ultra has the same issue, it's gotta be in the new OS.

[TheRabbi]

UPDATE: The tech support team got back to me today. They've confirmed the bug and are working on a fix!

I'm glad they at least noticed something is wrong. I swam with both my Watch Ultra AND an old Garmin Venu today. The Garmin perfectly counted 110 lengths; my Ultra counted 134. 🤨

[Herminator3]

I have EXACTLY THE SAME problem. Then at the end it multiplies the inflated lengths times 25 yards to give an inflated distance swum.

[Herminator3]

How will I know when the fix is out?

[TheRabbi]

At this point, I'm not sure. I've resorted to using my old Garmin Venu and using another app to sync my swims to Samsung Health. If they don't fix it in the next two months, this will be my last Samsung watch.

[realaud]

Did you ever put in an error report and send your logs? I have a watch 7 and I swim and I have not noticed a change in length or lap count; but, then again, I don't really pay much attention to that, as I swim by time only. But, I normally do check the length count and distance, which I know to be inaccurate anyway because no one knows the actual length of my community pool and I can only estimate. I do not yet, however, have OneUI8 on my watch, so I don't know if that will change when I get it. It seems like everyone has it already except me, but I'm not anxious for it, as it's ugly.

[TheRabbi]

First, I put in about six error reports and provided everything they asked for: logs, screenshots, extra logs....

Second: If you have OneUI 7, you have an accurate watch (not that you seem to care about length counts). Before my Watch 7 Ultra got OneUI8, it measured 110 lengths perfectly, every time. Once it got OneUI8, it started over-counting to the tune of HALF A MILE. I bought an 8 Classic and the 2025 Ultra, and they're both doing the same thing. Tech Support confirmed the issue based on what I sent them, but have yet to issue a fix.

Like I said, my 5-year-old Garmin measures the laps perfectly. I stopped using it because Samsung had actually caught up with accuracy, but it's back on my wrist for workouts because the Galaxy Watch is woefully inaccurate.

[realaud]

Ok.

[TheRabbi]

Trust me: stay on OneUI7. 😊 I'll post an update when and IF Samsung actually fixes the issue. I hope they're not just stringing us along.

[usercTNjnFfk41]

Well I wondered why all of a sudden my lap count was so far off, but I have the opposite problem - it doesn't see some of the turns so it undercounts the laps.  I'm just going on time for now.  I had a Watch 5 that rarely missed a lap but my 8 Classic is having the problem.  Hopefully they'll make a software fix for this.