public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Lars Grunewaldt <lgw@dark-reality.de>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] bluetooth headset - connects but no audio
Date: Thu, 20 Jan 2005 14:12:00 +0100	[thread overview]
Message-ID: <41EFAE20.7010901@dark-reality.de> (raw)
In-Reply-To: <41EF869D.8020705@fastwebnet.it>

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

WiseLYNX wrote:
| | well it *should* work with this setup, as it works on my system with
| | stock 2.6.10 plus mh1 patches. Anything else special, like, are you
| | using an SMP kernel?
|
| no, ? just checked and SMP is disabled. it may be some issue with other
| settings, maybe in the bluetooth section?

Don't know, things are quite straight-forward in there. Activate sco
support...

|
| | Maybe it's a problem with your dongle, do you have access to another one
| | to test this? (local setup: epox bt-dg03 + sony/eri. hbh-35 headset)
|
| it could be of course. I'll have a try with the one (other productor,
| but same chipset I fear) of a friend of mine, but it won't be before
| next week. anyway, isn't it strange that the dongle works fine with
| other applications (I'm able to connect via gprs with my phone)?

No, because headsets use the sco data transmission, while most other
services should use rfcomm data channels. So it's quite possible that
while other things work well, there's a problem with the dongle when it
comes to the sco channels.

| I'll do some more experiments on my own, and I'll let you know if I
| understand something.

Would be great. Good luck! I'm out of ideas :(

- - Lars


- --
Lars Grunewaldt
* software development
* multimedia design
skills: C/C++/Java/PHP/(X)HTML/Flash/audio/video
web: http://www.dark-reality.de
mail: lgw@dark-reality.de
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFB764fQWC6DTWkDAoRAgHvAJ0RlLnR67/Itmv2slWQF84yME0tbQCdGS4/
xiujbR/82e4y4vdqH7/rW8c=
=pGrr
-----END PGP SIGNATURE-----


-------------------------------------------------------
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-20 13:12 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
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 [this message]
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=41EFAE20.7010901@dark-reality.de \
    --to=lgw@dark-reality.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