I have the same issue, since friday. I make the update thursday : 2.40.38 on race S. HR measures stopped twice around 10-20 minutes until I restart each times. Yesterday, exactly the same : it stopped around 15-20, i don’t restart. I decided to reset, yesterday… This morning, my watch crash I start, twice a cycling activity. On the third attempt, it was entering “safe mode”. It work fine and same problem, HR crash…

Hello yes good idea with the possibility of measuring the activity

@2b2bff yes indeed, pressing lap button after the warm-up session to launch intervals set. Thanks will look into other topics

@Lorenz kommt der LAP-Screen nicht, oder vibriert es nicht? Vibration an sich sind aber aktiviert? Einstellungen->Allgemein->Töne->

@Adam-Loomis it gives you resting HR, stress level, body resources… All those metrics that are required to trash the recovery status, and improve the potential training plans that could come in the future… But anyway, each of us has their own vision BR

Same problem here. The belt is easily paired with the watch but when I start activity, it connects only once for 2-3 sec per couple minutes. Then disconnects… and over and over again. The battery change was the first thing I did when noticed unstable connection, but it didn’t help at all. The belt has worked fine with Garmin Fenix 5 and Wahoo Bolt v2 for the last year. I also tested it positively with my wife’s Garmin Forerunner 45s, so definitely the belt is not the issue here.

@Kraisun-Tunta Yes, I would also love to get it. I think a lot of runners have injuries sooner or later. GTC helps a lot to monitor the recovery

I’ve returned the Race… I would like to have an AMOLED but I follow a lot of routes and I do not want to suffer this abnormal behaviour. I will continue enjoying my Vertical.

@sky-runner sorry I’ve missed that thread. I’ve read it now and I can confirm many of the issue you have described! Thanks also for the magnetic declination tip

@peegee Did you try a watch restart ?

@Bjuanito nothing changed in that respect, unfortunately. I do not know the BLE standard for speed/cadence so I do not know if there is a way to determine if a sensor is speed or cadence (or both) and act accordingly

Same problem here (Polar H10). No reconnection is possible. Battery needs to be removed, then it works again.

@nseslija Thanks for the tip. Sadly, it looks like this problem has been around for at least 6 months. It’s been a long time since my watch was last rebooted or soft rest, so I’ll try that.

@isazi Thanks for the information

@Danny-poleg yes, that’s a good point. Like I said, it’s not a feature I really used a lot, I just thought I am maybe too “dumb” to find it

@Tomas-Fejfar no problem.

@Sascha-Domres I thought this was going to be fixed especially with SR release as the app would update training metrics and the watch metrics would be in sync with the app.

this is perfect, thanks