cordova-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Phil Lennon (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CB-13241) Potential issue with geolocation when device is set to GPS only
Date Wed, 06 Sep 2017 09:32:00 GMT

    [ https://issues.apache.org/jira/browse/CB-13241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16155079#comment-16155079
] 

Phil Lennon commented on CB-13241:
----------------------------------

Hi [~bowserj],

Thanks for the prompt response. If Cordova isn't responsible for this functionality then I
can definitely work around it with UX changes (eg checking for location options and asking
user for high accuracy enabled. 

My thoughts on this was that it was strange that I can't reproduce this on Pixel/Nexus hardware
and 14 out of 15 top devices are Samsung. Does this suggest that the Samsung GPS chips are
slower to get a location? It's worth pointing out however that Samsung could be at the top
purely because of market share.

> 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: issues-unsubscribe@cordova.apache.org
For additional commands, e-mail: issues-help@cordova.apache.org


Mime
View raw message