Hi everyone, I wanted to bring attention to a recurring error I’ve noticed with the swimming tracker on my Galaxy Watch (specifically when swimming in a 25-yard pool). The issue is with the pace per 100 yards—it's consistently miscalculated.
Example: If I swim a 25-yard lap in 25.2 seconds, Samsung Health reports a pace of 1'32" per 100 yards. But mathematically: 25.2 seconds × 4 = 100.8 seconds for 100 yards That’s 1 minute and 40.8 seconds, not 1'32" So the app is reporting a much faster pace than reality, which can be really misleading if you’re trying to track your swim progress accurately.
--- Why This Matters: It throws off training benchmarks You can't reliably compare workout progress over time The error might be rooted in a formula or unit mismatch (yards vs meters?) I’ve already submitted a report through Samsung Members and included exported health data and logs. But I haven’t seen any fixes or acknowledgments so far, which makes me wonder if others have noticed this too.
--- If you've seen this issue: Try checking your lap times and pace manually If it doesn’t match, consider submitting a report via Samsung Members Include log data (you’ll get the option when you submit) The more users report this, the more likely it is to get noticed Just wanted to share in case others are seeing the same thing and wondering if they’re doing the math wrong—you’re not! Let’s hope Samsung takes a closer look at this soon.
------------------------------------------------------------- Please mark any response that helped you as your solution. -------------------------------------------------------------
Thanks for the suggestion. I’ve already submitted detailed feedback through Samsung Members, including exported data and log files. That was several weeks ago, and so far there’s been no fix—or even confirmation that the issue is being addressed.
At this point, it seems like the bug just isn’t a high priority for the development team. I’m posting here in the hope that if more users notice and report it, it might finally get the attention it deserves.
This is a basic math error affecting workout accuracy, and it's frustrating to see it persist in such an otherwise advanced fitness platform.
I have seen this issue in my earlier Samsung Galaxy watch and the sams issue exists in the new Samsung Ultra that I've upgraded to. Seems more like a software issue then. The issue occurs more when you swim with long reach strokes in.free style. I get the correct pace for breaststroke.
And the pace is calculated correctly in a 50m pool. For some odd reason the turn time is just skipped for pace calculation per 100m when swimming in a 25m pool
I hope they solve this through some update soon. Can any of Garmin or Apple users comment if they get the same.issue in those products?
Thank you so much for taking the time to post this explanation. I really appreciate you clarifying what’s going on with the pace calculation in 25m pools. That makes a lot of sense now.
That said, it’s really unfortunate from a swimmer’s perspective. If the turn time is being skipped when calculating the 100m (or 100y) pace, then the number is essentially useless for actual training. As swimmers, we need the pace to reflect how long it actually takes to swim 100 yards including turns—because that’s how real races and workouts are structured. Excluding turn time gives an unrealistically fast pace and doesn’t help us gauge or track real-world performance.
Hopefully Samsung can revise the calculation so that the reported pace reflects total swim time, not just the mid-pool speed.
