Hi jgostylo,
On 07/15/2010 07:01 AM, jgostylo wrote:
All of this and people have only sort of answered my question. I
understand that the answer may just be I don't really know what it
would do and I understand that really isn't an answer people post on
the forum because it does not fill the
drpickett:
When I say I demand a certain accuracy from the GPS what I mean is
that when it reports a location I call getAccuracy and if it is not
good enough I throw away the result. Maybe I should just be more
lenient on the accuracy from a network location.
All of this and people have only
-- When it tells me my location is hundreds of miles from where I actually
am, will the call
-- to getAccuracy return hundreds of thousands of meters?
With my experience, sometimes I got a accuracy
of 10M, actually 100m away from where I was.
On Thu, Jul 15, 2010 at 1:01 PM, jgostylo
Hi! Could you provide some sample code for verifying which they are
getting results from (gps vs. Network)?
Thanks so much!
On Jul 10, 11:07 am, jgostylo jgost...@gmail.com wrote:
In answer to some questions. I am setting up the network location
finder and theGPSlocation finder using 2
Maybe I
can be choosy and say that if it GPS then I demand 20 meter accuracy
but if it is network then I only demand 500 meter???
Chuck Norris can demand a certain accuracy from GPS - You can't -
GPS reports its accuracy to you - It is a function of the number of
satellites in view, and other
2) in the backend applcation - Trains travel on tracks (hopefully) so
ignore all GPS positions that we cannot map on to a track.
Oh I'm highly jealous, wish I could filter on tracks as well.
Pent
--
You received this message because you are subscribed to the Google
Groups Android
Get enough data sets and you know where the tracks are :)
On Jul 10, 12:15 pm, Pent lee.wil...@googlemail.com wrote:
2) in the backend applcation - Trains travel on tracks (hopefully) so
ignore all GPS positions that we cannot map on to a track.
Oh I'm highly jealous, wish I could
That was my thought. Unless location provider registration is managed
through the variety of app lifecycle state changes, it is easy to put
an app in a state where it acquires the device location using Network
based location providers, even though the user selected GPS and
unselected everything
You can manage the orientation changes yourself and eliminate this
source of device confusion, it's quite easy, just add
android:configChanges=orientation to your manifest's activity.
As for the signal source, just make sure to check your provider for
gps - if it says gps, it will be from that
In answer to some questions. I am setting up the network location
finder and the GPS location finder using 2 separate
LocationListeners. I have some logic that determines what the user
has activated so I only listen to gps if the have gps enabled and so
forth.
From my user feedback it seems
I have had the same reports from my user community within my GPS
application for Android.
In my support emails I have been telling them that it is most likely a
hardware/OS issue, and a hard reset (battery pull) should fix it. I
have had a few users reply back and said that has fixed it.
I
Question: How are you getting your location fix? Are you using
ACCURACY_FINE and assuming it will use the GPS? Unless you
specifically test for the provider being GPS, it might default to
network, which would give you a position with limited accuracy. I've
seen this bouncing around effect when the
A GPS fix can be inaccurate - no matter how confident the GPS
device is :)
My experience here is from GPS units mounted on multiple trains
travelling about the UK, recording their position every few seconds.
A small percentage of the values we recieved from the GPS units were
completly
13 matches
Mail list logo
