GPS PositionOptions in clock

[bhwolf]

My clock needs location data but doesn't have to be accurate.  I am setting the PositionOptions like so:

var gpsOptions = { enableHighAccuracy: false, maximumAge: Infinity };
geolocation.getCurrentPosition(locationSuccess, locationError, gpsOptions);

Whenever I load the clock during development, it's always taking a new GPS reading (looking at the position timestamp) and takes a good bit of time (30-45 seconds).  Subsequent calls seem to return the cached value.  This might be by design, or might be a bug.  Just wanted to verify behavior -- makes initial load of the clock much slower.

[JonFitbit]

You may want to persist the last reading yourself, or request the GPS location from the companion while you're waiting.