rolinger opened a new issue, #287:
URL: https://github.com/apache/cordova-plugin-geolocation/issues/287
I am testing some new rewrites of my code for geolocation and am noticing
some peculiliar things and hoping others can help explain.
For both getCurrentPositions() and watchPosition() I use same following
options:
`var geoOptions = { maximumAge: 10000, timeout: 10000, enableHighAccuracy:
true };`
1. When app is deployed to iOS Simulator that `watchPosition()` fires a 4
times (every time) and then I get a timeout which is triggers my onError
callback. This happens on fresh install of app and redeploy and
updated/changed version of existing app on the simulator. On physical devices
and Android simulator this is not happening - I see it firing about once per
second (***)
2. When deployed a real device, watchPosition() seems to be firing every
second even though my device is plugged and sitting on and not moving. How
exactly is watchPosition working? I assume it would only trigger if it detected
an actual movement, but my debugging shows the same coordinates every time it
fires.
3. Is there a way to slow down the watchPosition to only "check" once per 10
seconds...I don't need extreme "watching" in my app but I do need to try and
update the users coordinates at certain intervals.
4. Last, how intensive is `enableHighAccuracy` on the device as well as
what are others experiences when not using it - the disabledHIghAccuraccy
coordinates versus the enableHighAccurracy coordinates? Is there really a
significant difference?
Thanks.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
