MicroLED would be the best alternative in the long term, but not now when MicroLED displays are still very expensive and prioritized for their extreme brightness rather than economy. MicoroLED displays have a very broad range of brightness and don’t suffer from burn-in, so they could be used in always on mode without a risk of damage while being more energy efficient than AMOLED. But the technology isn’t fully there yet.

@2b2bff We don’t have a dynamic icon in the data field that shows the turning direction; we’re working on it, and it’s something I’d love to have. The correct turn signal appears after 20 meters.

I think while the actual position data of a point may have some error, the distance measurement by GNSS is quite precise these days. Also some filtering occurs to the data measured every second. What we see is, that under some circumstances Rce 2 measures short, while this is not always the case (see John Korir’s Marathon distance in the other thread). As this is not a special setup only in Race 2, there is not much to do about it. If it does not happen everywhere and every time, this is just an arbitrary deviation with the range of 0.5%. Not sure what else to add to this thread now.

@Anthony-Guillemette said in Live location S+ app: SMS is still not working : “SOS message failed” i see an error, looks like missed implementation for pre-android12 telphony. I’ll publish new version today. @Anthony-Guillemette said in Live location S+ app: Linking the Suunto account doesn’t work (error 400: invalid redirect_uri) Oh! thanx for pointing out! Just checked suunto api profile, and they clear all api integration data!!! 🤯 ridiculous! won’t be difficult to restore but… @Anthony-Guillemette said in Live location S+ app: Another problem I encounter: when LiveTracking SuuntoPlus app is enabled by default on the training mode, I have to disable and then re-enable it, otherwise the watch is not detected by the application (“device search”). It’s not a bug but feature! you don’t need to re-connect it each time, just take a 5-15 sec to connect. TLDR; “Looking for watch…” - it’s a “cold start” during this time watch allocate memory and register all btle services. after that you could see “waiting S+ application…” at this stage s+ app is connected and waiting for handshake between mobile app and s+ app… but connection already happend! after that you could see the green text with a S+ app version. splitting connection on these three steps allows us immediatelly reconect to watch if service on phone has dropped or connection lost for some time, watch still registered on the gatt services, and we can try to restore it when connection back. you could check how it works, connect to the watch, than during workout disable service for a few second and enable it back, the watch should instantly reconnect. because every time on android we start from the fsecond phase, and if watch are registred in our GATT table, we fire handshake event imediatelly, if it pass we ready to work in miliseconds. if we just start a workout watch initially is unsubscribed from our gatt services, so in fact of this we need to proceed through the cold start. however, i agree it could look like a bug, but it should be solved in UX way… i’ll think about it…

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

@OutdoorMan said in Minimal watchface (feedback): @dreamer_ I personally just need to have a date in time only mode, because I never remember what date it is. And that’s it Totally agree. Battery icon also means you’,ll never forget charging your device but that is my feeling. I consider the rest of the things totally useless

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

@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

@Egika Yes, different colours make no difference unfortunately

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

@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

Hi. I also think the Vertical is still a good sports watch. I hope that in the next v1 update they’ll be able to include elevation contours in the maps at zoom resolutions that the MIP screen can display. Having them is useful in some conditions.

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…