Mobile Apps & Web

Garmin Connect Mobile Android Bug: Distance always 2,500m for uploaded pool swim activities

This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Bug: Distance always 2,500m for uploaded pool swim activities

Former Member over 10 years ago

In the list of activities in the Garmin Connect Android App, every pool swim activity uploaded from either my Garmin Swim or 920XT shows a distance of 2,500m. When I select an activity to get the details, then I get the correct distance. Currently using Garmin Connect 2.7 on a Nexus 4 with Android 4.4.4. The web interface is fine.

(Moved from Garmin Connect forum)

0 Former Member over 10 years ago

The swimming distances will now appear correctly when using the latest 2.7.5 version of Garmin Connect Mobile.

0 Former Member over 10 years ago

I get 5000m per swim every time.

Are you swimming in a 50m pool?

0 Former Member over 10 years ago

The swimming distances will now appear correctly when using the latest 2.7.5 version of Garmin Connect Mobile.

I updated to 2.7.5 and there is no change for me. Still showing 2,500m in the activity list.

0 Jojo1981 over 10 years ago

No change - all swimming activities in a 25 metre pool are being shown as 2 500 metres swimm.

0 Former Member over 10 years ago

I'm on 2.7.5 and still all swims are 2500m

0 Former Member over 10 years ago

I use 2.7.5 GCM, pool size 50m.
Community list and details are fine (1500 m), but Activities list is still wrong (5000 m).

Community.png
Details.png
Avtivites.png

Ps.: I can't insert image. Upload fail ...

0 jetsers over 10 years ago

also on 2.7.5 and I am still getting the same issues as reported.
Its not a big deal or anything, just a minor bug.

0 Former Member over 10 years ago

The fix did not make it into the 2.7.5 release. It will be in the 2.8.x release (in the next week or so).

0 Former Member over 10 years ago

I upgraded to 2.8. Now distance of swimming is good. :D

0 Former Member over 10 years ago

This was fixed in the latest 2.8 version. Thank you for your patience.