From: Brian Smith <door@shapeseeker.com>
To: Mikel Astiz <mikel.astiz.oss@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: Bluez patches for Multiple SCO Links
Date: Fri, 15 Jun 2012 15:24:03 +0100 [thread overview]
Message-ID: <4FDB4583.5070902@shapeseeker.com> (raw)
In-Reply-To: <CANT-zCXOzBBaYvXRj3Z7xb=2oz7mSNTWLPUFeZi5ghHs6KzBwA@mail.gmail.com>
Mikel Astiz wrote:
>
> Assuming your Kernel includes the patches, and you're using the latest
> upstream version of BlueZ, most probably the problems you are having
> are related to the MTU size.
>
> These issues are a bit obscure to me and I don't have a full
> explanation, but the MTU used during double-SCO needs to be twice as
> big. My patches regarding this problem were (reasonably) rejected so
> you will have to find a workaround.
>
> First make sure the adapter is configured with at least 128 bytes,
> using hciconfig hci0 scomtu 128:1. Once you have this, you should
> probably be able to receive/record audio properly. If you want to
> send/play audio, you might face some additional problems. However I
> must admit I haven't tested it with hstest.
>
>
Thanks for your reply Mikel. I tested your suggestion of changing the
MTU and it worked! It started as 64:8, changing to 128:1 didn't work
but changing to 128:8 solved the problem. (I am using kernel 3.5rc1,
BlueZ 4.100, 'Sitecom' branded CSR dongle, 'hstest.c' player). Also
I've tested both playback and recording on 2 headsets in parallel, both
are working well.
Cheers,
Brian.
--
Brian Smith.
"The bells of clocktowers stitch the sleeper's dreams together." - Memory Palace
next prev parent reply other threads:[~2012-06-15 14:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-15 11:45 Bluez patches for Multiple SCO Links Brian Smith
2012-06-15 13:17 ` Mikel Astiz
2012-06-15 14:24 ` Brian Smith [this message]
2012-07-01 15:21 ` Brian Smith
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=4FDB4583.5070902@shapeseeker.com \
--to=door@shapeseeker.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=mikel.astiz.oss@gmail.com \
/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).