I don't know what the behavior is called, but when I pan slowly on my Flame, there is a minimum distance my finger needs to travel before the screen actually starts panning. When that threshold is crossed, the scroll position is not adjusted by that threshold - instead, there is now an offset between the position of the touch start and the position the finger is now anchored on. This feels really bad.
So you're saying that, after we cross the threshold, the page should jump by the amount of the threshold, so that the content that was under your finger at touchstart remains under your finger?
This is intentional, in both Fennec  and the C++ APZ . It feels worse if the page "jumps" so that the spot you put your finger down on realigns with your finger. At least in the common case where the user is moving their finger fast.  http://mxr.mozilla.org/mozilla-central/source/mobile/android/base/gfx/JavaPanZoomController.java?rev=4d66d5d58232#632  http://mxr.mozilla.org/mozilla-central/source/gfx/layers/apz/src/AsyncPanZoomController.cpp#1941
Yes, I'm saying it should jump, and if it feels bad then I think that's a sign that the threshold is too high.
Bug 1116569 is on file for reducing the threshold, so that might help. Note that the flip side of reducing the threshold means that your finger will have less wiggle room when tapping things as we'll more easily go into a pan. I'm fine with adjusting it a bit though.
Markus, could you try the behaviour now that bug 1116569 had landed, and say whether you think a change should still be made?
The panning behavior on the Foxfooding device seems fine to me.