@elbee slower development and fewer bugs is always preferred. or let’s say: slower development and in general more complete and matured firmware, software, features… (…still don’t understand how my windows laptop takes ages to connect to the one single connected headphones while my mac just connects when I take them off the charger )

Had a crash during my run today, using a Race 2. It crashed at just after 2Km into the run. I had 3 S+ apps enabled (Cadence coach, ZoneSense and Running Economy) and was using a Polar H10 belt. Everything else were standard (no nav, battery on performance, feeling on, no music controls, etc). When I realise the watch had crashed and restarted, I’ve started a new activity to continue my run. However, this time I unselected the ZoneSense app, while keeping the other 2 S+ apps and the HR belt. The remaining 10.4Km went well, no problems. Hope this gets sorted soon by the team.

2.13 (2026-06-27) is live with a small bugfix: Each trend line now scales to its own movement, so a chart looks the same whether you view it in the combined drift view or in its own dedicated view. Fixed the effort direction for speed-based sports (such as hiking): moving faster than your average now correctly reads AHEAD instead of FADE (and correct green/red colors).

@mickywickyftw thanks for the update, I’ll try this week hopefully (on the same road, to compare). One suggestion could be to wait for a few more seconds when the slope reduces before using standard formula (I totally ignore if there are mathematics models behind this, just intuition and probably hard to calibrate). I mean we are still fast for a while when the grade drops from -4% to -2% for example.

@Calando Why is a chest strap necessary? Beat-by-beat data: ZoneSense uses a proprietary physiological algorithm (DDFA) that analyzes Heart Rate Variability (HRV) to determine stress and intensity levels. Optical limitations: Optical sensors (OHR) cannot reliably measure RR intervals (the exact time between heartbeats) while you are in motion. They are only accurate for this metric when you are at complete rest, such as during sleep. When pairing a chest strap, your watch will automatically disable the optical wrist monitor to ensure the data source provides the necessary accuracy for functionality.

@dimitrios-kanellopoulos it seems to affect more people. Can you tell if this is indeed a Suunto App bug?

@Nikolai-Simonov yes I built a custom interval workout because I wanted to use navigation at the same time. If I use the built in intervals I cannot use navigation (this is known Suunto functionality)

@pavel.samokha Ok, thanks.

I finally received mine and use them on a run yesterday for the first time. I noticed a bug: at first I could adjust the volume with the touch I had set up (triple tap), but after some time this stopped working; I had media controls on my watch, too, and when I chose the volume option nothing happened.

@Squirrel thank you!

@Łukasz-Szmigiel The ones I used didn’t have those tags and have been around for years, so they’re probably directly from Suunto.

@rémiP Thanks. This seems problematic. Is there any reason for this behavior @suuntopartnerteam?

@thailon I made one for my race. Haven’t tried it, but could fit for Vertical as well: https://www.thingiverse.com/thing:7108194

@sky-runner You’re right… ! I see it similarly… it is certainly very difficult not to overload the Maps… POI like water points would certainly be useful on larger zoom levels… But they don’t care about trash cans at all…

@maszop sometimes you realise at the moment to download maps and … Yeah, otherwise this is just a discussion.

@Stefan-T. I now can confirm this behavior. Today, after 13 days with some training and also HR broadcasting, I was down to 2% so I put it in the charging craddle. Some hour(s) ago I checked and the watch was on 100% and I put it on again. I could actually monitor, hot the percentage dropped and no I’m on 97%, which is about 1%/hour. That would give me some 4 days!! I I’ll did the soft reset and was back on 99%. So it’s definitely a software issue, that after charging some “counter” is running nuts So I hope this is fixed in the next FW update…

@sky-runner Tested today and multiple normal routes were synced during same activity. SV2 and Android, but some firmware and app versions ahead for testing. At least some hope…

@matram pm me with your GitHub name, I’ll add you to my S+ skill repo. I’ve already done the digging.

@withManish On iOS there is rungap for datamigration. And I use strava and intervals.icu. It collects data from multiple sources (I had different brands in the past). But most importantly, data of 5 or 10 years ago hardly has any relevance. But I’m no hardcore data collector.