From: Daniel Andor <da209@cam.ac.uk>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] bluetooth headset
Date: Tue, 18 Jan 2005 11:45:11 +0000 [thread overview]
Message-ID: <200501181145.11573.da209@cam.ac.uk> (raw)
Hi,
Had success with connecting to my laptop's headset profile, but not before
figuring out that it doesn't work with the default channel 7, but needs to be
made to use channel 8:
Does't work:
$ ./btsco 00:0B:6B:58:92:E9
Device is 3:0
Voice setting: 0x0060
RFCOMM channel 7 connected
Does work:
$ ./btsco 00:0B:6B:58:92:E9 8
Device is 3:0
Voice setting: 0x0060
RFCOMM channel 8 connected
recieved AT+BRSF=22
recieved AT+CIND=?
opened hwdep
connected SCO channel
Setting sco fd
Done setting sco fd
recieved AT+CIND?
AT+CMER=3,0,0,1=15
Sending up speaker change 15
recieved AT+CHLD=?
recieved AT+CCWA=1
recieved AT+CLIP=1
Details:
$ uname -a
Linux pooh 2.6.9-2-k7 #1 Sat Jan 8 15:38:24 EST 2005 i686 GNU/Linux
$ sudo hciconfig -a
hci0: Type: USB
BD Address: 00:02:72:40:AD:56 ACL MTU: 192:8 SCO MTU: 64:8
UP RUNNING PSCAN ISCAN
RX bytes:9550635 acl:181 sco:187095 events:359 errors:0
TX bytes:9545657 acl:188 sco:187095 commands:98 errors:0
Features: 0xff 0xff 0x0f 0x00 0x00 0x00 0x00 0x00
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF PARK
Link mode: ACCEPT MASTER
Name: 'pooh'
Class: 0x100100
Service Classes: Object Transfer
Device Class: Computer, Uncategorized
HCI Ver: 1.1 (0x1) HCI Rev: 0x20d LMP Ver: 1.1 (0x1) LMP Subver: 0x20d
Manufacturer: Cambridge Silicon Radio (10)
$ sudo hciconfig hci0 revision
hci0: Type: USB
BD Address: 00:02:72:40:AD:56 ACL MTU: 192:8 SCO MTU: 64:8
HCI 16.4
Chip version: BlueCore02
Max key size: 56 bit
SCO mapping: HCI
$ sudo hcitool info 00:0B:6B:58:92:E9
Requesting information ...
BD Address: 00:0B:6B:58:92:E9
Device Name: HANNAH
LMP Version: 1.2 (0x2) LMP Subversion: 0x694a
Manufacturer: Broadcom Corporation (15)
Features: 0xff 0xff 0x0d 0x38 0x08 0x08 0x00 0x00
<3-slot packets> <5-slot packets> <encryption> <slot offset>
<timing accuracy> <role switch> <hold mode> <sniff mode>
<park state> <RSSI> <channel quality> <SCO link> <HV2 packets>
<HV3 packets> <u-law log> <A-law log> <CVSD> <power control>
<transparent SCO> <enhanced iscan> <interlaced iscan>
<interlaced pscan> <AFH cap. slave> <AFH cap. master>
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2005-01-18 11:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-18 11:45 Daniel Andor [this message]
2005-01-18 16:01 ` [Bluez-devel] bluetooth headset Brad Midgley
2005-01-18 21:13 ` [Bluez-devel] " Paul Ionescu
-- strict thread matches above, loose matches on Subject: below --
2006-01-26 7:41 [Bluez-devel] Bluetooth headset Poovern Govender
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=200501181145.11573.da209@cam.ac.uk \
--to=da209@cam.ac.uk \
--cc=bluez-devel@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