Explain within client what each accuracy level means
Currently users cannot know what it means and it seems that changing accuracy to High solves significant portion of support requests.
My first interpretation of the "Location accuracy" setting was how many decimals should be included in the sent coordinates ;-) but in fact it affects also other reporting parameters (speed, direction...)
The old docs for android devs on 'User Location' seem to have vanished, in favour of the new Fused Location Provider (which needs Google Play Services): https://developer.android.com/training/location/
If I'm not mistaken - and I have not seen any hints of using FLP in Antons code - in Traccar-client the original Android framework APIs are being used: https://developer.android.com/reference/android/location/package-summary (and that's it, you have to dig through the left docs, any other tutorials are not visible there anymore).
High = GPS_PROVIDER, accuracy 0 - 50 meters (depending on hardware) Medium = NETWORK_PROVIDER, accuracy 100 - 1000 meters Low = PASSIVE_PROVIDER, accuracy and position depend on last acquired position of any App on your phone
@stefanb maybe intended to ask that the Traccar-Frontend (which happens to be a PreferenceFragment) should be (or might be) more informative:
- tell the meaning of an item
- tell the status/content of an item
Yes, user has no idea what the settings mean. He might know that it affects the meter accuracy, but there is no chance that user would know that the setting also affects the speed and direction, which are only present with the highest accuracy setting.
(I accidentally fat-finger closed the issue)
Is it accurate (hehe) to say that when Medium accuracy is set, that GPS High accuracy would be used if another app is using GPS? I notice LOW depends on the last acquired position of any App on your phone, I wonder if MEDIUM can also make use of other app's GPS requests?
TLDR: Does a phone running a map/driving app like Google Maps then allow a Traccar Client set to Medium to make use of the high precision GPS fix that the other app is using?
I don't think so, but Google doesn't really disclose those details in the documentation.