On Thu, 23 Jul 2015, Frank Praznik wrote:
When connected via Bluetooth the sixaxis periodically sends reports with
an ID of 1, the second byte 0xff and the rest zeroed. These reports are
not related to the controller state and must be dropped to avoid generating
false input events.
When connected via Bluetooth the sixaxis periodically sends reports with
an ID of 1, the second byte 0xff and the rest zeroed. These reports are
not related to the controller state and must be dropped to avoid
generating false input events.
These 'problem reports' were reported (*) over the
