Original topic:

Incorrect Swimming Pace Calculation in Samsung Health -- Anyone Else Noticing Th

(Topic created: 06-05-2025 06:05 AM)
517 Views
CindyJoy
Constellation
Options
Galaxy Watch
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.

0 Likes
2 Replies
realaud
Honored Contributor
Options
Galaxy Watch
0 Likes
CindyJoy
Constellation
Options
Galaxy Watch
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.
0 Likes