7.00 Fenix 5X Pool Swim Inaccurate

Just thought I'd report this, will send to beta team once I find the email for them.

Pool swimming seemed to be pretty good up until v7.00.

Pool length 50m
Pool length setting 50m
Swim stroke detection on. I have found turning this off can improve the recording, Im sure my swimming stroke is not elegant enough.

Swam 1000m
Watch recorded 1800m. Seems way to far off, almost like it was set to 25m.
  • Post a link to the activity, and a previous one for comparison?
  • I have another problem instead: if you leave default setting in swimming pool app, the lengths count works normally, but if you customize data field or add/remove pages, the lengths count start to go crazy: for example, if you swim 2 lengths the watch report 25m (1 length) until u will press lap or stop than magically the lengths became 2! It's very annoying since you can't trust in lengths count until you have finished a repeated...
  • Former Member
    0 Former Member over 7 years ago
    This is the exact problem I am having, due to eyesight in the pool, I have a custom screen that only shows set lengths & set pace. Up until a few weeks ago, it was perfect. Now it is always a length behind until you press lap or stop button!!

    So frustrating when something breaks that was working, bought the Fenix 5 to get away from separate run and swim watches.

    How do we raise an issue, seems impossible to get through to Garmin even after buying a £400 watch.
  • I have just had a reply from beta team. The are aware of this bug and they are working on a fix!
  • Former Member
    0 Former Member over 7 years ago
    They are aware because the bug is there and I noticed it as soon as you wrote about it.
    It's easy to spot because the watch has always been perfect in length detection until a few patches ago, as written by Maruzko. I did not report it because I'm swimming 25% of other water activities (Hydrobike and Aquagym) where I reported a few nasty bugs as well. The "problem" being I am mostly only swimming to warmup for the other 2 activities and if I engage the pool swim activity then I have to get out of the water to get the HR data and WAIT 2 minutes for the RecHR and TimeDec data. There is also a very serious problem with the HRMSwim which only appears if you are doing these activities and not if you do the pool swimming alone.
    Wilbur you can contact the DEVs at [email][email protected][/email] (explain the issue in detail and attach the .fit file for them to examine).
  • Up until a few weeks ago, it was perfect. Now it is always a length behind until you press lap or stop button!!


    I'm glad you said this as I "upgraded" from an F3X and was grossly disappointed with the SWIM performance of the F5X with the lap reporting and counting. The F3X was absolutely bullet proof when it came to lap counting. I don't swim that many laps per session so every one is important! lol.
  • Former Member
    0 Former Member over 7 years ago
    The F5X is as perfect as the F3, it's a patch that messed up the counter but here is important to note unless you're very proficient when hitting the block and pushing away and in managing others in your lane (at the block, pre-block or during the passes) it's easy to mess things up and then put the blame on the watch. I am VERY proficient in these so I know Renton is right in his report and Wilbur too (and Garmin in fact acknowledged the issue and is working on it).

    Gary you can fix the logs with the tool: http://www.swimmingwatchtools.com/ but of course this doesn't help during the activity. If I was swimming instead of doing aqua/hydro I'd be crazy with messed up data in the fields. Let's hope they fix it soon.
  • In 2.5 years of swimming using the F3X I never had one missed or miscounted lap. This problem with the F5X does not seem related to my swimming style or end of/starting of lap behaviour. I am hoping it is not accelerometer related.

    Thank you for the advice about the tool - unfortunately I have had to use it several times since purchasing my F5X. And I agree, let's hope it is fixed soon.
  • Post a link to the activity, and a previous one for comparison?


    Good tracking example 1025m
    https://connect.garmin.com/modern/ac...ErQiBZPs.email

    Bad tracking example logged 3300m but swam 1000m
    https://connect.garmin.com/modern/ac...E1ZjU14k.email

    Bad tracking example logged 1750mm but swam 1000m
    https://connect.garmin.com/modern/ac...E8Y4RuIw.email

    I also had a F3HR previously which tracked swimming laps fairly accurately.
  • Former Member
    0 Former Member over 7 years ago
    I haven't had this kind of errors. I have the kind of errors Renton described.
    It's ONE missing length, always.