32xx movement problem poll and data thread

[Dirt]

Originally Posted by dannyp

I tend to agree, at least for those who are looking out for a first problem. Had timekeeping been consistent and consistently good, as it was previously, I wouldn't have had cause to check amplitude, and probably wouldn't have been too concerned if it was a bit low (but still in spec). In this case, and at this stage, the low amplitude is a piece of supporting evidence that things are heading in the wrong direction, rather than a problem in and of itself.

The low amplitude is symptomatic of the problem.
Without opening up the watch(an invasive process) the simple act of recording of low enough amplitude is reason enough to trigger corrective action.