From: Iain Hibbert <plunky@rya-online.net>
To: nirav rabara <niravrabara@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: headset service search problem
Date: Fri, 6 Nov 2009 13:11:33 +0000 (GMT) [thread overview]
Message-ID: <1257513094.024986.889.nullmailer@galant.ukfsn.org> (raw)
In-Reply-To: <912bb79a0911060310t71211862q3c39fe3e08486d2a@mail.gmail.com>
On Fri, 6 Nov 2009, nirav rabara wrote:
> I have been trying to search only headset devices among other
> bluetooth devices using SDP.
>
> Problem - 1)
>
> -> when I search for UUID 0x1108 (for headset). It shows me mobile
> devices also because it support headset service
> Is there any other way to search particularly for headset only??
Well, you could do a device inquiry first and filter the responses using
the "Class of Device" value. A headset will claim to be an AV device
(major #4) rather than a Phone (major #2). See section 5.5.1 in the
Headset Profile specification..
Then, you can probe the devices you find and check for "Headset" in the
service class attributes but that might only apply to version 1.0 of the
HSP specification because the newer profile (v1.2) seems to provide
different UUIDs for "Headset HS" (0x1131), "Headset AG" (0x1112) and
"Headset Profile" (0x1108)
> Problem - 2)
>
> -> when I search for the search for the service(headset). Bluetoothd
> is going to get PIN no. because sometimes link key gets fail (in case
> of new headset device whose is getting connected first time ).
> -> Why bluetoothd need PIN when I am try to search for the service.
> (not connecting)
>
> Is there any way to search for the services without entering PIN ??
If the remote device requires authentication, then no.
iain
prev parent reply other threads:[~2009-11-06 13:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-06 11:10 headset service search problem nirav rabara
2009-11-06 13:11 ` Iain Hibbert [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=1257513094.024986.889.nullmailer@galant.ukfsn.org \
--to=plunky@rya-online.net \
--cc=linux-bluetooth@vger.kernel.org \
--cc=niravrabara@gmail.com \
/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