I need to get updates from the orientation sensor about once every 2 or 3 seconds, having the sensor events delivered to a background service thread. My options seem to be:
1. register the service thread as an event listener, and throw away most of the events, looking only at the most recent event every 2 or 3 seconds. 2. register the service thread as an event listener, get one event, and then unregister. repeat every 2 or 3 seconds. Which is more efficient? In Donut, all sensor activity delivered to an application element seems to be attributed to the application (even though it's running on the event thread), so #2 seems like it would make more sense if you want an app that is going to be recieving orientation events over the long haul. I wish that there was a #3: 3. deliver orientation events ever N milliseconds to the following event listener. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
