GPSLogger seems to be generally less accurate than other apps
I have what I think are somewhat permissive options set in performance:
- Logging GPS, network and passive
- logging every 180s
- distance 5m
- accuracy 50m
- duration to match accuracy 60s
- choose best accuracy in duration true
- absolute time to gps fix 120s
And yet I struggle to have any locations logged. According to the log most updates are accurate to over 60+m.
However when I turn on other GPS apps (most vacuously GPSTest), GPSLogger is wonderfully accurate and efficient.
It's almost as if GPSLogger doesn't give itself a chance to heat up. Obviously I don't want to keep GPS on all the time only to be used so infrequently, but would expect it to strive to get a solid location to log at least once every 3 minutes. At the moment it seems like the best strategy is to just log passive requests and to open GPSTest every 3 minutes!
Some sample profiles suited to general usecases might help here.
Yes that does look pretty permissive and you've got the duration to match accuracy in there as well. This indicates that the main GPS listener and network listener aren't getting a good accurate point at all even after repeatedly trying for 60 seconds. That's definitely unusual and not something I've seen before, even the default settings has worked for me on all the testing I've done.
What happens if you just keep GPS on and nothing else - does it still struggle to find anything, does it show it's able to find any satellites?
I took a walk this morning with network and passive off.
Results were good, every three minutes it gets a 20+ satellite lock within 4 seconds or so, averaging 10-20m accuracy, so I was even able to reduce the accuracy filter to 40m.
Indoors results in lots of skips due to poor accuracy, and I suspect that's why I increased it - and then added network since I was living with poor accuracy anyway. I guess the trick here then is to live with fewer logs indoors. In that sense duration to match accuracy should have been the first thing for me to try before increasing accuracy or location sources. At this point even passive logging isn't needed (although now that logs are reliable I may increase the interval and reintroduce it).
I'll monitor it going forward but it looks promising enough for me to think about the next steps (adjusting the interval based on activity). Thanks for the app and attention!