Compass is frozen while tracking with she SUP activity (fenix 5)

I noticed that the map would not orientate during standup paddling recording.

Then I added a compass screen to this activity and noticed the compass is simply locked

only unlocks if you put the activity on pause

other activities like running don't have the issue

anybody else having the same problem?

  • Issue affects both the SUP and Row apps. But doesn’t affect other apps such as trail run, hike, etc. My guess is that the activity tracking for these apps collects data in such a way that interferes with the compass data. It’s a big shame since a compass bearing is pretty important for ocean navigation. My work-around (not a solution) is to pause the activity, take a compass bearing, then resume the activity.

  • Just checked on my new fenix 6, still a problem, real shame indeed in those activities ... Had to get my phone out to find my way back last time :-)

  • Also checked an older unit, the Vivoactive HR, and same issue; SUP and Row apps freeze the compass, but compass still works for Walk app etc.

    I tried third party compass data fields and widgets from Connect IQ and compass remains locked while the water-based apps are running.

  • One addition workaround: On my Fenix 3, I’ve been using the “SUP” app up until now. But there is another app you can add to your favourites called “Paddleboarding”. If I use this app, the compass works (along with Sight n Go, etc)!

    However, when I save a “Paddleboarding” activity to Connect, some helpful data that is normally collected during “SUP” activities (namely stroke data, such as Stroke Rate, Distance per Stroke, Total Strokes, etc) is not displayed.

    But I do gain Elevation data (though this isn’t all that useful on the ocean).

    As an aside, if you do save a “Paddleboarding” activity in Connect, then edit the activity type and change it to a “SUP” activity, Connect does display the Total Strokes, Average Stroke Rate and Max Stroke Rate. Distance per Stroke is still not displayed.

    Anyway I hope this info is useful to someone besides myself...

  • searching from internet, come to this topic, cannot believe this issue is still here on my F5XP, latest version V15.40.