Return-Path: MIME-Version: 1.0 In-Reply-To: <1261563553.504805.2509.nullmailer@galant.ukfsn.org> References: <1261563553.504805.2509.nullmailer@galant.ukfsn.org> Date: Wed, 23 Dec 2009 16:40:17 +0530 Message-ID: Subject: Re: service search for headset From: bluezprofile kernel To: Iain Hibbert Cc: linux-bluetooth@vger.kernel.org Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-bluetooth-owner@vger.kernel.org List-ID: On Wed, Dec 23, 2009 at 3:49 PM, Iain Hibbert 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?