Seems to be working now Thanks everyone

I give a thumbs-up to Suunto Support and all the participants for quickly resolving the issue with the maps.thx

@johann.fuehrer thank you. Just did it, will see how it goes. Hopefully this issue will get fixed with the next update

@snow let’s see if it’s durable. Usually such things don’t last that much. Curious to see what improvements it will bring ; I use my chest straps all the time (except on very long ultra trail races)

@Dimitrios-Kanellopoulos Can confirm for Vertical 2 as well

@MKPotts first time I hear about such an issue. Sounds like something is wrong, so I’ll report it. Now if it is firmware related, I doubt the S9PP will get it fixed (unfortunately), but if it affects 3 different watches with different firmware may be backend related. I never had this issue, so I would need the logs of someone else.

@Dimitrios-Kanellopoulos Android for me too

@Thorlap71 Fixed via cloud updates than you for the report

@zt_zzzzz I still didn’t had the time to test on windows, but theorically fix the translation issues and the fact of server not running and gps status no updating . you can test new release and if not fix I will plunge during weekend on windows.

@herlas I have not any experience with this feature, just reported this issue with Wahoo and giving an update now. Because Race S did not get Q2 update sensors/BLE are a bit behind software wise. Next update should hopefully improve all the BLE related features.

@Lorenzo-Pintore Thanks mate!!! It was a bit hard to find. You first have to open the route for editing and then click the V-sign for accepting the edits, and only after that you can modify the activity types. Awesome, thanks!!!

@Nigel-Taylor-0 there are some server side issues, may be related to that

@Robbin053 Strange - make sure the Spark are not already connected somewhere else…?

I’m also on beta (Android), and I can confirm it seems to be solved on my Race 1

Is this issue solved? I did two dives with the new firmware and until now I did not see any Mandatory Gas Time Alarms in the beginning of the dive…

@martintrail no, it never left beta status. In my case!

@Tamás-Tompa Happening to my still several times in the past few weeks. Support have advised to follow the soft reset process - I have suggested a firmware update is necessary in order to resolve fully. FW version : 2.50.28

@2b2bff said: Or it is a hardware issue that is triggered with the new firmware. Had something like this before on a PC. Bad memory module - worked fine with Windows 98 or so, but failed with Linux. OMG I had the exact opposite! I could not use Win98 anymore because it would freeze a mere minutes after booting, and switched to Linux where my computer worked fine. The year was 1998