Assuming the 935 is identical to the Fenix 5 with regards the Run and Trail…
Doubt it is that simple. Anyway on most "trail" runs I have done your speed is vastly influenced by not just elevation but what you find under your feet and/or have to swerve round. In other words you…
Assuming the 935 is identical to the Fenix 5 with regards the Run and Trail Run apps, the default App settings and data screens are configured slightly differently and Garmin Connect does automatically recognise them distinctly as Run or Trail Run. But the key difference is less obvious and not in the manual; Trail Run inhibits the calculation of VO2 Max and LTHR. (A past implementation on the Fenix 3, as users were frustrated with bad VO2 Max figures calculated whilst running up and down steep terrain etc.)
Trail Run inhibits the calculation of VO2 Max and LTHR. (A past implementation on the Fenix 3, as users were frustrated with bad VO2 Max figures calculated whilst running up and down steep terrain etc.)
Wow, that explains a lot - I mostly do trail running and was wondering why I wasn't getting VO2M readings. How did you know that if it wasn't in the manual? Too bad they decided to just disable it instead of reconfiguring the algorithm to account for altitude.
Doubt it is that simple. Anyway on most "trail" runs I have done your speed is vastly influenced by not just elevation but what you find under your feet and/or have to swerve round. In other words you are going to go "slow" anyway and so trying to estimate something that is basically a figure that is meant to be for flat and firm road runs seems a bit pointless.
How did you know that if it wasn't in the manual?
Doubt it is that simple. Anyway on most "trail" runs I have done your speed is vastly influenced by not just elevation but what you find under your feet and/or have to swerve round. In other words you are going to go "slow" anyway and so trying to estimate something that is basically a figure that is meant to be for flat and firm road runs seems a bit pointless.