From: SA <sa@claborn.net>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] How to setup a headset as an audio device? Getting "Device busy" errors
Date: Tue, 5 Feb 2008 16:11:46 -0600 [thread overview]
Message-ID: <200802051611.46542.sa@claborn.net> (raw)
In-Reply-To: <200802051546.45851.sa@claborn.net>
I just found out that this headset does not support HSP:
# sdptool search --bdaddr 00:0D:3C:6F:0E:89 HS
Searching for HS on 00:0D:3C:6F:0E:89 ...
#
sdptool search --bdaddr 00:0D:3C:6F:0E:89 HF
Searching for HF on 00:0D:3C:6F:0E:89 ...
Service Name: Hands-Free unit
Service RecHandle: 0x10000
Service Class ID List:
"Handsfree" (0x111e)
"Generic Audio" (0x1203)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 1
Language Base Attr List:
code_ISO639: 0x656e
encoding: 0x6a
base_offset: 0x100
Profile Descriptor List:
"Handsfree" (0x111e)
Version: 0x0101
It's a "Jawbone" headset, from jawbone.com. Good quality. Apparently bad
engineering or design.
JW
--
----------------------
System Administrator - Cedar Creek Software
http://www.cedarcreeksoftware.com
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2008-02-05 22:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-25 4:56 [Bluez-users] How to setup a headset as an audio device? Getting "Device busy" errors SA
2008-01-28 0:16 ` Eugene
2008-02-04 23:52 ` SA
2008-02-05 2:04 ` Leszek Koltunski
2008-02-05 18:29 ` SA
2008-02-05 18:33 ` SA
2008-02-05 18:41 ` Brad Midgley
2008-02-05 21:42 ` SA
2008-02-05 21:46 ` SA
2008-02-05 22:11 ` SA [this message]
2008-02-06 8:43 ` Guillaume Bedot
2008-02-06 1:47 ` jayjwa
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=200802051611.46542.sa@claborn.net \
--to=sa@claborn.net \
--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