Arch Linux

harubyy

Member

Registered: 2017-03-09

Posts: 26

[RESOLVED] bluetooth headset connects, only system sounds

Hello all,
I have a taotronics bluetooth headset. I see that it's connected and I can receive the system sounds but I cannot hear any other sound coming from audio/video.

I changed the configuration to both HSP/HFP and A2DP on pavucontrol configuratin tab to try. But no luck.

Any help is appreciated.

Last edited by harubyy (2018-11-28 15:41:18)

Mr.Elendig

#archlinux@freenode channel op

From: The intertubes

Registered: 2004-11-07

Posts: 4,097

Re: [RESOLVED] bluetooth headset connects, only system sounds

Check the output routing in the mixer.

---

Evil #archlinux@libera.chat channel op and general support dude.
. files on github, Screenshots, Random pics and the rest

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 25,431

Re: [RESOLVED] bluetooth headset connects, only system sounds

Did you also move the applications to the headset? Pulse remembers the last output device, if not configured differently every application will start out on your internal sound and only be moved on active action from your side. If you want this automated, so that everything should switch to your bluetooth headset when it becomes available you should add

load-module module-switch-on-connect

before the if...udev-detect line your /etc/pulse/default.pa

FWIW post the output of

sudo fuser -v /dev/snd/*
pacmd list-cards
pacmd list-sinks
pacmd list-sink-inputs

during playback of an application you expect to hear.

harubyy

Member

Registered: 2017-03-09

Posts: 26

Re: [RESOLVED] bluetooth headset connects, only system sounds

Thanks for the answers.

I have just realized using alsamixer that I had some muted channels. I couldn't figure it out through pavucontrol.

I'm marking it as solved

Last edited by harubyy (2018-11-28 15:37:01)

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 25,431

Re: [RESOLVED] bluetooth headset connects, only system sounds

? You shouldn't have an accessible alsa card on a default bluethooth setup if I'm not mistaken, unless you controlled the ALSA <--> pulse module, in which case this definitely will have been reflected in pavucontrol in some form as well. But whelp whatever works.