@aplatonovs any newer watch than 9PP is a better choice. I bought a Race S for my wife as a replacement for 9PP and she couldn’t be more happier. No issues with the watch.

@Olaf-Gottschalk

@Audaxjoe correct; you can “force stop” the app (SA) and it helps. Btw. I had this problem for a while, but it disappeared around two weeks ago. Maybe, the new version of SA solved it

Hey same here also with a Redmi note 9 pro, MIUI 14.0.5 and android 12SKQ 1.211019.001.

I have an update. I chatted with Suunto, but they were not very helpful to be honest. Said will review the logs and discuss it with the team. But if issues persisted to send the watch back so they can check it. I did a factory reset and did not work either. I then reverted to the previous SW version and apparently that made it work. Granted it has been only one swim, but there were 0 issues with the laps.

@GiPFELKiND I had forgotten weather source and could not look it up.

@Tomas5 yes, you’re right, I actually never thought about how one could interpret the “like / dislike “ button in different ways to communicate in different ways. For me it always was/is a way to show my respect/thankfulness for helping others or telling something interesting or just about being communicative, and I only dislike rude or respect less posts. I may be quite too sensitive to respectless behaviour, which is maybe rooted in my martial arts background ( In most traditional martial arts showing even the slightest bit of disrespect in tournament e.g rolling your eyes or just waving with your hand normally results in direct disqualification). I may think different about dislikes now - thanks

It is normal i have to reset every 2 to 4 days my phone just because a part of the Communication between watch and phone is not anymore working? And the Information (Sync with Suunto App) why sometimes it takes hours to go away, what information need so long to travel. the phone is normaly not more then 1 to 5m away ? [image: 1766766193762-20251216_094250_cut.jpg]

@daveathletic +1

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: 1766748113856-img_5821.jpeg]

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!

@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]

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

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

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?