From: James Fitzsimons <james.fitzsimons@gmail.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] btsco and Nokia HDW-3 headset not working
Date: Tue, 29 Mar 2005 21:20:42 +0000 [thread overview]
Message-ID: <1112131242.11558.9.camel@localhost> (raw)
In-Reply-To: <4241FBEE.9060408@xmission.com>
[-- Attachment #1: Type: text/plain, Size: 1069 bytes --]
Hi Brad,
On Wed, 2005-03-23 at 23:29, Brad Midgley wrote:
> > Ok, I've just rebuilt using the latest cvs version. I am still having
> > the same issue where I can connect to the headset, volume etc works, but
> > no sound (eg from XMMS).
>
> You're using the current kernel module too, right?
I think so. This is in cvs too right?
athos synce-librapi2-0.9.0 # modinfo snd_bt_sco
author: Jonathan Paisley <jp@dcs.gla.ac.uk>
description: Bluetooth SCO Headset Soundcard
license: GPL
vermagic: 2.6.9-gentoo-r14 gcc-3.3
depends:
> I think I remember having troubles like this when my alsa configuration
> wasn't quite right, the alsa stuff wasn't run at bootup, or something
> like that. fwiw, my /etc/alsa/modutils/1.0 looks like:
...
Ok, I changed a couple of things in my /etc/modules.d/alsa file now
looks like yours (your /etc/alsa/modutils/1.0) but still no luck. It
connects, but I can't get any sound.
What do I try next?
Cheers,
James
--
It's 5.50 a.m.... Do you know where your stack pointer is ?
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2005-03-29 21:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-22 21:59 [Bluez-devel] btsco and Nokia HDW-3 headset not working James Fitzsimons
2005-03-22 22:24 ` Brad Midgley
2005-03-23 12:38 ` James Fitzsimons
2005-03-23 23:18 ` James Fitzsimons
2005-03-23 23:29 ` Brad Midgley
2005-03-29 21:20 ` James Fitzsimons [this message]
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=1112131242.11558.9.camel@localhost \
--to=james.fitzsimons@gmail.com \
--cc=bluez-devel@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