Yeah, after adopting your advice, I was able to find a good starting last known location from all providers, then spin up my listener to do the comparison, at which after 10 seconds, it kicked off my message thread to shut everything down and send the result back to my callback. It was close enough the returned location.
On Dec 22, 6:43 pm, TreKing <[email protected]> wrote: > On Thu, Dec 22, 2011 at 5:04 PM, Diego Tori > <[email protected]>wrote: > > > What I want to know is after I fetch the last known location as my > > initial best location and kick off my thread, how do I set up the > > coarse criteria so that I receive a more accurate one than the initial > > one (in order to compare the two), which is diametrically different > > from my current location? > > You're over-complicating this. Get that last known location - that's your > base, assuming it's not null. > Register a listener for new update using whatever criteria you need. > Immediately after, post your 10 second "stop" message. > If and when your listener is hit, save that as the best location. > When you stop message is called, remove the callback and use the last one > found. > > There's no need for this "every half second" stuff. > > ------------------------------------------------------------------------------------------------- > TreKing <http://sites.google.com/site/rezmobileapps/treking> - Chicago > transit tracking app for Android-powered devices -- 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
