From: Fred Schaettgen <buez-devel@schaettgen.de>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] how to recognize whether the connected device is a headset
Date: Thu, 21 Oct 2004 13:00:07 +0200 [thread overview]
Message-ID: <200410211300.07230.buez-devel@schaettgen.de> (raw)
In-Reply-To: <1098352217.1912.4.camel@debian>
On Thursday 21 October 2004 11:50, Chen Bin wrote:
> Hi all,
>
> Thanks very much for previous help from Holtman, and I happen a new
> problem when I try to find out whether a connected device is a headset.
>
> It can't be browsed using sdptool in both connected mode and discovery
> mode(paring state), I wonder how I can know its charactics after
> connected?
You can look at the device class first.
And instead of browsing try to search for the profile instead with
sdptool search --bdaddr <add> <uuid>
You are supposed to use the headset uuid (0x1108), but you can use the
L2CAP-UUID (0x100) just as well. This little trick will list almost every
service of a device, even if it's not in the public browse group.
Fred
--
Fred Schaettgen
bluez-devel@schaettgen.de
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2004-10-21 11:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-21 9:50 [Bluez-users] how to recognize whether the connected device is a headset Chen Bin
2004-10-21 11:00 ` Fred Schaettgen [this message]
2004-10-21 17:41 ` Marcel Holtmann
2004-10-22 1:18 ` Chen Bin
2004-10-22 10:32 ` Marcel Holtmann
2004-10-22 1:27 ` Chen Bin
2004-10-22 10:45 ` Marcel Holtmann
2004-10-22 1:31 ` Chen Bin
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=200410211300.07230.buez-devel@schaettgen.de \
--to=buez-devel@schaettgen.de \
--cc=bluez-users@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox