On 01/19/2016 11:40 PM, Antonio Ospite wrote:
Seems like the controller keeps sending axis information even if the
axis aren't touched at all.
IIRC this is because the controller has a lot of axes and they end up in
the multi touch range (ABS_MT_*) which apparently sends event
continuously.
I remember I did some experiments about remapping the axes to a more
meaningful setup and there were some improvements but that work
depended on some experimental changes to the linux input layer from
David Herrmann (the ABS2 proposal) and I do not know if the latter ever
reached mainline. This is a linux-input topic BTW.
I guess that those are just the numbers, used by Sony, directly sent
out, right?
If you disconnect the device from bluez (either from an applet or from
command line) the sixaxis should turn off.
JFYI a possible hardware way is to keep pushed the PS button for some
seconds, this also should turn the sixaxis off.
Both ways work. Thank you.
Just to be sure if this is not another linux-input topic:
If I first connect my PS3 controller via bluetooth, then all LEDs are
turned off after some flashing. I think a better default configuration
would be to set the first LED to be on. If all are off it is not obvious
that the controller is turned on...
Thanks in advance
Best regards,
Manuel
--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
