From: Lars Steinke <sf@lsweb.de>
To: bluez-users@lists.sourceforge.net
Cc: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] Re: btsco - headset profile activated but no sco packets transmitted ???
Date: Fri, 15 Apr 2005 14:16:33 +0200 [thread overview]
Message-ID: <20050415121633.GA4265@lsweb.de> (raw)
In-Reply-To: <20050415111207.GA4885@lsweb.de>
Phew, got it finally,
it was the bloody ehci_hcd audio problem others have come across:
http://sourceforge.net/mailarchive/message.php?msg_id=11431438
Using ohci_hcd, btsco works a treat in recording and playing, thanks for
the good work !!!
PS: Should others have trouble using the BT110, keep in mind it has very
stringent power saving and thus will turn off very soon after the last
audio packets have been transmitted (the confimation tone will notify you
of that) - btsco will then quit with "RFCOMM channel lost"...
Regards,
Lars
-------------------------------------------------------
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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-04-15 12:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-04 19:45 [Bluez-users] btsco - headset profile activated but no sco packets transmitted ??? Lars Steinke
2005-04-04 19:50 ` [Bluez-users] " Lars Steinke
2005-04-15 11:12 ` Lars Steinke
2005-04-15 12:16 ` Lars Steinke [this message]
2005-04-15 14:31 ` [Bluez-devel] " Brad Midgley
2005-04-04 20:00 ` [Bluez-users] " Brad Midgley
2005-04-04 21:22 ` Pavel Ruzicka
2005-04-13 5:38 ` Benny
2005-04-14 14:32 ` Pavel Ruzicka
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=20050415121633.GA4265@lsweb.de \
--to=sf@lsweb.de \
--cc=bluez-devel@lists.sourceforge.net \
--cc=bluez-users@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.