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

Activity doesn't save, then goes back to start run screen

Watch: vívoactive 4
Software version: 5.60.0.0
Serial Number: 5ZM039975

What happened:

- started run activity after gps connected like normal
- ran 3 miles, watch was recording all data it normally does
- got within ~30ft from apartment door, clicked stop button like normal (top right)
- watch showed screen to start new running activity (If I remember correctly--it may have also showed saving for a bit then went to start new run screen, but regardless, it confusingly went back to start new run screen)
- plugged watch into computer to see if the .fit file was maybe in "This PC\vívoactive 4\Primary\GARMIN\Activity" folder, but didn't see one from today :(
- took note of time and saved log files to "This PC\vívoactive 4\Primary\GARMIN\EVNTLOGS" to dropbox here: https://www.dropbox.com/sh/xus1xo1tq5pbh46/AACABZi_DUQ9oNu31NLXxOj4a?dl=0

I saved the files maybe ~20min after I finished the run at about UTC: 2021-03-31 02:39:01, Local: 2021-03-30 20:39:01

I suspect maybe since I was close to my place, the watch tried to connect to my phone or my wifi, thought it connected, blew away the data, connect/upload failed, it panicked and just offered to...do it again?

Let me know if any other log files on the watch would be helpful. Or if they'd be deleted by now, let me know if you have any ideas of what I can do next time this happens (if it happens again).

I looked at related questions and connected to the Garmin Express app and ran updates/synced from there. 

Looks like plenty of space on my watch too, so I don't think it'd be necessary to blow away Activity folder, but let me know if I should do that anyway.

  • I also tried software to recover lost files, but no luck. This has only happened 1 time in the past. Similar situation if I remember correctly.

  • One of the log files had "WIFI Connection Error: ", but doesn't look like the "timeDay" would line up with when it happened either utc or local, so that's maybe something unrelated.

    I did notice "---Invalid Time--- " though, so seems like the log code has a bug there?