I used java.util.Timer and TimerTask instead of the Runnable and this resulted in much improved performance, allowing me to schedule the task at 40Hz (on average).
As expected, given this is not a RTOS, the cycles vary +/-1-2ms, however I the the average cycle time is 25ms as desired. So, it is shown that the Timer performs better than Runnable for scheduling tasks at frequencies around 40Hz (on the Galaxy S3). Thanks very much for your help. -- 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
