Any ideas on how to average the fixes?. On Nov 1, 12:44 am, gjs <garyjamessi...@gmail.com> wrote: > Hi, > > I think you will find getAccuracy() will continue to vary within the > 10 metres range or more. And you will not know which is 'most > accurate' without averaging the fixes over some period of time. All of > which is harder if the device is also moving. > > Regards > > On Nov 1, 5:44 am, Ab Caballero <a...@mac.com> wrote: > > > > > That's what i did by using if(hasAccuraacy() && getAccuracy() < > > minDistance)... > > It just doesn't seems to limit the fixes enough > > > On Oct 29, 6:01 am, lbendlin <l...@bendlin.us> wrote: > > > > yes. write your own logic to accept fix events or not
-- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
