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+
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 wrote:
> yes. write your own logic to accept fix events or not
--
You received this message because you are subscribed to the Google
Group
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 wro
Any ideas on how to average the fixes?.
On Nov 1, 12:44 am, gjs 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
thanks
On Nov 1, 1:21 pm, Kristopher Micinski wrote:
> http://code.google.com/p/gps-averaging/
>
>
>
> On Tue, Nov 1, 2011 at 4:11 PM, Ab Caballero wrote:
> > Any ideas on how to average the fixes?.
>
> > On Nov 1, 12:44 am, gjs wrote:
> > > Hi,
>
> > > I think you will find getAccuracy() will
http://code.google.com/p/gps-averaging/
On Tue, Nov 1, 2011 at 4:11 PM, Ab Caballero wrote:
> Any ideas on how to average the fixes?.
>
> On Nov 1, 12:44 am, gjs wrote:
> > Hi,
> >
> > I think you will find getAccuracy() will continue to vary within the
> > 10 metres range or more. And you wi
6 matches
Mail list logo
