Position.Info.when Problem

It is a bug that affects the vivoactive and fr920xt. It may affect other devices. I sent a test case to the folks at Garmin last week.

Travis

Hi,
do you think this will be fixed ?
Cordialement.
J.D.

I'm not sure. Hopefully Shannon, Brandon, or one of the other Garmin peoples will post here with an update.

Same problem here. This is serious !!!!

With my brand new Quatix 3, I spent many days working on my app.
With the simulation everything was fine but in real life i noticed that the timestamps belonging to each position info can not be used at all. :mad::mad::mad:

I was going to use that app during my sailing trip next week but now it becomes completely useless.
Now I am beginning to regret paying 599 Euro for that watch.

Is this forum the correct channel to ask Garmin to do soemthing about that very old issue ?

Are you using the following in your watch-app?

Position.enableLocationEvents(Position.LOCATION_CONTINUOUS, method(:onPosition));

In onPosition() you'll get the current location and it's quality (including QUALITY_LAST_KNOWN, and QUALITY_NOT_KNOWN)

It's called with Position.Info as an argument, so you always get the newest data.


"when" is something you may only need if you looking at data without GPS being on for the app, where you would be looking at old data.

Hi Jim,

Thanks for your quick reply.
Yes, I am using onPosition as you described. However, I am storing the info objects in an array to do some more calculations. These calculations are also based on the different timestamps at whch the info objects were collected.
In the simulation, everything works fine. When running the App on my watch, the delta time between timestamps is always 0.

This seems in line with the issue reported by other members. Do you know if Garmin is aware about this problem and wehther they are working on a solution ? Who can I contact about that ?

Thanks
Uwe

I reported several problems with the GPS data supplied to the position callback (or retrieved with Position.getInfo()) on the fr920xt on 2/20. I don't believe a fix has been released yet.

mergenlideki - to get around this, instead of using the "when" you see, couldn't you just set it to be the current time in when you're in onPosition()?

mergenlideki - to get around this, instead of using the "when" you see, couldn't you just set it to be the current time in when you're in onPosition()?

yes, i am thinking about that as a workaround. i am just worried that the memory consumed by my history array will be even bigger :(

I reported several problems with the GPS data supplied to the position callback (or retrieved with Position.getInfo()) on the fr920xt on 2/20. I don't believe a fix has been released yet.

I have no experience with the responsiveness of Garmin. Hopefully, they also regard this issue as a serious matter.
What is the official way to report such problems ?