From: Benjamin Eikel <benjamin@eikel.org>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] Re: Sucessfully paired and used Broadcom BT-Dongle an BTH-100 Headset
Date: Sun, 19 Feb 2006 18:45:47 +0100 [thread overview]
Message-ID: <200602191845.47384.benjamin@eikel.org> (raw)
Hello Florian,
I thought Broadcom chipsets and SCO audio is not possible with BlueZ. I am
using
a Belkin F8T008 USB dongle and a Logitech Mobile Pro Headset. I tried the
patch
you posted here and in my hciconfig the SCO MTU value changed too:
hciconfig hci0 revision
hci0: Type: USB
BD Address: D0:DO:NG:LE:00:00 ACL MTU: 377:10 SCO MTU: 64:8
Firmware 0.3 / 9
I connected the headset with
btsco -v 00:HE:AD:SE:T0:00
btsco v0.41
Device is 1:0
Voice setting: 0x0060
RFCOMM channel 1 connected
Using interface hci0
But I could not send any sound to the headset. I tried it already some months
ago and it is not working as I expected. The BlueZ developers told me at that
time that Broadcom dongles are not supported.
When I play a file with xmms or aplay, I get the following output from btsco:
speaker volume: 11 mic volume: 8
i/o needed: connecting sco...
connected SCO channel
Done setting sco fd
speaker volume: 11 mic volume: 8
driver is not in use
disconnected SCO channel
recieved AT+VGS=11
Sending up speaker change 11
Maybe you can give me any hint how you achieved the sound output with that
dongle.
Regards,
Benjamin Eikel
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
reply other threads:[~2006-02-19 17:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200602191845.47384.benjamin@eikel.org \
--to=benjamin@eikel.org \
--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;
as well as URLs for NNTP newsgroup(s).