From: Ramagudi Naziir <naziirr@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: Re: bluetooth audio fails
Date: Mon, 16 Nov 2009 12:09:23 +0200 [thread overview]
Message-ID: <dfb262380911160209v42da3134y8e645b33ac65ccdb@mail.gmail.com> (raw)
In-Reply-To: <dfb262380911150431h79650f28kadea09c26aee811f@mail.gmail.com>
I have just tried that with bluez 3.36 and it works!
So - should I downgrade to bluez 3.36 ?
Can you just tell me how you would debug this ?
On Sun, Nov 15, 2009 at 2:31 PM, Ramagudi Naziir <naziirr@gmail.com> wrote:
> I have just tried that also with a Motorola H700 headset,
> and got exact same error message.
>
> (I also tried bluez 4.56 and got same error)
>
> please help me to debug this.
>
> thank you,
> naziirr
>
>
> On Sat, Nov 14, 2009 at 8:26 PM, Ramagudi Naziir <naziirr@gmail.com> wrote:
>> Hi all,
>>
>> Can anyone pls help me debug this:
>>
>> # aplay -D bluetooth /startup.wav
>> ALSA lib audio/pcm_bluetooth.c:1607:(audioservice_expect)
>> BT_GET_CAPABILITIES failed : Input/output error(5)
>> aplay: main:608: audio open error: Input/output error
>>
>> I'm running the latest bluez git sources with a 9xxPlantronics HFP headset.
>> I tried both "auto" and "voice" in .asoundrc:
>>
>> pcm.bluetooth {
>> type bluetooth
>> device mybdaddr
>> profile “voice”
>> }
>>
>>
>> Any idea what this could be and how to debug/fix it ?
>>
>> thank you
>> naziirr
>>
>
next prev parent reply other threads:[~2009-11-16 10:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-14 18:26 bluetooth audio fails Ramagudi Naziir
2009-11-15 12:31 ` Ramagudi Naziir
2009-11-16 10:09 ` Ramagudi Naziir [this message]
[not found] ` <1080565272.3913901258382253455.JavaMail.root@sz0149a.westchester.pa.mail.comcast.net>
2009-11-16 19:46 ` Ramagudi Naziir
[not found] <232854869.4251721258419865790.JavaMail.root@sz0149a.westchester.pa.mail.comcast.net>
[not found] ` <830792141.4253161258419999163.JavaMail.root@sz0149a.westchester.pa.mail.comcast.net>
2009-11-17 7:56 ` Ramagudi Naziir
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=dfb262380911160209v42da3134y8e645b33ac65ccdb@mail.gmail.com \
--to=naziirr@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
/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