Return-Path: X-Original-To: apmail-cordova-issues-archive@minotaur.apache.org Delivered-To: apmail-cordova-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id DCB9E1072A for ; Tue, 17 Dec 2013 12:09:42 +0000 (UTC) Received: (qmail 78758 invoked by uid 500); 17 Dec 2013 11:55:15 -0000 Delivered-To: apmail-cordova-issues-archive@cordova.apache.org Received: (qmail 78739 invoked by uid 500); 17 Dec 2013 11:55:11 -0000 Mailing-List: contact issues-help@cordova.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cordova.apache.org Delivered-To: mailing list issues@cordova.apache.org Received: (qmail 78730 invoked by uid 99); 17 Dec 2013 11:55:08 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 17 Dec 2013 11:55:08 +0000 Date: Tue, 17 Dec 2013 11:55:06 +0000 (UTC) From: "Clayton Grassick (JIRA)" To: issues@cordova.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (CB-5663) Geolocation minTime on Android is 60s, preventing realtime updates MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Clayton Grassick created CB-5663: ------------------------------------ Summary: Geolocation minTime on Android is 60s, preventing realtime updates Key: CB-5663 URL: https://issues.apache.org/jira/browse/CB-5663 Project: Apache Cordova Issue Type: Bug Components: Android Affects Versions: 3.3.0 Environment: Android 4.2, Intel Yolo phone Reporter: Clayton Grassick cordova-plugin-geolocation / src / android / GPSListener.java has the minTime parameter on the locationManager.requestLocationUpdates(LocationManager.GPS_PROVIDER, 60000, 0, this) set to 60 seconds. On Android platforms that respect that parameter, it means that the GPS location will only update every 60 seconds, making it less useful. I suggest changing it to 1000ms instead. -- This message was sent by Atlassian JIRA (v6.1.4#6159)