From: Brad Midgley <bmidgley@xmission.com>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] Re: Headset with snd-bt-sco
Date: Tue, 29 Jun 2004 15:54:34 -0600 [thread overview]
Message-ID: <40E1E51A.3080106@xmission.com> (raw)
Hi
I get the same result when either using the bluetrek 1.0 headset or the
jabra 200 (upgraded to handsfree profile) headset.
Can anyone confirm that snd-bt-sco still works with the hbh-60? The
previous maintainer is not working on it any more unfortunately...
Brad
On 0, Lasse Jansen <l.jansen@gm...> wrote:
> Hi all,
> I have some problems with making my BT headset work. Bluetooth works, I
> can e.g. exchange files with my T610. For the Headset I downloaded the
> snd-bt-sco driver (http://www.dcs.gla.ac.uk/~jp/snd-bt-sco/),
> kernel-2.6.4 and alsa-1.0.3 as said in the README. Everything went fine,
> when I run
> | btsco-0.2/btsco 00:0D:FD:00:7B:CC 1
> I hear a little background noise. When I increase/decrease the volume at
> the headset, it will be printed on the screen, so there is a connection.
>
> But when I try to play a sound file, nothing happens. E.g.
> | aplay -D plughw:Headset /usr/kde/3.2/share/sounds/KDE_Logout_new.wav
> hangs in a loop. Xmms says "couldn"t open audio".
> I have deactivated the "loopback" option in the mixer settings.
>
> Any ideas?
--
Brad
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next reply other threads:[~2004-06-29 21:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-29 21:54 Brad Midgley [this message]
2004-07-07 18:36 ` [Bluez-users] Re: Headset with snd-bt-sco Brad Midgley
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=40E1E51A.3080106@xmission.com \
--to=bmidgley@xmission.com \
--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