The average move speed and average move pace are showing as blank on the activity recorded after FW 12.23 update
The average move speed and average move pace are showing as blank on the activity recorded after FW 12.23 update
All,
We have reversed a change that prevented Moving Time and Average Moving Pace from being calculated for activities have Run/Walk Detection included.
Moving Time and Average Moving Pace should now be…
I spoke with Garmin Customer Service on the Phone. They stated that average moving time was removed on purpose. I'm not sure whether they intended to remove moving pace as well, because the metric of "run…
I've also contacted Garmin via online chat. They asked me to share an activity with them showing the fault and to test with a different profile. Walking tested and works ok. Shows av. moving pace when…
+1 for this. Noticed it over the last week, there’s no moving pace.
Disappointing response from Garmin help desk:
Hope you are well, I am contacting you in regards to a case we have open for you.
The issue you have reported is by design.
If a compatible device records Run/Walk/Idle time to an activity, Connect will not display Moving Time.
Sorry for any inconvenience caused by this
my response back:
This is at total odds to what has happened prior to the latest upgrade. Forum users are all reporting this fault across many different models of device. If your response was correct, then walking, paddling etc wold also no longer display ‘average MOVING pace/speed, which they still do. Please look again.
I spoke with Garmin Customer Service on the Phone. They stated that average moving time was removed on purpose. I'm not sure whether they intended to remove moving pace as well, because the metric of "run time" is not a substitute for pace. They stated that they are adding customers that wish the reinstatement of this metric to a ticket, and if they get enough requests it may be considered for reinstatement. So, if you haven't already, give them a call so that you can be added to the ticket, and we can get this metric back. I also sent them an email describing my logic for why average moving pace should not be removed:
Dear Garmin,
I am reaching out to explain my reasoning as to why Garmin should continue to show Average Moving Pace in Garmin Connect.
Garmin has apparently removed support for this metric, instead only showing "run time" and average pace. For me, Average Pace is a meaningless metric, because I take breaks during runs, and do not pause my watch, so the average pace is farrrr slower than my actual running pace, and varies significantly from run to run depending on break time. "Run time" is also meaningless, because I could do a 2 mile run, or a 7 mile run, and clearly I would get far more running time, but I would have to do a separate calculation to see my pace, which is the only metric of use for my performance. In short, my "average moving pace" was the MOST important metric I looked at to gauge and compare my performance, and I rank it alongside Aerobic/Anaerobic TE, Load, and VO2 Max as far as usefulness in my training. I do not see the logic of removing this metric, and I sincerely wish to see this metric reinstated in Garmin Connect. Everyone else I have spoken to, including my brother and parents who also have Garmin watches, feels the same.
One other thing- to describe the singular importance of this metric, I would like to highlight how Strava displays data. When an activity is uploaded to Strava, the three metrics that are shown on the main screen are distance, average moving pace, and moving time. Perhaps this elucidates the significance of this metric, if one of the largest athletic platforms (Strava) considers this metric to be of primary importance. Please bring it back to Garmin Connect.
Regards,
Dag Johnsrud
Same. It was working and then a week ago quit. I contacted support and they asked me for all the versions of software on my watch. Everything is up to date. I am getting idle, walking and running times. However, I believe it to be an issue with the app not calculating as Strava has no issues when synced. Again, Garmin can’t seem to keep their crap together. If they keep on, I’ll go to Coros. Their UI is 10x better. Fed up with Garmins always buggy software.
Garmin is lame. It’s a simple metric than can be calculated using a variable algorithm just like anything else. It’s pure laziness and doesn’t take any more work to keep/calculate it than it does anything else. All you’re doing is finding X filling in the blank with using other calculated info. That’s what Strava does. I don’t understand how math changes. Garmin keeps it up and they’ll have another Coros exodus.
The left hand has no idea what the left hand is doing never mind the right hand … typical support call center answers … half the time (or more) they have less idea of what the issue is than an educated user …