Many phones get this wrong (and HTML5 implementations too). Android's documentation on getOrientation from a rotation matrix is also incomplete and ambiuguous, and there own implementation doesn't seem to follow what they document. I believe this is a poor attempt to cover there gaffe of using left-handed conventions in their deprecated ORIENTATION sensor. Here is a good blog on the topic that may be helpful: http://www.sensorplatforms.com/understanding-orientation-conventions-mobile-platforms/
On Sunday, October 4, 2009 5:57:30 AM UTC-7, DD wrote: > > Hi, > > It seems that for onSensorChanged(), the orientation readings > (yaw,pitch,roll) are not detected directly, but computed from the > acceleration readings. Does anybody know how they do this calculation? > is it by rotationmatrix..? May I know exactly the calculation process? > > Thanks! -- -- 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 --- You received this message because you are subscribed to the Google Groups "Android Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
