Linux-Bluetooth Archive on
 help / color / Atom feed
From: "Gix, Brian" <>
To: "" <>
Cc: "" <>,
Subject: Re: Determinate EDR speed
Date: Fri, 11 Oct 2019 19:00:09 +0000
Message-ID: <> (raw)
In-Reply-To: <20191011183502.ao45xlyfabpbadxo@pali>

Hi Pali,

On Fri, 2019-10-11 at 20:35 +0200, Pali Rohár wrote:
> Currently bluez API, method Acquire() already inform called application
> what is socket MTU for input and output. So from this information it is
> possible to detect if device supports EDR 3 or not.
> But it is too late to have this information. I need to send SBC
> parameters to bluez first when doing A2DP negotiation, this is early
> steps before Acquire() is called.

This seems to be the kind of information which is fixed, for the life of the pairing.

What if you assumed the lower speed the first time you connected, determined the
speed during the first streaming, and then either immediately renegotiate (caching the identifying information
of the SNK), or just cache the information for future connections.

Or the reverse, and assume fast, but immediately adjust down if you aren't getting what you hoped for.

In any case, this would be a "Device Setup" glitch which you could note as a routine part of pairing in the

> Therefore I'm asking for some way how to get information if device
> supports EDR 2 or EDR 3. This is basically requirement for proper
> implementation of SBC in high quality mode. So if there are not such API
> yet, could it be exported from kernel to userspace and bluetoothd
> daemon?
> See these two articles for more details about SBC and its high quality:
> > > Is there any bluez API for it?
> > > 

  reply index

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-11  8:27 Pali Rohár
2019-10-11 18:15 ` Gix, Brian
2019-10-11 18:35   ` Pali Rohár
2019-10-11 19:00     ` Gix, Brian [this message]
2019-10-11 19:05       ` Gix, Brian
2019-10-11 20:04         ` Pali Rohár
2019-10-12  7:23           ` Luiz Augusto von Dentz
2019-10-13  7:36             ` Pali Rohár
2019-10-13  8:45               ` Luiz Augusto von Dentz
2019-10-13  9:39                 ` Pali Rohár
2019-10-13  9:49                   ` Luiz Augusto von Dentz
2019-10-16 19:06                   ` Marcel Holtmann
2019-10-16 19:13                     ` Pali Rohár
2019-10-19 19:47                       ` Marcel Holtmann
2019-10-16 19:05           ` Marcel Holtmann

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Linux-Bluetooth Archive on

Archives are clonable:
	git clone --mirror linux-bluetooth/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-bluetooth linux-bluetooth/ \
	public-inbox-index linux-bluetooth

Example config snippet for mirrors

Newsgroup available over NNTP:

AGPL code for this site: git clone