LOCATION_ONE_SHOT always QUALITY_LAST_KNOWN?

Hi,

I'm developing a widget which uses GPS LOCATION_ONE_SHOT.

When testing on my va hr it always returns the last known position (if available).
I'm in a city, so maybe the last known is faster then a "real one shot"?
Or is this the default behavior?

Thx for help!
  • I just tried a quick test with a va-hr with a test device-app I have. Here's what I see.

    (it had been a few hours since I used anything with GPS).

    The first time I ran it it took a minute or two, but then I got an accuracy of "Good" (4), but then if I ran it again right after that, I got "Last Known" (1). What may be happening is that if it has a fairly recent reading, it just returns that, and if not it fires up GPS and gets a new one. Returning "last known" would spped things up in a case like this.

    Not sure how long it returns "last known" but I just waited about 5 min and that still was the case. I'd not noticed this behavior before but it could have been the case for a long time.

    I suppose you could just use "Continuous", and then disable GPS once you get data that's not "last good" if you want it to be more accurate.

    I'll see what happens after 10 min with the test app.

    Ok, after 10 minutes on the va-hr, still "last known", but also tried on a 230 and Edge 520, and on the both, it gets a new location each time my test app is run, so it does seem to be something off with the va-hr
  • Thanks for confirmation.

    Sometimes I got the last known over the whole day.

    It only clears immediately after starting a new activity which uses "Continuous" (e.g. the running app).

    My next attempt would be to use "Continuous" and if there is a "last known", the user can tap or hold the screen to use it.

    So they can access the widget faster, when the last known position is their current position in real life (approximately).

    Otherwise it searches for "usable" GPS.
  • I updated my last last post, as I also tried the app on the 230 and Edge 520. and they return "fresh" locations all the time.

    This looks to be a bug on the va-hr to me. I can see it returning "last known" for a few minutes, but I've waited 30 minutes and that seems way too long to me.
  • Ok, thank you very much.

    Also for the info about the other devices. I only have the va-hr at the moment.

    This means I could use the "one shot" for the other devices and the "workaround" for the va-hr till the bug is removed.
  • I've opened up a ticket to determine the expected behavior for this. I would tend to agree with you and think that it would try to refresh the information like other units, but will have to find out more from the device team.

    Thanks,
    Coleman
  • BTW Coleman -

    This morning after I woke up, I ran my test app on the va-hr again (so it had been 8+ hours since GPS had been on) , and I still got "Last Known" when doing a One-shot.

    This is clearly a bug IMHO. Let me know and I'll email you the test app if you want.
  • BTW Coleman -

    This morning after I woke up, I ran my test app on the va-hr again (so it had been 8+ hours since GPS had been on) , and I still got "Last Known" when doing a One-shot.

    This is clearly a bug IMHO. Let me know and I'll email you the test app if you want.


    That would be fantastic. Thanks for all your help everyone!

    -Coleman
  • Thanks to all!

    Hope this is only a bug and will be fixed :)
  • If this is a bug (I believe it is and has to do with the FW), the fix won't be available until at least the next FW drop for the va-hr, so it may not be fixed for a while. Just a heads up..