Yes, I know. What I am saying is that for me, it worked from the very beginning under 1.0 as it is described now -- it attempted to take HR every 10 minutes, but skipped reading/recording every once in a while. I'm guessing that people didn't complain because they didn't get any skipped readings. Then in 1.01, I think the criteria for when it skipped readings got upped too much, and now everyone is complaining. Then someone noticed that they'd forgotten to mention the skipping readings feature in the manual, so they updated the manual. But they could leave the manual as it is, and adjust the motion sensitivity so it doesn't skip readings so frequently.
Ah okay got it. I just don't think the 10 minutes should start over because I check what time it is. It's too sensitive, like you said.
 rep who said that the engineering department is aware of the issues with activity tracking, steps, and calories being unstable, and that those issues will be resolved in the next update.  I didn't bring the HR into the conversation because really I just want it to track activity like it should.  I did tell him that so far I hadn't heard anything about this update addressing the activity tracking issues, so I was a bit doubtful about what he's saying but I guess time will tell...