Distance tracking bug instinct 2x

There seems to be a bug when tracking longer distances:

When using the the watch to track drives with the car the max distance recorded is always 167.xx km even though the actual distance was longer. The track in the map is correct though. This happened 5 times using the track me activity.

Top Replies

All Replies

  • Your watch is not designed around using the Track Me option for 100+ mile car rides. Our Automotive Drive series devices are designed around what you have described.

  • Thank you for the quick clarification. However, I would like to understand what the reason for the limitation is. If it's a memory thing, would ultratrac be a way to track longer distances?

    And does the limitation also apply to the overland activity, which clearly is designed to be used driving a vehicle?

  • If it's a memory thing,

    Since you tell the track is full, it does not seem to be caused by any memory limitation. Cycling GPS activities over 167 km are quite common (even here, at Instinct 2 users), so technically there should be no problem tracking longer tracks with other activity types either. To me, it looks like an intentional limitation, or some unintentional omission specifically in this activity profile.

    would ultratrac be a way to track longer distances?

    You can try it, but I doubt it will make any difference. It looks like a limitation of the Track Me activity profile.

    And does the limitation also apply to the overland activity, which clearly is designed to be used driving a vehicle?

    Please try it, and let us know. If not, try using eBike or something similar.

    And if you want to see the true distance at your old activities, you can save the respective activity as Course and then view the distance in Courses. And if your account is linked to Strava, there is another possibility there - using the feature "Correct Distance" recalculates the distance using the GPS track data, so it should give you the true distance too.

  • So, ultratrac seems to have the same limitation. A 350km drive registered as 152.4 km. The track line is okay though. When I view the activity in Garmin explore the distance is still wrong. Funnily though, when I copy the activity as a course that new one shows the correct distance. 

    I really think this should be fixed by Garmin. When the points are there, why shouldn't the watch be able to calculate the distance correctly? And if it's really a hardware limitation, at least there should be some notification that it can't track the distance any longer.