breautek commented on issue #273: URL: https://github.com/apache/cordova-plugin-geolocation/issues/273#issuecomment-1944391811
> enableHighAccuracy:true this does not fix the issue Can you confirm your device location settings? Settings -> Location -> Location Services ![Screenshot from 2024-02-14 14-33-14](https://github.com/apache/cordova-plugin-geolocation/assets/11200662/b7ba7572-5d7a-4ec1-9ecb-65a0d85e9616) Google Location Accuracy should be enabled, otherwise high accuracy / FINE location will not work. Additionally, the app permission should have Precise enabled: Settings -> Location -> App location permissions -> Your Application ![Screenshot from 2024-02-14 14-35-08](https://github.com/apache/cordova-plugin-geolocation/assets/11200662/7dc6a609-26e3-40fb-a6df-03673c89fa4b) Ensure location access is enabled with precise location. If either `precise location` or `Google Location Accuracy` is disabled, then regardless of the app requesting high accuracy the device will only return COARSE location which will be a victim of the aforementioned android 12 bug. The app permissions will be set by the user on the first time they use your app, but it's possible they disallow precise permission on the permission prompt which will trigger the android 12 bug. Google Location Accuracy is a user setting that can't be programmatically controlled, the user must enable it to enable high accuracy location. Usually it's enabled by default from factory. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org