public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Roth <sebastian.roth@esk.fhg.de>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] Re: snd-bt-sco problem
Date: Tue, 07 Dec 2004 08:37:56 +0100	[thread overview]
Message-ID: <cp3mkk$m7t$1@sea.gmane.org> (raw)
In-Reply-To: <20041206225609.GA1177@zeus.galaxy.org.uk>

Hi Chris,

I'm new to this bluetooth things so please don't mind if my suggestions 
are not completely correct.

I've had some problems with my bluetooth headsets too.
The first problem was the dongle. I've used an usb-dongle from Anycom 
(Transilica chip). Exchanging the dongle with a D-Link DBT-120 
(Cambridge Silicon Radio chip) helped me because this chip routes the 
SCO data over HCI.
Please post the ouput of `hciconfig hci0 revision'

The second issue was that all "sound-apps" were blocking (hanging) 
without playing any sound. My headsets (both from Anycom) must be 
activated with the switch to recieve the sound. Just like answer the 
telephone.

Everone, please feel free to correct me if I'm wrong!

Best regards,
Sebastian



-------------------------------------------------------
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

  reply	other threads:[~2004-12-07  7:37 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 ` Sebastian Roth [this message]
2004-12-07  8:21   ` [Bluez-devel] " 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
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='cp3mkk$m7t$1@sea.gmane.org' \
    --to=sebastian.roth@esk.fhg.de \
    --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