From: Tobias Lang <tobias-lang@gmx.de>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] Hama BT1000 Headset Problems
Date: Sun, 15 May 2005 14:50:42 +0200 [thread overview]
Message-ID: <20050515145042.70745815.tobias-lang@gmx.de> (raw)
[-- 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 --]
next reply other threads:[~2005-05-15 12:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-15 12:50 Tobias Lang [this message]
2005-05-15 14:47 ` [Bluez-users] Hama BT1000 Headset Problems Brad Midgley
2005-05-15 14:51 ` Brad Midgley
2005-05-15 17:20 ` Tobias Lang
2005-05-15 19:18 ` Brad Midgley
2005-05-15 20:35 ` Tobias Lang
2005-05-15 21:18 ` Brad Midgley
2005-05-18 14:31 ` Tobias Lang
[not found] ` <428BBFD2.7040304@xmission.com>
2005-05-19 12:39 ` Tobias Lang
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=20050515145042.70745815.tobias-lang@gmx.de \
--to=tobias-lang@gmx.de \
--cc=bluez-users@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