@freeheeler nope I mean climb guidance

@Dimitrios-Kanellopoulos yeah, @sky-runner always provides valuable input. The problem is no time to read all feedback

@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. And pod features could also be improved in a future firmware update. An analogy is running with a 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.

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

@Nikolai-Simonov I have intense jungle training this weekend; I’ll be testing both Vertical 2 and the update.

@gkaempfer Same here

@Egika Yes, different colours make no difference unfortunately

@Highlands These are great! Thanks

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

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

@aiv4r no worries. I think the current way is not bad at all. It just need to be consistent. Having a 5km run as PB for 5k - great, Having a 10.xkm run as PB for 10k instead of the 9.95km race I did last time - accepted Having a 20.4km run as PB for the half marathon - what? And nothing I can do to decline that half marathon PB and go back to the one before… support hasn’t been that helpful with that, yet…

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

Received the Spark today after a weekend order. Paired & updated quickly and have supreme sound. Haven’t tried them in action (on the bike trainer or out for a run) but are quickly becoming my favorites in spite of owning multiple sets of Sonics. [image: 1776298642069-sonic.png]

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

@Gunnar said in Map Design Update 2.53.42: memory is not storage Unfortunately, I can’t find any information anywhere about the difference in RAM between the Race and the Race2.

The watch and phone are connected via Bluetooth, and I’m receiving notifications, but the app shows no connection. I turned Bluetooth off and on on the phone, but it didn’t fix the problem. What else can I do? [image: 1776097483350-a11.jpg]