[
https://issues.apache.org/jira/browse/RIPPLE-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomsz Trejderowski updated RIPPLE-38:
-------------------------------------
Environment: Windows 7 Home Edition, x86, Chrome browser (newest stable
version), Ripple Emulator extension for Chrome (newest stable version taken
from Chrome Store).
> CompassHeading.headingAccuracy is incorrect under Windows for Cordova/Android
> platform
> --------------------------------------------------------------------------------------
>
> Key: RIPPLE-38
> URL: https://issues.apache.org/jira/browse/RIPPLE-38
> Project: Apache Ripple
> Issue Type: Bug
> Environment: Windows 7 Home Edition, x86, Chrome browser (newest
> stable version), Ripple Emulator extension for Chrome (newest stable version
> taken from Chrome Store).
> Reporter: Tomsz Trejderowski
> Priority: Trivial
>
> According to PhoneGap API / CompassHeading object description:
> http://docs.phonegap.com/en/2.9.0/cordova_compass_compass.md.html#compassHeading
> CompassHeading.headingAccuracy is the deviation in degrees between the
> reported heading and the true heading. And there is an Android Quirk below,
> that says that trueHeading is not supported, but reports the same value as
> magneticHeading and headingAccuracy is always 0 because there is no
> difference between the magneticHeading and trueHeading.
> However, when running compass using application in Ripple emulator with
> Cordova / Android / Samsung Nexus platform, CompassHeading.headingAccuracy is
> always = 100.
> This is incorrect. CompassHeading.trueHeading is equal to
> CompassHeading.magneticHeading under Ripple (correct), so
> CompassHeading.headingAccuracy must return 0.
--
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
