Received-SPF: pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Message-ID: <699f55a2f9d574943af0b5cc80c47d08d48953f7.camel@hadess.net>
Subject: Re: sixaxis patch proposal
From:   Bastien Nocera <hadess@hadess.net>
To:     Lionel Jeanson <lionel.jeanson@gmail.com>
Cc:     linux-bluetooth@vger.kernel.org
Date:   Tue, 08 Dec 2020 10:53:29 +0100
In-Reply-To: <CAMxp8948=LGwO6NE_oij2WgXxzXCY7nByj_XmmhPZFMiookseA@mail.gmail.com>
References: <CAMxp894ThdL9qxNz49561WrDj3XhWxpFMf+9afMD9WqMbSPBbw@mail.gmail.com>
         <2fb922ffced103ba09571567366968d5462f9267.camel@hadess.net>
         <CAMxp8948=LGwO6NE_oij2WgXxzXCY7nByj_XmmhPZFMiookseA@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.38.1 (3.38.1-1.fc33) 
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Precedence: bulk

On Tue, 2020-12-08 at 10:45 +0100, Lionel Jeanson wrote:
> Hi;
> 
> yes, I've seen your commit, and actually I don't get it, since it was
> integrated, and bluez updated, sixaxis pads are not working as well
> as
> they used to, I need to repair the device again and again.
> 
> I tried to do it with the pairing agent using bluetoothctl but
> couldn't get it to work as expected, any hint? I can't find anything
> on google or anywhere else.

1. Start bluetoothctl
2. Plug in the device
3. Answer yes when bluetoothctl asks to pair

The same should work using GNOME's Bluetooth Settings.

If it doesn't work, send the bluetoothd logs when reproducing the
problem.