GPS stops with "maximumAge: 0" in HTML5 geolocation

[costales]

Hi!

If I use this:
 navigator.geolocation.watchPosition(
 function (pos) {
  console.log('new pos');
 },
 function (error) {
  console.log(error.code == 1);
 },
 {
  enableHighAccuracy: true,
  maximumAge: 0
 }

The GPS will not give more new positions after X kilometers (so random), because of the "maximumAge" parameter (I put 0 because I don't want older positions).

We see the behavior in the current version of uNav (0.59). After remove that command, the GPS never stops.

I think it could be from oxide, because there isn't dumps in the log and if I kill the app and launch again, the GPS works again.

Thanks in advance!

[David Barth (dbarth)]

It looks similar to bug #1551686

[Alberto Mardegan (mardy)]

A spent a bit of time investigating this report, and I believe that, if indeed there's a bug, that's in Oxide: the handling of maximumAge happens entirely in the Oxide/Chromium code, because the maximumAge parameter is not even being passed to the location service.

In any case this is puzzling because maximumAge default value is already 0, so setting it to 0 shouldn't have any effect at all.

[Chris Coulson (chrisccoulson)]

maximumAge is a red herring. It only effects the behaviour of the initial location (ie, setting it to zero means the app has to wait for the first location update. Setting it to non-zero means the application gets a cached location before the first location update if it's not too old)