@EzioAuditore and once again it must be remembered that the GPS data collection of the Race 2 is very good, the problem comes later with the software processing of the information to calculate the distance to be displayed.

@sky-runner I second this. In my case it happend 3 times over 18 months or so. Problem with those race conditions is that there is seldom something you can do to avoid them - on the user side.

Scusate ma non capisco il voto negativo!!!

I finally received mine and use them on a run yesterday for the first time. I noticed a bug: at first I could adjust the volume with the touch I had set up (triple tap), but after some time this stopped working; I had media controls on my watch, too, and when I chose the volume option nothing happened.

@2b2bff said: @stromdiddily there is no universal “This is a workout file, deal with it watch” format. If you are pushing a workout to Garmin, you define the steps. If you push the workout to Suunto, you define a SuuntoPlus Guide. I don’t know how Coros or Apple Watch does handle it. So, Training Peaks - or any other platform for that matter - has to include the respective framework for each brand individually… The other way around, if you read the finished activity from the watch, there is a format that has been widely adopted: Garmin FIT files. I see, this makes sense…thank you

Experiencing exactly the same issue

@withManish On iOS there is rungap for datamigration. And I use strava and intervals.icu. It collects data from multiple sources (I had different brands in the past). But most importantly, data of 5 or 10 years ago hardly has any relevance. But I’m no hardcore data collector.

@cosme.costa said: Rearding the OFF ROUTE alerts when you are on track, check what I said. Is the route created with SA or imported? I think I’ve seen it both ways - both when it is created in SA and when it is imported. This has never happened before but started happening regularly after the last update. What the new implementation doesn’t take into the account that the map may not be accurate enough, so it may think you are off route because the trail on the map is slightly off from the real trail.

Hopefully they’re able to fix it soon. It feels like with every update they just introduce more problems. Currently still experiencing the auto-update bug (can’t disable it essentially), and now the battery bug has gotten even worse.

@Squirrel thank you!

@Łukasz-Szmigiel The ones I used didn’t have those tags and have been around for years, so they’re probably directly from Suunto.

@baaaa said: It’s disappointing that you’re aware of the issues but aren’t addressing them. This is not correct. Suunto devices and services, like any complex products, have many issues and areas for improvement, while resources are always limited. That’s why issues have to be prioritized and cannot all be addressed at once. Every user naturally feels that their own issues and requests are the most important, and that’s understandable. However, the bigger picture often looks different. @baaaa said: your company, but… Sadly, it’s not my company, only my employer. If it were my company, many things would probably be different. @baaaa said: it seems to me that your users who report bugs should be worth their weight in gold, and you should provide them with a simple and convenient tool for reporting bugs and suggesting new features. Instead, they have to go to some glitchy forum It sounds like you’re looking for official customer support channels. Those can be found at suunto.com. This is a community forum, not an official support or feedback channel. If someone is answering here they do it in their free time, not on duty. @baaaa said: search for relevant threads Yes, that’s the only practical way to keep the forum in a decent state. If everyone posted their own rant in arbitrary topics, the forum would quickly become a mess, making it even harder to find information and identify recurring issues. @baaaa said: wait for a moderator to approve their post… Unfortunately, that’s the only way to deal with spam. Users who have built up some reputation can post immediately, but newcomers need to wait for their messages to be approved.

@sky-runner You’re right… ! I see it similarly… it is certainly very difficult not to overload the Maps… POI like water points would certainly be useful on larger zoom levels… But they don’t care about trash cans at all…

@maszop sometimes you realise at the moment to download maps and … Yeah, otherwise this is just a discussion.

@matram pm me with your GitHub name, I’ll add you to my S+ skill repo. I’ve already done the digging.

@GiPFELKiND What phone model? and what error? also on lates android build, knowing issue if you app swiped out from activity list, you probably could lost connection, fixed but not released yet. in general race for BTLE connection between suunto app and live.τ app still exist, but observation said that it’s not a big deal, and connection works in general well. personally i usually lost connection in some difficult areas near military objects, or radio polluted regions… not sure if it’s your case. you can try to the latest apk build here - https://artifact.fra1.cdn.digitaloceanspaces.com/live-t/apk/1.0.18/live-t.apk or if you use google play join internal builds here - https://play.google.com/apps/internaltest/4701596347369604163

@Joaquin Be careful not to chase perfection and in the end nothing is completed. The komoot route is a bit cumbersome and komoot is far from perfect (even if I tell komoot to not change the route, the route on my suunto race s is different than on my wife’s apple watch.) The garmin/wahoo way (select a gpx file and use the open with app) would be an improvement, even if not all tbt alerts are perfect. My first gps watch (a ambit 3 sport) only had breadcrumb navigation. Did I ever got lost? No. My watch after that, a forerunner 935, had breadcrumb and tbt alerts. (Which didn’t work well. A route could only have 50 navigation alerts and if you did your route reversed you lost all tbt alerts). Did I ever got lost? No. My first watch with maps (a forerunner 965) and having some context is nice. Eventually garmin fixed the 50 alert limit, but not the reverse problem and they introduced a timing bug (up to 10k the alerts are before a corner, after 20k alerts are in a corner, or after). And yes, on a twisty road you get alerts for every corner. Did I ever get lost? No. Now I have a suunto. Komoot is fine, but could be better. Autodetect of going reverse is good. No problem if I do a round route and the end is detected before the start (garmin has problems with this. Navigations stops when you reach the goal, which could be before you actually started). Autozoom actually works as one would except (garmin had autozoom, but that doesn’t work, or not as one should expect). But do I get lost ever? No. In the end, all are equally good in the “do not get lost” requirement. Is everything perfect? No. But don”t wait until everything is perfect. Release small steps. Get feedback. Improve some more.