Nokia BH-801 why??

So got an other new headset with the hope it would work...

The nokia website sad it was bluetooth 2.0 instead of the 1.0 headset i first tried. But I does not work... Can somebody please enlight me why?

Kind regards,

Jelle

sudo hciconfig -a
hci0: Type: USB
BD Address: 00:1B:DC:00:32:71 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN
RX bytes:967 acl:0 sco:0 events:27 errors:0
TX bytes:360 acl:0 sco:0 commands:26 errors:0
Features: 0xff 0xff 0x8f 0xfe 0x9b 0xf9 0x00 0x80
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Name: '[debian-eeepc] / BT Device 0'
Class: 0x080108
Service Classes: Capturing
Device Class: Computer, Server
HCI Ver: 2.0 (0x3) HCI Rev: 0xc5c LMP Ver: 2.0 (0x3) LMP Subver: 0xc5c
Manufacturer: Cambridge Silicon Radio (10)

sudo hciconfig hci0 features
hci0: Type: USB
BD Address: 00:1B:DC:00:32:71 ACL MTU: 310:10 SCO MTU: 64:8
Features: 0xff 0xff 0x8f 0xfe 0x9b 0xf9 0x00 0x80
<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> <paging scheme> <power control> <transparent SCO> <broadcast encrypt> <EDR ACL 2 Mbps> <EDR ACL 3 Mbps> <enhanced iscan> <interlaced iscan> <interlaced pscan> <inquiry with RSSI> <extended SCO> <EV4 packets> <EV5 packets> <AFH cap. slave> <AFH class. slave> <3-slot EDR ACL> <5-slot EDR ACL> <AFH cap. master> <AFH class. master> <EDR eSCO 2 Mbps> <EDR eSCO 3 Mbps> <3-slot EDR eSCO> <extended features>

sudo hciconfig hci0 -a
hci0: Type: USB
BD Address: 00:02:72:13:06:42 ACL MTU: 1017:8 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN
RX bytes:24916 acl:2019 sco:0 events:612 errors:0
TX bytes:1748434 acl:2133 sco:0 commands:39 errors:0
Features: 0xff 0xff 0x8d 0xfe 0x9b 0xf9 0x00 0x80
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Name: '[debian-eeepc] / BT Device 0'
Class: 0x080100
Service Classes: Capturing
Device Class: Computer, Uncategorized
HCI Ver: 2.0 (0x3) HCI Rev: 0x4000 LMP Ver: 2.0 (0x3) LMP Subver: 0x430e
Manufacturer: Broadcom Corporation (15)

sudo hciconfig hci0 features
hci0: Type: USB
BD Address: 00:02:72:13:06:42 ACL MTU: 1017:8 SCO MTU: 64:8
Features: 0xff 0xff 0x8d 0xfe 0x9b 0xf9 0x00 0x80
<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> <broadcast encrypt> <EDR ACL 2 Mbps> <EDR ACL 3 Mbps> <enhanced iscan> <interlaced iscan> <interlaced pscan> <inquiry with RSSI> <extended SCO> <EV4 packets> <EV5 packets> <AFH cap. slave>
<AFH class. slave> <3-slot EDR ACL> <5-slot EDR ACL> <AFH cap. master> <AFH class. master> <EDR eSCO 2 Mbps> <EDR eSCO 3 Mbps> <3-slot EDR eSCO> <extended features>

hcitool scan
Scanning ...

    00:53:53:FB:7E:9C   Nokia BH-801

sudo hcitool info 00:53:53:FB:7E:9C
Requesting information ...
BD Address: 00:53:53:FB:7E:9C
Device Name: Nokia BH-801
LMP Version: 2.0 (0x3) LMP Subversion: 0x212b
Manufacturer: Broadcom Corporation (15)
Features: 0xbc 0xfe 0x8f 0x7e 0x18 0x18 0x00 0x80
<encryption> <slot offset> <timing accuracy> <role switch> <sniff mode> <RSSI> <channel quality> <SCO link> <HV2 packets> <HV3 packets> <u-law log> <A-law log> <CVSD> <paging scheme> <power control> <transparent SCO> <broadcast encrypt> <EDR ACL 2 Mbps> <EDR ACL 3 Mbps> <enhanced iscan> <interlaced iscan> <interlaced pscan> <inquiry with RSSI> <AFH cap. slave> <AFH class. slave> <AFH cap. master> <AFH class. master> <extended features>

May 15 13:39:55 debian-eeepc hcid[8991]: Audio API: sending BT_GETCAPABILITIES_RSP
May 15 13:39:55 debian-eeepc hcid[8991]: Audio API: received BT_SETCONFIGURATION_REQ
May 15 13:39:55 debian-eeepc hcid[8991]: config sco - device = 00:53:53:FB:7E:9C access_mode = 1
May 15 13:39:57 debian-eeepc hcid[8991]: link_key_request (sba=00:02:72:13:06:42, dba=00:53:53:FB:7E:9C)
May 15 13:39:57 debian-eeepc kernel: hci_scodata_packet: hci0 SCO packet for unknown connection handle 1
May 15 13:39:57 debian-eeepc last message repeated 3 times
May 15 13:39:57 debian-eeepc kernel: hci_scodata_packet: hci0 SCO packet for unknown connection handle 1
May 15 13:39:57 debian-eeepc last message repeated 13 times
May 15 13:39:57 debian-eeepc hcid[8991]: Badly formated or unrecognized command: AT+CCWA=1
May 15 13:39:57 debian-eeepc hcid[8991]: Badly formated or unrecognized command: AT+COPS=3,0
May 15 13:39:57 debian-eeepc kernel: hci_scodata_packet: hci0 SCO packet for unknown connection handle 1
May 15 13:39:57 debian-eeepc last message repeated 2 times
May 15 13:39:57 debian-eeepc hcid[8991]: Badly formated or unrecognized command: AT+CMEE=1
May 15 13:39:57 debian-eeepc kernel: hci_scodata_packet: hci0 SCO packet for unknown connection handle 1
May 15 13:40:28 debian-eeepc last message repeated 10190 times

pcm.headset {
    type bluetooth
    #~ device 00:0D:18:A0:35:70
    device 00:53:53:FB:7E:9C # Nokia BH-801
    #~ device 00:0C:55:D1:C9:78 # Motorola S805
    #~ device 00:0D:FD:18:6E:3C # motorola s9
    #~ profile hifi
    profile voice
    #profile auto
}

pcm.softvol {
type softvol
slave.pcm headset
control.name Headset
control.card 0
}
pcm.!default {
#~ type hw
#~ card 0
type plug
slave.pcm softvol
}

-------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users

On Thu, 15 May 2008, Jelle de Jong wrote:

-> So got an other new headset with the hope it would work...
->
-> The nokia website sad it was bluetooth 2.0 instead of the 1.0 headset i first -> tried. But I does not work... Can somebody please enlight me why?

sudo hcitool info 00:53:53:FB:7E:9C
Requesting information ...
BD Address: 00:53:53:FB:7E:9C
Device Name: Nokia BH-801
LMP Version: 2.0 (0x3) LMP Subversion: 0x212b
Manufacturer: Broadcom Corporation (15)
Features: 0xbc 0xfe 0x8f 0x7e 0x18 0x18 0x00 0x80
<encryption> <slot offset> <timing accuracy> <role switch> <sniff mode> <RSSI> <channel quality> <SCO link> <HV2 packets>

Still looks like a plain SCO ^^^^^^^

<HV3 packets> <u-law log> <A-law log> <CVSD> <paging scheme> <power control> <transparent SCO> <broadcast encrypt> <EDR ACL 2 Mbps> <EDR ACL 3 Mbps> <enhanced iscan> <interlaced iscan> <interlaced pscan> <inquiry with RSSI> <AFH cap. slave> <AFH class. slave> <AFH cap. master> <AFH class. master> <extended features>

May 15 13:39:57 debian-eeepc hcid[8991]: Badly formated or unrecognized 
command: AT+CCWA=1
May 15 13:39:57 debian-eeepc hcid[8991]: Badly formated or unrecognized 
command: AT+COPS=3,0
May 15 13:39:57 debian-eeepc kernel: hci_scodata_packet: hci0 SCO packet for 
unknown connection
handle 1
May 15 13:39:57 debian-eeepc last message repeated 2 times
May 15 13:39:57 debian-eeepc hcid[8991]: Badly formated or unrecognized 
command: AT+CMEE=1
May 15 13:39:57 debian-eeepc kernel: hci_scodata_packet: hci0 SCO packet for 
unknown connection
handle 1
May 15 13:40:28 debian-eeepc last message repeated 10190 times

The error messages also look like those when eSCO gets sent to a SCO only device. Maybe it's possible for bluetooth 2.0 devices to still be SCO-only? I don't know the qualifications ...

-------------------------------------------------------------------------
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 [email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users

Yes, it seem so but does this feature <EDR ACL 3 Mbps> not indicate that its a 2.0 device?

Thanks in advance,

Jelle

-------------------------------------------------------------------------
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 [email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users

On Sun, 18 May 2008, Jelle de Jong wrote:

-> > The error messages also look like those when eSCO gets sent to a SCO only -> > device. Maybe it's possible for bluetooth 2.0 devices to still be SCO-only? -> > I don't know the qualifications ...
->
-> Yes, it seem so but does this feature <EDR ACL 3 Mbps> not indicate that its -> a 2.0 device?

I'm not sure, learning as I go. Did you try hardware compatibility lists (HCL), like the one at linuxquestions.org and other places? Maybe you could find what you need there, since then you know other linux users are using it with success.

-------------------------------------------------------------------------
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 [email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users