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 <[email protected]> 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 <[email protected]> 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, "[email protected]" <[email protected]> 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: [email protected] >> >ReplyTo: [email protected] >> >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 >> >>
