Sounds like writing some unit test cases would help. Of course, you may need to refactor the code to make it testable.
The advantage would be that you will see more clearly the input parameters and the constraints. It would divide and conquer the problem. The test cases would be the theory of what the sensors say and what the algorithm should output. If either of these theories needs adjustment, it is then easier to fix the algorithm. -- 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
