Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 9E930200D04 for ; Mon, 11 Sep 2017 23:57:06 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 9D4FB1609C4; Mon, 11 Sep 2017 21:57:06 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id D38A31609B7 for ; Mon, 11 Sep 2017 23:57:05 +0200 (CEST) Received: (qmail 42193 invoked by uid 500); 11 Sep 2017 21:57:04 -0000 Mailing-List: contact issues-help@cordova.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@cordova.apache.org Received: (qmail 42096 invoked by uid 99); 11 Sep 2017 21:57:04 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Sep 2017 21:57:04 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id CEA9AD2B20 for ; Mon, 11 Sep 2017 21:57:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id QvnHcW582jQc for ; Mon, 11 Sep 2017 21:57:02 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 3A5855FE16 for ; Mon, 11 Sep 2017 21:57:02 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id A165BE0E3F for ; Mon, 11 Sep 2017 21:57:01 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 3015A2415D for ; Mon, 11 Sep 2017 21:57:01 +0000 (UTC) Date: Mon, 11 Sep 2017 21:57:01 +0000 (UTC) From: "Joe Bowser (JIRA)" To: issues@cordova.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CB-13241) Potential issue with geolocation when device is set to GPS only MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 11 Sep 2017 21:57:06 -0000 [ https://issues.apache.org/jira/browse/CB-13241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16162095#comment-16162095 ] Joe Bowser commented on CB-13241: --------------------------------- [~jcesarmobile] Who are you addressing that question to? I don't remember saying this. > 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