Bad accuracy with latest F-Droid client, "high" accuracy?

OverkillTASF6 years ago

For kicks, during a drive while my cell was plugged in, I cranked down the reporting interval to 5 seconds and set the accuracy to medium.

https://imgoat.com/uploads/1f491a404d/128278.png
I was driving East to Gretna, and then North on 29.

It seems that a lot of my location reports were sent from some poorly calculated points, all near each other and in a row.

https://imgoat.com/uploads/1f491a404d/128280.png
I thought, maybe my location provider services are all jacked up... But then I saw it was correctly reporting the inaccuracy of these points.

I also noticed that when I opened satstat or any other GPS app, it seemed like my phone had to wait a bit to get its fix; Given the low interval on my phone, I thought Traccar would keep the GPS on and fixed.

The area I was driving through would not have had much in the way of wifi from which to get a "medium" accuracy fix... so I'm assuming those badly reported points were based purely on a cell tower fix.

Curious why Traccar may not have been using GPS for this?

Anton Tananaev6 years ago

Even if GPS is always ON, it doesn't mean that it's always possible to get a valid location from it. For example, GPS doesn't work indoors. Tall buildings can also block signal.

OverkillTASF6 years ago

This was driving on a rural highway with mostly open fields. SatStat had a consistent fix, and even during that time that I had it open and was watching it, Traccar doesn't seem to have logged locations as expected.

I will try it again with an ADB Logcat running and see if something more interesting shows up.