On Wed, Jul 20, 2011 at 8:04 PM, Carlos Silva <[email protected]> wrote:
> After some digging, looks like my accelerometer events are getting > "dropped" by me because they are unreliable. > I filter the events on the eventlistener: > // If the sensor data is unreliable return > if (event.accuracy == SensorManager.SENSOR_STATUS_UNRELIABLE) > > And they really are. Compared to the N1 I get something differences from 50 > to 60 degress between the two (pointing to the same direction of course). > Yes, you will want to calibrate your device. If you're developing things with the compass/accelerometer you will find you will be doing this many, many times. You can use the unreliable accuracy to notify your users to do the same. Also to add, I have 2 portions of my app, one uses ORIENTATION, one uses raw MAG+ACCEL. The orientation I have never had a complaint about. The Mag + Accel which I need to use for augmented reality, several users have reported issues with it being off by 90 or 180 degrees, or upside down. Upon investigation it is discovered that certain OTA updates have hosed the firmware so that it is behaving wrong -- it also affects the compass in google maps, skymap, and other apps that use the mag+accel. So just something to keep in mind. Orientation seems to be implemented more consistently; anecdotally it seems there have been issues from various manufacturers for various firmwares which can affect implementations of MAG+ACCEL. And the finger gets pointed at you, google, the developers, etc, until it's discovered that it's a firmware issue. -- 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
