Dramatic shift in location accuracy distribution starting February 15

Question

I am trying to make sense of an inexplicable situation — starting February 15, a remarkably high percentage of the location readings we captured in our app are reporting exactly 10.0m accuracy, which seems strongly correlated with those arriving from a GPS source, as we see it almost exclusively with High-Accuracy and Sensor-Only mode (though there have been occasions where Battery Saving).

After reviewing our system, we don't see any point where we could be introducing this ourselves. It affects all deployed versions of our app.

We have begun to instrument our application to get more metadata, but would love to have a better understanding of how something like this could happen approximately instantaneously, which affected multiple versions of the app at a time when we did not change any running services.

Here area a few potentially-related issues:

• navigator.geolocation.getCurrentPosition in cordova gives only 10 meter accuracy
• FusedLocationApi Performance Issue: Accuracy seems capped at 10.0 meters
• Wierd and very unexpected issue with location.getAccuracy()
• Why does FusedLocationProviderApi never report accuracy better than 10m? Is this documented?
• Cordova geolocation accuracy gets capped at 10 meters

And some graphs to show what we are seeing:

So — has anyone else seen anything similar, or have an explanation as to what might be going on here?

Answer 1

it is a Google Play Service issue, reported internally here and it will be fixed from version 13.4.0