From: Brad Midgley <bmidgley@xmission.com>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] bluetooth-alsa: a2recv stutteringsound from WM5.0 AKU2.0
Date: Tue, 06 Jun 2006 08:31:32 -0600 [thread overview]
Message-ID: <448591C4.9010102@xmission.com> (raw)
In-Reply-To: <96B7A15232D6CF42836BFD428AD6B6034E556A@deexmb01.de.icap.com>
Guido
>>argh... well i will try to run this test with my brother's aku2 device
>>this weekend and see if i can see the problem.
>
> Is there any progress?
sorry, I reported it in a new thread.
So when I tried things on an imate jamin aku2 device with a2dp hacked on
top, the audio sputtered a little bit at the start and then worked. It
sounded fine. fwiw, the codec settings it prints out upon connect are:
Channels=2, speed=44100 channel_mode = 2 allocation_method = 1 subbands
= 1 block_length = 1 min_bitpool = 48 max_bitpool = 48
I did run a2recv as a regular user, not root, so that may be why role
switch didn't work. It may be a good thing it didn't work... who knows.
One time it did disconnect on its own with the message "unsupported
signalling command: 9" but other than that, it worked as expected. I did
not play around with avrcp at all.
Brad
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2006-06-06 14:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-06 9:35 [Bluez-users] bluetooth-alsa: a2recv stutteringsound from WM5.0 AKU2.0 Guido Reimer
2006-06-06 14:31 ` Brad Midgley [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-06-07 6:16 Guido Reimer
2006-05-30 7:41 Guido Reimer
2006-05-30 6:30 Guido Reimer
2006-05-30 7:38 ` Brad Midgley
2006-05-29 7:42 Guido Reimer
2006-05-29 8:08 ` Brad Midgley
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=448591C4.9010102@xmission.com \
--to=bmidgley@xmission.com \
--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 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).