@MdzOtt Same issue here. I’m using Suunto 9 Peak (long time no firmware update) so it seems to be 100% SA related.

And since this issue occured (around last 5 days) battery consumption went up too. From 5-6% a day to 8-9% a day.

@AYHAN-YILDIZ said in Suunto Vertical 2 General Discussion: By performing a factory reset, you cleared any temporary data and configurations on your watch that might have caused the function to malfunction, thus allowing the correct function logic to work properly. Shouldn’t a factory reset fix things, if anything at all? For me it doesn’t make much sense.

I would very much like to disable VO2max detection for trail running activities too. When I owned Garmin, my VO2max continuously declining because a do at least 1-2 serious trail runs per week on a steep terrain. Once I disabled trail running VO2max on Garmin, the estimate steadily went up from 47 to over 52 in just a few months. Now, that I have owned Suunto Race S and S for over a year, my VO2max has been stuck in the 48-49 range, occasionally going to upper 49. I feel that is a bit too low. Every time I do a trail run, it always goes down to lower 48 or even upper 47. The funny thing is that I am a relatively better trail runner than I am a road runner. I have good and efficient technique when running on technical trails, but despite that the VO2max estimate is always punished!

@herlas said in race 2 + HR strap = : current design to connect to HR devices is for each sports mode to remember the HR device it connected to and next time you open the same sport mode it’ll try to connect automatically to that device only That’s how it is supposed to work, but it doesn’t quite work that way. Here’s an issue that I have just experienced today: On my trail run profile, the watch is paired to Coros HRM. On my road run profile the last few times I used the built-in wrist HR sensor. Yesterday I couldn’t find find my Coros HRM so I used the run profile with the built-in HRM. Today as I was wearing Coros HRM and about to start a trail run, the watch showed a popup telling me that Coros HRM was connected. Good! But since the run profile was preselected, it was flashing the built-in HRM icon trying to obtain the lock. OK, since that was the wrong sport profile, I went ahead and changed the profile to trail run. Nevertheless the watch continued to try to obtain the built-in HRM lock rather than switching to Coros HRM, despite the fact that the built-in HRM is explicitly turned off for trail run profile. So basically it was stuck - trying to use built-in HRM without success because it is turned off rather than using Coros HRM that it told me it has already successfully connected to. What a mess! To me this looks like this has never been properly tested! In the past when I tried to use a mix of Coros HRM and Suunto HRM on different profiles, it was even worse.

True, reboot solves the issue. Keep in mind if you stop an activity for lunch break!

@cdfreet After a few weeks of testing, the issue started to occur again. The OHR sensor turns off without warning and does not turn back on until the watch is removed from the wrist or a forced restart is performed. [image: 1766697067740-img_5821.jpeg]

@Dimitrios-Kanellopoulos said in Q4 2025 Firmware Update Infos?: moved to START OF THE NEW YEAR Any publicable list of fixed issues/bugs ?

Está claro que esto es un fallo recurrente. A mí Sunnto Run con el que llevo algo más de una semana le pasa lo mismo. De 9 días he recibido el informe matinal 3 veces

@Brad_Olwin @SuperFlo75 Thanks, I’ll wait for the update and hope it solves the issue

@Sergio-Nasi Bonjour, je rencontre le même problème, les capteurs de mesure de fréquence cardiaque s’arrêtent. Obligé de redémarrer la montre. Y’a t-il une solution à ce problème ?

@Adam-Ward this method worked for me as well. Thankyou would’ve been a frustrating Christmas otherwise!

@Horizontal_2, I agree. Normally, recorded GPS track should be completely independent from the followed route. Did you use “snap to route” option by any chance? Also, what battery mode did you use?

What’s happening to me is that in the Suunto app the intervals appear correctly, but when I sync with RunMotion they are not recognized. Does anyone know about this issue and what the solution might be?

I have this issue you described with my SV1… it appeared after the last firmware update. I used two belts, one was really new, both belts the same crazy behavior. In my opinion, it’s the watch firmware.

I’m also having this problem. Basically, nothing from Suunto plus is syncing. Guides, watch faces, apps, etc., are not syncing for me. It’s super annoying when you’re about to sync some workouts before heading out and basic functionality is missing.