I believe that you'll have to lower the time and keep GPS on all time. There are also great differences in hardware; for example, I am doing a gps fix every 60 seconds, and having different accuracy values on a Samsung Galaxy Note and a ZTE china something. Surprisingly, the average values for the ZTE are under 18m and the Galaxy Note around 30m. If I keep the GPS on all the time, values improve (ZTE is still better, again, surprisingly).
On 24 August 2012 14:36, Domanet <doma...@mail.com> wrote: > Thanks. > > My problems is that I’m doing that already but with 20 seconds and it keeps > returning about 64 feet. > > I guess my only choice is to lower the time and keep the GPS on all the > time. > > If a call .RequestLocationUpdates more than once is that a problem? > > Can I call .RequestLocationUpdates with 5 seconds and then change to 20 > once > I get the accuracy I need and then go back to 5 seconds again if the > accuracy gets higher? > > Once the GPS has a good fix it tends to keep it for a while. > > Do you have an example of GPS in a background thread? > > I’ve seen examples using a thread and a looper but have been unable to > convert. > > > > > -- > View this message in context: > http://mono-for-android.1047100.n5.nabble.com/GPS-tp5711530p5711533.html > Sent from the Mono for Android mailing list archive at Nabble.com. > _______________________________________________ > Monodroid mailing list > Monodroid@lists.ximian.com > > UNSUBSCRIBE INFORMATION: > http://lists.ximian.com/mailman/listinfo/monodroid > -- Gonçalo Oliveira
_______________________________________________ Monodroid mailing list Monodroid@lists.ximian.com UNSUBSCRIBE INFORMATION: http://lists.ximian.com/mailman/listinfo/monodroid
