cordova-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joe Bowser (JIRA)" <>
Subject [jira] [Resolved] (CB-9424) Speed is “null” with geolocation plugin on Android 5+
Date Fri, 07 Aug 2015 18:12:47 GMT


Joe Bowser resolved CB-9424.
    Resolution: Won't Fix

Cordova's Geolocation plugin only turns on Geolocation on the WebView, it does not provide
any additional functionality.  This is a problem with the Chromium implementation of Geolocation,
and is not something that we can fix.

I would recommend either upgrading your System WebView or using the Crosswalk engine and seeing
if that resolves your issue.

> Speed is “null” with geolocation plugin on Android 5+
> -----------------------------------------------------
>                 Key: CB-9424
>                 URL:
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: Android, Plugin Geolocation
>         Environment: Samsung Galaxy S4 (A5.0.1), Nexus 5 (A5.1.1), LG G3 Stylus D690
>            Reporter: Anton Trutnev
> “Speed” value is always “null” in Android 5+. We use these:
> •	Core: Cordova - 5.1.1
> •	Platform: Cordova-Android 4.0.2
> •	Plugin version: 1.0.1
> •	Devices: Samsung Galaxy S4 (A5.0.1), Nexus 5 (A5.1.1), LG G3 Stylus D690 (A5.0.2).
> After updating few of our test devices to Android 5, “Speed” value from the plugin
is always “null”. Works fine on Android 4 and iOS though. We tried both getCurrentPosition
and watchPosition – no luck. HighAccuracy is “true”.
> No matter what we try, we always receive speed as “null”. We had to implement workaround
for Android 5 using getCurrentPosition (instead of perfectly working watchPosition for other
OSes), which in many times results in calculating speed for some intervals as up to 400 km/h,
while calculating more or less accurate speed overall.
> Are there any permissions for Android 5 we are missing? What can we do to resolve this
issue? We’d like to use one code for all platforms as it should be, and keep using watchPosition
as it works good. Any suggestions? Is this a known issue?
> On a related note: are there any known bugs/issues for Cordova with Galaxy devices in
general? Thanks!

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message