So, the timeout parameter specifies the maximum time allowed to send a new position object. If no new position object is sent within the timeout period, the timeout error is raised.
You have very little control over how often your device sends position updates. Generally these happen (fairly) frequently, but if you're not moving a lot, I wouldn't be surprised if at some point the device doesn't send a new position update within the timeout period. I'm just guessing on that; I haven't had time to fully test that theory.
Furthermore, receiving a timeout won't cancel the watch, so you may receive multiple timeouts in a row. Assuming you have a position report available, I would probably just treat a timeout as "no position update" and continue to use the previous position until you get a new one.
That suggests the following to try with your devices: Try taking a walk with your device and see if you get position updates after the initial 3.
You might also try removing the plugin and using HTML5 geolocation to see if there is a substantive difference in how it behaves.
On Tuesday, October 18, 2016 at 2:11:28 PM UTC-5, Pete wrote:
...