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;
MIME-Version: 1.0
References: <010201715012e482-bca51111-db3c-4101-9bd4-208b69a0ff03-000000@eu-west-1.amazonses.com>
 <01020171a3203016-7d1d5c39-46ee-4ba9-8ff3-a6928a329d2a-000000@eu-west-1.amazonses.com>
 <CABBYNZJ2tn6Riz7uouxD0qa1M-dT7GbtUSkD-dbn1nj1B372iQ@mail.gmail.com>
In-Reply-To: <CABBYNZJ2tn6Riz7uouxD0qa1M-dT7GbtUSkD-dbn1nj1B372iQ@mail.gmail.com>
From:   James Belchamber <james@belchamber.com>
Date:   Thu, 23 Apr 2020 11:06:22 +0000
Message-ID: <01020171a6b79a5e-6f98b660-3a61-4542-b956-70276882f469-000000@eu-west-1.amazonses.com>
Subject: Re: Setup Synchronous Connection fails when switching Sony WH-H900N
 headset to HSP
To:     Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc:     Marcel Holtmann <marcel@holtmann.org>,
        Johan Hedberg <johan.hedberg@gmail.com>,
        "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Feedback-ID: 1.eu-west-1.iLkSOx0ll0H29nNg//Fx25T4fmIhOvUmYvVubjmmX6g=:AmazonSES
Sender: linux-bluetooth-owner@vger.kernel.org
Precedence: bulk

Only difference in the btmon output is the handle (256 instead of 67)
- otherwise it all looks the same and it connects first time.

What logs are useful? I have the Chromebook in developer mode and so I
can capture whatever you want (hopefully!)

On Wed, 22 Apr 2020 at 23:32, Luiz Augusto von Dentz
<luiz.dentz@gmail.com> wrote:
>
> Hi James,
>
> On Wed, Apr 22, 2020 at 11:27 AM James Belchamber <james@belchamber.com> wrote:
> >
> > Just bumping this for visibility, still an issue with the latest kernel.
> >
> > Happy to test anything thrown my way.
> >
> > On Mon, 6 Apr 2020 at 16:19, James Belchamber <james@belchamber.com> wrote:
> > >
> > > When using my Sony WH-H900N headphones and switching from A2DP to
> > > HSP/HFP the following error appears in journalctl:
> > >
> > > (  60.063|   0.000) D: [pulseaudio] module-bluez5-device.c: Acquiring
> > > transport /org/bluez/hci0/dev_04_5D_4B_E9_C9_90/fd34
> > > (  60.063|   0.000) I: [pulseaudio] backend-native.c: doing connect
> > > (  60.174|   0.111) E: [pulseaudio] backend-native.c: connect():
> > > Function not implemented
> > >
> > > And using btmon I can see the HCI command comes back with a failure
> > > (full log attached):
> > >
> > > < HCI Command: Setup Synchronous Connection (0x01|0x0028) plen 17
> > >         Handle: 67
> > >         Transmit bandwidth: 8000
> > >         Receive bandwidth: 8000
> > >         Max latency: 10
> > >         Setting: 0x0060
> > >           Input Coding: Linear
> > >           Input Data Format: 2's complement
> > >           Input Sample Size: 16-bit
> > >           # of bits padding at MSB: 0
> > >           Air Coding Format: CVSD
> > >         Retransmission effort: Optimize for power consumption (0x01)
> > >         Packet type: 0x0380
> > >           3-EV3 may not be used
> > >           2-EV5 may not be used
> > >           3-EV5 may not be used
> > > > HCI Event: Command Status (0x0f) plen 4
> > >       Setup Synchronous Connection (0x01|0x0028) ncmd 1
> > >         Status: Success (0x00)
> > > > HCI Event: Max Slots Change (0x1b) plen 3
> > >         Handle: 67
> > >         Max slots: 1
> > > > HCI Event: Synchronous Connect Complete (0x2c) plen 17
> > >         Status: Unspecified Error (0x1f)
> > >         Handle: 67
> > >         Address: 04:5D:4B:E9:C9:90 (Sony Corporation)
> > >         Link type: eSCO (0x02)
> > >         Transmission interval: 0x00
> > >         Retransmission window: 0x00
> > >         RX packet length: 0
> > >         TX packet length: 0
> > >         Air mode: u-law log (0x00)
> > >
> > > This works on ChromeOS, which also uses a (modified) BlueZ stack -
> > > though I can't work out why :)
>
> It doesn't look like it is a host problem and Ive never seem this
> error before, have you tried with the same controller on Chrome OS? It
> may be worth trying to capture the logs in Chrome OS so we can compare
> if there is something different in the command parameters, but it
> could as well be that Chrome uses HFP instead of HSP as PulseAudio
> does and the headset is sensitive to that.
>
> --
> Luiz Augusto von Dentz