Here is every data field you can choose out of the different categories they fall under. Once you have found the correct data fields that match what you want, it will be easier to find them going through the categories: Fenix 5 Series Data Fields
Hopeless, to be honest I am surprised these two fields are present in F5+ at all even if also you did confirm that they are strictly restricted to Climbs, which btw I did not check.
My experience is that disposal of Moving and Stopped time is related to handhelds, neither triathlon watches nor outdoor wearables dont offer them.
I can also confirm that it is not possible to add every field to every activity. I was not aware of that, maybe because I never used those fields. For cycling I use the Auto Pause Funktion which works very well there, For running I pause manually, because there the current pace is not very reliable and it can happen that the watch pauses when you are running a steep hill under dense trees. So I have the information about my moving time and the whole time is shown in the app after uploading.
Before you all confirmed it I had reported it Garmin support with a slight hope that somebody else would do the same and finally these metrics will introduce to Fenix family generally.
My pain is that auto stop works quite unreliably at slow speed, so I switch it off and on for walk and hike periodically. Tested both When stopped option and the lowest available speed, namely 1.6 km/h.
As mentioned I use Auto Stop only for cycling and not for slower activities.
But I don't get your point when it comes to hiking. In the hiking-app you can use all timer data fields - if you really think it is relevant to know during the hike how much time you were in movement or standing, you can easily configure a screen with that.
1. Originally I was not looking for special timer data, timer and elapsed time was enough for me. I used auto stop fpr everything, with a cut-off speed of 3 km/h for running and cycling, and 1.6 km/h for walking and hiking. Thus timer showed the moving time and elapsed time moving+stopped.
2. After a while I realized that for me auto pause works only with open sky conditions for wlak and hike. Among trees auto pause gave me false signals of stops and restarts. Sometimes it beeps and vibrates by 2-3 seconds even if I climb a hill at 3-4 km/h. And this behavior was independent from setting to GPS or GPS+Glonass.
3. Therefore I started to switch off and on auto pause and test it as I wrote before.
4. Accidently I found the stopped and moving time like days ago, so I set them for hike and got rid of auto pause. But I did not have the time to thoroughly test it.
5. But as I wrote, too, there are no stopped and moving time for walk, so I know I will be still struggling with auto pause.
So when you dont get the point when it comes to hiking, it is understandable, but
As the error of the current pace is very high at low pace, auto stop doesn't work well then. I once read that the reason should be, that at low speed the device cannot differentiate well between real and reflected signals.
If the hiking app has all data fields you need, why not tracking everything with hiking? You can change it later in the app to whatever you want.
I have seen a discussion somewhere in the forum, whether Walking refers to the athletics discipline Walking....
I would like to see this added and am surprised it hasn't been. Makes you think maybe the programmers/developers don't actually use these products they make. Strava seems to have no problem calculating moving time (and it's also deep in connect), so the data is there and shouldn't be too difficult to add this Data field on the device. You would think.
