From: Fredrik Tolf <fredrik@dolda2000.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Headset reconnection
Date: Tue, 23 Aug 2005 01:52:28 +0200 [thread overview]
Message-ID: <1124754748.21719.82.camel@pc7.dolda2000.com> (raw)
In-Reply-To: <43022E86.7080909@xmission.com>
On Tue, 2005-08-16 at 12:20 -0600, Brad Midgley wrote:
> Fredrik,
>
> You can get pdfs from bluetooth.org. The relevant ones are 6_headset.pdf
> and "HFP Spec Version 1_0.pdf"
>
> Most headsets attempt to make the rfcomm connection to the last-used
> handset (or only handset if they only keep one pairing) on power-up. The
> stereo headsets tend to wait until the first click of the answer button.
Indeed -- I tried clicking the button on my headset, and judging from
hcidump, it attempts to connect to my computer (although I have a mono
headset, not a stereo). After that, however, weirdness occurs.
Looking at the data from hcidump, the headset requests a connection, and
the computer replies with a success message. The next package, the
headset disconnects again immediately (and the computer acknowledges
that). Then the headset connects again, and disconnects again, over and
over.
> I don't think we are doing the device class or sdp stuff to even make
> the headset aware that it can make this connection. On top of that, we
> need to be listening for connections.
Indeed, I'm not even attempting to public SDP data to the headset at
this point, but if that were the problem, I would think that the headset
wouldn't even attempt to connect to begin with, rather than going into a
loop of connecting and disconnecting all the time, right?
Does anyone have any idea what the cause of this could be?
Fredrik Tolf
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2005-08-22 23:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-16 18:02 [Bluez-devel] Headset reconnection Fredrik Tolf
2005-08-16 18:20 ` Brad Midgley
2005-08-16 19:50 ` [Bluez-devel] No sound in Plantronics M2500 Nelson Murilo
2005-08-22 23:52 ` Fredrik Tolf [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=1124754748.21719.82.camel@pc7.dolda2000.com \
--to=fredrik@dolda2000.com \
--cc=bluez-devel@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.