Linux bluetooth development
 help / color / mirror / Atom feed
From: Brad Midgley <bmidgley@xmission.com>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Audio service class?
Date: Sun, 18 Sep 2005 21:47:49 -0600	[thread overview]
Message-ID: <432E34E5.3070704@xmission.com> (raw)
In-Reply-To: <200509181721.55295.mmarshall@myrealbox.com>

Matthew,

Device class on the host seems to be a first-level service advertisement 
queried by devices initiating a connection to the host. Device class, 
sdp record, and listening/server socket are all necessary to accept a 
new connection "cold" from the headset. We don't support this currently, 
but we should.

We do have a lot of trouble with dual boot systems or using a dongle on 
different hosts to talk to the same headset. Are you doing either of 
those? (we have some hints on bluetooth-alsa.sf.net)

You're putting the headset in pairing mode before the scan, right? Most 
sets flash between blue and red while in pairing mode.

Brad

Matthew Marshall wrote:
> On Sunday 18 September 2005 10:02 pm, Brad Midgley wrote:
> 
>>Matthew
>>
>>
>>>haven't been able get the dongle to pick up the headset.
>>
>>what does this mean? it isn't found by 'hcitool scan' or something?
> 
> 
> Yeah, that's what I mean.
> 
> 
>>>The class is set to 0x3e0100, but Audio is not included in the Service
>>>Classes list.  (I assume this is the reason why the headset is not being
>>>detected.)
>>
>>the host sets the service class mask--it's not a feature of the dongle.
> 
> 
> That's what I thought.  From the hcid.conf man page, I see that Audio is bit 6 
> which is set by 0x3e.  So why isn't Audio listed?  (For that matter, 0x3e 
> should also enable Object Transfer, which isn't in the list either.)  I tried 
> other classes as well, with no success.  (Such as 0x200100, which should give 
> me only Audio, but gives me nothing.)
> 
> Any clue what is causing this?
> 
> Thanks!
> 
> MWM
> 
> 
> -------------------------------------------------------
> SF.Net email is sponsored by:
> Tame your development challenges with Apache's Geronimo App Server. 
> Download it for free - -and be entered to win a 42" plasma tv or your very
> own Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users


-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. 
Download it for free - -and be entered to win a 42" plasma tv or your very
own Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2005-09-19  3:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-18 16:32 [Bluez-users] Audio service class? Matthew Marshall
2005-09-18 22:02 ` Brad Midgley
2005-09-18 17:21   ` Matthew Marshall
2005-09-19  3:47     ` Brad Midgley [this message]
2005-09-19 16:51       ` Matthew Marshall

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=432E34E5.3070704@xmission.com \
    --to=bmidgley@xmission.com \
    --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