MIME-Version: 1.0
References: <CADS+iDUDv=Keo6661q3dY8C5=f+fZtfCe5gdPutO-psc9Pe0UQ@mail.gmail.com>
In-Reply-To: <CADS+iDUDv=Keo6661q3dY8C5=f+fZtfCe5gdPutO-psc9Pe0UQ@mail.gmail.com>
From:   Sathish Narasimman <nsathish41@gmail.com>
Date:   Wed, 6 Mar 2019 13:57:55 +0530
Message-ID: <CAOVXEJ+bEQ=jmqwPEZygzaP7ChtKk2GwLc7183VyiRe5tbOzUQ@mail.gmail.com>
Subject: Re: Strange SCO problem
To:     Yaroslav Isakov <yaroslav.isakov@gmail.com>
Cc:     linux-bluetooth@vger.kernel.org,
        Sathish Narasimman <sathish.narasimman@intel.com>
Content-Type: text/plain; charset="UTF-8"
Sender: linux-bluetooth-owner@vger.kernel.org
Precedence: bulk

Hi,

Intel adapter 9260 and 9265(with the latest Firmware - from
Bluetooth-next) supports USB ALT 6 settings and was verified.

Along with backend ofono
https://patchwork.freedesktop.org/patch/245272/

https://www.spinics.net/lists/linux-bluetooth/msg76982.html

Regards,
Sathish N


On Wed, Mar 6, 2019 at 5:15 AM Yaroslav Isakov
<yaroslav.isakov@gmail.com> wrote:
>
> Hello! I'm currently trying to modify pulseaudio to be able to use HFP
> profile with mSBC codec on native backend, but found that, while
> working de-jure, real sound is completely ruined, so I can barely hear
> what is sent over SCO link. I've tried two different Intel adapters
> (included in 8260 and 8265 chipset) and KillerWifi (ath10k driver), on
> two different PCs with two different headsets, results are mostly the
> same, the only difference is that on ath10k words are more or less
> distinguishable.
>
> I've even tested with pulse just for profile setup, and SCO is sent
> via modified scotest from bluez, which sends some test sound, manually
> encoded via sbcenc (with added h2, of course). I've tried also msbc
> branch from bluez-alsa, same result.
>
> I'm sure that every time socket is connected with setsockopt(fd,
> SOL_BLUETOOTH, BT_VOICE, &voice, sizeof(voice));
>
> I've also tried with this patch
> https://www.spinics.net/lists/linux-bluetooth/msg76982.html, with no
> luck.
>
> Any ideas?