Vivoactive HR and GPS position

Former Member over 8 years ago

Hi,

I'm the author of the Altitude widget: https://apps.garmin.com/en-US/apps/cab807f9-1c6f-4141-8266-06190421fa44

I'm getting complains (and bad reviews) about the widget reporting the same altitude over and over again regardless of where the user is. The widget is basically reporting the same altitude it did report the first time the user used the widget.

Something familiar?

jim_m_58 over 8 years ago

How are you getting the altitude? Firing up a one shot GPS or from sensor.info?

I just tried a simple widget on the va-hr that uses sensor.info and it looks like it works fine. (the va-hr has a baro altimeter)

Former Member over 8 years ago

How are you getting the altitude? Firing up a one shot GPS or from sensor.info?

I just tried a simple widget on the va-hr that uses sensor.info and it looks like it works fine. (the va-hr has a baro altimeter)

One shot GPS. The GPS position is then sent to the backend which returns the altitude. The point is to not use / rely on the barometric altitude. So in this case it looks like the one shot always provides with the same GPS coordinates.

jim_m_58 over 8 years ago

I added a one-shot to my test widget, and display both the altitude and lat/lon from it, ans that too seems to be working fine on the va-hr.

(the altitude is the same as from Sensor.Info, and looks to be correct)

Are you caching the lat/lon and reusing it if the one-shot isn't getting a fix?

I'm guessing you're using makeJsonRequest() to get the data - what happens if you get an error on that? Do you re-use some cached data for that? I'm seen some weird errors when doing a makeJsonRequest() on the 2.65 beta FW for the va-hr (it's got the 2.1.0 VM) (I reported them do Garmin a while back)

Former Member over 8 years ago

I'm not caching anything in the widget and/or backend.

Only vivoactive HR users are reporting the issue and they have to restart the watch to get the proper altitude back, and then something's cached again, restart, ...

I don't know what the issue is and can't test on a vivoactive HR since I don't own one. I'm just going to remove support for the HR since it only brings bad reviews.