From: martin f krafft <madduck@madduck.net>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] btusb+sco failing to play sound through Jabra BT500v headset (was: SCO flowcontrol patch v4.4 on 2.6.25/6 causes) hardlocks when connecting to BT device
Date: Tue, 26 Aug 2008 17:35:45 +0100 [thread overview]
Message-ID: <20080826163544.GA5068@lapse.rw.madduck.net> (raw)
In-Reply-To: <1219394015.7591.441.camel@violet.holtmann.net>
[-- Attachment #1.1: Type: text/plain, Size: 1461 bytes --]
also sprach Marcel Holtmann <marcel@holtmann.org> [2008.08.22.0933 +0100]:
> what about not using that patch at all? I am using the new audio
> interface without that patch. And you wanna use the btusb driver
> and since 2.6.27-rc4 that one actually has SCO support.
If I had known... :)
Unfortunately, I have not yet succeeded. I modprobed 'sco' and then
ran headsetd as before, but that just prints
headsetd[9417]: Bluetooth headset daemon version 0.5
headsetd[9417]: Configuration phase ended: target bdaddr is 00:1A:45:14:EE:D7, timeout is 90000 ms
headsetd[9417]: Changing state: Idle-->Paging
headsetd[9417]: Changing state: Paging-->Connecting
headsetd[9417]: Changing state: Connecting-->Ready
headsetd[9417]: Changing state: Ready-->Opening
At this point, the headset makes the sound it makes when
a connection is established, but there is no sound coming from it.
After about 40 seconds, the client says:
aplay: main:564: audio open error: Connection timed out
and headsetd writes:
headsetd[9417]: unable to open SCO channel to headset: Connection timed out
headsetd[9417]: Changing state: Opening-->ZombieAppl
headsetd[9417]: Appli closed socket
headsetd[9417]: Changing state: ZombieAppl-->Idle
So something's still broken... :(
--
martin | http://madduck.net/ | http://two.sentenc.es/
never underestimate the power of human stupidity.
spamtraps: madduck.bogus@madduck.net
[-- Attachment #1.2: Digital signature (see http://martin-krafft.net/gpg/) --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
[-- Attachment #2: Type: text/plain, Size: 363 bytes --]
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2008-08-26 16:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-22 7:36 [Bluez-devel] SCO flowcontrol patch v4.4 on 2.6.25/6 causes hardlocks when connecting to BT device martin f krafft
2008-08-22 8:33 ` Marcel Holtmann
2008-08-26 16:35 ` martin f krafft [this message]
2008-08-26 17:19 ` [Bluez-devel] btusb+sco failing to play sound through Jabra BT500v headset (was: SCO flowcontrol patch v4.4 on 2.6.25/6 causes) " Marcel Holtmann
2008-08-26 20:34 ` martin f krafft
2008-08-27 5:18 ` Marcel Holtmann
2008-08-27 21:03 ` martin f krafft
2008-09-05 16:26 ` [Bluez-devel] "unable to install hw params" to bluetooth (SCO) headset (was: btusb+sco failing to play sound through Jabra BT500v headset) martin f krafft
2008-09-05 17:00 ` Marcel Holtmann
2008-09-08 20:33 ` martin f krafft
2008-09-23 13:00 ` [Bluez-devel] "unable to install hw params" to bluetooth (SCO) headset martin f krafft
2008-09-23 13:37 ` Stuart Pook
2008-09-29 21:41 ` SCO headset, bluez-4.9 & linux 2.6.27-rc7 -> Unable to install hw params Stuart Pook
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=20080826163544.GA5068@lapse.rw.madduck.net \
--to=madduck@madduck.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox