John- Great idea you got there! One question: so you say you're killing the Listener that "loses", correct? So that means if the COARSE location wins, you kill the FINE listener and therefore never receive the GPS coordinates even when a fix can be obtained... This isn't the best option for my app as it is important to eventually receive the GPS location [so I can accurately calculate geographic distances from the user] if the user does have GPS enabled [if they don't, Network will have to do... And in the case no provider is enabled I tell the user to go enable one and give them a button to go to the Location pref pane.]...
So I suppose I will want to have the two LocationListeners running side-by-side and I'll use whatever Location comes first, whether it be COARSE or FINE, and if it is COARSE that I received I will keep both Listeners running until the FINE location fix is obtained at which point I will kill the COARSE Listener and switch over to only GPS coordinates. Does this sound right? I'll tackle this over the next few days.. If anyone has any pointers regarding my idea, that'd be great! Thanks so much to all who have helped so far! -Nick On Apr 1, 12:40 pm, "Maps.Huge.Info (Maps API Guru)" <[email protected]> wrote: > The method I use, which seems fairly effective, is to start two > listeners, one for coarse and one for fine and let them both try and > get a position. The first one to get it, "wins." One of my apps > continues to report location updates to move a location pin on a map, > as far as I can tell, it is just as fast as the Google map. > > -John Coryat > > "Radar Now!" -- 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.
