View Single Post
Posts: 214 | Thanked: 140 times | Joined on Aug 2010
#123
Originally Posted by ndi View Post
15 seconds is plenty with a-GPS.

Configuration of timeout could be nice, but if it's not locked in 15 secs you probably don't have a-GPS or haven't locked before, meaning the next timeout is the full GPS cycle of 90 seconds plus in perfect conditions, 4-5 minutes under less than ideal. It's a bit on the large side?
Yes, 15 seconds is plenty with good reception, I "normally" get a fix within about 5 seconds (or as little as 3). But since my code does have a 15 second timeout (where it then reverts to the cell tower location), and I've found that, sometimes, I still get cell-towers (maybe when the phone is in my pocket or whatnot), clearly 15 seconds isn't quite enough.

I will probably be adding a third mode that is "Always use GPS", which has the same logic and timeouts, but simply will *never* use a cell location, simply not posting any update at all if it didn't get a "gps quality" fix within the timeout. Then you, as a user, have the choice suitable for your environment, i..e

- very urban (New York city-canyons and offices): Cell only
- medium (smaller city with some open spaces): Cell+GPS
- rural (nearly always good gps fixes): GPS only

Should be a trivial change.

/Z