Re: Reaching out again for serious bug in sixaxis plugin

[Sergey Kondakov <virtuousfox@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 2561 bytes --]

On 14.07.2015 21:54, simon@mungewell.org wrote:
> 
> As the original poster stated that this DOES NOT occur with a USB
> connection, it does kind of point to a Bluetooth problem (or maybe with
> device itself). Has anyone been able to replicate?

Indeed. And don't forget that it doesn't occur under Windows either. Or
at least I wasn't able to detect such. The BT dongle used is of quite
questionable quality and DS3 itself is quite old. But no direct signs of
malfunction on their part. And if it's software issue someone should
have stumbled upon it already. So it's quite mysterious.

> My suggestion would be to display/capture the hidraw interface and see if
> the missing data is present there. This can be done as root with
> --
> $ hexdump -v -e '49/1 "%02x " "\n"' < /dev/hidraw0
> --
> 
> The '49' is the byte count, and might be wrong (working from memory).

Now that's the real answer !
I tried that and seen this one odd line in the middle about the time
that stick axises have spiked with bogus values:
01 00 00 00 00 00 79 7f 7b 7f 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 03 05 16 ff be 00 1b 33 af 77 01 c0 00 02 ea 01 90 01 e6 01
01 00 00 00 00 00 79 7f 7b 7f 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 03 05 16 ff be 00 1b 33 af 77 01 c0 00 02 e9 01 90 01 e7 01
01 ff 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
01 00 00 00 00 00 79 7f 7b 7f 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 03 05 16 ff be 00 1b 33 af 77 01 c0 00 02 e9 01 8f 01 e7 01
01 00 00 00 00 00 79 7f 7b 7f 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 03 05 16 ff be 00 1b 33 af 77 01 c0 00 02 ea 01 90 01 e6 01

No idea what that means.

> 
> The multi-touch/many-axis stuff is a pain, but the linux-input list is the
> place to discuss that...
> Simon

Yeah, probably. I thought maybe BT stack has some special input handling
for BT input devices.

On 14.07.2015 16:32, Bastien Nocera wrote:
> ...
> Did you re-read your original mail? Are you genuinely still wondering
> why you didn't receive an answer?

I'm not your psychologist, girlfriend or a telepath for figuring out
what magic words are to your liking. I gave pretty detailed description
with all the tech info available. Which you still managed to miss twice,
as was pointed above.
So seeing your behaviour I'm not wondering anymore but advising to read
things at least once. Or get a bug tracker.



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 278 bytes --]