@Olaf-Gottschalk It might be software it might be hardware, that impacts software crash, but I think what this forum trying to tell you, that having crashes like that so often is not really normal and nobody else gets that. So you should contact Suunto and get it replaced or fixed. (Of course if you already tried that and was denied, I understand your frustration)

@Alessandro-Fasiello-0 very strange behavior, contact support and follow their instructions

@Olaf-Gottschalk Hmm - I am pretty close to your use level (24/7 an d10-15 hours a week recording. With an earlier device I would have issues near specific locations - not so much GPS issues, but total connectivity - I think folks in those areas had cell phone/RF blockers (illegal, but it was an interesting part of LA) and sometimes those are around LE or Mil installations. Do you issues crop up around the same geog area? just a WAG from my own experiences.

@freeheeler Had another crash today during a structured workout. How do I get the logs off the watch to send them to you?

22mm are definitely easier to find.

@isazi @martin-vrska thanks for trying! I’m hoping it was just an anomaly that won’t happen again until they update diary to let us resume after any technical issues like strava (fingers crossed) It’s all saved in diary so we should be able to use that and resume even if we aren’t at that exact gps coordinate. Strava just does a straight line the next starting point (doesn’t look the best but it’s better than nothing). TDLR tech isn’t perfect which means there needs to be safety nets

Perhaps I experienced a fluke. Subsequent runs went without a hitch.