Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Potential Issue with Auto Pause and V 3.30 Firmware?

Former Member
Former Member over 9 years ago
Short version. Started using the speed sensor this weekend with the V 3.30 firmware, auto pause enabled. Unit would occasionally auto pause and then resume while riding. Happened on a couple of rides this weekend. On Sunday ride also noticed speed go to 0, then register erratically for a few seconds, then come back. Wide open, flat road, no power lines, etc. nearby. At first I thought it was an issue with the speed sensor. However.

Started looking at data from Sunday ride. Shows average speed of 17.7 mph, but average moving speed of 15.9 mph. Huh? Total time of 1:47:54, total moving time of 2:00:00. Huh? Went back and looked at some other rides. June 25 was first time I had an issue with my moving time being GREATER than my total time, and I believe that's right after I loaded the V 3.30 firmware. Issue has been consistent on every ride since then, I just didn't notice it until this weekend. Looking at data from yesterday and from a couple of shop rides where I know we took long breaks for new peeps, I suspect the unit is NOT auto pausing when stopped, even though it says it's paused. This is happening both with and without speed sensor connected, so don't think it's related to the speed sensor.

Turned auto pause off Sunday for the warm down ride home. Only about 3 miles, but avg moving speed slightly higher than avg speed, and moving time just slightly less than total time as you'd expect. Hoping to test it on a longer ride a little later this week.
  • Former Member
    0 Former Member over 9 years ago
    I checked my last three activities and it shows the same thing: elapsed time > moving time > time and consequently moving avg speed < avg speed. I never noticed this, but I never paid attention either. This is with 3.30 firmware, speed sensor (VeloComputer.com) and AutoPause on.

    Not sure what are those three different times anyway. I'd only expect two: moving and total.

    On the other hand I do not get any unexpected auto-pauses. Only when I really stop. The moving time > time might as well be problem with Garmin Connect swapping the figures. It wouldn't be the first bug in Connect. I can also confirm I see the same swapped figures in Web Connect and in Android Connect.

    If I look at the same activity auto-imported from Connect to Strava, the Strava only shows two times and they do make sense:
    Strava's Elapsed Time = Connect's Elapsed Time which is the total time of activity including stops
    Strava's Moving Time = Connect's Time, which is the smallest of the three. I can't see the "middle" Connect's "moving time" anywhere in the Strava. No idea what's it's meaning and how it's generated.

    Example of real numbers:
    [FONT=Courier New]
    Connect[/FONT][FONT=Courier New]
    Elapsed Time [/FONT][FONT=Courier New]22:10[/FONT][FONT=Courier New]
    Moving Time [/FONT][FONT=Courier New]21:48[/FONT][FONT=Courier New]
    Time [/FONT][FONT=Courier New]21:35[/FONT][FONT=Courier New]

    Strava
    [/FONT][FONT=Courier New]Elapsed Time [/FONT][FONT=Courier New]22:10
    [/FONT][FONT=Courier New]Moving Time [/FONT][FONT=Courier New]21:35

    Endomondo
    [/FONT][FONT=Courier New]Duration [/FONT][FONT=Courier New]21:35
    [/FONT]
    So it appears the 21:48 is some nonsense.

    Edit: What I did experience though was loss of sensors connection in the middle of ride. I noticed my HR showing --. When I stopped to investigate, I eventually finished the activity in the Edge and started another one and the Edge immediately found all the sensors again, so there was clearly nothing wrong with the sensors. This already happened twice.
  • Former Member
    0 Former Member over 9 years ago
    Yeah the bug is in Connect. Seems to be happening with ALL of the Garmin units when auto pause is used, there's a general thread on it. I've never really understood why there are 3 times either, seems total time and moving time would be enough. Rode yesterday with auto pause off and the times look as they should. Still doesn't explain why mine auto pauses in middle of a ride though.
  • Former Member
    0 Former Member over 8 years ago
    Still having problems with my unit suddenly auto pausing in the middle of a ride while moving, then resuming again a few seconds later. Happened 4 or 5 times on ride Saturday. Anyone else having this issue?
  • 0 over 8 years ago
    I tried auto pause tonight after seeing this and mine did the same, riding along and is paused, then started again several seconds later. However, I am thinking my Edge 25 is faulty or certainly not good value.
  • Former Member
    0 Former Member over 8 years ago
    In my previous post above I stated I did not get any unexpected auto-pauses. Well, this has changed once I enabled GLONASS. Do you guys have it enabled? Until I enabled it, I did not suffer from unexpected auto-pauses.
  • Former Member
    0 Former Member over 8 years ago
    1010

    GLONASS should be off on mine unless it turned on last time I updated. I'll double check. Weird thing is there are a couple of spots on one route where it always seems to happen.
  • Former Member
    0 Former Member over 8 years ago
    Revisiting this, GLONASS is turned off on my Edge 25. And it's still happening. There's one route I ride frequenty and it happens in just about the same location, just about every time, whether northbound or southbound. Suddenly auto pauses for a few seconds, then auto resumes. Would be nice if Garmin Support got on here and gave feedback. I can't be the only one this is happening to.
  • Former Member
    0 Former Member over 8 years ago
    Is there something about that location? ie a sudden change in speed, heavy tree cover, tall buildings etc?
  • Former Member
    0 Former Member over 8 years ago
    Is there something about that location? ie a sudden change in speed, heavy tree cover, tall buildings etc?


    Nope. Wide open road, flat. And it shouldn't matter anyway because the speed sensor takes priority. So, even if I lose satellite there's no reason for my unit to auto pause. That is, if Garmin can get it to work the way it's supposed to. Installed an update Friday but rode without my Garmin this weekend, so haven't tested.
  • Former Member
    0 Former Member over 8 years ago
    Props to Garmin for their response on this. Finally contacted them directly and emailed a couple of rides where I had this issue, and one where I rode without the sensor connected and had no issues. They decided there was a sensor issue and shipped me a new one ASAP.