btsco and Nokia HDW-3 headset not working
Hi all,
I am trying to get btsco working with my Nokia HDW-3 headset so I can use skype from linux. I am can use skype under Windoze at the moment with the headset and dongle so I know this setup works.
The thing is, I can connect and pair with the headset under linux. I can even control the volume in alsamixer using the headset controls. I just can't get any sound! For example if I configure XMMS to use the headset as output it simply doesn't play.
I have included the following output suggested to assist with debugging from http://bluetooth-alsa.sourceforge.net.
The output of hciconfig hci0 -a:
hci0: Type: USB
BD Address: 00:10:60:AC:B0:7A ACL MTU: 377:10 SCO MTU: 16:0 UP RUNNING PSCAN ISCAN
RX bytes:1394 acl:36 sco:0 events:62 errors:0
TX bytes:849 acl:23 sco:0 commands:25 errors:0
Features: 0xff 0xfe 0x0d 0x38 0x08 0x08 0x00 0x00 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Name: 'Athos'
Class: 0x000100
Service Classes: Unspecified
Device Class: Computer, Uncategorized
HCI Ver: 1.2 (0x2) HCI Rev: 0x1 LMP Ver: 1.2 (0x2) LMP Subver:0x6963
Manufacturer: Broadcom Corporation (15)
athos root # hciconfig hci0 revsion
hci0: Type: USB
BD Address: 00:10:60:AC:B0:7A ACL MTU: 377:10 SCO MTU: 16:0
UP RUNNING PSCAN ISCAN
RX bytes:1671 acl:36 sco:0 events:65 errors:0
TX bytes:858 acl:23 sco:0 commands:28 errors:0So I think this dongle should be fine right?
Now when I try to connect I get the following:
athos root # sdptool search --bdaddr 00:03:89:67:8F:F7 0x1108 Class 0x1108
Searching for 0x1108 on 00:03:89:67:8F:F7 ... Service Name: Headset
Service RecHandle: 0x10000
Service Class ID List:
"Headset" (0x1108)
"Generic Audio" (0x1203)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 1
Profile Descriptor List:
"Headset" (0x1108)
Version: 0x0100
athos root # btsco 00:03:89:67:8F:F7 1
Device is 2:0
Voice setting: 0x0060
RFCOMM channel 1 connected
recieved AT+CKPD=200
opened hwdep
connected SCO channel
Setting sco fd
Done setting sco fd
recieved AT+VGS=15
Sending up speaker change 15
recieved AT+VGS=11
Sending up speaker change 11
recieved AT+VGS=09
Sending up speaker change 9
recieved AT+VGS=08
Sending up speaker change 8
recieved AT+VGS=09
Sending up speaker change 9
recieved AT+VGS=11
Sending up speaker change 11
recieved AT+VGS=15
That last bit is me fiddling with the volume controls on the headset.
athos root # hcitool info 00:03:89:67:8F:F7 (headset address) Requesting information ...
BD Address: 00:03:89:67:8F:F7
Device Name: Nokia HDW-3
LMP Version: 1.2 (0x2) LMP Subversion: 0x615
Manufacturer: Cambridge Silicon Radio (10)
Features: 0xbc 0x28 0x01 0x00 0x08 0x08 0x00 0x00
<encryption> <slot offset> <timing accuracy> <role
switch>
<sniff mode> <SCO link> <HV3 packets> <CVSD> <AFH cap.
slave>
<AFH cap. master>
athos root # hcidump -X
HCIDump - HCI packet analyzer ver 1.12
device: hci0 snap_len: 1028 filter: 0xffffffffffffffff
Quoted 2 lines
ACL data: handle
0x0006flags0x02dlen 17
ACL data: handle0x0006flags0x01dlen 2
L2CAP(d): cid 0x0040 len 15 [psm 0]
0000: 09 ff 15 01 41 54 2b 56 47 53 3d 31 35 0d 5c
....AT+VGS=15.\
< ACL data: handle 0x0006 flags 0x02 dlen 14
L2CAP(d): cid 0x0048 len 10 [psm 0]
0000: 0b ef 0d 0d 0a 4f 4b 0d 0a 9a .....OK...Quoted 1 line
HCI Event: Number of Completed Packets (
0x13) plen 5
0000: 01 06 00 01 00 .....
Quoted 2 lines
ACL data: handle
0x0006flags0x02dlen 17
ACL data: handle0x0006flags0x01dlen 2
L2CAP(d): cid 0x0040 len 15 [psm 0]
0000: 09 ff 15 01 41 54 2b 56 47 53 3d 31 31 0d 5c
....AT+VGS=11.\
< ACL data: handle 0x0006 flags 0x02 dlen 14
L2CAP(d): cid 0x0048 len 10 [psm 0]
0000: 0b ef 0d 0d 0a 4f 4b 0d 0a 9a .....OK...Quoted 1 line
HCI Event: Number of Completed Packets (
0x13) plen 5
0000: 01 06 00 01 00 .....
I am running gentoo linux with the following kernel:
athos root # uname -a
Linux athos.porthosnet.com 2.6.9-gentoo-r14 #11 Fri Mar 4 18:30:23 Local time zone must be set--see zic manu x86_64 AMD Athlon(tm) 64 Processor 3400+ AuthenticAMD GNU/Linux
net-wireless/bluez-libs
Latest version available: 2.10
Latest version installed: 2.10
Size of downloaded files: 261 kB
Homepage: http://bluez.sourceforge.net/
Description: Bluetooth Userspace Libraries
License: GPL-2
* net-wireless/bluez-utils
Latest version available: 2.10-r1
Latest version installed: 2.10-r1
Size of downloaded files: 283 kB
Homepage: http://bluez.sourceforge.net/
Description: bluetooth utilities
License: GPL-2
I appreciate any assistance you can provide.
Cheers,
James
Signature · 13 lines
It's 5.50 a.m.... Do you know where your stack pointer is ? ------------------------------------------------------- This SF.net email is sponsored by: 2005 Windows Mobile Application Contest Submit applications for Windows Mobile(tm)-based Pocket PCs or Smartphones for the chance to win $25,000 and application distribution. Enter today at http://ads.osdn.com/?ad_id=6882&alloc_id=15148&op=click _______________________________________________ Bluez-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bluez-devel
James
Quoted 1 line
athos root # sdptool search --bdaddr 00:03:89:67:8F:F7
0x1108
Do our docs still recommend this? The channel has been autodetected for some time.
Quoted 4 lines
athos root # btsco 00:03:89:67:8F:F7 1
Device is 2:0
Voice setting:0x0060
RFCOMM channel 1 connected
This is not the latest cvs version. It's silent unless you specify "-v" flag. Where did you get the kernel module and btsco daemon you are trying?
Quoted 5 lines
I am running gentoo linux with the following kernel:
athos root # uname -a
Linux athos.porthosnet.com 2.6.9-gentoo-r14 #11 Fri Mar 4 18:30:23 Local time zone must be set--see zic manux86_64AMD Athlon(tm) 64 Processor 3400+ AuthenticAMD GNU/Linux
It would really be a lot easier to debug if you were using the most recent kernel release (we don't have enough resources to maintiain several versions for what is supposed to be a stable kernel series)
Make sure you are using the integrated alsa, not the standalone that is distributed separately. IIRC, this came up because gentoo uses the standalone alsa.
Brad
-------------------------------------------------------
This SF.net email is sponsored by: 2005 Windows Mobile Application Contest Submit applications for Windows Mobile(tm)-based Pocket PCs or Smartphones for the chance to win $25,000 and application distribution. Enter today at
http://ads.osdn.com/?ad_id=6882&alloc_id=15148&op=click
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel
Hi Brad, thanks for your reply.
Quoted 4 lines · Brad Midgley
Quoted 1 line
athos root # sdptool search --bdaddr 00:03:89:67:8F:F7
0x1108Do our docs still recommend this? The channel has been autodetected for some time.
Not sure sorry, I copied this from a howto on the gentoo forums.
Quoted 7 lines
Quoted 4 lines
athos root # btsco 00:03:89:67:8F:F7 1
Device is 2:0
Voice setting:0x0060
RFCOMM channel 1 connectedThis is not the latest cvs version. It's silent unless you specify "-v" flag. Where did you get the kernel module and btsco daemon you are trying?
That may be the case, I built this a few weeks ago. I will update tonight. I am using an ebuild produced by someone in the gentoo community, however I am pretty sure it gets the kernel modules and btsco daemon source from cvs. I will check this and rebuild to see if that helps.
Quoted 3 lines
It would really be a lot easier to debug if you were using the most recent kernel release (we don't have enough resources to maintiain several versions for what is supposed to be a stable kernel series)
I understand, however as I am running an amd64 machine I prefer to use the gentoo sources as they have some amd64 specific patches applied.
Quoted 2 lines
Make sure you are using the integrated alsa, not the standalone that is distributed separately.
I am definately using the intergrated alsa.
Quoted 2 lines
IIRC, this came up because gentoo uses the
standalone alsa.
Actually I don't think this is the case any longer.
Thanks again,
James
-------------------------------------------------------
This SF.net email is sponsored by: 2005 Windows Mobile Application Contest Submit applications for Windows Mobile(tm)-based Pocket PCs or Smartphones for the chance to win $25,000 and application distribution. Enter today at
http://ads.osdn.com/?ad_id=6882&alloc_id=15148&op=click
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel
Quoted 9 lines · James Fitzsimons
Quoted 2 lines · Brad Midgley
This is not the latest cvs version. It's silent unless you specify "-v" flag. Where did you get the kernel module and btsco daemon you are trying?
That may be the case, I built this a few weeks ago. I will update tonight. I am using an ebuild produced by someone in the gentoo community, however I am pretty sure it gets the kernel modules and btsco daemon source from cvs. I will check this and rebuild to see if that helps.
Ok, I've just rebuilt using the latest cvs version. I am still having the same issue where I can connect to the headset, volume etc works, but no sound (eg from XMMS).
Output:
athos root # btsco -v 00:03:89:67:8F:F7
btsco v0.4
Device is 2:0
Voice setting: 0x0060
RFCOMM channel 1 connected
recieved AT+CKPD=200
speaker volume: 11 mic volume: 1
driver is in use
connected SCO channel
Done setting sco fd
recieved AT+VGS=15
Sending up speaker change 15
recieved AT+VGS=11
Sending up speaker change 11
recieved AT+VGS=15
Sending up speaker change 15
Any ideas?
Thanks very much for your help,
James
Signature · 13 lines
It's 5.50 a.m.... Do you know where your stack pointer is ? ------------------------------------------------------- This SF.net email is sponsored by Microsoft Mobile & Embedded DevCon 2005 Attend MEDC 2005 May 9-12 in Vegas. Learn more about the latest Windows Embedded(r) & Windows Mobile(tm) platforms, applications & content. Register by 3/29 & save $300 http://ads.osdn.com/?ad_id=6883&alloc_id=15149&op=click _______________________________________________ Bluez-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bluez-devel
James
Quoted 3 lines
Ok, I've just rebuilt using the latest cvs version. I am still having the same issue where I can connect to the headset, volume etc works, but no sound (eg from XMMS).
You're using the current kernel module too, right?
Try xmms with /dev/dsp1 as well as the alsa plughw:Headset output device.
I think I remember having troubles like this when my alsa configuration wasn't quite right, the alsa stuff wasn't run at bootup, or something like that. fwiw, my /etc/alsa/modutils/1.0 looks like:
# Example Configuration of ALSA 0.9 for Debian GNU/Linux
alias char-major-116 snd
alias char-major-14 soundcore
options snd major=116 cards_limit=2
alias sound-service-0-0 snd-mixer-oss
alias sound-service-0-1 snd-seq-oss
alias sound-service-0-3 snd-pcm-oss
alias sound-service-0-8 snd-seq-oss
alias sound-service-0-12 snd-pcm-oss
alias snd-card-0 snd_intel8x0
alias snd-card-1 snd_bt_sco
#alias snd-card-2 snd-share
#alias snd-card-3 snd-virmidi
alias sound-slot-0 snd-card-0
alias sound-slot-1 snd-card-1
alias sound-slot-2 snd-card-2
alias sound-slot-3 snd-card-3
Brad
-------------------------------------------------------
This SF.net email is sponsored by Microsoft Mobile & Embedded DevCon 2005 Attend MEDC 2005 May 9-12 in Vegas. Learn more about the latest Windows Embedded(r) & Windows Mobile(tm) platforms, applications & content. Register by 3/29 & save $300 http://ads.osdn.com/?ad_id=6883&alloc_id=15149&op=click
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel
Hi Brad,
Quoted 5 lines · Brad Midgley
Quoted 3 lines
Ok, I've just rebuilt using the latest cvs version. I am still having the same issue where I can connect to the headset, volume etc works, but no sound (eg from XMMS).
You're using the current kernel module too, right?
I think so. This is in cvs too right?
athos synce-librapi2-0.9.0 # modinfo snd_bt_sco
author: Jonathan Paisley <[email protected]> description: Bluetooth SCO Headset Soundcard license: GPL vermagic: 2.6.9-gentoo-r14 gcc-3.3
depends:
Quoted 3 lines
I think I remember having troubles like this when my alsa configuration wasn't quite right, the alsa stuff wasn't run at bootup, or something like that. fwiw, my
/etc/alsa/modutils/1.0looks like:
...
Ok, I changed a couple of things in my /etc/modules.d/alsa file now looks like yours (your /etc/alsa/modutils/1.0) but still no luck. It connects, but I can't get any sound.
What do I try next?
Cheers,
James
Signature · 1 line
It's 5.50 a.m.... Do you know where your stack pointer is ?