Acknowledged
10 days ago
CIQQA-3459

bug: no way to set elevation unit on vivoactive 5

This probably should also be reported in the vivoactive 5 forum, but since that's not monitored by Garmin employees, I'll try here.

A user of one of my apps reported that they can't change the elevation unit from feet to meters. I told them to do it in the system settings (my app uses DeviceSettings.elevationUnits). But it turns out that Garmin left that possibility out from vivoactive 5.

The only settings (both on-watch and via Garmin Connect) are:
distance, weight, height, temperature, pressure.

Note, it's not a mistake, it's height, with cm or inches, and not elevation or altitude that's supposed to be meters or feet.

This is vivoactive 5 with FW version 14.15

Yes, there's no barometer in va5, but it doesn't matter, because the watch displays the correct elevation based on GPS, just in feet.

See also: https://forums.garmin.com/sports-fitness/healthandwellness/f/vivoactive-5-series/418980/bug-no-way-to-set-elevation-unit-on-vivoactive-5

flocsy🤠
Parents
  • 3 days ago

    I did a test on a real fr55 (also without baro). Interesting results.

    I started a Walk activity with my Hiker DF on it. I waited for the GPS to become green, then started the activity. It displayed my elevation as 104m. It is incorrect, my actual elevation was 23m. However this proves that both ActivityInfo.altitude and DeviceSettings.elevationUnits return actual values.

    I saved the activity, and looked in Garmin Connect, where interestingly there was an elevation graph, and it showed 24m (which is very close to the actual 23m) which means that the elevation displayed in GC disregards the values the watch "gives" to CIQ apps.

    I looked at the fit file in fitfileviewer.com and it's even more interesting, because the same thing I see in device settings is also recorded in the fit file:

    User Profile: elev setting: metric

    And I was wrong! The fit file does include the GPS "enhanced altitude": 105.0, 104.8. Note it's enhanced altitude (which I would've guessed means the auto corrected one), but it actually has the values I saw on the device screen from ActivityInfo.altitude. So the 24m we see in GC is the auto correction (which BTW can't be turned off on this activity because it was recorded on fr55. On fr965 there's a way to disable it)

    Note: 24m ~ 78ft, so the difference in not caused by wrong unit!

Comment
  • 3 days ago

    I did a test on a real fr55 (also without baro). Interesting results.

    I started a Walk activity with my Hiker DF on it. I waited for the GPS to become green, then started the activity. It displayed my elevation as 104m. It is incorrect, my actual elevation was 23m. However this proves that both ActivityInfo.altitude and DeviceSettings.elevationUnits return actual values.

    I saved the activity, and looked in Garmin Connect, where interestingly there was an elevation graph, and it showed 24m (which is very close to the actual 23m) which means that the elevation displayed in GC disregards the values the watch "gives" to CIQ apps.

    I looked at the fit file in fitfileviewer.com and it's even more interesting, because the same thing I see in device settings is also recorded in the fit file:

    User Profile: elev setting: metric

    And I was wrong! The fit file does include the GPS "enhanced altitude": 105.0, 104.8. Note it's enhanced altitude (which I would've guessed means the auto corrected one), but it actually has the values I saw on the device screen from ActivityInfo.altitude. So the 24m we see in GC is the auto correction (which BTW can't be turned off on this activity because it was recorded on fr55. On fr965 there's a way to disable it)

    Note: 24m ~ 78ft, so the difference in not caused by wrong unit!

Children
No Data