Nick, In some apps, all I want is the first "fresh" location so as soon as I get one, I kill both listeners. Other apps, like the moving map one, continue to use both listeners and the one with the best accuracy takes the lead. What I do is keep a location object that starts out as null until the first fix, then the location with the best accuracy takes over the object.
As for saving a location, the problem is time dependent. If the user is in a car going 70 mph, the location "saved" (last known location) is stale in a matter of a minute or so. I've found the last known location is essentially worthless. I haven't looked into the power issue, perhaps someone else will chime in with that answer. -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 To unsubscribe, reply using "remove me" as the subject.
