From: "Olivier Arnaud" <oarnaud79.linux@gmail.com>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] sdptool browse not working
Date: Wed, 8 Mar 2006 11:37:22 +0100 [thread overview]
Message-ID: <695f62bb0603080237q7f26f393q@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 431 bytes --]
Hi,
I'm using sdptool v2.19 to retrieve the SDP record of a BT device i am
developping.
When trying to browse it, my host (on which BlueZ is running) stops and
seems to disconnect the link.
I compared it with a working one (with a phone), and it seems that the
difference is in the L2CAP configuration request order.
Find enclosed the Merlin traces of this.
Can someone help me with this?
Thanks,
br,
Olivier
[-- Attachment #1.2: Type: text/html, Size: 460 bytes --]
[-- Attachment #2: SdpBrowse.tfb --]
[-- Type: application/octet-stream, Size: 237268 bytes --]
[-- Attachment #3: SdpBrowseWithPhone.tfb --]
[-- Type: application/octet-stream, Size: 396804 bytes --]
next reply other threads:[~2006-03-08 10:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-08 10:37 Olivier Arnaud [this message]
2006-03-17 9:34 ` [Bluez-devel] sdptool browse not working 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:
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=695f62bb0603080237q7f26f393q@mail.gmail.com \
--to=oarnaud79.linux@gmail.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.