Hey folks, So I just read another poor soul begging Suunto for seasonal watchfaces, and honestly… same energy here. At this point I’m convinced Suunto has, like, one designer left, and they’re being held hostage somewhere fixing GPS issues 24/7. I mean—other brands are out here dropping Halloween, Christmas, Lunar New Year, National Potato Day watchfaces… Meanwhile Suunto is like: “Here’s one new watchface for the year. Use it wisely.” Why so stingy? Does adding a pumpkin icon drain the battery by 0.0001% or something? Are we violating some Scandinavian minimalism law? I love the watch, I really do. But man… throw us a bone. A sparkle. A ghost. A snowflake. Just anything that says “Yes, we acknowledge that seasons exist.” Anyway, if Suunto doesn’t release a festive watchface soon, I swear I’ll start designing one myself— and trust me, nobody wants to see that happen. Cheers to hoping

@WanessaJimenez since Suunto 9 Peak Pro has an LCD MIP display, brightness setting only applies to when the backlight is activated, for example when you press a button or when the backlight is configured on activate when you turn your wrist. Most of the time the backlight is turned off to conserve the battery.

I’ve been in contact with Stryd support on this issue since this 5K race. Every run I have done on my Suunto Race S is not using my Stryd pod for pace and distance. Here is the data recorded by my Race S and here is the data recorded by Stryd. As you can see, both the pace and distance disagree: Suunto: Time: 20’31.0 Pace: 06’20/mile Distance: 3.24 mi Stryd (only at the race segment): Time: 20’31.0 (14:37 - 35:08) Pace: 07’12/mile Distance: 2.85 mi Checking in on the runs for Monday, Tuesday, and today, the watch distance and pace differs from Stryd’s distance and pace. I have Stryd Duo, which is two foot pods paired together for right/left balance metrics. Things I’ve done to troubleshoot: Unpair the pods from the mobile app, then pair them again paying attention to which pod is paired first. Unpair the pod from my watch and pair again, confirming it uses the first pod that paired with the mobile app. Do a hard reset, restoring the watch to factory settings, updating to the latest firmware, and pairing the first pod again. With the help of Stryd support, we are convinced that Suunto is ignoring the pace and distance from Stryd, although it’s correctly sourcing power from the pod. Can anyone look at this, or is the Race S no longer the priority and we’re stuck with this regression bug?

@Kevin-Major There is no tide complication. Apparently the new dive computers will have this. I do not know whether the Ocean will get tide information or not.

I have had this issue on and off, as well as with my Garmin Enduro 2. It is tied to using multiple apps on the phone that play audio - such as using podcasting and music apps on the phone. I have been able to get it to work by rebooting, or closing all apps that play audio except one. I haven’t done this in a while, but it’s worth a try. I use an iteration of the google pixel.

@PetrMisek No Problem hope for fix it! But i dont understand why they change existing things…

@Brad_Olwin yes, Race 2. The thing is, it is implemented for Running, but not Trail running. It doesn’t make sense. Thank you for consideration. It should be easy fix.

@harristyle please export the workout to a FIT file and open it with fitfileviewer or runallyzer and look for r-r data.

@Hari-Seldon True, I moved here when I realized it’s probably an issue with the Suunto Run. A big difference between the H10 and Verity Sense / Coros HRM is that only the former provides R-R intervals. This fact surely affects how the watch interacts with the sensor since e.g. the watch knows that zonesense should not be available with the optical ones. I would guess something in how the watch treats them causes the spikes, and that this is somehow related to the bogus R-R data recorded by the watch. I don’t know whether or not this also happens with the Coros OHR sensor.

@2b2bff I can only say for Race 1, but I think Race 2 is the same in size. Compared to fenix, they’re about the same even though fenix is 47 mm and race is 49 mm in width. They feel kind of the same. I think it’s the bezel size and pins that hold the wrist belt. On Race they are a bit steeper, so the whole size looks a bit more compact, and on the other hand Fenix is more spread out, so it feels a bit larger.

@arpoodle I use a usb=>usb-c dongle ; cheap, can stay plugged.

Vertical 2 is finally on sale in Türkiye, but it’s very expensive. I’m already happy with Vertical 1. Maybe Vertical 5 too

@Regis-Letowski-0 oui ça peut arriver ; sur les données de récup a priori bug ponctuel. La question fondamentale : quel impact sur ton entrainement ou ton activité ? La seule aide à ce stade : juste prendre un peu de hauteur sur ces métriques et ta montre qui n’est pas un appareil médical. Blague à part, à titre perso je regarde le sommeil comme un indicateur, et j’ai rarement de gros ratés (race S pour ma part pour la nuit). La durée récup je ne la suis pas, je ne l’ai jamais trouvée pertinente ; le suivi de charge est beaucoup plus cohérent et utile (CTL/TSS…) AMHA.

@Dimitrios-Kanellopoulos Same probleme. Low measurements and no manual possible. SW 2.48.16 app Android 6.4.7

@pavel.samokha perfect. Thanks. All works again since last night.

@Sergio-Nasi I’d switch a long time ago if only there was an alternative. Sadly, all sport watches are half-assed these days. No idea why, it’s a huge market, so there should be enough revenue going to keep things nice for everyone.

On my side I noticed it is worst when the outside temperature is low and that very regulary the HR is locked on the step frequency -> Please suunto implement a sw Countermeasure to reject it