@bartolomeo6 On my Polar H10, I have had problems wirh dry belt, low battery and even a firmware hang that required reset of the sensor. It is always good to try to rule out alternative causes.

@mssjk the water temperature. Or maybe I don’t understand your question…

@EzioAuditore Thank you for your answer. One Space more for another S+ App

@Sascha-Domres I am with you. And luckily in places where you need orientation (in the wild - not in the cirty), most likely not too many trash cans will populate your screen

@Steven-Hambleton These are the font sizes available. There is plenty of options for larger size … f-d-xxxl: data field font, 85px for medium, 155px for large display f-d-xxl: data field font, 65px for medium, 118px for large display f-d-xl: data field font, 57px for medium, 103px for large display f-d-l: data field font, 50px for medium, 91px for large display f-d-m: data field font, 42px for medium, 78px for large display f-d-s: data field font, 35px for medium, 65px for large display f-d-xs: data field font, 25px for medium, 46px for large display However there is not much room for fine tuning at the lower end. I tried rendering text on a canvas and displaying that. It works but takes a bit more effort to program.

This may not help you directly. But I posted around font positioning and differences in font rendering between watch and simulator here … https://forum.suunto.com/topic/15262/precise-alignment-of-text-and-numbers What you see is probably a result of this effect, where the app author maybe only tested on the simulator (the image you see on the web). There is nothing much you can do apart from pushing the developer. For the future more information about rendering differences between watch and simulator in the documentation would help developers get it right.

@2b2bff I think there may be some confusion between the standard running dynamics already available on the watch and the additional metrics provided by the Suunto Spark. The Race series can already record metrics such as cadence and some running dynamics. However, one of the new metrics provided by the Suunto Spark is Ground Contact Time Balance (left/right balance), which shows how evenly you load your left and right foot while running. As far as I know, this specific metric is currently only supported within the Suunto ecosystem when using the Suunto Run. I have not seen it being recorded or displayed in the activity summary on the Race 2 yet. So if Ground Contact Time Balance is the data you’re looking for, that may be the reason it is missing rather than a connection problem between the Race 2 and the Spark.

@dimitrios-kanellopoulos can this be related to the crashes. https://forum.suunto.com/topic/15193/activities-end-by-itself-when-the-destination-reached-message-appears

Hello, Is there any timeline for the next update. I experience the issue when backlight stays on even when it’s not activated in settings. This drains batterry extremelly fast. I did not find a way to replicate the issue - it happens from time to time. If anything is to be prioritized I suppose this is it Thank you

@Łukasz-Szmigiel Promise to be brief this time. In LOTS of additional testing we have confirmed an exact limit of drawing line segments in a canvas is 181 line segments if they are chunked in blocks of 20. One more and it always fails silently resulting in a black canvas on a Race S. But we have also found another resource limit that manifest itself in the event log as #3505354 03.06.2026 06:30:14 : WRN WBMAIN : pool id:0 full! (S 120/120) Exactly what the pool is, we are not sure. We speculate that it has to do with communication between FW, app (main.js) and UI (t.html). Symptoms on the watch when this happens is that the watch becomes extremely sluggish, takes several seconds to react to the press of a pause button and the pause / resume screen renders slowly in steps over several seconds. We think the root cause is the simultaneous pressure from drawing in multiple canvases at the same time, we currently have three. The current solution is staggering redraws in different 10Hz ticks and to refresh only when content of the canvas has truly changed. So far it appears to work!

A bit more input on the font theme. I have struggled with the differences between how the simulator and watch renders fonts drawn on a canvas. This is the simulator. [image: 1780597051748-font-test-simulator.jpg]. Left column is monospaced text, mid is “plain”, right is sans-serif. The rows are 10, 14 and 16px as the text says. As you can see the “plain” font (only size given) is not supported on the simulator which will default to a standard font at one size. This is the same code run on a Race S. [image: 1780597208786-font-test-watch.jpg]. The difference is pronounced. It looks like the watch renders at least twice the size that the simulator does. On the watch I think the plain font works best. The monospace font is much too wide. Unfortunately when you use that font you cannot evaluate in the simulator.

Today I had two crashes a few minutes after that message appeared. I walked around for a few minutes, but before I could save the activity, it crashed and restarted. Something should be done – these crashes are happening too often, and they’re repeatable situations. I lost most of the activity data.

[image: 1780592357630-img_9467.png]

@vinc14 there is an S+ app with weather trends which you may use. It’ll show you a chart with barometric trend.

@Danny-poleg Totally agree. It has been highlighted a few times in other posts aswell.