Watch stopped measuring mid run
-
My suunto Race, stopped measuring mid run.
Fortunately I glanced at the map I was following throughout the run and noticed I wasn’t in the workout.This happened to me before when my vertical just came out. Happily it was dealt with with one of the fixes.
I really can’t understand or accept that the watche’s basic and most important function as a sport/running watch just stops mid run.
I don’t know if is related to last update, which seems to have multiple problems: lousy sleep tracking and now this….
I just can’t accept such a bug!!! -
@peegee Hi, had the same behaviour today on my Race S. As you said thats an absolute No Go and I will also not accept a device thats not reliable in the main function.
I’m using GPS watches from Garmin and Suunto since about 20 years and never had a device failing like that.
I’ll take a look at what Garmin and Coros can offer -
@VoiGAS Garmin Fenix 7 / Epix range has a similar issue currently. Longer activities might stop in between… Nothing is perfect…
-
@2b2bff Really? Thats a bummer. I just want a working watch without watchfaces, sleep tracking, HRV and everything. It seems the companies cannot handle all the stuff.
So no idea, maybe I will use the old Ambit3 with Belt again. But I really started to love the maps for runs in unknown terrain…Edit: Found bug reports for Garmin and Polar with the same problem, but nothing for Coros. But maybe thats only due to the limited users / history
-
V VoiGAS referenced this topic on
-
Same happened to me on the latest update. Around the 20km mark it just froze. I had to soft reset to make it work again. The activity was tracked until the watch was turned off. The last 10km of my 30km run I wrote in manually as I didn’t have time to fiddle with my watch during the run. Have had long runs later on and haven’t experienced it again. Seems like it happened randomly.
-
This happened to me yesterday as well during a very short hike with my Race (running the latest firmware). The total distance was just under 10 km, and after about 2 km, my Race froze and then automatically restarted after approximately 60 seconds. If I hadn’t happened to look at the display at that moment, I wouldn’t have even noticed it. However, since I did, I was able to restart the activity after the reboot. In the end, the first 2 km were still saved, but at the end of the total distance, I had two separate recordings, and a few hundred meters were missing.
The real issue, though, is that I can no longer trust my Race. I never had such a crash with my S9B-Ti, and I will probably switch back to it and sell the Race. A watch that fails in such basic functions is useless to me. It doesn’t matter how much I like the Race otherwise.
-
@Arju-Ambin said in Watch stopped measuring mid run:
Same happened to me on the latest update. Around the 20km mark it just froze. I had to soft reset to make it work again. The activity was tracked until the watch was turned off. The last 10km of my 30km run I wrote in manually as I didn’t have time to fiddle with my watch during the run. Have had long runs later on and haven’t experienced it again. Seems like it happened randomly.
Another crash happened mid run yesterday at the 5km mark, I ran 10km in total. I couldn’t be bothered to fix it mid run but the watch eventually rebooted by itself. Half of the run was tracked. This is the second time it happens. Half of the screen turned black and everything just froze. Anyway, I went for a 10km run today at the same time as yesterday and the watch didn’t crash at all. I’m on the latest firmware 2.40.38. last time I was one the previous firmware. This seems so random.