From: Brad Midgley <bmidgley@xmission.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] snd-bt-sco problem
Date: Tue, 07 Dec 2004 20:10:33 -0700 [thread overview]
Message-ID: <41B670A9.4030804@xmission.com> (raw)
In-Reply-To: <20041206225609.GA1177@zeus.galaxy.org.uk>
Chris,
Did it start working when you clicked the 'connect' button on the
headset? Sebastian pointed out that this was something one might miss so
I highlighted it recently in the docs.
Brad
Chris Boyle wrote:
> Hi, I can't get snd-bt-sco (bluetooth-alsa) to work and was told this
> was the best place to ask for help:
>
> The problem is, btsco starts up successfully, the device indicates a
> connection has been made, but no audio can be read or written, and after
> maybe a minute the device indicates the connection has been dropped.
> There is no noticeable difference on the host side at this point, i.e.
> audio apps directed at the headset still just hang, and btsco is still
> there. The mixer produces output from btsco, but has no effect on the
> device.
>
> Driver version: bluetooth-alsa CVS checked out 02/12/2004
> Kernel: 2.6.9 debian (presence / absence of hci_usb patch seems to make
> no difference)
> Host bluetooth adapter: Trust BT180 USB
> http://www.trust.com/home/default.htm?viewpage=service/sss/preview.htm%3Fartnr%3D13853
> Headset: Logitech Mobile Bluetooth Headset
> http://www.thinkgeek.com/computing/speakers/headsets/65ff/
> Also tested: Nokia 6310i, various channels (this functionality works
> under windows)
>
> I'd be grateful for any hints you can give me.
>
> Thanks,
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-12-08 3:10 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-06 22:56 [Bluez-devel] snd-bt-sco problem Chris Boyle
2004-12-07 7:37 ` [Bluez-devel] " Sebastian Roth
2004-12-07 8:21 ` Marcel Holtmann
2004-12-07 9:06 ` [Bluez-devel] Problems with anycom usb dongle (was: snd-bt-sco problem) Sebastian Roth
2004-12-07 9:17 ` Marcel Holtmann
2004-12-07 13:13 ` [Bluez-devel] Re: Problems with anycom usb dongle Sebastian Roth
2004-12-07 13:22 ` Marcel Holtmann
2004-12-07 14:07 ` Sebastian Roth
2004-12-07 17:05 ` Marcel Holtmann
2004-12-08 8:59 ` Sebastian Roth
2004-12-08 9:06 ` Marcel Holtmann
2004-12-08 9:39 ` [Bluez-devel] CVS doubles suche.org
2004-12-08 9:48 ` Marcel Holtmann
2004-12-08 10:33 ` suche.org
2004-12-08 11:08 ` Marcel Holtmann
2004-12-08 11:46 ` [Bluez-devel] Re: Problems with anycom usb dongle Steven Singer
2004-12-08 12:00 ` Marcel Holtmann
2004-12-08 13:00 ` Steven Singer
2004-12-08 13:19 ` Marcel Holtmann
2004-12-08 11:53 ` Sebastian Roth
2004-12-08 10:34 ` [Bluez-devel] Re: snd-bt-sco problem Chris Boyle
2004-12-08 10:38 ` [Bluez-devel] Re[2]: " suche.org
2004-12-08 14:35 ` [Bluez-devel] " Lars Grunewaldt
2004-12-07 7:57 ` [Bluez-devel] " Marcel Holtmann
2004-12-08 10:24 ` Chris Boyle
2004-12-08 3:10 ` Brad Midgley [this message]
2004-12-08 10:26 ` Chris Boyle
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=41B670A9.4030804@xmission.com \
--to=bmidgley@xmission.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