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

[14.13 - BUG] Weird stopping (by itself) behaviour during activity

FlipStone
over 2 years ago

Might be pure coincidence but did my first interval run with the 14.13 fw and during the latest interval it went into some auto-stop loop after manually pausing to wait for a stoplight.

After I pressed resume it immediately stopped again, pressed resume again, it stopped again (within 1 or 2 seconds). Then thought 'screw it' and chose to save the activity after which it hung at the 'saving acitivity progress circle'.

Watch didn't seem to respond and then suddenly got the message that the next 'interval' started (the 'cooldown') and I was in the activitiy again which was running. So I finished another km or 2 and saved it, which then worked fine and it synced fine.

Anyone ever experieced something similar?

I think I remember once where the watch acted strange when I manually paused a run at the EXACT moment an (auto-)lap ended though I don't recall exactly what happened so perhaps it's just a rare coincidence. But as it's the first run with the 14.13 fw, well... 

Doing a normal easy run tomorrow and some more intervals next week so we'll see how that goes.

  • 0 over 2 years ago

    I confirmed that happened with 14.12 and I reported in this forum. Good to know that long press "up" fixed it,  Because Sunday and Friday I finished the workout with watch panel freezed and workout running in background, so running blind without a referring lap time and pace. 

    No good Garmin...no good...

  • 0 over 2 years ago in reply to Abraxas

    same issue

    for me every subsequent activity is still stuck on 0 speed with random pausing and even loading into previously discarded activities after a reset

  • 0 over 2 years ago in reply to 5994630

    I don't think so, the issue is completely different and doesn't belong from watchface

  • 0 over 2 years ago in reply to francisti

    It's an activity/non-activity state machine, and can be triggered by various things. I suspect some other process is writing to that flag which shouldn't be.

  • 0 over 2 years ago in reply to 5994630

    yesterday I've experience that "resume later" affect positively this issue and restarting activity it goes well. even if you made that procedure (resume later") but before restaring activity pending, you choose a different menu as "recover cardio frequency" for example, then when you resume activity you'll experience again issue.

  • 0 over 2 years ago

    happened to me on several runs after pausing a "TODAY'S SUGGESTION" workout at a stop light (The auto-pause seems to be disabled when doing a suggested workout, so I have to manually PAUSE the workout at a traffic signal or water fountain or toilet stop)..  This bug has happened for regular runs, i.e. not a suggested workout when I have paused the workout then resumed the workout only to see that the watch has gone into PAUSE mode all by itself within a few seconds of having had resumed the run.

    my  solution that seems to work most of the time is to use the "RESUME LATER" then press the start button to return the workout screens and that USUALLY works but sometimes I have to  put it into "RESUME LATER" mode more than once.

    Haven't tried the LONG MENU Press yet.

    NOTE - recorded 5 days of skiing in the SKI activity and this bug did NOT occur.

  • 0 over 2 years ago

    yes. I am having exactly the same problem - stopping the watch during a "today's suggestion" interval and resuming when the traffic signal changes and then it goes into a auto-stop loop. The only way I've been able to "fix" it was to press RESUME LATER then resuming as normal.

    My activity, however, did not "hang up:  and I was able to resume the activity and  save it