Subcategories

  • All resolved bugs and issues

    192 Topics
    5k Posts
    No new posts.
  • Gefahrene Touren(Routen) werden in der Karte nicht angezeigt

    5
    0 Votes
    5 Posts
    791 Views
    E
    @Egika und @Shrek3k Vielen Dank für den Tip und Hinweis. Ja so funktioniert es wieder. LG Enrico1705
  • Sleep calculation wrong in recovery widget

    1
    0 Votes
    1 Posts
    244 Views
    No one has replied
  • How comes this run is classified in Suunto App as anaerobic?

    41
    1
    1 Votes
    41 Posts
    4k Views
    M
    @OutdoorMan I had the same a while ago. Well I always wondered why it was considered anerobic altough ZoneSense as well as heart-rate should consider this as aerobic or long-aerobic. Long story short: I updated the pace-zones in the watch to values that correlate and afterwards it was correct. If someone has an idea how it’s possible to control that (I’d prefer it would use the info coming from ZoneSense), it would be much appreciated
  • Routes sync problem ( Race & Race 2 )

    6
    1 Votes
    6 Posts
    1k Views
    sky-runnerS
    @Matteiva I’ve noticed the same with both Race S and Race. Every time a watch is paired to the app, it tries to sync all routes. Then it becomes difficult to remove routes from the watch because that repeatedly fails.
  • Version 6.2.2 saved track bug an invisible position

    1
    0 Votes
    1 Posts
    243 Views
    No one has replied
  • Suunto app not syncing with strava

    3
    0 Votes
    3 Posts
    477 Views
    G
    @Pietro-Ciarimboli I’ve had the same issue for the last couple of days
  • 1 Votes
    3 Posts
    653 Views
    S
    It’s a bug in the watch. In: Settings - Training - Intensity zones - Default HR zones… f. e. the value 145bpm is set as minimum of the Z3. (That is also showed in the app). But if You choose any activity and go to Exercise options - Intensity zones - HR zones - Set Target Zone. You’ll see, that the value 145bpm is set as the maximum of Z2 and as minimum of Z3. (I had this very same bug on Garmin FR955)
  • Bug Report: Battery Optimization Setting Reverts on Android 16

    4
    0 Votes
    4 Posts
    532 Views
    WlodiPawel 87W
    Same issue
  • Auto commuting tag not working anymore - Suunto Race

    7
    0 Votes
    7 Posts
    961 Views
    T
    @pumarkin it’s probably software, because 6.22 tags fine still on Android.
  • No Popularität routen in app

    1
    0 Votes
    1 Posts
    319 Views
    No one has replied
  • -1 Votes
    1 Posts
    240 Views
    No one has replied
  • Question about the voice feedback

    Moved
    38
    0 Votes
    38 Posts
    3k Views
    I
    This works now! Not sure when it was fixed, but nice anyway
  • 6.1.4

    22
    4 Votes
    22 Posts
    2k Views
    S
    @CroShark thank you that worked. Very awkward process and bad development compared to former app-versions, but it works … if I stand outside my flat, in the cold, waiting for GPS-reception … happy with the outcome, not happy with the way - and the (non-/thoughtless-) ‘design’ of that capability of the app.
  • MyPlan Wrong Heart Rate Zones

    1
    4
    0 Votes
    1 Posts
    286 Views
    No one has replied
  • Please limit resources graph to 100%

    2
    1 Votes
    2 Posts
    512 Views
    S
    @brave_dave I agree. Similarly, sometimes I have the limit at 90%
  • Search Function

    3
    0 Votes
    3 Posts
    176 Views
    M
    @timecode Thank you
  • Version 5.3.7 and all before - wrong distance in multisport

    2
    3
    0 Votes
    2 Posts
    575 Views
    W
    @wotus Also in the latest version 6.1.4, the error is still present. So it is near impossible to analyze different sections of multi sport exercises.
  • Incorrect sync of in-route waypoints from Strava

    6
    2
    0 Votes
    6 Posts
    927 Views
    sky-runnerS
    Thanks @Dimitrios-Kanellopoulos! Let’s try to make this right for all users! Looking at the iOS version of the app running on my MacBook, it appears that the app already handles GPX import right. For example, let’s download a GPX course from https://canyons.utmb.world/races/100K and open it in the Suunto App, then tap on the waypoint that is 3rd from the right in the below screenshot: [image: 1756143044785-screenshot-2025-08-25-at-10.29.53-am.png] You can see that it shows two distances from the start. So that is good! It would be great to also show this waypoint at both distances on the elevation profile in the app (similarly to how waypoints are shown in Climb Guidance 2.0 on a watch) and to be able to manage waypoints by tapping on them on the elevation profile. Let’s finish importing the above route in the iOS app on MacBook, save it, and reopen it in the latest beta version of Android Suunto App running on my Pixel 9 Pro phone. What we see is that the app now shows a list of waypoints - that is really great! However, with regards to waypoints, we see that the Deadwood aid station waypoint (the one shown in the above screenshot) no longer has two distances here. The same applies to the Devils Thumb aid station waypoint: [image: 1756144563094-screenshot_20250825-105335.png] So basically each of the waypoints that should be visited twice appears in the list only once at a randomly matched distance - one of them got matched on the way out in that out-and-back section of the race course and another - on the way back. So clearly this is bad, especially considering that this is a UTMB World race where Suunto is a major partner. The correct behavior when importing from a GPX route would be to match all distances and show the same waypoint multiple times in the list. Now, let’s discuss import of routes from Strava. This is a more tricky case because, as I understand it, Strava routes are read-only in the Suunto App and are supposed to be edited in Strava. Strava has implemented a very good waypoint management that is fully compatible with Garmin Up Ahead feature. Perhaps I can claim that I gave them the idea to allow waypoints to be named and to include distance with every named waypoint so that it works correctly with Up Ahead. I suppose Strava syncs routes in FIT format because that is the only way to include distance information. If the Suunto App also receives routes from Strava in FIT format, then it should take advantage of waypoint distance included with each waypoint. The correct behavior would be to match all points on the route that are at the same location as a waypoint, but insert a waypoint only at one distance that is the closest to the original waypoint distance. That would ensure that whatever user has in Strava is exactly what they get in Suunto.
  • Heart Rate from imported FIT files are ignored

    5
    4
    0 Votes
    5 Posts
    681 Views
    D
    @Mff73 Right now I’m more focused on the HR values. If I add 3h of more workout containing HR data I would expect other values (h:mm’ss) in screenshot 4 but I get the same values like in screenshot 3 (taken prior to importing an additional workout).
  • Watch Face Issues

    1
    1
    0 Votes
    1 Posts
    273 Views
    No one has replied

Suunto Terms | Privacy Policy