Komoot app for Garmin - distance cut in half

I went for a hike yesterday using Komoot app for Garmin on Venu 3 watch. I followed a route previously planned in Komoot on web.

After about 2.1 km the watch stopped increasing distance travelled, and for the next cca 4.5km it showed that number of 2.1 km as the total distance travelled, after which point it resumed tracking distance for a total of 4.38 km acummulated tracked distance (obviously ignoring 4.5km travelled between since it stopped increasing distance traveled until it resumed again).

The result is the gps track that is correct, but the total distance is cut in half, 4.38 km recorded vs 8.6km planned.

This part of the route is ignored in total distance:

This is a major problem with Komoot app for Garmin, and a deal breaker for me, because when this activity is exported to Garmin Connect it will account for drastically lower distance. 

I have paid premium subscription for Komoot because I wanted navigation with maps on Garmin Venu 3, but I didn't know I had to settle for distance travelled cut in half.

Anyone else with similar issue?

  • Have you used "Contact Developer" for the Komoot app?  Garmin doesn't have the source code, so Komoot may be the ones ones that can help, even if it turns out to be a Garmin bug..

  • Haven't used Komoot on the watch yet, but there was an update for it about 3 days ago. You can easily check this with Garmin Express on the PC or Connect IQ on your mobile phone. Or maybe they broke it in this update.

  • Hi 1514695

    I had the same problem on my Venu 3 with the Komoot app.

    However using it for a 2nd tracking it worked without issues and shows the complete distance till now

    So give it another try

  • I am the komoot developer and we are looking on these issues.

    So far I have not been able to replicate it. It seems to be only related to Venu 3 (we haven't received any similar reports from other devices).

    We are using the in-built activity recording. We just start the recording and then finish it. Everything from the route recording to activity upload is handled by the Garmin's firmware. We have no influence on this.

    You can try to enable / disable the automatic pause of the activity. Is it a difference if you lock the display, or not? What is your display settings, always on, or only when looking? Can you try recording an activity with another Connect IQ app, for example the My InLine?

    Thank you, Tomas

  • I have tried it with latest update and version before, and the issue is still there.

  • Tomas. my display is set to turn on when looking. Will try your other suggestions.

  • On 2 out of 3 tests of the Komoot app the distance was cut in half (real distance >3km), on the other test it was comparable to real,but the total distance was <2km.

  • Hello Tomas,

    I think I have found a bug regarding this issue.

    We are using the in-built activity recording. We just start the recording and then finish it. Everything from the route recording to activity upload is handled by the Garmin's firmware. We have no influence on this.

    You have  the option in Komoot app for Garmin to pause or finish recording (on the last data screen). Therefore this is under your control by using some Garmin API call I presume. I am not Garmin developer so this is purely speculative.0

    I am thinking you are not handling Garmin events right, and by this I mean when user interacts with watch outside of your app, like for instance, swipes to the right to see the watch face and then looks at the glances etc, and in the end swiping to the left to return to your app.

    It seems to me that when user leaves your app to see watch face, that you are pausing the recording (which you should not be doing because user should be allowed to look at the time or other glances while he is recording the activity) and then when user gets back on the Komoot app screen you forget to unpause it.

    Anyway, here is the elevation/distance graph of my last recording to demonstrate it more clearly:

    At around 1,83km distance I looked at the watch face at glanced to see step count, then I returned to the komoot app.

    After that you see on the graph a jump in elevation because komooot app paused the recording until later when I manually pressed pause/resume button at which point the activity recording resumed.

    To see If I can recreate this issue, I tried again at 2.0km swiping right and checking step count, and after that swiping to the left to get back to the komoot app screen, and sure enough the recording paused again, because the displayed distance was stuck at 2.0 km and not increasing. But after a while when I pressed the first button twice to force pause/resume recording, the distance displayed started increasing again indicating the recording had resumed.

    So there it is, a way to recreate the issue. If it is under control of Komoot developers, I think you should be able to fix it easy. But, if all of this is in Garmins domain then I hope their developers are reading this forum and they will find time to test and fix this issue with Komoot app now that it is easily reproducible.

    Maybe this steps should be reproduced with another app, like Tomas mentioned. If the issue persists, then it is in Garmins domain.

  • Today I have tried above mentiined steps with another app from Connect IQ store, Low power activity recorder, and I can confirm the same issue here.

    So either do both of these apps have the same bugs, or there is a problem with Garmin Venu 3 firmware. That of pausing activity recording when swiping out of the app into watch face.

    Maybe the newly added touch screen interface to Garmin smartwatches needs some extra polishing.

    Hope the fix comes soon, in the meanwhile there is this workaround of manually resuming activity, just have to remember it every time you glance away from the main app.

  • Thank you for the info, that's very useful.

    Yes, there seems to be some difference between the watch models (Venu vs. Fenix). Which firmware do you have in your Venu 3?

    We will look on the fix.