Related
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

Absurd speeds and distances

Nytaros
over 1 year ago

Hi all, 

Lately my wife's vivosmart 5 is calculating absurd intervals and statistics.

Recently we went on a walk where she apparently walked vastly libger than I did. Inspecting the data she apparently managed to walk 4.63 km in 1.1 seconds. Or minutes? Both pretty astonishing. 

Today we went biking. Again, she achieved inhuman feats:

She is getting pretty serious with her biking. But I'm fairly certain she did not go 237 kph on her bike. Even better, she did manage to achieve this 5 kilometers of this interval in just about 300 meters.

This may be related:

Pretty sure her bike isn't rated for this speed. I plan to do a full inspection on her bike just in case she did achieve 0.2 percent of the speedbof light on her bike.

Jokes aside this is a recent development and we are wondering if this may be related to the update about a week ago. GPS is done on the phone, we know, but it does seem illogical that there are no safeguards against data or GPS issues when calculating speed or distance. I have had flawless GPS reception during the same ride. On my 955 as well as the phone. She and I both use a samsung s23 in case that is something you are interested in.

Any tips how to improve the situation?

  • 0 over 1 year ago in reply to christoph

    A bikeride of 22 km was registered as 37 km. Cause: in the first record/trackpoint the distance was 15 km instead of 0, following distances were correct, but total is 15 too high.

    I reset the device to factory settings, wondering if that helps.

  • 0 over 1 year ago in reply to ctammes

    I have found the same thing, I think. If I'm going to have a problem with the distance it will show right at the start. It will show one lap complete and a distance. All I did was start the walk. 

  • 0 over 1 year ago in reply to navionic

    I'm changing my review. There is a problem, but it seems to me that Garmin doesn’t want to deal with it.

    up

  • 0 over 1 year ago in reply to navionic

    I'm tempted to get a Fitbit charge 6 because of this issue. Such a pain in the ass to restart the device every time I want to record a ride.

  • 0 over 1 year ago in reply to Garmin-Sara

    I have the same situation for 3 days. First time it calculated 0 km, yesterday it calculated 1.85 km instead of about 3.5 km, today I walked 700 meters and it calculated 77.85 km.

    Routs in the maps are created correctly.

    Vivosmart 5 software version 3.22, Android app version 4.73.4.

    • Do we have permission to contact you via email? YES
    • Do we have permission to access your Garmin Connect account? YES
    • What Country are you located in? LITHUANIA
  • 0 over 1 year ago in reply to navionic

    I have the exact same issue. Since a few weeks, my watch says I ran about 80 km for every km that I actually ran. I can also walk and it will report my maximum heart rate constantly for hours to go. Support tells me that the precision of measuring can vary from person to person and from connected phone to phone. They ignore that I tell them the watch has been accurate for some time, but this is screaming 'technical error'

  • 0 over 1 year ago

    Hey mate, I had the same issue. Simply resetting the watch solved the situation for me. Before I have tried to change my smartphone, reinstall the connect app, remove and reconnect the watch. Resetting was the big help. I hope it works for you as well! Some firmware update seemed to need the reset.

  • 0 over 1 year ago in reply to 4045371

    It's now been a couple of days since I reset my Garmin. So far it seems to be working.

  • 0 over 1 year ago in reply to 4045371

    My friend, I sold the bracelet a month ago. I'm tired of overloading it every time before activity and looking for new solutions to problems.

  • 0 over 1 year ago

    THIS is what I have been experiencing for a week. Now I am a little frustrated because it was written 7 months ago. Was everything fixed (and being happening again)? Or am I the only person who struggles with this issue now?