First of all it all device dependent because SENSOR_DELAY_FASTEST has value 0ms in Android git but 10ms - Samsung Galaxy S. Using 0ms should result in close to 100% CPU usage so some sensors drivers have internal logic to prevent such case and add some delay inside.
On the other side "sampling rate" is the frequency of measurements when it seems like you are trying to check how often do you get SensorEvent. You should use timestamps inside sensor event if you are interested in the stability of the sampling rate. With respect to the unstable rate you get updates from the SensorManager - this is not a bug, but a feature (explicitly described in the SensorManager documentation). On Jan 13, 12:35 am, outi <[email protected]> wrote: > Hello, > > does anybody know, why the sensor sampling rate is fluctuating between > 85 and 115 Hertz [Hz] ? > I tested my accleretation sensor app up to 60 seconds. And I > calculated the mean sampling rate. In any continous I get an another > mean sampling rate... > > I'm using the SENSOR_DELAY_FASTET constant: > > sensorManager.registerListener(accelerationListener, sensor, > SensorManager.SENSOR_DELAY_FASTEST); > > Thank you for your replies! -- 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
