Cycling a course today of 27.4 miles on my new Edge 1030 i noticed is constantly pausing for anything between 5 to 10 seconds for many times per mile before starting recording again. I uploaded the ride to Strava and it measured 25.3 miles. I pressed the recalculate option, which is for dealing with inaccuracy in GPS distance recording and the course updated to the 27.4 it should have been. So the constant pausing lost a little over 2 miles! I have Auto-Pause on stop/start set, GPS set to gps and glonass and data recording to every second. I need to test the 1030 over the next few days changing these options to see if that helps. I would be interested if anyone else has this issue
I've got six rides logged on my new Edge 1030. I've kept my IPhone running Strava in my back pocket during all five of these rides. I have noted that my Garmin has been pausing during my rides while I am moving at speeds > 10 kph. On average I'm losing 5 minutes of data on a 90 minute ride. Additionally, the elevation gain recorded over 1000m of climbing is about 200m less than my IPhone. The elevation difference I also saw with my Garmin 810, and 705 so was not too surprised. During one ride the %Grade value was jumping from negative 10 to positive 35 degrees during a steady 7 to 10 % grade. It was pretty raining that day, and I haven't seen this phenomena since.
Today I changed the "Autopause" option in my 1030 from "When Stopped" to "When speed falls below 6mph" (which is the lowest setting allowed) today's ride of 15.4 miles was accurately recorded and I had no Pausing during my ride. This has fixed the issue, but the 1000 recorded perfectly accurately for years on "autopause when stopped" Why Garmin have made some sort of change to the units software that has caused this error is beyond me!
Today I changed the "Autopause" option in my 1030 from "When Stopped" to "When speed falls below 6mph" (which is the lowest setting allowed) today's ride of 15.4 miles was accurately recorded and I had no Pausing during my ride. This has fixed the issue, but the 1000 recorded perfectly accurately for years on "autopause when stopped" Why Garmin have made some sort of change to the units software that has caused this error is beyond me!
For me 1030 stop and never restart (but he continues to record !). My speed is egal to 0 but on the map I see that I'm mooving and when I transfer the file on strava, segment are available (during the time that GPS seems to be out), my travel on the map is recorded and strava can modify the total distance to give me the exact distance of my ride. It is definitively a software problem. It's been a while since it lasts. So, Garmin, thank you for fixing this malfunction quickly!
