Sorry, one last thing. Getting an incorrect location is just as bad a not getting a location for me. That is why I am not currently considering getLastKnownLocation. If I am mistaken about the usefulness of getLastKnownLocation that would also be helpful.
If the user was on the North side of town when the last location was given to him and he travels to the South part of town and starts the app I do not want the app to tell him he is on the North side of town while the app is waiting 30-40 seconds to get a location. -- 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.
