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

Ski Activity on Forerunner 265S counting descents and also ascents in chairlift

Hello everyone,

Yesterday I went skiing with my Garmin 265S watch. I used the specific build-in application called "Ski". Unfortunately after I finished the activity and it got uploaded to Garmin Connect App (iOS system), it showed me double the distance that I've made, because it counted both ascents and descents (the chairlifts are even shown in a different color). What is even more surprising, is that on the tab called "Runs" it shows the exact amount of descents that I've made and the correct totals.
Also, the second issue is that the watch kept creating new laps every time I moved in the queue to the chairlift, making an enormous 68 runs which in reality I've made 19 of them.
My wife using 2 years old Venu 2S with a built-in app "Ski" has correct data and her watch stops automatically when she enters the queue to the chairlift.
Did anyone encounter similar issues? Didn't find any way to adjust the data in Garmin Connect App to show (and upload to Strava) only descents.

Garmin Forerunner 265S version: 17.26 (DFU-4d1582)

Garmin Connect Version: 4.73.1.6

Disclaimer for Garmin Team: YES, you have permission to email me. YES, you have permission to view/access my Garmin Connect Account. I live in Poland, Europe. 

  • I'm having the same issues. My old Forerunner 645 counted ski runs correctly using the ski activity, but the 265 does not, I'm also getting double the distance, chair-lift rides counted as "runs", and an extra lap at the bottom of each lift if I wait for more than a minute. I actually upgraded to a Venu 3 last week, which had this problem, but then quickly exchanged it for the 265 (to get more training insights) and it also has this problem...

    Interestingly the GPS paths for the Forerunner 265 are much better than the 645, it's the extra laps and distance from lift rides that are broken.

    Garmin Forerunner 265 version 17.26, with Garmin Connect on Android, in Colorado, USA

  • Same issue on fenix 7. And more interesting it was recording properly early December and since 3 days ago started to log ascent. It seems some issue on the garmin side 

  • All,

    We have been working on improvements for the ski activity profile. I am not sure when these improvements will be available at this time. With your permission, please 'vote up' on this comment so I can add you to the impact of our report. 

  • I have the same problem on the Fenix 7 PRO. For one of the top models I would expect an immediate fix and apology, but Garmin doesn't seem to be doing anything about it. This is probably the third skiing problem in the last year. Very disappointing.

    EDIT: the calculation is not only wrong for distance, but also for average speed, so the watch is useless this winter.
    EDIT2: the data are correct in the web version of Connect, I don't understand why they are wrong in the mobile app and in the export to Strava...

  • Today's update to Garmin Connect has corrected the data in the app. Unfortunately it didn't affect the watch retrospectively, plus I guess a fix will still be needed in the watch software, so is this more of a temporary patch?

  • Similar issue here, use to record perfectly with my 645, but getting double runs on the watch. It ends a run whenever I stop, even if it's in the middle of a hill. The 645 used to only create a lap when it sensed I was on a chair lift. A short term fix would be to turn off the Auto run run feature in the ski settings, and just manually record a lap with the lap key every time you get on a lift. However, since the issue seems to be fixed on the Connect side (the correct number of runs is shown there), I may just leave the auto run feature on & hope a fix comes to the watch soon.

    There is definitely something funky going on in the code. Even though Connect shows the correct number of runs, when I look at the activity in Strava, it lists the incorrect number of runs from the watch.

  • Exactly, also noticed the same. Strava keep double count, not sure how its possible when Connect shows corrent runs. Lets wait for a a fix. Although winter season is almost overJoy

  • Hello spacehippie2k.

    Garmin Team has been working on this issue and there is already beta version of new upgrade (18.15). You can download this by participating in beta testing program (https://support.garmin.com/en-US/?faq=bVo5U5BV292BSr2gkZhY2A&searchQuery=beta%20program) or just wait for the official version of update. 

    Hasn't tried yet if the new version works as the weather in my country changed dramatically but this week I'm planning to go abroad and will have occasion to check it.

    Cheers!

  • Hello!

    Yesterday I went for ski and tried new update. It looks like the problem is fixed. 54km on Garmin Connect -> 54km on Strava. Activity was on all of the time, with AutoPause Off. Good job Garmin Team!