So, iOS bug and not new feature, because it is still OK in android [image: 1776431360742-screenshot_20260417_150755_suunto.jpg]

@Stoke80 I have Assioma PRO-MX2 paired up my Suunto race S, it works just fine, what’s yours specific questions?

@Brainicus 4th degree not needed…I’m neither moderator or suunto related. Even some users here are close to suunto, it’s still supposed to be a help forum between users, not an official suunto support tool. If I had wanted things to be better I guess I would had created my own brand and done everything well since begining and better than garmin, coros, suunto and all the others, and promise a lifetime update support with clear vision of what tech and developpement will be in the futur… I personnaly use SV1, it’s a 3 years old watch, it has already been improved a lot, and I’m confident we will have updates, but also understand hardware can limit update in the (close?) futur. SV1 works like a charm, can for sure be better but is already a best seller on his kind. For ocean my understanding is that it’s a device that must at first be strong on “diving” features and that it can’t suffer about regression bugs on those features. So I guess improvements and testings can’t be nothing else than 100% sure.

@Egika those running metrics are far superior in something like the head than in very moving one arm. It is explained in that video. That is also a reason with PODs exist in other brands or chest straps with POD features. And pod features could also be improved in a future firmware update. An analogy is running with an HR chest strap. It’s better than the wrist sensor and if you are running with the strap, is because you do want the metrics of the strap. It has no sense to have 2 activities in that scenario. Watch’s metrics should be avoided when running with the Spark paired (in my opinion the contrary is clearly a bug once you have both products in the same workout)

@Egika said in Race 2 accuracy: I have confirmation, that Race2 indeed measures a little short, compared to other models. cannot share more details, but the watch works as designed. Thanks for the reply!

@snow said in Downloading map takes a very long time: @muurain said in Downloading map takes a very long time: Suunto’s cloud service that throttles the downloads. Fair they don’t I think it has been mentioned when maps download was introduced, that the watches processing speed is the limiting factor here. So, yes. It is slow and always has been slow. While newer watches are a little faster. The watch processors are selected to consume as little energy as possible for long battery life. Thus they can handle the data transfer and unpacking only slowly. As it is only required a single time, it should not really matter.

@Hashly-Iian but isn’t this an easy to implement Upgrade which would be very heplful! All data and technical basis is already given. Maybe with the step from beta workout plans to the final version…hope so.

@rwmastel0 this should be fixed with an update

Should be fixed in next release, being currently tested.

@Thibault-B. The PREV INT panel does not bother me and is probably very useful to most runners. My problem, and probably simalar for other older runners, is that I have troubles to read the small numbers. Thus, a temporary screen after an INT would be perfect (maybe 3 sec). I guess most runners would like that in INT REST mode but maybe in INT INT mode it might disturbs some. One other idea, of which I do not know if it possible: Is it possible to show a blow-up screen with the information about the previous lap for a short time after tapping on the PREV INT panel?

@2b2bff said in Race S: Extremely high battery use rate: @sky-runner this thread is in the Race S forum and has Race S in the title. I guess it is related to the Race S then? I know this is a thread in Race S forum because it was me who started it. I suspect this is a software issue so it is likely the same across all models. Anyway, I haven’t had a chance to verify this with Race S. Perhaps I’ll do that next week. Currently I am using Vertical 2 and Race S is unused.

@freeheeler nope I mean climb guidance

thanks - strava treats auto and manual as the same - simply LAPS - hence the sensible strava display on the right of the same run from Coros Vertix2 - and yes i guess it must mean that coros record auto 1km laps since the previous auto or manual lap - but what’s wrong with that? to me that makes far more sense it would be nice to have an option in suunto to record separate/independent versus overlapping auto and manual laps - or at least an option to export/synch with them as auto laps, manual laps, or merged and I did use a FIT viewer already to understand that the auto laps are not exported if you have manual laps recorded - because that’s what i was seeing in strava and wanted to understand

@ScottBH7 said in Feature Improvement: Add step count to available activity metrics: Hi there, I have a Feature Improvement request. Basically, the (Total) Step Count should be available as a metric to activities such as walking (and to a lesser extent running). I frequently go for walks and wonder what my total step count is, but cannot tell easily while the Walking activity is active. This seems like a glaring oversight. It’s already there? Here’s a walking activity, Steps: 2,374 [image: 1776395874743-1e1b34b1-56a3-4a87-96de-57f7df964f37-image.png]

@Nelson-Diogo ohhh, at least this makes sense also for Suunto … let’s see if they implement in there Race and improve in the Run

@Egika Yes, different colours make no difference unfortunately