On Sun, 15 May 2005 15:18:35 -0600
Brad Midgley <bmidgley@xmission.com> wrote:

> yes, the bluetooth adapter is more often the problem than the headset.
> 

Well, I tried the HS with a CSR Dongle:

~$ hciconfig -a
hci0:   Type: USB
        BD Address: 00:09:DD:10:75:75 ACL MTU: 192:8 SCO MTU: 64:8
        UP RUNNING PSCAN ISCAN
        RX bytes:235 acl:0 sco:0 events:28 errors:0
        TX bytes:393 acl:0 sco:0 commands:22 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: SLAVE ACCEPT
        Name: 'BlueZ (0)'
        Class: 0x3e0100
        Service Classes: Networking, Rendering, Capturing
        Device Class: Computer, Uncategorized
        HCI Ver: 1.1 (0x1) HCI Rev: 0x175 LMP Ver: 1.1 (0x1) LMP Subver: 0x175
        Manufacturer: Cambridge Silicon Radio (10)

But now, I am even not able to connect to the HS (both in pairing and normal mode)

~$ btsco <headset> -v
	btsco v0.4b
	Device is 1:0
	Error: Failed to connect to SDP server: Permission denied
	Assuming channel 2

	Voice setting: 0x0060
	Can't connect RFCOMM channel: Permission denied

Does this mean, the HS is not compatible, or is there anything else really wrong?

Regards, Tobi