All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Pezzei <ben@webstuhl.net>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] Again: Problems with Dongle, Headset or btsco
Date: Fri, 21 Jan 2005 12:44:10 +0100	[thread overview]
Message-ID: <41F0EB0A.1020302@webstuhl.net> (raw)

Hi

I still try to use my Anycom 240 USB Dongle with the Plantronics 2500
Headset.  As Marcel stated in a previous Thread, this dongle looks
like to have an RSSI inquiry bug.

to make it short: shall I buy another dongle? And which one is known
to work without problems?

Here is the List what I did:

compile 2.6.10 Kernel (without patch-2.6.10-mh1.gz). In
previous trys I used the bluez libs and tools (compiled
them outside the kernel).

compile the latest btsco csv

btsco <addr> connects to the headset and i can change
the volume via the headset-button.

So i guess the rfcomm Communication is ok

But aplay -D plughw:Headset soundfile doesnt work.
either arecord ...
(btw: Should aplay ... be executed while btsco is connected
to the HS?)

weird thing: when using the hstest prog in bluez-utils i am
able to record _something_ but it's more or less static
(although the noises appear to be the spoken text - with
wrong frequency/speed).

Any Hints?

friendly regards
ben





-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

             reply	other threads:[~2005-01-21 11:44 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-21 11:44 Ben Pezzei [this message]
2005-01-21 13:07 ` [Bluez-devel] Again: Problems with Dongle, Headset or btsco Lars Grunewaldt
2005-01-21 16:08   ` Ben Pezzei
2005-01-21 17:04     ` Lars Grunewaldt
2005-01-21 17:14       ` mirko_3
2005-01-22 13:59       ` Ben Pezzei
2005-01-22 14:19         ` mirko_3
2005-01-22 14:40           ` ligi
2005-01-22 15:35         ` [Bluez-devel] " Paul Ionescu
2005-01-22 17:43           ` Ben Pezzei
2005-01-22 19:24             ` [Bluez-devel] " Paul Ionescu
2005-01-22 15:40         ` [Bluez-devel] " Sebastian Roth
2005-01-22 17:50           ` Ben Pezzei
2005-01-23 17:52             ` Lars Grunewaldt
2005-01-24 10:46               ` Ben Pezzei
2005-01-24 11:21                 ` Lars Grunewaldt
2005-01-24 12:20                   ` Marcel Holtmann
2005-02-02  5:00                     ` [Bluez-devel] " Jesse Guardiani

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=41F0EB0A.1020302@webstuhl.net \
    --to=ben@webstuhl.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.