Cannot open shared library about bluez-alsa HOT 10 CLOSED

Is this /usr/lib/x86_64-linux-gnu/alsa-lib/libasound_module_pcm_bluealsa.so file present? Because it is rather strange location for alsa modules. You might try to copy the libasound_module_pcm_bluealsa.so file (from the ./build/src/asound/.libs/ directory) manually to this location.

from bluez-alsa.

Ok I found out that I had an alsa-lib directory in /usr/lib where it was stored and just had to move it from there. Now he finds the file but gets a further error:
aplay -D bluealsa:HCI=hci0,DEV=50:C9:71:B9:96:53,PROFILE=a2dp voice.wav ../../../src/asound/../shared/ctl-client.c:102: Connecting to socket: /var/run/bluealsa/hci0 ../../../src/asound/../shared/ctl-client.c:213: Getting transport for 50:C9:71:B9:96:53 type 1 ALSA lib ../../../src/asound/bluealsa-pcm.c:660:(_snd_pcm_bluealsa_open) Couldn't get BlueALSA transport: No such device aplay: main:722: audio open error: No such device
Does this mean that he doesnt find my bluetooth headset or is there something wrong with my Alsa?
(But I dont think that it is because of the headset since it is connected through bluetoothctl)
Edit: However I found out that my headset is still somehow in the pactl list and not showing up under aplay -L

from bluez-alsa.

BlueALSA and PulseAudio does not work together. See troubleshooting section in the readme.

from bluez-alsa.

Yeah i know that but why isnt the headset showing up under my alsa devices

from bluez-alsa.

BlueALSA does not expose BT devices via the kernel ALSA interface. It provides only a PCM software plugin. If you want your PCM to be displayed alongside aplay -L PCMs, you have to add hint description in the configuration file.

See:
http://alsa.opensrc.org/Asoundrc
http://alsa.opensrc.org/Plugin_Documentation

from bluez-alsa.

But still what does this error mean
ALSA lib ../../../src/asound/bluealsa-pcm.c:660:(_snd_pcm_bluealsa_open) Couldn't get BlueALSA transport: No such device aplay: main:788: audio open error: No such device

from bluez-alsa.

from bluez-alsa.

amixer -D bluealsa ../../../src/asound/../shared/ctl-client.c:102: Connecting to socket: /var/run/bluealsa/hci0 ../../../src/asound/../shared/ctl-client.c:125: Subscribing for notifications: true

Simple mixer control 'Jabra STEALTH a1.2 | Battery',0 Capabilities: pvolume pvolume-joined Playback channels: Mono Limits: Playback 0 - 9 Mono: Playback 0 [0%]

Simple mixer control 'Jabra STEALTH a1.20.0 - SCO',0 Capabilities: pvolume pvolume-joined cvolume cvolume-joined pswitch pswitch-joined cswitch cswitch-joined Playback channels: Mono Capture channels: Mono Limits: Playback 0 - 15 Capture 0 - 15 Mono: Playback 15 [100%] [on] Capture 15 [100%] [on]
Ok now I see my BT device but still cant play any sound

from bluez-alsa.

Ok I got the headset working now, only problem is that the headset always disconnects after I played a sound or recorded something. Also the recordings have a really disturbing sough.

from bluez-alsa.

/ # aplay 0.pcm
aplay: symbol 'eventfd_read': can't resolve symbol
aplay: symbol 'eventfd_write': can't resolve symbol
ALSA lib dlmisc.c:254:(snd1_dlobj_cache_get) Cannot open shared library /lib/alsa-lib/libasound_module_pcm_bluealsa.so
aplay: main:786: audio open error: No such device or address
/ # ls /lib/alsa-lib/libasound_module_pcm_bluealsa.so
/lib/alsa-lib/libasound_module_pcm_bluealsa.so
alsa-lib 1.1.1 and alsa-util1.1.1

from bluez-alsa.