public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Johan Hedberg <johan.hedberg@gmail.com>
To: Thomas Gillespie <tjg35@cam.ac.uk>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: A2DP headset
Date: Fri, 1 May 2009 22:27:34 +0300	[thread overview]
Message-ID: <20090501192734.GA2966@jh-x301> (raw)
In-Reply-To: <1241201091.12079.4.camel@localhost.localdomain>

Hi Thomas,

On Fri, May 01, 2009, Thomas Gillespie wrote:
> I'm trying to connect my A2DP headset to my computer. It works fine in
> HSP/HFP mode, but when i try to connect to the audio sink via dbus it
> won't connect. I get 
> "bluetoothd[1618]: No matching ACP and INT SEPs found"
> in my /var/log/messages file. What does this mean? 

A2DP has a concept of Stream End Points (SEPs). To create an audio stream
you need to hook up an Audio Source SEP on one device (in your case your
computer) to an Audio Sink SEP on another device (your headset). That
message you got means that bluetoothd didn't find an Audio Sink SEP in the
headset that would match in it's properties (codec, etc) an available
Audio Source SEP on your computer.

Why this all is happening is another matter though. Have you done any
special changes to /etc/bluetooth/audio.conf? Could you enable bluetoothd
debug messages (-d switch) and give us the complete log when trying to
connect A2DP to the headset. The output of hcidump -XV when connecting
A2DP might also provide some useful information.

Johan

      reply	other threads:[~2009-05-01 19:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-01 18:04 A2DP headset Thomas Gillespie
2009-05-01 19:27 ` Johan Hedberg [this message]

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=20090501192734.GA2966@jh-x301 \
    --to=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=tjg35@cam.ac.uk \
    /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