[
https://issues.apache.org/jira/browse/CB-3023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13629558#comment-13629558
]
Joe Bowser edited comment on CB-3023 at 4/11/13 11:24 PM:
----------------------------------------------------------
Based on what you're telling me, this is the built in geolocation on the
device.
Unfortunately, the HTML5 geolocation spec isn't as robust as some Android
geolocation implementations that will use a combination of Cell Signal, GPS as
well as WiFi coverage to triangulate a position. useHighAccuracy only uses the
GPS, and doesn't use whatever is available, which may be why your Geolocation
is taking forever for onSuccess to be called. I recommend not using high
accuracy if you want to have a position right away if accuracy isn't as big of
an issue.
was (Author: bowserj):
Based on the responses, this is the built in geolocation on the device.
Unfortunately, the HTML5 geolocation spec isn't as robust as some Android
geolocation implementations that will use a combination of Cell Signal, GPS as
well as WiFi coverage to triangulate a position. useHighAccuracy only uses the
GPS, and doesn't use whatever is available, which may be why your Geolocation
is taking forever for onSuccess to be called. I recommend not using high
accuracy if you want to have a position right away if accuracy isn't as big of
an issue.
> Geolocation API does not work on Motorola Xoom tablet (and perhaps/probably
> other devices)
> ------------------------------------------------------------------------------------------
>
> Key: CB-3023
> URL: https://issues.apache.org/jira/browse/CB-3023
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
> Affects Versions: 2.3.0, 2.4.0, 2.5.0
> Environment: Mac OS X 10.8.3, Eclipse 4.2.1, Cordova 2.5.0, Motorola
> Xoom tablet running Android v4.1.2
> Reporter: Jack Piccininni
> Assignee: Joe Bowser
> Priority: Minor
> Labels: Geolocation, Xoom,
>
> In a nutshell: the Geolocation API does not work on the Xoom tablet. The
> "success" callback never gets called after getCurrentPosition() or
> watchPosition().
> More details... Neither the:
> - navigator.geolocation.getCurrentPosition(onSuccess, onError, { maximumAge:
> 2000, timeout: 5000, enableHighAccuracy: true }) nor
> - navigator.geolocation.watchPosition(onSuccess, onError, { maximumAge: 2000,
> timeout: 5000, enableHighAccuracy: true })
> methods result in the "onSuccess" callback being called.
> Without the optional options ("{ maximumAge: 2000, timeout: 5000,
> enableHighAccuracy: true }") included in the methods, the "onError" callback
> never (unless the default timeout is several minutes, if there is a default)
> gets called either. With the options included, it does, and the timeout error
> (error.message = "Timeout expired") is generated. Only the onError callback
> gets called, never the onSuccess callback, when running on the Xoom.
> Tested on other devices (Droid3 and iPhone) and these methods work (though
> watchPosition is slow on Droid3, another bug). Manifest and inspection of
> permissions look correct. Xoom is able to show its location using other apps
> like Google Maps.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
