diff options
| author | Unsuk Jung <unsuk@google.com> | 2015-09-29 21:51:33 -0700 |
|---|---|---|
| committer | Unsuk Jung <unsuk@google.com> | 2015-10-06 07:55:36 +0000 |
| commit | d07f7af0e6639e49db3e481553e50f949185834f (patch) | |
| tree | d90e439225da19979c0f56816de052858ecf4a94 | |
| parent | e3689d075711af87b014239c8c43832c9e5c8f31 (diff) | |
| download | source.android.com-d07f7af0e6639e49db3e481553e50f949185834f.tar.gz | |
CDD: Require rotation vector when accel, gyro, magneto available
The rotation vector is now a requirement when a device
includes an accellerometer, a gyroscope sensor and a magentometer
sensor. The requirment has become MANDATORY now as the Android Open
Source project provides the rotation vector sensor implementation
when all 3 base sensors are correctly implemented in the Sensor HAL.
Accelerometer measurements requires at least 12bit resolution.
Bug: 18984395
Bug: 24376867
Change-Id: I6b742954506da72083ec6b1f22c473842e790f94
| -rw-r--r-- | src/compatibility/android-cdd.html | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/src/compatibility/android-cdd.html b/src/compatibility/android-cdd.html index 82781134..461d05ff 100644 --- a/src/compatibility/android-cdd.html +++ b/src/compatibility/android-cdd.html @@ -3333,7 +3333,7 @@ sensor. If a device implementation does include a 3-axis accelerometer, it:</p> Android APIs [<a href="http://developer.android.com/reference/android/hardware/SensorEvent.html">Resources, 74</a>].</li> <li>MUST be capable of measuring from freefall up to four times the gravity (4g) or more on any axis.</li> - <li>MUST have a resolution of at least 8-bits and SHOULD have a resolution of at + <li>MUST have a resolution of at least 12-bits and SHOULD have a resolution of at least 16-bits.</li> <li>SHOULD be calibrated while in use if the characteristics changes over the life cycle and compensated, and preserve the compensation parameters between device @@ -3352,7 +3352,7 @@ dynamic or static condition.</li> TYPE_LINEAR_ACCELERATION composite sensors and SHOULD implement the TYPE_GAME_ROTATION_VECTOR composite sensor. Existing and new Android devices are STRONGLY RECOMMENDED to implement the TYPE_GAME_ROTATION_VECTOR sensor.</li> - <li>SHOULD implement a TYPE_ROTATION_VECTOR composite sensor, if a gyroscope sensor + <li>MUST implement a TYPE_ROTATION_VECTOR composite sensor, if a gyroscope sensor and a magnetometer sensor is also included.</li> </ul> @@ -3385,7 +3385,7 @@ while in use or during the production of the device.</li> <li>SHOULD have a standard deviation, calculated on a per axis basis on samples collected over a period of at least 3 seconds at the fastest sampling rate, no greater than 0.5 µT.</li> - <li>SHOULD implement a TYPE_ROTATION_VECTOR composite sensor, if an accelerometer + <li>MUST implement a TYPE_ROTATION_VECTOR composite sensor, if an accelerometer sensor and a gyroscope sensor is also included.</li> <li>MAY implement the TYPE_GEOMAGNETIC_ROTATION_VECTOR sensor if an accelerometer sensor is also implemented. However if implemented, it MUST consume less than @@ -3424,7 +3424,7 @@ parameters between device reboots.</li> or rad^2 / s). The variance is allowed to vary with the sampling rate, but must be constrained by this value. In other words, if you measure the variance of the gyro at 1 Hz sampling rate it should be no greater than 1e-7 rad^2/s^2.</li> - <li>SHOULD implement a TYPE_ROTATION_VECTOR composite sensor, if an accelerometer + <li>MUST implement a TYPE_ROTATION_VECTOR composite sensor, if an accelerometer sensor and a magnetometer sensor is also included.</li> <li>If an accelerometer sensor is included, MUST implement the TYPE_GRAVITY and TYPE_LINEAR_ACCELERATION composite sensors and SHOULD implement the |