This is a known issue with a verified solution. Forceful haptics create a disturbance that will cause the IMU to output erroneous data. A 3ms haptic pulse that couples into the IMU doesn’t create a 3ms acceleration disturbance. It causes the IMU to output that erroneous data for 100-200ms. If you attempt to ignore that data, it’s easy to chain together enough haptics that you are essentially ignoring the IMU forever. There is a method to filter the event that has been used successfully and it is outlined in the 1.5 Tracker Dev Guidelines that can be found that the link below. The Tracker FW build that supports this functionality is available now.
Even with this solution, you should provide damping and secure the Tracker firmly to the peripheral to mechanically isolate the IMU from the vibration source.
... View more