Why Does Fusedlocationproviderapi Never Report Accuracy Better Than 10m? Is This Documented?

A data collection app that used LocationManager directly was updated to use FusedLocationProviderApi. With LocationManager, most devices quickly report 5m accuracy or better when c

Solution 1:

No. It is best effort only. No guarantee.

If you have a good devices, and in a location which has large number of Android user. (which for example, SSID database will become more accurate), it can go to 2-3m accuracy.

Otherwise, mixing location information from different source will have a larger variance, and result as lower accuracy.

e.g. Source A accuracy is 5m. Source B accuracy is 15m.

Using Source A alone of course accuracy is 5m. But if mixed A and B, the accuracy of course will be >= 5m. (consider adding noise to clean data)

Solution 2:

This was confirmed as a Google Play Services bug on the Google issue tracker. A fix that allows accuracies down to 3m is projected for Play Services 13.4.0. It's unclear why it will be capped at 3m rather than using the accuracy reported by the raw location source.