That was my thought. Unless location provider registration is managed through the variety of app lifecycle state changes, it is easy to put an app in a state where it acquires the device location using Network based location providers, even though the user selected GPS and unselected everything else (Namely, "Use wireless networks:). The downside of unregistering and registering location providers with every lifecycle state change (i.e. in onPause(), onResume() and so forth) is when users manically switch device orientation back and forth. This leads to a series of lifecycle breakdown and restart calls that seem to have the potential of getting Android location provider registration "confused". If you haven't done already, I'd recommend to experiment with this for a few hours to get a feel how it all plays out in relation to your apps.
On Jul 9, 7:50 am, "Maps.Huge.Info (Maps API Guru)" <[email protected]> wrote: > Question: How are you getting your location fix? Are you using > "ACCURACY_FINE" and assuming it will use the GPS? Unless you > specifically test for the provider being GPS, it might default to > network, which would give you a position with limited accuracy. I've > seen this bouncing around effect when the wireless location (network) > provider is trying to figure out where the device is, as it zeros in > on the location, it can hop all over the map. > > Bottom line: Don't assume that ACCURACY_FINE will be GPS, unless you > have GPS satellites in view and the user has enabled GPS, you'll be > using the network location service instead. > > -John Coryat -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
