IssueTracker

2. I want to use my phone in an autonomous vehicle that requires Orientation and Linear Acceleration. The implementation exists to give me both but one has been sodomised. The Orientation Sensor (Deprecated) documentation suggests that there are artificial limits on the angles, -180<=pitch<=180 and -90<=roll<=90. From testing, not only is it true, but the response is even worse than documented, roll 90 rapidly turns into 180 on the pitch and then gets completely crazy.

Solution: Remove retarded sensor data limits. Somewhere in the background it works anyways considering that the extraction of the Gravity Vector works very well. This output specification requires manufacturer developers to output bad data.

Please primarily output good data. Please output normal Roll Pitch Yaw.

The Rotation Vectors are also plagued by this issue as it is inherited, and on all devices tested Rotation Vector gives Game Rotation Vector and so the Magnetometer and Gyroscope need to be fused again by the user because of this bad implementation.

3. https://source.android.com/docs/core/interaction/sensors/sensor-types#orientation_deprecated