From: bluezprofile kernel <bluezprofile@gmail.com>
To: Iain Hibbert <plunky@rya-online.net>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: service search for headset
Date: Wed, 23 Dec 2009 16:40:17 +0530 [thread overview]
Message-ID: <ba5648fa0912230310g5f638af0p408f46b468afb7d5@mail.gmail.com> (raw)
In-Reply-To: <1261563553.504805.2509.nullmailer@galant.ukfsn.org>
On Wed, Dec 23, 2009 at 3:49 PM, Iain Hibbert <plunky@rya-online.net> wrote:
> On Wed, 23 Dec 2009, bluezprofile kernel wrote:
>
>> I have done between two laptops and I am able to see the services available.
>> When I do the same for my hands free device, I am not able to get the
>> service details of handsfree unit.
>> I have debugged this using sdptool application source.
>> sdptool application sends the attribute request to the hands free
>> device, in the reply I am not getting anything. (sdp_send_req and sdp_read_rsp)
>
> All that a "browse" does is start searching for the "Browse Group Root"
> UUID and if the handsfree device doesn't provide that UUID in any of the
> records then it will return no results when you search for it. Many
> devices don't provide "Browse Groups" at all (see SDP specification),
> probably your handsfree is like that.
>
> Searching for L2CAP will usually suffice to find all of the (relevant)
> service records in a Bluetooth environment, as most bluetooth protocols
> operate over L2CAP.
>
> iain
>
>
>
Thanks for your help. I will refer the SDP spec.
Do I need to use --l2cap option for finding service for such cases? Is
this mandatory?
next prev parent reply other threads:[~2009-12-23 11:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-23 10:00 service search for headset bluezprofile kernel
2009-12-23 10:01 ` bluezprofile kernel
2009-12-23 10:19 ` Iain Hibbert
2009-12-23 11:10 ` bluezprofile kernel [this message]
2009-12-23 12:02 ` Iain Hibbert
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=ba5648fa0912230310g5f638af0p408f46b468afb7d5@mail.gmail.com \
--to=bluezprofile@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=plunky@rya-online.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;
as well as URLs for NNTP newsgroup(s).