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 think this may be a issue with the API that is is providing use the wrong information when we request it. In my eyes I see this as a bug with Android if it provides the wrong information once we request it. Justin On Jul 9, 8:48 am, jgostylo <jgost...@gmail.com> wrote: > This is a general question about GPS accuracy reporting based on > feedback from my user community. > > My app has an issue where many players get bounced all over kingdom > come when using GPS to get a signal. I had this issue with my G1 on > occasion but not on my Nexus One. I am talking hundreds of miles from > their real location. I changed the code to throw out anything that > was not at least 500 meters accurate. My question is, if the location > placement is hundreds of miles off, how reliable will the accuracy > reporting be? Does it realize that it could be hundreds of miles off? > > I am asking the community because I cannot reproduce the scenario with > what I currently have so I can't test if my fix is meaningful. Does > GPS know when its readings are that far off? -- 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
