Backcountry/Skiing/Snowboarding Unified thread

I’m creating this thread to centralize all the various bugs and issues related to these similar mountaineering activities in the hopes that Garmin engineers will work with us experienced riders to fix them and make them truly useful and more functional. And hopefully quickly as the ski season has just begun ! Please contribute to this thread, upvote it, and keep it alive and visible so that Garmin makes fixing these activities a PRIORITY.

Scroll down to TLDR for the list of bugs.

Backcountry Skiing

In France, backcountry skiing often includes a section with a gondola ride. Or tram, or train. I’m thinking Chamonix, Aiguille du midi, Grands-Montets etc. Backcountry activities should include the option to Auto-pause gondola rides and not include the added vertical to the ascents.

Example : I start in the village of Argentiere 1200m and take the gondola up to the Bochard station at 2800m, I ski back down to the intermediary station (1980m) , and do this once or twice to warm up. Then I take the gondola back up a third time but this time only ski down 100m, then put on my skins and climb up to the Grands Montets peak at 3250m. I ski down to the mid station and repeat this gondola/skin combo a few times, but on my last descent from the top of Grands Montets I ski all the way down to the village at 1250m. Then If I’m really motivated I may take the gondola up once more to to the mid station to do a final run back down to the village. None of these gondola rides up should be included in my vertical ascent. But if I have to manually pause the activity there’s a good chance I’ll forget to pause or unpause it. It should be SET and FORGET.

On the way up to Grands Montets, I cross a mountain pass with a hut that everyone uses as an intermediary reference point (it’s a useful gauge to see how you’re doing). In Auto Tracking mode, clicking the lap button adds a lap. So ideally i’d hit the lap button when I pass the hut to see my split time, which I do see on the watch face - but this data gets lost and you don’t see it in the Garmin Connect app afterwards. Under the “Splits” tab, you see the ascent|transition|descents only. None of the manually pressed laps during the activity.

In real world conditions, I’m often skiing with my friends. We’re laughing and joking on the gondola ride up, it’s cold and i have gloves on and a thick jacket. If I have to pause the activity to avoid counting the gondola ride up, there’s a good chance I’ll forget to start it again up top. It’s also a pain in the ass to take off gloves, unvelcro my jacket sleeve to unpause the watch. Also when transitioning, it’s often cold and windy and you want to get the skins on as quickly as possible - and often forget to start the activity. Then when you get to the top, you have a sandwich, some hot tea, , talk trash with your buddies have a swig of some strong local beverage (génépi anyone?) , before taking off again and forgetting to start the watch. This is why why auto-detect everything is so useful. I just want to set it and forget it.

When I get back home, I just want to see the total distance I climbed, how fast I ascended (MAX VERTICAL SPEED), my AVERAGE VERTICAL SPEED, my TOP SPEED on the way down, and the total distance I skied down.  I want to see these values for the activity as a whole, and for each separate split (Ascent Descent). The LAST thing I want is to spend more time trying to figure out what Garmin tried calculating than the actual time spent doing the activity !

In auto tracking mode , the lap button triggers a lap, but this lap doesn’t get displayed anywhere.

Descents always shows hundreds of meters of vertical ASCENT, I assume this is a bug ?

When you hit pause in MANUAL TRACKING mode, then scroll down and tap “lap”, it changes from ascend to descend and remains in pause mode. BUT the screen no longer displays a red ring around the menu which is a bit confusing when you’re on the mountain and in a rush. If you then tap  “resume later” the red ring is still NOT visible.

TLDR

So to recap :

Ascent vertical should include physical climbing only, no vertical should be added from any gondola ride up.

Descent vertical should include ANY and ALL skiing regardless of how you got to the top. Skiing is skiing.

Manual laps should be saved in the activity and visible in Garmin Connect. Vertical ascent speed should also be calculated per lap. These manual laps should be calculated relative to the current ascent or descent : so the first time you hit the lap button the elapsed time will be calculated based on the time the ascent started. The second manual lap relative to the first etc.. These manual laps could have a separate tab in GC, or be included in the Splits Tab with a stopwatch icon and lap number (1,2,3..)

Average and Maximum vertical ascent speeds should be visible for the activity as a whole and per ascent. These metrics should be visible in Garmin Connect and in the activity on the watch. The “Stats” tab should include the average and maximum vertical speeds for the activity as a whole, while the “Splits” tab should show these metrics per ascent /descent.

The splits numbering sequence in GC is also confusing. Ascending and descending should probably have their own sequence. So ascent 1 followed by descent 1 in the order they were done. You could conceivably have multiple descents before an ascent if you are taking a gondola ride. Maybe the gondola ride could be shown in orange as an ascent without the vertical being calculated in the stats.

There should be no large vertical ascent data, during a Descent with no climbing, in the splits tab - bug ?

When set to MANUAL TRACKING, the red pause ring should be visible after tapping “lap” on the pause screen, same after “resume later”. Bug?

Skiing and snowboarding activities should not count gondola rides as separate laps. Or else at least give you the option not to include them with a toggle.

Hopefully we can get these issues sorted out quickly - Thanks to every who contributes to this thread and please help keep it alive until the problems are fixed !

  • This is the bug list that I reported via PM to Chris:

    1. While the activity is running, Whatsapp messages lack the "mark as read" option

    2. In Backcountry Skiing activity settings there is no toggle to disable the lap button (even if you have mode tracking to auto).

    3. I experienced a strange behavior while trying to scroll the map via touch. The map scrolled ok, but at the next touch to scroll it further, the center of the map would go back roughly to the previous starting place and then scroll again. And it went on like this, making it impossible to scroll more than 1 screen length. This happened only in one the only two recording that i made after the update.
    see here: https://youtu.be/xHnHYrta4D8?feature=shared

    4. Backcountry Skiing activity on GC for Android:
    In the summary of the activity, the mini map shows starting, ending and transition points, but not the route:

    https://ibb.co/1rMV0JH

    but inside the map main screen, the route is visible.

    https://ibb.co/2dMtF4N

    This does not happen in the other activities

  • Ok thanks for that. For point number 2, Garmin makes it confusing : in Manual Tracking the lap button changes between ascent and descent and adds a split/lap time that gets transferred to GC , but in auto tracking the lap button displays a lap/split time which disappears into oblivion and is NOT transferred to GC. So it’s not very functional to begin with.. it would be nice to have the option to toggle it AND to have the split time saved to GC. 

  • 1. number of runs on watch is doubled

    2. total descent vs. sum of descents in the lap section does not match 

    3. from time to time a run (ride) is not recorded

    4. it takes sometimes up to a minute for the run to stop (meaning sitting already 1 min on the lift going up and time still runs).

    5. total distance disappears from watch (last activity function) after save and sync

    6. total distance in CG on main activity screen does not match with  sum of laps distance

    I assume they have a mess recognising what is ride what is lift and data is sometimes being combined, sometimes not. 

    Those would be my issues experienced in last 3 days. 
    Tomas

    p.s. This is also being discussed on beta forum as I am running beta 15.74.

    Would make sense that people also write what FW version they are on

  • After my first Ski tour with a Fenix 7/Epix 2 I found out that in mobile app the track is all red even though it says that red is for ascents. Secondly, the graph shows almost the whole ascent as transition. Also, on mobile the track is horribly inaccurate meaning far less GPS points so you can't really see tight turns but you CAN see them in web browser. And finally, when it comes to Fenix 7, backcountry skiing is the only app displaying black backgrounds even though they're set to white.

  • I use FENIX 7 and have the same problems.
    I can confirm the problems after the update in these points:

    1. number of runs on watch is doubled

    2. total descent vs. sum of descents in the lap section does not match 

    3. from time to time a run (ride) is not recorded

  • I have been experiencing inconsistent backcountry recording (ok for the most part except steps don't get counted on the uphills) and abysmal snowboard (resort) reporting. I ride all day but Garmin says I took 0 lifts, did 1-3 runs, did some vertical, and did almost no distance. Frustrating as it performed so well last season. 

  • https://forums.garmin.com/beta-program/fenix-7-series/f/announcements/354281/v15-76---live-release

    Fixed an issue where some ski/snowboard runs were not tracked as expected.
    Fixed an issue where ski/snowboard total descent was not reported correctly.

  • Fixes count of rides, total descent. 

    does not fix total distance vs sum of all laps. looks like still adds lifts to total distance on main CG activity screen. Watch indicated correctly. 

  • does not fix total distance vs sum of all laps. looks like still adds lifts to total distance on main CG activity screen. Watch indicated correctly. 

    This will be a future fix. The overall process of making the changes needed are not 100% complete.