From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Cc: victor@win.tue.nl
Subject: Re: [Bluez-devel] Connection with a phone stays open after closing RFCOMM channel
Date: Mon, 28 Feb 2005 09:07:48 +0100 [thread overview]
Message-ID: <1109578068.17256.0.camel@pegasus> (raw)
In-Reply-To: <Pine.LNX.4.44.0502271406520.18458-100000@antilope>
Hi Victor,
> My prog. listens on a RFCOMM chan. (adv. as HF channel via SDP) of a
> laptop, when I
> connect from my phone to the laptop the chan. is opened, I send some
> commands to configure the phone and when finished, close the chan. The
> problem is that L2CAP connection stays open, from the output of hcidump I
> see that laptop sends DISC request on dlci 6 and receives UA, but then
> according to protocol it should also then send DISC for dlci 0, and then
> terminate L2CAP -- it does not happen...
> If I do the same, but initiating connection from laptop - it works fine...
> I'm sure there is no other RFCOMM chan. opened.
sounds like a bug in the phone. Send in the "hcidump -X -V" for it.
Regards
Marcel
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2005-02-28 8:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-27 13:25 [Bluez-devel] Connection with a phone stays open after closing RFCOMM channel Victor Shcherbatyuk
2005-02-28 8:07 ` Marcel Holtmann [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=1109578068.17256.0.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=victor@win.tue.nl \
/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