@freeheeler nope I mean climb guidance

@Nikolai-Simonov phone number is correctly defined and sms authorization toot, but sms is still in error. I have an Huawei P30. [image: 1776896461802-screenshot_20260423_001944.jpg] [image: 1776896559101-screenshot_20260423_002204.jpg] [image: 1776896461866-screenshot_20260423_001546_one.athletica.live_edit_176306121803305.jpg]

@sky-runner I agree, the average gradient is nice for the current climb, but it would be even better to also have sectioned gradients to know whats coming because the small graphed line is hard to tell when gradients change

I can’t tell which is more accurate between Running Dynamic and Suunto Spark on the watch, so I’m not confident enough to speak about it.

One thing that is not actual navigation but very much related: In yesterday’s Race I loaded the course and started navigation without TbT just to be able to see where the route would be just in case. As I run through the finish point, I got a full screen notification that I reached the end of the course and had to dismiss this notification to be able to actually stop my activity tracking. I think the upper button should have paused regardless…

@Brad_Olwin that difference is on the ‘bigger’ side. I had similar shortening with Fenix 6x and Galaxy 3 (I think) and these were no multi-band, multi-system watches. Having ~750m difference on a marathon (race) is not small number I believe. That being said I think someone has shown here that the distance is good but the watch filters the gps points that leads to shorter track, so theoretically increasing the snr threshold should ‘fix’ this. In any case R2 for training and V2 for the race day for me

@suzzlo 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 but… you can download maps for the mobile phone that are much faster… so… if we think, same server is delivering them… this should not be the problem… Anyway, I can live with it You’re right! I didn’t even realize that, even though I did download mobile maps too And yeah this does seem like an understandable constraint of small smart devices. I too am happy to have the convenience of WiFi downloads, even if they are pretty slow compared to bigger devices. My old Garmin Fenix maps downloaded way faster, but it was via USB cable and a PC. But given the analysis here, the original post does now sound like a WiFi issue or a bug. Maybe try downloading maps on some other place or WiFi…? If the download speed is considerably less than 1GB / hour (or ~2Mbps), it should work faster and there are not many broadbands this slow.

@dreamer_ said in Minimal watchface (feedback): Ocean has seconds Right, that’s why I’ve been using it since I got the watch in May 2025. I need seconds. Weirdly enough, shortly after I installed it, the preview picture in the Watch face store lost the seconds. 🤨 I didn’t know whether the watch face was updated, removing the seconds, but if you still see them, that means that current version still has them. Maybe someone with inside info can inquire why the preview pic in S+ store does not show the seconds. In My watch faces / In S+ Store > Watch faces (missing seconds) [image: 1776790703954-ocean.jpg] [image: 1776790729983-ocean2.jpg]

@MdzOtt yes, SA is the one not doing it ;). In my case with Karoo Gen 3 I see same avg power with zeros included (gold standard) like you get see with garmin/Strava

@gkaempfer Same here

@maszop Thanks. And weirdly it has now synced correctly some 20+ hours after finishing the activity. That’s what usually happens an hour or two after I’ve grumbled about it on here. I’m inclined to suspect some sort of Bluetooth issue but whether it’s the phone or the watch I can’t say. It’s annoying.

@Egika Yes, different colours make no difference unfortunately

@Manuel-Extreme There are 3 things Should the the watch always record data even if it can determine the data is incorrect? No Should suunto look into crashes? Yes Am I less concerned with loosing some heart rate data than you? Yes. My original reply is about the first point. But since it is an important point for you I will no longer capture your topic. (Btw, I was not able to reproduce your steps on my race 2, so it could be model specific)

@thibault-b. Good job !!! I test the last version today. It seems perfect all information I need size … thanks !

In my case, with the Vertical 1 Titanium Solar, I’m confident the issues started with version 2.43.12 released in June 2025. I had been monitoring battery consumption, which increased from about 3% per day during normal use to around 7%. It’s not a dramatic spike, but it reduces battery life from roughly 21–22 days down to no more than 14–15 days. Wouldn’t it be enough to check what changed between version 2.40.44 and 2.43.12?

@Highlands These are great! Thanks

Should be fixed in next release, being currently tested.

@Egika this was exactly the bug I referred to in my post. Anyway my point is that there is a difference between fixing watch breaking busy and niggles, so it would be good to know what to expect…