@sky-runner my response wasn’t to you. I can see your original comment. But the comments just before mine suggested that you couldn’t see the time when sitting on the settee.

@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…

@Freezer indeed, it does. thank you. Let‘s hope this is a permanent fix.

[image: 1768070565680-screenshot_20260110-182044.png] Screenshot from the spectrum analyser

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.

@Stoke80 currently I am not sure if this was probably fixed with 2.50.26. can anyone check please? thank you!

@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.

@jjpaz Yesterday I tested the behaviour of the new firmware on terrain with a bit more elevation: [image: 1768039371113-screenshot-2026-01-10-at-11.44.32-copy.png] Race 2 v2.50.26 Distance: watch: 13.15km, GPX: 13.40km, Strava corrected: 13.40km Ascent: watch: 1023m, GPX: 1048m, Strava corrected*: 1003m

@matteo_000 there is no such option on the V2. You can choose Always On Display, but that implies a dimmed version of the display after some seconds that you don’t interact with the watch.

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

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]

@krakra the maps go dark with AOD. But only an issue if cycling with the watch on your handlebars. You can still follow on the bike when they darken. In other modes like running, walking etc where you raise your wrist they wake up so quickly it doesn’t make any difference. I have the V2 now, from the V1. The V2 is much easier to read if your eyes aren’t perfect. I need reading glasses but can read a lot of fields on the V2 I couldn’t of read on the V1. I purchased the V2 at launch, I think September, and have found the watch excellent for my user case.

@OutdoorMan Thank you. Indeed you can toggle badge (Group Title) visibility under Edit profile. Although I’m not sure additional titles are supposed to be visible automatically by default, the first one reached (Bronze) was definitely visible by default. @Dimitrios-Kanellopoulos Issues with group Join button erroneously displayed or missing as described in previous posts still applies.

@Egika You are so patient to help lazy forumers.

@Tami999 I have similar issues from time to time. Sometimes it gets stuck trying to connect to the built-in OHR sensor even though it tells me that it has connected to the external sensor - the way I can tell is that the sensor icon is different between the OHR and the external sensor. And sometimes it completely fails to connect to the external sensor no matter what, and I have to unpair the sensor and pair it again, and that sometimes takes a few attempts like you described. The whole experience is sub-par! And if I try to use two external sensors - that works even worse!