public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: WiseLYNX <wiselynx.naima@fastwebnet.it>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] bluetooth headset - connects but no audio
Date: Wed, 19 Jan 2005 14:27:14 +0100	[thread overview]
Message-ID: <41EE6032.7070708@fastwebnet.it> (raw)
In-Reply-To: <41EE66A2.1040106@dark-reality.de>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

| Sounds like it might be the fault of the dongle, or the bluez stack has
| an issue with it. Did you try with M$windows?

no, nor I can try. my pc is M$ stuff free :)

| no, it's not patched with mh1. Best thing would be to use the vanilla
| kernel (i.e. get it directly from kernel.org) and patch it with -mh1
| patchset from bluez. I'm using gentoo, too, btw, so it should work this
| way.

I'd rather keeping the gentoo-dev kernel. isn't it possible to patch it?

| it should. You can use this as the simplest and fool-proof testing
| method, as it does not involve any alsa library stuff beyond the
| snd-bt-sco-kernel module itself, so there are not many other error
| sources than the dongle and the headself itself.

I'll have another try so..

| Maybe there's a problem with the hci_usb implementation for your dongle=
...

I'll try with another dongle when I'll be able to (it belongs to a
friend of mine, I should see him soon)

- --

=B0=B0=B0 Wise
~ O  LYNX

GPG key: http://wiselynx.interfree.it/wiselynx.naima.asc
MD5 checksum: http://wiselynx.interfree.it/wiselynx.naima.asc.md5

- -----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GE>$/IT/S d+ s: !a>? C++(+++)>$ U P>+ L++>++++ E--- W++ N ?o ?K w-- ?O ?M
?V>+ PS+ !PE Y+ PGP+ t- ?5 X- R+(*) tv- b+(++)>+++ DI(++) !D G e++ h!*@
r%>++ y-->+
- ------END GEEK CODE BLOCK------

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFB7mAxkYE9G6fXLlgRAun5AJ9mdIGObx0aPoUBuLj06NF+IDfmWQCfc7Ov
clpfM3jtfJh64bi2Ja4jMRE=3D
=3D7DWM
-----END PGP SIGNATURE-----


-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2005-01-19 13:27 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-19 10:41 [Bluez-devel] bluetooth headset - connects but no audio WiseLYNX
2005-01-19 12:22 ` Lars Grunewaldt
2005-01-19 11:55   ` WiseLYNX
2005-01-19 13:54     ` Lars Grunewaldt
2005-01-19 13:27       ` WiseLYNX [this message]
2005-01-19 15:26         ` Lars Grunewaldt
2005-01-19 14:08       ` WiseLYNX
2005-01-19 17:27         ` Lars Grunewaldt
2005-01-19 21:52           ` WiseLYNX
2005-01-20  1:40             ` Lars Grunewaldt
2005-01-20 10:23               ` WiseLYNX
2005-01-20 13:12                 ` Lars Grunewaldt
2005-01-26  7:46                   ` WiseLYNX
2005-01-26 11:41                     ` Lars Grunewaldt

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=41EE6032.7070708@fastwebnet.it \
    --to=wiselynx.naima@fastwebnet.it \
    --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