[Bluez-users] Hama BT1000 Headset Problems

[Bluez-users] Hama BT1000 Headset Problems

[Tobias Lang]

[-- Attachment #1: Type: text/plain, Size: 4293 bytes --]

I have a problem using Bluetooth with a Hama BT1000 Headset.
I installed th elatest Bluez Version (2.17) and the snd-bt-sco driver
via cvs. I followed the instructions on how to install the bt-sco module
and userland program and everything worked fine.
I already searched the archives, but found nothing helpful.

The first problem I encountered was, that I am not able to pair the HS
with my computer. I put the HS in pairing mode and run the command:

	btsco <headset> -v

Then I get the following:

	btsco v0.4b
	Device is 1:0
	Error: Failed to connect to SDP server: Invalid exchange
	Assuming channel 2

	Voice setting: 0x0060
	Can't connect RFCOMM channel: Invalid exchange

However, when I ignore the fact, that I haven't paired yet I can still connect the HS
just as I would have done and I am able to start xmms playback. However, I don't
hear a sound on the HS and xmms freezes after the 1 second of playback. Although
the Status LED on the HS indicates data transfer and I can change the volume. This
is what the userland program says:

	:~$ btsco 00:0B:2E:06:15:74 -v
	btsco v0.4b
	Device is 1:0
	Voice setting: 0x0060
	RFCOMM channel 6 connected
	speaker volume: 15 mic volume: 15
	i/o needed: connecting sco...
	connected SCO channel
	Done setting sco fd
	recieved AT+VGS=15
	Sending up speaker change 15
	recieved AT+VGS=14
	Sending up speaker change 14
	recieved AT+VGS=14
	speaker volume: 15 mic volume: 15
	driver is not in use
	disconnected SCO channel
	speaker volume: 15 mic volume: 15
	i/o needed: connecting sco...
	Can't connect SCO audio channel
	: Connection timed out
	speaker volume: 15 mic volume: 15
	RFCOMM channel lost

Don't really now, what is happening. But it somehow seems, that the audio-data never reaches the headset
(but that is simply a guess from someone not knowing whats going on).A yes, I get the same, when I am
doing an 'aplay' like mentioned in the README.

Here are some additional infos:

/var/log/messages:
	May 15 14:19:07 localhost kernel: snd-bt-sco: playback_open
	May 15 14:19:07 localhost kernel: snd-bt-sco: prepare ok bps: 16000 size: 8000 count: 800
	May 15 14:19:07 localhost kernel: snd-bt-sco: prepare ok bps: 16000 size: 8000 count: 800
	May 15 14:19:07 localhost kernel: snd-bt-sco: playback_trigger 1
	May 15 14:19:07 localhost kernel: snd-bt-sco: setting playback to bspcm
	May 15 14:19:44 localhost kernel: snd-bt-sco: playback_trigger 0
	May 15 14:19:44 localhost kernel: snd-bt-sco: setting playback to NULL
	May 15 14:19:44 localhost kernel: snd-bt-sco: Disposing of previous socket count 2
	May 15 14:19:44 localhost kernel: snd-bt-sco: playback_open
	May 15 14:19:44 localhost kernel: snd-bt-sco: prepare ok bps: 16000 size: 8000 count: 800
	May 15 14:19:44 localhost kernel: snd-bt-sco: prepare ok bps: 16000 size: 8000 count: 800
	May 15 14:19:44 localhost kernel: snd-bt-sco: playback_trigger 1
	May 15 14:19:44 localhost kernel: snd-bt-sco: setting playback to bspcm
	May 15 14:19:51 localhost kernel: snd-bt-sco: playback_trigger 0
	May 15 14:19:51 localhost kernel: snd-bt-sco: setting playback to NULL

>: hciconfig -a
	hci0:   Type: USB
	        BD Address: 00:0B:0D:04:BB:98 ACL MTU: 120:20 SCO MTU: 64:0
	        UP RUNNING PSCAN ISCAN
	        RX bytes:187 acl:0 sco:0 events:22 errors:0
	        TX bytes:353 acl:0 sco:0 commands:18 errors:0
	        Features: 0xff 0xff 0x05 0x38 0x18 0x18 0x00 0x00
	        Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
	        Link policy: RSWITCH HOLD SNIFF PARK
 	       Link mode: SLAVE ACCEPT
 	       Name: 'melchior-0'
 	       Class: 0x000100
 	       Service Classes: Unspecified
	       Device Class: Computer, Uncategorized
  	       HCI Ver: 1.2 (0x2) HCI Rev: 0x0 LMP Ver: 1.2 (0x2) LMP Subver: 0x757
   	       Manufacturer: Silicon Wave (11)

>: hciconfig hci0 revision
	hci0:   Type: USB
 	       BD Address: 00:0B:0D:04:BB:98 ACL MTU: 120:20 SCO MTU: 64:0
  	      Unsupported manufacturer

>: hcitool info 00:0B:2E:06:15:74
	Requesting information ...
	Can't create connection: Input/output error

One last thing. The USB Bluetooth Dongle(Class II) is working. I can share data with my
mobile phone just fine.

Thanks for your help, Tobias Lang

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [Bluez-users] Hama BT1000 Headset Problems

[Brad Midgley]

Tobias

>>: hciconfig hci0 revision
> 
> 	hci0:   Type: USB
>  	       BD Address: 00:0B:0D:04:BB:98 ACL MTU: 120:20 SCO MTU: 64:0
>   	      Unsupported manufacturer

the docs now state that if you don't see SCO mapping info at all, you 
may need a different (CSR) adapter.

the fact that the adapter can pass data to your phone doesn't 
necessarily mean it's able to pass SCO audio properly.

Brad


-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_id=7393&alloc_id=16281&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] Hama BT1000 Headset Problems

[Brad Midgley]

Tobias

> However, when I ignore the fact, that I haven't paired yet

this sounds strange. when you click the connect button on the headset, 
what does btsco print out?

brad


-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_id=7393&alloc_id=16281&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] Hama BT1000 Headset Problems

[Tobias Lang]

[-- Attachment #1: Type: text/plain, Size: 903 bytes --]

On Sun, 15 May 2005 08:51:37 -0600
Brad Midgley <bmidgley@xmission.com> wrote:

> Tobias
> 
> > However, when I ignore the fact, that I haven't paired yet
> 
> this sounds strange. when you click the connect button on the headset, 
> what does btsco print out?
> 
> brad

The print out is like this:
$~: btsco 00:0B:2E:06:15:74 -v
	btsco v0.4b
	Device is 1:0
	Voice setting: 0x0060
	RFCOMM channel 6 connected
	speaker volume: 15 mic volume: 15
	i/o needed: connecting sco...
	connected SCO channel
	Done setting sco fd
	recieved AT+VGS=15                                 #Changeing Volume
	Sending up speaker change 15
	recieved AT+CKPD=200                              #When pressing the HS button

I also get one beep out of the HS, when starting XMMS playback via ALSA. However the
playback doesn't really start. The timecode on the XMMS player stops after 1sec.

Tobi

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [Bluez-users] Hama BT1000 Headset Problems

[Brad Midgley]

Tobias,

My first guess was the the SCO routing was not right for your adapter, 
but if the audio player is blocking on a write, then it's somewhere else.

Again, it could be that the linux drivers don't support audio on your 
adapter.

Brad

Tobias Lang wrote:
> On Sun, 15 May 2005 08:51:37 -0600
> Brad Midgley <bmidgley@xmission.com> wrote:
> 
> 
>>Tobias
>>
>>
>>>However, when I ignore the fact, that I haven't paired yet
>>
>>this sounds strange. when you click the connect button on the headset, 
>>what does btsco print out?
>>
>>brad
> 
> 
> The print out is like this:
> $~: btsco 00:0B:2E:06:15:74 -v
> 	btsco v0.4b
> 	Device is 1:0
> 	Voice setting: 0x0060
> 	RFCOMM channel 6 connected
> 	speaker volume: 15 mic volume: 15
> 	i/o needed: connecting sco...
> 	connected SCO channel
> 	Done setting sco fd
> 	recieved AT+VGS=15                                 #Changeing Volume
> 	Sending up speaker change 15
> 	recieved AT+CKPD=200                              #When pressing the HS button
> 
> I also get one beep out of the HS, when starting XMMS playback via ALSA. However the
> playback doesn't really start. The timecode on the XMMS player stops after 1sec.
> 
> Tobi


-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_id=7393&alloc_id=16281&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] Hama BT1000 Headset Problems

[Tobias Lang]

[-- Attachment #1: Type: text/plain, Size: 335 bytes --]

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

> Tobias,
> 
> My first guess was the the SCO routing was not right for your adapter, 
> but if the audio player is blocking on a write, then it's somewhere else.

But where are talking about the USB Dongle and not the Headset, are we?

Tobias

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [Bluez-users] Hama BT1000 Headset Problems

[Brad Midgley]

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

Tobias Lang wrote:
> On Sun, 15 May 2005 13:18:57 -0600
> Brad Midgley <bmidgley@xmission.com> wrote:
> 
> 
>>Tobias,
>>
>>My first guess was the the SCO routing was not right for your adapter, 
>>but if the audio player is blocking on a write, then it's somewhere else.
> 
> 
> But where are talking about the USB Dongle and not the Headset, are we?
> 
> Tobias


-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_id=7393&alloc_id=16281&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] Hama BT1000 Headset Problems

[Tobias Lang]

[-- Attachment #1: Type: text/plain, Size: 1296 bytes --]

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

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [Bluez-users] Hama BT1000 Headset Problems

[Tobias Lang]

[-- Attachment #1: Type: text/plain, Size: 635 bytes --]

On Wed, 18 May 2005 16:21:06 -0600
Brad Midgley <bmidgley@xmission.com> wrote:

> i don't know how solid our command-line processing is, so try btsco with 
> the -v before the address.
> 

Still makes no difference.
Userland output in Normal-Mode:

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

	Voice setting: 0x0060
	Can't connect RFCOMM channel: Resource temporarily unavailable

And in Pairing-Mode:

~$ btsco -v <headset>
	btsco v0.4b
	Device is 1:0
	Voice setting: 0x0060
	Can't connect RFCOMM channel: Permission denied

Regards, Tobi

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]