I believe that it is the Magnetic Sensor that can sometimes get stuck in a 7-8Hz mode. This locks Orientation to 7-8Hz and Orientation will lock Acceleration to 7-8 Hz. Even when the device is in this mode Acceleration and Gyroscope either separately or together still run at their normal rates. Power cycling the device fixes the problem for me. I couldn't figure out how to reproduce this but it happens every few hours during development.
dsm On Feb 16, 5:36 am, GoG <[email protected]> wrote: > Hi everybody, > and thanks Greg for registered this bug (before me ;). > On my Nexus S, 2.3.2, I experienced same issue : > Fastest = ~35 Hz acc/mag and ~800 Hz gyro > But acc/mag frequencies came down to ~8 Hz recently. > > First: sensor delay (fastest, game, ...) doesn't seem to > affect gyro frequency. > > Second: why such a difference between sensors frequency ? > 30-40 Hz seems ok since it avoids overloading cpu and save battery. > But what about a 800 Hz gyro ? I think that even high precision > (military) devices don't use such a precision. The iPhone 4 (sorry > :P)http://developer.apple.com/library/ios/#documentation/EventHandling/C... > max frequency is more about 100 Hz... > > Hope this can help. > FYI, I measured frequencies differents ways and always found same > results. > I used to think my app went wrong 'till I read this post. I'll try to > remove > the battery too to check if it'll fix acc/mag freq. > Thanks. > > GoG -- 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
