Issue metadata
Sign in to add a comment
|
Geolocation accuracy limited to >= 10m |
||||||||||||||||||||
Issue descriptionChrome Version: 67.0.3396.87 OS: Android What steps will reproduce the problem? (1) Visit https://reillyeon.github.io/scraps/watch-position.html. (2) Watch accuracy as the device acquires a GPS lock. What is the expected result? With a clear view of the sky accuracy should be able to reach <10m. What happens instead? Accuracy is capped at 10m. This issue is not reproducible with Firefox for Android. It is not yet known when this regression occurred.
,
Jun 27 2018
I can repro this on an Android device with Chrome 67.0.3396.87. I have Android 8.1.0 with Google Play Services 12.6.5 (090400-197041431). If I start with Android's Location option set to "ON / High accuracy" then it reports an accuracy around 12-13m. If I change this to "ON / Device only" then the accuracy jumps to 3m. Accuracy should not be worse in High Accuracy mode! The GmsCore API we are using is deprecated (FusedLocationProviderApi). We should investigate switching to the newer FusedLocationProviderClient. Firefox uses the Android location API, not the GmsCore location API, so if the issue is in GmsCore it makes sense that it would not repro in Firefox.
,
Jun 28 2018
hi, I originally reported this to Reilly. I think this is high priority as people (such as me) using Cordova for building hybrid apps have exactly the same issue as Cordova directly delegates the geolocation API on Android to the underlying webview, which is Chrome. @mattreynolds I tried with Reilly's link and switching to device only jumps to an accuracy below 10m, but only like for a couple of secs, then stabilizes again around 10m and doesn't drop any more. Also tested this on Chrome Beta (for Android) v68.0.3440.33 Reproduced on the following devices: ------------------------------------- - Samsung, Android 5.1.1, Chrome 67.0.3396.87, Google Play Services 12.6.85 (020306-197041431) - Google Pixel 2, Android 8.1.0, Chrome 67.0.3396.87, Google Play Services 12.6.85 (0900400-197041431) - Nokia Android One, Android 8.1.0, Chrome 67.0.3396.87, Google Play Services 12.6.85 (040400-197041431) Timeline: ---------- Our clients started to report issues with geolocation accuracy since last week, but there are Stackoverflow posts that date back to February: https://stackoverflow.com/questions/48925394/navigator-geolocation-getcurrentposition-in-cordova-gives-only-10-meter-accuracy
,
Jun 28 2018
It looks like this issue has been reported to the Android team and they are investigating: https://issuetracker.google.com/issues/79189573
,
Jun 28 2018
@Reilly True, but seems like there's no update over there 😉. Have seen that issue before.
,
Oct 1
This issue will be resolved in Google Play Services version 13.4.0. Closing this issue as there is no further action to be taken on Chromium's part. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by reillyg@chromium.org
, Jun 27 2018Owner: mattreynolds@chromium.org
Status: Assigned (was: Untriaged)