@sky-runner your first point even weight more if you don’t turn a map in the size of the screen, but a map that is larger than the screen, as the centre point of this “disc” is off-centre of the watch screen… IIRC Garmin just uses the RAM of the SoC and Suunto use the same SoC (at least in the Race and Race S) with additional RAM. From my memory it is 11 MB, but that doesn’t really changes the whole situation…

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]

@Turo-Jantunen the fix for this skiing issue is planned for the Q1 firmware afaik

Maybe because Hyrox is not a sport? Anyway, who cares about step counting during CrossFit sessions? The value would be meaningless anyway, unless you connect the watch to an external camera so it can understand what you are doing…

Very nice indeed!

@suzzlo totaly agree with this. For me current watch faces are enough, but i would like to try develop own if it was possible.

After 17 walking activities with SV2, some on flat terrain and some on hilly terrain I got 1st V02max today. It was a brisk walk on flat terrain in zone 1 with good GPS and OHR. Great way to finish this year.

@prairiedog Wow! Well, I tried a million things. First, I tried downgrading, but it only put the watch in safe mode for several hours. Then I reinstalled the same firmware version. Multiple soft resets. Nothing. I did a hard reset, and it was useless. Then I went back to using my 9PP (disconnecting the Race S), on which sleep tracking worked. I went back to the Race S, still nothing. Then I adjusted the sleep time on the 9PP from 0.00 to 0.00 and went back to the Race S again. Nothing. Finally, I reinstalled the app with the Race S connected, and magically, it worked. So I don’t know if it was a combination of factors or just the app reinstallation.

I will reply to myself, since my last post saying that I got bad ox saturation got downvoted, I understand there is some distrust in my claim, i re-enabled the widget (that I removed because the last time I used it my watch rebooted itself…). Here is two SpO2 measurement taken back to back in good conditions, using the original silicon wristband, showing levels that should have taken me to a hospital (i’m fine) [image: 1767609596185-51b12383-0d94-4f8a-ab5f-5b3f9ccf9960-image.png] [image: 1767609640779-6fe90a5e-a424-4e4d-9fe1-df608a591d16-image.png]

@Tony-Monteiro yes we dont have a development team anymore. (sarcasm)

@sky-runner Thanks for information. I thought Strava was processing everything itself.

@TED77 But generally, the number itself doesn’t matter, nor do these types of comparisons. If the trend or graph is more or less the same in both tools, the difference in numerical values ​​can simply be ignored.

[image: 1767591977772-2a84154e-bf1d-431b-8437-0cd418bb9442-image.png] Last one (I think ). The blue line is measured. The purple one is the model! It was hard to train during these holidays. There were 6,5 hours of training this 2 week period. Okay, this is pretty alright. I think the battery isn’t draining linear with the percentage. I’m really satisfied right now! I was a bit down when the battery was so low this morning. It’s on the charger right now Sometimes it does like there is more drain that expected. After the first run and the last run. I’ve resetted the watch and for a few hours on the Airplane mode. Other notable things: The last run was with maps on ‘light mode’. It’s better visible in snow than ‘dark mode’. It seems to be draining much more battery than dark mode I’ve used the flashlight almost every day. One day even for a few minutes. My girlfriend couldn’t read the menu in a restaurant. I can’t see this back in the chart

@JaakkoK same. My polar H10 connects ok and stays connected. My Suunto sensor connects then the connection ‘flaps’. This was a replacement (last 12 months) for an older Suunto sensor. I was hoping this update would fix this, but it does seem to point to the sensor being faulty. Maybe a bad batch?

Seems I am a Goldmember again [image: 1767816154640-f8e99374-4007-4e70-b349-84e24ee5e3a3-screenshot-2026-01-07-at-20.01.25.png] Screenshot 2026-01-07 at 20.01.25 Thank you!