Mailing-List: contact callback-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: callback-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of fil@adobe.com designates
 64.18.1.23 as permitted sender)
From: Filip Maj <fil@adobe.com>
To: "callback-dev@incubator.apache.org" <callback-dev@incubator.apache.org>
Date: Thu, 15 Mar 2012 16:43:58 -0700
Subject: Re: Normalization of acceleration values
Thread-Topic: Normalization of acceleration values
Thread-Index: Ac0DBYANAWSbW0G9SOiT8y8XzXPyRQ==
Message-ID: <CB87CB76.20BC%fil@adobe.com>
In-Reply-To: 
 <CADVgkyMrU+73aMyPooSMrmH613gzaEgEy=vXQxS_Upm9r4fe9A@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/14.14.0.111121
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Hey all,

I'm bringing this one back up :)

https://issues.apache.org/jira/browse/CB-152


I am leaning towards going with the spec Jesse linked to [1] and having
all the platforms roll with units expressed as m/s^2.

>From a conversation I just had with Jesse this issue just came up in WP7
as well.

I will do some testing on my iPod + android and see what the different
return values are currently. I'll try to consolidate. We will have to
update docs for this as well!

[1] http://dev.w3.org/geo/api/spec-source-orientation.html#devicemotion

On 2/8/12 3:54 PM, "Brian LeRoux" <b@brian.io> wrote:

>rather than a vote thread I'm thinking we continue to treat W3C
>recommendation 'the right way' to do stuff
>
>(I realize that in itself is debatable!!!)
>
>On Tue, Feb 7, 2012 at 7:48 AM, Simon MacDonald
><simon.macdonald@gmail.com> wrote:
>> It seems to be on Android that it is returning the value in m/s*s. When
>>my
>> device is resting on the desk the x and y values are close to 0 while
>>the z
>> is close to 9.8. Depending on what Android device you have your
>> accelerometer may be more accurate or able to go up to a higher level
>>of g.
>> So, it looks like if we want to standardize on g as the unit to be
>>returned
>> for the accelerometer I'll need to divide by 9.81.
>>
>> Also, can someone else run the MobileSpec code and go into Accelerometer
>> and do a Start Watch while leaving your phone flat on the desk? I want
>>to
>> make sure that other devices don't correct for gravity as I only have
>> Samsung devices here.
>>
>> Simon Mac Donald
>> http://hi.im/simonmacdonald
>>
>>
>> On Tue, Feb 7, 2012 at 3:36 AM, Filip Maj <fil@adobe.com> wrote:
>>
>>> Let's decide, please. A vote thread?
>>>
>>> My vote is using what the W3C spec [1] suggests, which, as Jesse points
>>> out in the JIRA issue, seems to be m/s^2.
>>>
>>> My problem looking at this a few weeks ago was figuring out what the
>>> reference point/units on the various native platforms was (I.e. What is
>>> -10 / +10 on Android? What is -1000 / +1000 on Blackberry? What are
>>>those
>>> units?). It's not very well documented :s
>>>
>>> On 12-02-07 3:00 AM, "gtanner@gmail.com" <gtanner@gmail.com> wrote:
>>>
>>> >Also to note that I think the values on BlackBerry are -1000 to +1000.
>>> >
>>> >Dan was noticing this last week while working on an app
>>> >------Original Message------
>>> >From: Shazron
>>> >To: callback-dev@incubator.apache.org
>>> >ReplyTo: callback-dev@incubator.apache.org
>>> >Subject: Normalization of acceleration values
>>> >Sent: Feb 6, 2012 8:57 PM
>>> >
>>> >https://issues.apache.org/jira/browse/CB-152
>>> >
>>> >Should we decide?
>>> >
>>> >Sent on the TELUS Mobility network with BlackBerry
>>>
>>>