Oui, on est plusieurs à avoir constaté ça. Espérons que Suunto corrige le bogue rapidement.

@nomison maybe it is a bug or unexpected behavior. No matter what it is I do not expected will be updated. Our Vertical 1 is now out of date with bugs and potential improvements.

snow said: That said, I’m curious to know if and when features related to running dynamics and the like will be available. The data is already available, and I’ve finally figured out how to retrieve it. Select “Suunto Spark” in SA, choose the only available activity—namely, “Running”—and then start the session. When you’re done, stop the session, and it will be saved. [image: 1787162605447-whatsapp-image-2026-08-19-at-20.01.03.jpeg] The data doesn’t make sense: I was walking while I was testing it…

@pg1999 thanks, I forwarded this to Suunto.

I was wrong ! but please Suunto, communicate, communicate !

@Art-C hi when you clear the alarm you should see the bar’s in the tank pressure window again!!

To add to this one, I have the lovely death of HR experience today. See below: [image: 1786859596217-screenshot_20260816-074727.png] [image: 1786859596253-screenshot_20260816-074744.png] I sent logs of course, latest firmware. But somewhat perturbed that this is the end firmware for the watch and this happens. Resources is also stuck at 70%, despite being at 10% before the night. So I suspect a reboot or something is involved?

@David-Jakobsson well, advanced running zones are only for running based sports, not paragliding I will report the original issue for you.

I agree with the points above, the app is absolutely useless at this point. There should be a dedicated app for Suunto diving products.

@Ldive It’s a matter of respect for those who bought a Nautic and placed their trust in Suunto. Unfortunately, I shouldn’t have

Follow-up: I ran the test, and I can answer my own question 5. The eviction path does not release the app’s JS context, and the shared heap is exhausted inside a single four-minute exercise. Method: fresh reboot, one exercise, three apps enabled, triggering the eviction repeatedly by switching screens and opening/closing the map. After each eviction I re-enabled my app from the SuuntoPlus menu without ending the exercise. Four evictions in four minutes # time how long my app survived after being enabled 1 14:48:40 118 s 2 14:49:07 14 s 3 14:49:57 33 s 4 14:50:27 15 s 118 s the first time, 21 s on average afterwards — an 87% collapse. The heap is at 99.5% Two lines from the firmware itself, 16 seconds before the first eviction: 14:48:24 : WRN UI_FRAMEWORK : JsTotMem 129980/133120 (97.6%) 14:48:29 : WRN UI_FRAMEWORK : JsTotMem 132412/133120 (99.5%) This is the only figure the system has ever given me about its own limits, and it is not documented anywhere. An earlier report on this forum (topic 15490) describes the watch freezing at essentially this same level. Nothing is ever released None of the four evictions is followed by JS discard. The first and only one in the whole session appears at 14:50:35, when I stop the exercise. So every Disable → Load script → Enable cycle instantiates the module scope again while the previous one is still held. That also reframes the “three apps” case. It is not that a third app is too big — my own footprint is 12.4 KB, resident main.js plus the single mounted template. It is that three apps cycling through evictions exhaust a shared pool that nothing empties until the exercise ends. One caveat on reading this The intervals between evictions look almost constant (27, 50, 30 s). That number measures how fast I re-enabled the app by hand, not the watch. Survival time is the honest metric. And the last three survival times being similar does not mean it stabilised — it means the pool was already full before I started measuring. At 99.5%, any re-enable trips the release callback almost immediately. So, concretely Is Zapp X:Disable without a following JS discard expected to leak the module scope? If yes, a firmware eviction is not a recoverable event — it permanently consumes shared heap, and the watch degrades within a single session. Is there a supported way to make an app release its context on eviction, or to be re-enabled cleanly within the same exercise? What is the intended budget per app against the 133 120 B shared heap when three apps are enabled, which is the configuration FW 2.50.26 added? I have the full logs and the built blob available if that helps, and I am happy to run any test you would like measured.

@SergioB This has already been suggested and seemingly ignored. Also, the font size for the remaining distance in the zoomed in mode should be increased - it is difficult to see. And yes, because of the blue labels rendered on top of the screen it is now impossible to see remaining ascent/descent in the zoomed in mode.

@2b2bff it happens the same to me, but I haven’t understand the pattern yet. Sometimes I see only one activity type, sometimes more than one. The only thing I have discovered is that the summary discards always at least one activity, it is never complete.

[image: 1786344212040-29362.jpg] [image: 1786344212067-29363.jpg]

@Martin-Tuharský Hi Same issue here. 4 Days old Race 2 watch updated to the latest firmware on day one rebooted twice. Luckily only in time mode and not during my 100km race a day ago therefore there must be some kind of issue with this

On my Race S, black grids occur at least once on every walk or hike. I have not noticed a change in frequency over several watch updates.

@paul28 I recently started using the suunto+ stryd app on my race s and was puzzled why I sometimes see groundcontacttime and other metrics beside power and sometimes only power. Now I know. I also have the problem that my heartrate sensor looses connection with my watch and doesn’t reconnect. That’s going on for over half a year and no solution in sight. There might be a next firmware update which might arrive in august but that will not contain a fix. And a firmware after that? I really doubt it. I will report this to suunto support to keep the pressure on.

Not sure what I did, but the forum now works on my iMac

@roadrunner this feature was implemented earlier this year in other models (Race, Race S, Race 2, Vertical 2) with a software update that vertical have not received yet due to some hardware limitation. In many post in this forum it is stated that Suunto devs are working to bring some of these new functionalities also to Vertical 1, so maybe your request will be implemented!

@pvricardo Either the barometer sensor is dirty or the sensor has failed. I had the exact failure with my Race and had the watch replaced on warranty. In case the issue is caused by dirt, you can try soaking the watch in water, then let it dry and check if that has resolved the issue.