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

Activites imported from Strava to Garmin Forerunner 965 are crashing the watch

Hello.

Recently, I have acquired Forerunner 965 and haven't had any issues besides one. Before I had it, I was using Strava to log my activities. Today, I have imported them using .fit files to Garmin Connect and so far there were no problems. When I open them on my Forerunner 965 and see details like route or basic info, screen goes black and watch reboots.

Is it the issue with the activity? Or using .fit file? Has anybody has similar issue?

Alex

  • I only tried this with fut files that were recorded with a different but Garmin device. But let's just say that obviously the thing you described is not the "intended" way to use the watch, so I doubt you'll be able to get Garmin's or Strava's attention to "fix" this. I think you'll have to live with it. I hardly look at the activities on the watch that I recorded with the watch, it's not very user friendly, so I mostly use GC app. Why do you want to look at the old activities from the watch?

  • Hey, just wanted to second this, I've got the same issue.

  • Very strange usage of the watch I must say... 

    I have in these cases of recording activity on a different device (phone Strava, iFit treadmill , wahoo app, export from some fitness platform, edited .FIT files from fitfiletools etc...) have just  uploaded into Garmin on the website.  Then you can view on web/phone App really well...  

    https://connect.garmin.com/modern/import-data

  • I believe garmin has changed the FIT file produced from 965.  The lap "timestamp" field is not correctly updated as on 945.??

  • I don't understand what you're trying to see. When you record an activity and it's synced from the fr965 to GC, then the lap times are OK?

  • Yes, in gc it's fine. But the FIT file is not. So programs like maprun who import the FIT file no longer show correct splits...  It is DEFINITELY Garmin that writes the FIT file timestamps incorrectly.

  • Every platform that I use (intervals.icu, Runalyze, and Strava) show my manual or automatic splits/laps just fine.  

    Not sure what you are seeing on Mapmyrun... (but that site is a mess anyhow typically... so not sure I would call it a garmin thing).    I don't have a paid membership there so lap data is their default options.

  • Thanks for your input.

    Not "mapmyrun", it's "maprun".... Simple enough to export FIT file and Splits csv from a 965 run and a 945 run and see that the 965 "lap timestamps" have changed...