I inserted a Log.d() in the ApiDemos/OS/Sensors application to confirm that the sensor data is inverted (not just the display of it) from SDK 2.2 to SDK 2.3. The orientation of the sensor data is correct in SDK 2.3 (i.e., +1 g of acceleration in the z direction due to the force from the table), but does anyone know why a SDK 2.2 application running on a SDK 2.3 device would cause the change in sensor orientation?
By the way, kudos to ST MicroElectronics, Samsung, and Google on the choice and implementation of the gyroscope sensor: its output is impressively pristine. On Dec 24, 5:02 pm, greg <[email protected]> wrote: > The following test was with Nexus S lying flat on table with display > up. > > When running the ApiDemos/Sensor application in SDK 2.2, the red and > green lines (i.e., x-axis accelerometer and y-axis accelerometer, > respectively) are at the 0 g axis and the blue line (i.e., z-axis > accelerometer) is at the -1 g axis. However, when running the > ApiDemos Sensor application in SDK 2.2, the blue line is at the +1 g > axis. Looking at Sensor.java, it appears to me that the application's > scaling is the same. Looking through the documented API differences, > I didn't see any mention of sensor orientation change. Yet, the > screen y-axis appears in the ApiDemos/Sensor applications in SDK 2.2 > and SDK 2.3 are inverted. What changed? > > - Greg -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
