You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cordova.apache.org by "Filip Maj (Updated) (JIRA)" <ji...@apache.org> on 2012/03/16 01:36:38 UTC

[jira] [Updated] (CB-152) Normalize Acceleration object x,y,z to return same range for all devices.

     [ https://issues.apache.org/jira/browse/CB-152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Filip Maj updated CB-152:
-------------------------

          Component/s:     (was: Android)
                           (was: iOS)
                       Docs
          Description: 
Acceleration object should be consistent across platforms.  Documentation mentions range of x,y,z to be 0-1, but Android returns ranges in -10 to +10.  This needs to be made consistent so the same code works on all platforms. 

Let's work towards using the DeviceMotion specification: returning values in m/s^2. At rest, with the screen pointing upwards, values should be x=0, y=0, z=9.81

Android uses the above by default. iOS: I have a commit coming (merge into master tomorrow).

Documentation needs updates for this.

  was:Acceleration object should be consistent across platforms.  Documentation mentions range of x,y,z to be 0-1, but Android returns ranges in -10 to +10.  This needs to be made consistent so the same code works on all platforms. 

    Affects Version/s: 1.5.0
        Fix Version/s: 1.6.0

Removed Android and iOS tags, added Docs.
                
> Normalize Acceleration object x,y,z to return same range for all devices.
> -------------------------------------------------------------------------
>
>                 Key: CB-152
>                 URL: https://issues.apache.org/jira/browse/CB-152
>             Project: Apache Callback
>          Issue Type: Bug
>          Components: BlackBerry, Docs, WP7
>    Affects Versions: 1.5.0
>            Reporter: Bryce Curtis
>            Assignee: Filip Maj
>             Fix For: 1.6.0
>
>
> Acceleration object should be consistent across platforms.  Documentation mentions range of x,y,z to be 0-1, but Android returns ranges in -10 to +10.  This needs to be made consistent so the same code works on all platforms. 
> Let's work towards using the DeviceMotion specification: returning values in m/s^2. At rest, with the screen pointing upwards, values should be x=0, y=0, z=9.81
> Android uses the above by default. iOS: I have a commit coming (merge into master tomorrow).
> Documentation needs updates for this.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira