[
https://issues.apache.org/jira/browse/CB-13241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16168625#comment-16168625
]
Filip Maj commented on CB-13241:
--------------------------------
OK, so I tried to reproduce this but could not on an Galaxy S7 Edge (model
SM-G9350) running Android 7.0.
I created a cordova project using cordova-cli@7, added [email protected]
and [email protected] to it, and used a slightly modified
standard cordova project (the app's [app.js replacement is available in a gist
if you want to take a
look|https://gist.github.com/filmaj/89a30995504952dabd686d5fd79e96e5]) to test
out two calls to {{getCurrentPosition}} using the options provided by
[~frontendphil].
On the S7 I mentioned above, after installing, the app would immediately ask me
for permission to use Geo. I accepted. I would then get two "geo success"
calls. I'm testing this in an open area where GPS tracking should not be an
issue.
> Potential issue with geolocation when device is set to GPS only
> ---------------------------------------------------------------
>
> Key: CB-13241
> URL: https://issues.apache.org/jira/browse/CB-13241
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-android, cordova-plugin-geolocation
> Environment: Reproducible by me on: Samsung Galaxy S5 when phone
> location settings are set to GPS only.
> Error reporting has logged the issue on (based on most first):
> Samsung Galaxy S7 (international and European version)
> Samsung Galaxy S6 (SM-G920F)
> Samsung Galaxy A5 2017 (SM-A520F)
> Samsung Galaxy S8 (SM-G950F)
> [etc....]
> The top 15 devices are Samsung with the exception of the Sony Xperia XA
> (F3111).
> There are other devices on the list but they happen a handful of times so
> could be false positives or users have poor reception for example.
> Of note: Google Pixel and Pixel XL does not appear in the list of devices. I
> am also unable to reproduce the issue on Nexus 5X.
> Reporter: Phil Lennon
> Assignee: Filip Maj
>
> Pinging [~filmaj] who asked to be assigned this.
> My app uses the Geolocation getCurrentPosition() function on both IOS and
> Android. I have had an estimated 1.6k Android users unable to get a location
> with a timeout error code 3. There are no problems on IOS.
> I first try to get location with the following settings:
> this.geolocationOptionsFirst = {
> enableHighAccuracy: true,
> maximumAge: 300000,
> timeout: 10000
> }
> if that fails I then try again with the following settings:
> this.geolocationOptionsSecond = {
> enableHighAccuracy: false,
> maximumAge: 300000,
> timeout: 6000
> }
> The app is failing with a timeout after 16 seconds in total. My testing has
> made me believe it's something to do with setting phone location settings to
> GPS only. Please see environment for affected devices.
> Happy to provide more information if needed. I am available on the
> cordova-android Slack channel as frontendphil.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
