From: Chris Carlin <carlin@jlab.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] RE : Plugz, a2dpd, and a2dpd2 strangeness
Date: Fri, 27 Apr 2007 14:49:12 -0400 [thread overview]
Message-ID: <463245A8.1020804@jlab.org> (raw)
In-Reply-To: <46321D59.5050503@access-company.com>
Well there are things that make me think it almost works. For example,
a2play under btsco basically worked, and if I force the chirps to occur
quickly enough (by pausing and unpausing the player's process... each
cycle causes a chirp) they merge into music. To my uninformed mind this
suggests that plugz might work with the headphones if it would just send
the data.
So perhaps just to satisfy my own curiosity, why is a2dp not sending any
data over bluetooth, as shown through hcidump? Is it waiting for some
sort of acknowledgment from the headset?
And what's the status of a2dpd versus a2dpd2?
~Chris
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-04-27 18:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-27 1:28 [Bluez-devel] Plugz, a2dpd, and a2dpd2 strangeness Chris Carlin
2007-04-27 4:03 ` Brad Midgley
2007-04-27 6:18 ` [Bluez-devel] RE : " Frederic Dalleau
2007-04-27 14:37 ` Chris Carlin
2007-04-27 15:57 ` Frederic Dalleau
2007-04-27 18:49 ` Chris Carlin [this message]
2007-04-27 14:26 ` [Bluez-devel] " Chris Carlin
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=463245A8.1020804@jlab.org \
--to=carlin@jlab.org \
--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;
as well as URLs for NNTP newsgroup(s).