When doing a ride on ROUVY, my data comes in but recently it's showing much shorter times.
This morning's 11.67km ride took 19m 4s according to Strava (where the upload from ROUVY also goes) but only 11m and 17s on Garmin Connect.
When doing a ride on ROUVY, my data comes in but recently it's showing much shorter times.
This morning's 11.67km ride took 19m 4s according to Strava (where the upload from ROUVY also goes) but only 11m and 17s on Garmin Connect.
Which of the time values are you looking at? There are three of them:
Elapsed Time: Includes all time from the initial starting of the timer to when the activity is saved.
Moving Time: Includes only the time you were moving.
Time/Timer: Includes time moving and time not moving as long as the timer was running (if Auto Pause is turned on this will prevent time not moving from being included in this total).
Strava often uses a different time than Connect, in the header. Connect uses the 3rd option listed above (at least at native activities recorded by Garmin devices). Though Connect reports all three times, on the detailed Stats tab. Have a look at it, and see whether you have the longer time there too.
But why should the moving and elapsed times be different?
It's not being recorded on the Garmin device: it's recorded in the ROUVY app as one ride from start to finish and then shared to Strava and ROUVY.
Looking at the blatantly incorrect Connect data for the last short ride, it shows a now-corrected Total Time of 21:12. On the stats tab, it shows Total Time 21:12 (corrected by me), Moving Time of 11:29 (which clearly cannot be right) and Elapsed Time of 21:13.
Strava shows Moving Time of 21:12 and Elapsed Time of 21:12.
My wife's having the same issues.
Today was even more bizarre: the main ride was imported correctly, but both the warmup and cool down rides were incorrectly timed.