How can I get sound in my wireless blue tooth headphone ?
If someone feels inclined, I could use help.
Not sure where you are on this Andy, but:
Did you make your adapter visible?
Is your sound output on headphones?
Did you mark your adapter trusted?
Can you connect to the headphones? Generally you do not pair anymore for headphones.
Bluetooth software installed and listed in Synpaitc:
What are you trying to get sound from? Web Browser? Music Player? Video Player? Anything else?
Let us know.
5 Likes
Is you system finding your USB card/dongle? Does it support Linux?
sudo lshw -C sound (lists your available sound cards/USB sound devices, including relevant drivers/chipsets)
Your headphones should give you a tone or sound when they connect, are you hearing that?
Do your headphones have a volume button? Is it turned all the way up to start?
Do you have something else to hook the headphones up to to see if they even work? A cell phone or friend or relatives Windows computer?
5 Likes
This does not show my blue tooth dongle. It functions fine as I use it with Amazon's Echo device which uses Bluetooth. I forgot what command lists it.
*-multimedia:0
description: Audio device
product: Kaveri HDMI/DP Audio Controller
vendor: Advanced Micro Devices, Inc. [AMD/ATI]
physical id: 1.1
bus info: pci@0000:00:01.1
logical name: card0
logical name: /dev/snd/controlC0
logical name: /dev/snd/hwC0D0
logical name: /dev/snd/pcmC0D3p
version: 00
width: 64 bits
clock: 33MHz
capabilities: pm pciexpress msi bus_master cap_list
configuration: driver=snd_hda_intel latency=0
resources: irq:34 memory:feb64000-feb67fff
*-usb
description: Video
product: Microsoft
vendor: Microsoft
physical id: 2
bus info: usb@3:2
logical name: card2
logical name: /dev/snd/controlC2
logical name: /dev/snd/pcmC2D0c
version: 1.03
capabilities: usb-2.00
configuration: driver=snd-usb-audio maxpower=500mA speed=480Mbit/s
*-multimedia:1
description: Audio device
product: FCH Azalia Controller
vendor: Advanced Micro Devices, Inc. [AMD]
physical id: 14.2
bus info: pci@0000:00:14.2
logical name: card1
logical name: /dev/snd/controlC1
logical name: /dev/snd/hwC1D0
logical name: /dev/snd/pcmC1D0c
logical name: /dev/snd/pcmC1D0p
logical name: /dev/snd/pcmC1D1p
logical name: /dev/snd/pcmC1D2c
version: 01
width: 64 bits
clock: 33MHz
capabilities: pm bus_master cap_list
configuration: driver=snd_hda_intel latency=32
resources: irq:16 memory:feb60000-feb63fff
~$
I don't think it supports Linux.
1 Like
Notice it supports Ubuntu in the description.
1 Like
I have already spent money on a bluetooth dongle that someone here recommended.
You can probably understand my hesitation at buying any more hardware.
There is a funny saying.
Fool me once, shame on you. Fool me twice, shame on me.
Andy, I am really sorry you continue to have problems. Let's try and start over a bit.
First of all, do you have bluetooth on your computer? If yes, have you tried connecting it without the dongle? The dongle is really only necessary if you are using a bluetooth headset and you want to talk through it. Otherwise, if you are just going to use it for output, you don't need it.
Regardless, bluetooth connections can be obnoxious, and frankly, as much as I love Linux, it can be a headache sometimes to get things working. For example, you might have multiple sound servers running with different apps running. The following command will show your sound servers:
inxi -A
Here is my output:
Audio:
Device-1: Intel Comet Lake PCH-LP cAVS driver: snd_hda_intel
API: ALSA v: k6.8.0-47-generic status: kernel-api
Server-1: PipeWire v: 1.0.5 status: active
As you can see, I just have ALSA to help the sound card communicate and PipeWire is the server. If you have a Server-2 as well, then there is a conflict and we will need to address that.
Regardless, here is a link with the definitive information on bluetooth and linux. Perhaps we can find a solution here.
2 Likes
I understand that, I am frugal myself, just trying to help.
1 Like
I will try the Cli methods first. I feel it is often easier than GUI methods that have a lot
of "bells and whistles. I need the Dongle for my Amazon Echo.
It can play my favorite disco and C/W music. It will help me relax while I track down how to get Redtooth going so I can send music from my home computer to my phone or a future bluetooth boombox.
Pulse audio is not showing anything bluetooth,
My phone paired with something.
It says "Connected for calls and audio."
On another screen, it offers buttons to unpair, disconnect, and rename.
Time for some music.
Waiting to connect to bluetoothd...[bluetooth]# Agent registered
[bluetooth]# power on
[bluetooth]# Changing power on succeeded
[bluetooth]# agent on
Agent is already registered
[bluetooth]# default-agent
[bluetooth]# Default agent request successful
[bluetooth]# scan on
[bluetooth]# SetDiscoveryFilter success
[bluetooth]# Discovery started
[bluetooth]# [CHG] Controller 5C:F3:70:AB:A6:36 Discovering: yes
[bluetooth]# [NEW] Device 72:0C:45:14:DE:18 72-0C-45-14-DE-18
[bluetooth]# [NEW] Device 78:02:B7:69:8D:97 P99
[bluetooth]# [NEW] Device 5E:10:CA:79:B7:4B 5E-10-CA-79-B7-4B
[bluetooth]# [CHG] Device 78:02:B7:69:8D:97 RSSI: 0xffffffb4 (-76)
[bluetooth]# [CHG] Device 78:02:B7:69:8D:97 ManufacturerData.Key: 0x0000 (0)
[bluetooth]# [CHG] Device 78:02:B7:69:8D:97 ManufacturerData.Value:
[bluetooth]# 78 02 b7 69 8d 97 x..i..
[bluetooth]# [DEL] Device 72:0C:45:14:DE:18 72-0C-45-14-DE-18
[bluetooth]# [NEW] Device 72:0C:45:14:DE:18 72-0C-45-14-DE-18
[bluetooth]# [NEW] Device BC:52:74:A2:91:19 Drew's A14
[bluetooth]# [DEL] Device 78:02:B7:69:8D:97 P99
[bluetooth]# [NEW] Device 78:02:B7:69:8D:97 P99
[bluetooth]# [CHG] Device 78:02:B7:69:8D:97 RSSI: 0xffffffb8 (-72)
BC:52:74:A2:91:192:74:A2:91:19
Invalid command in menu main: BC:52:74:A2:91:19
Use "help" for a list of available commands in a menu.
Use "menu <submenu>" if you want to enter any submenu.
Use "back" if you want to return to menu main.
[blueBC:52:74:A2:91:192:74:A2:91:19
Attempting to pair with BC:52:74:A2:91:19
[CHG] Device BC:52:74:A2:91:19 Connected: yes
[Drew's A14]# Request confirmation
[Drew's A14]# 1;39m[agent] Confirm passkey 616159 (yes/no): [DEL] Device 78:02:B7:69:8D:97 P99
[agent] Confirm passkey 616159 (yes/no): [DEL] Device 5E:10:CA:79:B7:4B 5E-10-CA-79-B7-4B
[agent] Confirm passkey 616159 (yes/no): [DEL] Device 72:0C:45:14:DE:18 72-0C-45-14-DE-18
[agent] Confirm passkey 616159 (yes/no): yes
[Drew's A14]# [CHG] Device BC:52:74:A2:91:19 Bonded: yes
[Drew's A14]# [CHG] Device BC:52:74:A2:91:19 Modalias: bluetooth:v0075p0100d0201
[Drew's A14]# [CHG] Device BC:52:74:A2:91:19 UUIDs: 00001105-0000-1000-8000-00805f9b34fb
[Drew's A14]# [CHG] Device BC:52:74:A2:91:19 UUIDs: 0000110a-0000-1000-8000-00805f9b34fb
[Drew's A14]# [CHG] Device BC:52:74:A2:91:19 UUIDs: 0000110c-0000-1000-8000-00805f9b34fb
[Drew's A14]# [CHG] Device BC:52:74:A2:91:19 UUIDs: 0000110e-0000-1000-8000-00805f9b34fb
[Drew's A14]# [CHG] Device BC:52:74:A2:91:19 UUIDs: 00001112-0000-1000-8000-00805f9b34fb
[Drew's A14]# [CHG] Device BC:52:74:A2:91:19 UUIDs: 00001115-0000-1000-8000-00805f9b34fb
[Drew's A14]# [CHG] Device BC:52:74:A2:91:19 UUIDs: 00001116-0000-1000-8000-00805f9b34fb
[Drew's A14]# [CHG] Device BC:52:74:A2:91:19 UUIDs: 0000111f-0000-1000-8000-00805f9b34fb
[Drew's A14]# [CHG] Device BC:52:74:A2:91:19 UUIDs: 0000112f-0000-1000-8000-00805f9b34fb
[Drew's A14]# [CHG] Device BC:52:74:A2:91:19 UUIDs: 00001132-0000-1000-8000-00805f9b34fb
[Drew's A14]# [CHG] Device BC:52:74:A2:91:19 UUIDs: 00001200-0000-1000-8000-00805f9b34fb
[Drew's A14]# [CHG] Device BC:52:74:A2:91:19 UUIDs: 00001800-0000-1000-8000-00805f9b34fb
[Drew's A14]# [CHG] Device BC:52:74:A2:91:19 UUIDs: 00001801-0000-1000-8000-00805f9b34fb
[Drew's A14]# [CHG] Device BC:52:74:A2:91:19 UUIDs: 931c7e8a-540f-4686-b798-e8df0a2ad9f7
[Drew's A14]# [CHG] Device BC:52:74:A2:91:19 UUIDs: a82efa21-ae5c-3dde-9bbc-f16da7b16c5a
[Drew's A14]# [CHG] Device BC:52:74:A2:91:19 ServicesResolved: yes
[Drew's A14]# [CHG] Device BC:52:74:A2:91:19 Paired: yes
[Drew's A14]# Pairing successful
[Drew's A14]# [CHG] Device BC:52:74:A2:91:19 ServicesResolved: no
[CHG] Device BC:52:74:A2:91:19 Connected: no
[bluetooth]# [NEW] Device 5E:10:CA:79:B7:4B 5E-10-CA-79-B7-4B
[bluetooth]# [NEW] Device 78:02:B7:69:8D:97 P99
[bluetooth]# [DEL] Device 5E:10:CA:79:B7:4B 5E-10-CA-79-B7-4B
[bluetooth]# [CHG] Device 78:02:B7:69:8D:97 RSSI: 0xffffffad (-83)
BC:52:74:A2:91:19A2:91:19
Invalid command in menu main: BC:52:74:A2:91:19
Use "help" for a list of available commands in a menu.
Use "menu <submenu>" if you want to enter any submenu.
Use "back" if you want to return to menu main.
[bluetooBC:52:74:A2:91:192:74:A2:91:19
Attempting to connect to BC:52:74:A2:91:19
[CHG] Device BC:52:74:A2:91:19 Connected: yes
[Drew's A14]# [NEW] Endpoint /org/bluez/hci0/dev_BC_52_74_A2_91_19/sep1
[Drew's A14]# [NEW] Endpoint /org/bluez/hci0/dev_BC_52_74_A2_91_19/sep2
[Drew's A14]# [NEW] Endpoint /org/bluez/hci0/dev_BC_52_74_A2_91_19/sep3
[Drew's A14]# [NEW] Endpoint /org/bluez/hci0/dev_BC_52_74_A2_91_19/sep4
[Drew's A14]# [NEW] Endpoint /org/bluez/hci0/dev_BC_52_74_A2_91_19/sep5
[Drew's A14]# [NEW] Transport /org/bluez/hci0/dev_BC_52_74_A2_91_19/sep1/fd3
[Drew's A14]# Connection successful
[Drew's A14]# [NEW] Player /org/bluez/hci0/dev_BC_52_74_A2_91_19/player0 [default]
[Drew's A14]# [CHG] Device BC:52:74:A2:91:19 ServicesResolved: yes
[Drew's A14]# [CHG] Player /org/bluez/hci0/dev_BC_52_74_A2_91_19/player0 Type: Audio
[Drew's A14]# [CHG] Player /org/bluez/hci0/dev_BC_52_74_A2_91_19/player0 Subtype: Audio Book
[Drew's A14]# [CHG] Player /org/bluez/hci0/dev_BC_52_74_A2_91_19/player0 Status: stopped
[Drew's A14]# [CHG] Player /org/bluez/hci0/dev_BC_52_74_A2_91_19/player0 Name: Media Player
[Drew's A14]# [CHG] Transport /org/bluez/hci0/dev_BC_52_74_A2_91_19/sep1/fd3 Volume: 0x004d (77)
[Drew's A14]# [CHG] Player /org/bluez/hci0/dev_BC_52_74_A2_91_19/player0 Repeat: off
[Drew's A14]# [CHG] Player /org/bluez/hci0/dev_BC_52_74_A2_91_19/player0 Shuffle: off
[Drew's A14]# [CHG] Player /org/bluez/hci0/dev_BC_52_74_A2_91_19/player0 Track.Title: Not Provided
[Drew's A14]# [CHG] Player /org/bluez/hci0/dev_BC_52_74_A2_91_19/player0 Track.TrackNumber: 0x00000001 (1)
[Drew's A14]# [CHG] Player /org/bluez/hci0/dev_BC_52_74_A2_91_19/player0 Track.NumberOfTracks: 0x00000001 (1)
[Drew's A14]# [CHG] Player /org/bluez/hci0/dev_BC_52_74_A2_91_19/player0 Track.Duration: 0x00000000 (0)
[Drew's A14]# [CHG] Player /org/bluez/hci0/dev_BC_52_74_A2_91_19/player0 Track.Album:
[Drew's A14]# [CHG] Player /org/bluez/hci0/dev_BC_52_74_A2_91_19/player0 Track.Artist:
[Drew's A14]# [CHG] Player /org/bluez/hci0/dev_BC_52_74_A2_91_19/player0 Track.Genre:
[Drew's A14]# [CHG] Player /org/bluez/hci0/dev_BC_52_74_A2_91_19/player0 Position: 0x00000000 (0)
[Drew's A14]# [CHG] Player /org/bluez/hci0/dev_BC_52_74_A2_91_19/player0 Position: 0x00000000 (0)
[Drew's A14]# [CHG] Device 78:02:B7:69:8D:97 RSSI: 0xffffffb6 (-74)
[Drew's A14]# [NEW] Device 5E:10:CA:79:B7:4B 5E-10-CA-79-B7-4B
[Drew's A14]# pulseaudio
Invalid command in menu main: pulseaudio
Use "help" for a list of available commands in a menu.
Use "menu <submenu>" if you want to enter any submenu.
Use "back" if you want to return to menu main.
[Drew's A14]# [NEW] Device 72:0C:45:14:DE:18 72-0C-45-14-DE-18
[Drew's A14]# [DEL] Device 5E:10:CA:79:B7:4B 5E-10-CA-79-B7-4B
[Drew's A14]# [NEW] Device 5E:10:CA:79:B7:4B 5E-10-CA-79-B7-4B
[Drew's A14]# [CHG] Device BC:52:74:A2:91:19 RSSI: 0xffffffad (-83)
[Drew's A14]# [DEL] Device 5E:10:CA:79:B7:4B 5E-10-CA-79-B7-4B
[Drew's A14]# [DEL] Device 72:0C:45:14:DE:18 72-0C-45-14-DE-18
[Drew's A14]# [NEW] Device 5E:10:CA:79:B7:4B 5E-10-CA-79-B7-4B
[Drew's A14]# [CHG] Device 78:02:B7:69:8D:97 RSSI: 0xffffffac (-84)
[Drew's A14]# [CHG] Device 5E:10:CA:79:B7:4B ManufacturerData.Key: 0x004c (76)
[Drew's A14]# [CHG] Device 5E:10:CA:79:B7:4B ManufacturerData.Value:
[Drew's A14]# 10 06 7e 1e af 7d f5 d0 ..~..}..
[Drew's A14]# [CHG] Device 78:02:B7:69:8D:97 RSSI: 0xffffffb7 (-73)
[Drew's A14]# [DEL] Device 5E:10:CA:79:B7:4B 5E-10-CA-79-B7-4B
[Drew's A14]# [CHG] Transport /org/bluez/hci0/dev_BC_52_74_A2_91_19/sep1/fd3 State: pending
[Drew's A14]# [CHG] Transport /org/bluez/hci0/dev_BC_52_74_A2_91_19/sep1/fd3 State: active
[Drew's A14]# [CHG] Player /org/bluez/hci0/dev_BC_52_74_A2_91_19/player0 Status: playing
[Drew's A14]# [CHG] Player /org/bluez/hci0/dev_BC_52_74_A2_91_19/player0 Position: 0x00000000 (0)
[Drew's A14]# [CHG] Transport /org/bluez/hci0/dev_BC_52_74_A2_91_19/sep1/fd3 State: idle
[Drew's A14]# [CHG] Player /org/bluez/hci0/dev_BC_52_74_A2_91_19/player0 Position: 0x00000000 (0)
[Drew's A14]# [CHG] Player /org/bluez/hci0/dev_BC_52_74_A2_91_19/player0 Status: stopped
[Drew's A14]# [CHG] Player /org/bluez/hci0/dev_BC_52_74_A2_91_19/player0 Position: 0x00000000 (0)
[Drew's A14]# [NEW] Device 5E:10:CA:79:B7:4B 5E-10-CA-79-B7-4B
[Drew's A14]#
With all the probing you've done lately, I don't know if those including trying this: "hw-probe".
- The site that explains the purpose.
- The tool that is used: sudo -E hw-probe -all -upload
- The report that you get: they will give you a URL for an HTML page summarizing your configuration and reported issues. (that will be similar to this for mine.)
Don't know how much that would help to make incompatible equipment work, but it would give you a "categorical" view of what is (has been?) supported.
The publishers of those results publish more detail on their GitHub site, where they have a "usage count" of instances where various components were used successfully. They have those reports broken down into categories. Given your use of the dongle, the USB top-level would apply, and within that, maybe these two sub-categories would reflect your chosen headphones or dongle.
Hope that helps.
3 Likes
I am sorry for my response. I just realized that the money I spent and the person who recommended it, solved my Amazon Echo issue.
2 Likes
inxi -A
Audio:
Device-1: AMD Kaveri HDMI/DP Audio driver: snd_hda_intel
Device-2: AMD FCH Azalia driver: snd_hda_intel
Device-3: Microsoft LifeCam HD-5000 driver: snd-usb-audio,uvcvideo
type: USB
API: ALSA v: k6.8.0-45-generic status: kernel-api
Server-1: PipeWire v: 1.0.5 status: active
Does this mean what I think it does?
I do not have any more slots. 
P.S. I may have lost one resource for Ubuntu-Mate questions. I still have some others.
Can I ask what is the Brand/Model for your Bluetooth Headphones?
1 Like
Well here goes. You do not have to ask.
My computer paired with my cell phone.
I can also transfer audio files using a cable.
I had to install a music player.
I can now hear music.
I am not sure where I am, but I think I have found an answer.
(Getting old is rough)
5 Likes
If you made it work, that's what counts! Linux is about giving solutions, not always elegant, but at least it will work!
2 Likes
Great news!
So was the solution to install a music player?
1 Like
Doesn't seem right as rhythm box comes installed by default for sound, unless Andy had un-installed it, but then his computer would have had no sound. It could be he didn't have a default player selected. We'll he got it working and that is good.
I was talking about my cell phone.
Samsung has no built in music player that I could find.