You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At least on Android, the accuracy of an already-instantiated sensor can change dynamically based on user or platform actions [1]. For example it may take some time for a sensor to calibrate itself or it may revert to a low accuracy mode in a battery saving situation. This information could be important for applications, but it's not exposed through the generic API.
I don't know how easy it would be to strictly define the accuracy levels reported through that API [2]. It may be dependent on the sensor type and implementation.
At least on Android, the accuracy of an already-instantiated sensor can change dynamically based on user or platform actions [1]. For example it may take some time for a sensor to calibrate itself or it may revert to a low accuracy mode in a battery saving situation. This information could be important for applications, but it's not exposed through the generic API.
I don't know how easy it would be to strictly define the accuracy levels reported through that API [2]. It may be dependent on the sensor type and implementation.
[1] https://developer.android.com/reference/android/hardware/SensorEventListener.html#onAccuracyChanged(android.hardware.Sensor, int)
[2] https://developer.android.com/reference/android/hardware/SensorManager.html#SENSOR_STATUS_ACCURACY_HIGH
The text was updated successfully, but these errors were encountered: