An uninitialised device transformation matrix caused a calculation to generate zero on certain movements on devices with absolute axes. The transformation matrix is used to bind a device to a specific area on the screen (or a specific screen). This bug only triggered if the device did not change the device transformation matrix and left it at its default value.
The generated zero value causes a reset of the pointer coordinates to 0/0, i.e. a jump to the top-left corner.
The matrix is initialised to the identity matrix.
Pointer movement now works as expected.