@freeheeler nope I mean climb guidance

@Anthony-Guillemette I investigated an issue, unfortunatelly there was a real bug. TLDR; what happend - misconfiguration of CI/CD leads to non googlePlay version was built with google play internals without sms sending module so, could you try the latest preview build? https://artifact.fra1.digitaloceanspaces.com/live-t/apk/btle/live-t.apk should be - 1.0.16 (101) And again thanx a lot for point out this issue!

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

Edit. I just realized joaquin’s photo I was referencing is comparing a Coros with Garmin, and that Coros does also have an offset, which seems even bigger than what is seen in Suunto. Removed bad photo. In those photos you see only a 3 meter offset with Garmin, but I’m finding many turns with much more distance offset with Komoot’s algorythms, as explained. Even something like 15 meters several times.

@Brad_Olwin said in Race 2 accuracy: 80 km trail race here is distance from V2 and R2 well within GPS error. First V2 and second R2 with V2 right wrist and R2 left wrist. Last Saturday 18/04 [image: 1776864227179-68ed9987-2f06-4e28-bd97-9853e4aff7c0-image.png] Distance 85.76 Km 84.32 Km 1.44 Km (1.7%) To be able to compare the raw data recorded with both watches, can you share the final distance shown in the graph in your www.sports-tracker.com/ activity information? Maybe that raw distance is more similar in both watches than the showed distance, showing the shorting distance behavior also in your Race 2.

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

To recap this thread, and I’m my opinion: Light grey color is missing for complications. This color is very interesting to make the watchface battery saver and more comfortable (specially when you are at home) Customizable font colors are missing for main fonts. Same reason as previous point. The bright white is not the best color depending of the watchface. A minimal watchface is missing. Just one is enough, but we should have at least one to choose. Like the Ocean after removing the outer complication and even with the same fonts. What it happens is that the hour digits are smaller than they should if you remove the outer complication and considering the 1.5 inches screen.

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