linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Frank Praznik <frank.praznik@gmail.com>
To: Antonio Ospite <ao2@ao2.it>
Cc: "Martin Kjær Jørgensen" <mkj@gotu.dk>, linux-bluetooth@vger.kernel.org
Subject: Re: DS4 issues
Date: Mon, 28 Dec 2015 10:48:21 -0500	[thread overview]
Message-ID: <0F6173F5-CF72-47E8-BB6B-44200F75EB6E@gmail.com> (raw)
In-Reply-To: <20151228101822.03253569407ac9dfe4ea15be@ao2.it>


> On Dec 28, 2015, at 04:18, Antonio Ospite <ao2@ao2.it> wrote:
> 
> On Mon, 21 Dec 2015 15:46:07 +0100
> Martin Kjær Jørgensen <mkj@gotu.dk> wrote:
> 
>> Is there any "full" support for a Sony DualShock 4 in the bluez/kernel
>> stack?
>> 
> 
> CC-ing Frank as he is the author of the DS4 hid kernel driver.
> 
>> The one I own works perfectly when using USB cable.
>> 
>> When using bluetooth it gets recognized as a somewhat generic
>> Bluetooth Wireless Controller. Pairing it up with my system seems to
>> work as it creates a joystick device (/dev/input/js0) but when testing
>> it with jstest, only the touchpad on the DS4 triggers two of the
>> axis. None of the buttons or sticks reacts in jstest.
>> Pairing it with the usual bluetoothctl makes the DS4 LED dimmed blue
>> light.
>> 
>> I know of the ds4drv project and have used it to connect my DS4, but
>> it seems a big buggy and I was hoping it was or will be merged into
>> bluez/kernel, making it superfluous.
>> 
>> Using the DS4 makes the LED brighter than using ordinary bluetoothctl,
>> perhaps because ds4drv knows how to intruct the LED.
>> Even if my DS4 is almost next to my bluetooth radio device, the ds4drv
>> reports "Signal strength low (29/40/38) reports"
>> Testing with jstest seems to trigger all buttons and axises. The
>> touchpad itself as a button triggers, but touching the pad doesnt trigger
>> anything.
>> In some games the digital keys on the left doesnt get recognized, even
>> if they get triggered by jstest and other programs like Steam
>> recognizes them.
>> 
>> 
>> 
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
> 
> -- 
> Antonio Ospite
> http://ao2.it
> 
> A: Because it messes up the order in which people normally read text.
>   See http://en.wikipedia.org/wiki/Posting_style
> Q: Why is top-posting such a bad thing?

What kernel version are you using and how new the controller?  This sounds
like a bug others were having due to Sony making a change to the HID
descriptor in the controller firmware.  It’s been fixed in newer kernels, but it
will take time for the fix to make it’s way to most distros.

The patch is here if you are interested:
http://thread.gmane.org/gmane.linux.kernel.input/46634/focus=46902

Regards,
Frank

  reply	other threads:[~2015-12-28 15:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-21 14:46 DS4 issues Martin Kjær Jørgensen
2015-12-28  9:18 ` Antonio Ospite
2015-12-28 15:48   ` Frank Praznik [this message]
2015-12-28 16:40     ` Martin Kjær Jørgensen
2015-12-30 11:09       ` Martin Kjær Jørgensen
2015-12-30 15:36         ` Frank Praznik
2016-02-14 10:47           ` Martin Kjær Jørgensen
2016-04-21 16:15             ` Martin Kjær Jørgensen
2016-04-27  1:22               ` Frank Praznik

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=0F6173F5-CF72-47E8-BB6B-44200F75EB6E@gmail.com \
    --to=frank.praznik@gmail.com \
    --cc=ao2@ao2.it \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=mkj@gotu.dk \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).