From: Manuel Reimer <manuel.reimer@mailbox.org>
To: Antonio Ospite <ao2@ao2.it>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: PS3 controller (SIXAXIS) never gets into "IdleTimeout"
Date: Fri, 22 Jan 2016 16:50:07 +0100 [thread overview]
Message-ID: <56A24FAF.3000203@mailbox.org> (raw)
In-Reply-To: <20160119234026.0db2304963ec8bfc99665ff1@ao2.it>
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
prev parent reply other threads:[~2016-01-22 15:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-19 18:57 PS3 controller (SIXAXIS) never gets into "IdleTimeout" Manuel Reimer
2016-01-19 22:40 ` Antonio Ospite
2016-01-22 15:50 ` Manuel Reimer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56A24FAF.3000203@mailbox.org \
--to=manuel.reimer@mailbox.org \
--cc=ao2@ao2.it \
--cc=linux-bluetooth@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.