linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Brouillet <marcel@brouillet.org>
To: linux-bluetooth@vger.kernel.org
Subject: [BlueAlsa] connected but no possibility to record or play
Date: Mon, 29 Jul 2019 21:52:34 +0200	[thread overview]
Message-ID: <545763ea-aa51-fe38-e6a7-c6e5dd6adefe@brouillet.org> (raw)

Hello,

I have compiled BlueAlsa from git, and followed the README.md.

I disabled pulseaudio (pavucontrol does not connect).

I am able to connect my phone and my linux computer (though only for 
phone-calls, not yet audio).

Bluealsa [as root] outputs the following and remains running :

bluealsa: bluez.c:1010: Called: org.bluez.Profile1.NewConnection()
bluealsa: bluez.c:931: RFCOMM: HSP Audio Gateway configured for device 
74:EB:80:E2:D7:E7
bluealsa: ba-transport.c:592: State transition: 0 -> 2
bluealsa: io.c:2052: Created new IO thread: RFCOMM: HSP Audio Gateway
bluealsa: rfcomm.c:597: Starting loop: RFCOMM: HSP Audio Gateway
bluealsa: ba-transport.c:592: State transition: 0 -> 2
bluealsa: io.c:2052: Created new IO thread: HSP Audio Gateway
bluealsa: io.c:1565: Starting IO loop: HSP Audio Gateway

I have no new device in aplay -l nor arecord -l [as user][nor as root].

I tried calling my phone. The phone displays the bluetooth symbol when 
presenting the call. I pickup the call and there is not output sound in 
the phone (so it seems it channels it through bluetooth).

As suggested in README.md I tried capturing sound which yields an error :

$ arecord -D bluealsa capture.wav

ALSA lib bluealsa-pcm.c:718:(_snd_pcm_bluealsa_open) Couldn't get 
BlueALSA PCM: Rejected send message, 1 matched rules; 
type="method_call", sender=":1.200" (uid=1000 pid=24653 comm="arecord -D 
bluealsa capture.wav " label="unconfined") 
interface="org.bluealsa.Manager1" member="GetPCMs" error name="(unset)" 
requested_reply="0" destination="org.bluealsa" (uid=0 pid=24471 
comm="bluealsa " label="unconfined")
arecord: main:788: audio open error: No such device

Similarly, playing a sound (not relying on my ~/.asoundrc)

$ aplay -D bluealsa:SRV=org.bluealsa,DEV=74:EB:80:E2:D7:E7,PROFILE=a2dp 
/usr/share/sounds/sound-icons/trumpet-1.wav
ALSA lib bluealsa-pcm.c:718:(_snd_pcm_bluealsa_open) Couldn't get 
BlueALSA PCM: Rejected send message, 1 matched rules; 
type="method_call", sender=":1.202" (uid=1000 pid=24698 comm="aplay -D 
bluealsa:SRV=org.bluealsa,DEV=74:EB:80:E2" label="unconfined") 
interface="org.bluealsa.Manager1" member="GetPCMs" error name="(unset)" 
requested_reply="0" destination="org.bluealsa" (uid=0 pid=24471 
comm="bluealsa " label="unconfined")
aplay: main:788: audio open error: No such device

Please help me with these questions :

- Is this more an Alsa issue or a Bluez issue ?

- Where can I get help ? (depending on the latter)

- What is my next debug step ?

- What should I do to allow also connection for general A2DP audio, not 
just phone calls ?

Thank you !!

Marcel.


                 reply	other threads:[~2019-07-29 21:08 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=545763ea-aa51-fe38-e6a7-c6e5dd6adefe@brouillet.org \
    --to=marcel@brouillet.org \
    --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;
as well as URLs for NNTP newsgroup(s).