Bluetooth is enabled and I can choose to connect to my earphones, but then the problems start. In one ear I hear “connected”, a bit later I hear the same in the second but the first one then gets disconnected. Always when one ear get connected, the other gets disconnected. This can go on for ever. I try to switch off both earphones and switch them back on and it might be that it works now, often it doesn’t.
When it does work the sound is terrible. It sounds like I’m listening to an old radio which is a little offset to a station.
Thing is, when I connect the same earphones to my Windows 10 office laptop I have no problem what soever. Also connected to my Android phone they work great. It’s just the laptop which has problems.
Does anyone have these problems as well? They started some weeks ago, before that it was great, always connected, great sound, wonderful. Something changed however and I don’t know what to do to make it work again.
I use Tumbleweed fully updated.
Interesting, never knew headphone with two earphones which can be individually switched on and off existed.
Assuming you use pulseaudio, can you do a “pactl list sinks” when both earphones are enabled (with terrible sound) and share the output for the sinks that are Running/bluetooth?
Also the output of “sudo journalctl -b -t bluetoothd” can be helpful
sudo journalctl -b -t bluetoothd
[sudo] password for root:
Mar 26 12:50:38 localhost.localdomain bluetoothd[1672]: Bluetooth daemon 5.63
Mar 26 12:50:38 localhost.localdomain bluetoothd[1672]: Starting SDP server
Mar 26 12:50:38 localhost.localdomain bluetoothd[1672]: Bluetooth management interface 1.21 initialized
Mar 26 12:50:39 localhost.localdomain bluetoothd[1672]: Admin Policy Set interface registered
Mar 26 12:50:39 localhost.localdomain bluetoothd[1672]: Admin Policy Status interface registered
Mar 26 12:50:46 localhost.localdomain bluetoothd[1672]: Player registered: sender=:1.57 path=/media_player0
Mar 26 12:50:46 localhost.localdomain bluetoothd[1672]: Endpoint registered: sender=:1.57 path=/MediaEndpoint/A2DPSource/ldac
Mar 26 12:50:46 localhost.localdomain bluetoothd[1672]: Endpoint registered: sender=:1.57 path=/MediaEndpoint/A2DPSource/aac
Mar 26 12:50:46 localhost.localdomain bluetoothd[1672]: Endpoint registered: sender=:1.57 path=/MediaEndpoint/A2DPSink/sbc
Mar 26 12:50:46 localhost.localdomain bluetoothd[1672]: Endpoint registered: sender=:1.57 path=/MediaEndpoint/A2DPSource/sbc
Mar 26 12:50:46 localhost.localdomain bluetoothd[1672]: Endpoint registered: sender=:1.57 path=/MediaEndpoint/A2DPSink/sbc_xq
Mar 26 12:50:46 localhost.localdomain bluetoothd[1672]: Endpoint registered: sender=:1.57 path=/MediaEndpoint/A2DPSource/sbc_xq
Mar 26 12:50:46 localhost.localdomain bluetoothd[1672]: Endpoint registered: sender=:1.57 path=/MediaEndpoint/A2DPSource/faststream
Mar 26 12:50:46 localhost.localdomain bluetoothd[1672]: Endpoint registered: sender=:1.57 path=/MediaEndpoint/A2DPSource/faststream_duplex
Mar 26 12:50:49 localhost.localdomain bluetoothd[1672]: src/profile.c:ext_start_servers() RFCOMM server failed for Headset unit: rfcomm_bind: Address already>
Mar 26 12:50:49 localhost.localdomain bluetoothd[1672]: src/profile.c:ext_start_servers() RFCOMM server failed for Hands-Free Voice gateway: rfcomm_bind: Add>
Mar 26 12:50:49 localhost.localdomain bluetoothd[1672]: Endpoint registered: sender=:1.69 path=/MediaEndpoint/A2DPSink/sbc
Mar 26 12:50:49 localhost.localdomain bluetoothd[1672]: Endpoint registered: sender=:1.69 path=/MediaEndpoint/A2DPSource/sbc
Mar 26 12:50:49 localhost.localdomain bluetoothd[1672]: Endpoint registered: sender=:1.69 path=/MediaEndpoint/A2DPSink/sbc_xq_453
Mar 26 12:50:49 localhost.localdomain bluetoothd[1672]: Endpoint registered: sender=:1.69 path=/MediaEndpoint/A2DPSource/sbc_xq_453
Mar 26 12:50:49 localhost.localdomain bluetoothd[1672]: Endpoint registered: sender=:1.69 path=/MediaEndpoint/A2DPSink/sbc_xq_512
Mar 26 12:50:49 localhost.localdomain bluetoothd[1672]: Endpoint registered: sender=:1.69 path=/MediaEndpoint/A2DPSource/sbc_xq_512
Mar 26 12:50:49 localhost.localdomain bluetoothd[1672]: Endpoint registered: sender=:1.69 path=/MediaEndpoint/A2DPSink/sbc_xq_552
Mar 26 12:50:49 localhost.localdomain bluetoothd[1672]: Endpoint registered: sender=:1.69 path=/MediaEndpoint/A2DPSource/sbc_xq_552
Mar 26 12:50:53 2a02-a443-5925-1-efda-76f6-5d9c-ce81.fixed6.kpn.net bluetoothd[1672]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP re>
Mar 26 19:17:04 2a02-a443-5925-1-efda-76f6-5d9c-ce81.fixed6.kpn.net bluetoothd[1672]: src/profile.c:connect_io() Unable to connect Hands-Free Voice gateway: >
Mar 26 19:17:04 2a02-a443-5925-1-efda-76f6-5d9c-ce81.fixed6.kpn.net bluetoothd[1672]: src/profile.c:record_cb() Connecting Hands-Free Voice gateway failed: I>
Mar 26 19:17:07 2a02-a443-5925-1-efda-76f6-5d9c-ce81.fixed6.kpn.net bluetoothd[1672]: src/profile.c:connect_io() Unable to connect Hands-Free Voice gateway: >
Mar 26 19:17:07 2a02-a443-5925-1-efda-76f6-5d9c-ce81.fixed6.kpn.net bluetoothd[1672]: src/profile.c:record_cb() Connecting Hands-Free Voice gateway failed: I>
lines 1-29/29 (END)
I hope I explained what I have here well: I have 2 earphones, one for the left and one for the right ear, which belong together. But I can switch off one if I want to. Thing is when I do that, Linux doesn’t see the other one still being attached to the computer and it switches back to using the normal loudspeakers instead of the one connected earphone.
Did this help you in helping me? I’ve been reading the output of the commands and I see a lot of words I know, but I have no idea what they mean together. Is it something good what I read, or is something not working as it should?
Open then the bt.log file and paste the output here.
Can you also run “bluetoothctl info” and share the output? That will list which BT profiles are supported by this ENV-1666.
This is the output of the bt.log file with the 7 error lines:
cat bt.log
Mar 27 07:20:31 2a02-a443-5925-1-b95e-e9d0-a8ec-e4d4.fixed6.kpn.net bluetoothd[1670]: src/profile.c:ext_start_servers() RFCOMM server failed for Headset unit: rfcomm_bind: Address already in use (98)
Mar 27 07:20:31 2a02-a443-5925-1-b95e-e9d0-a8ec-e4d4.fixed6.kpn.net bluetoothd[1670]: src/profile.c:ext_start_servers() RFCOMM server failed for Hands-Free Voice gateway: rfcomm_bind: Address already in use (98)
Mar 27 07:20:35 2a02-a443-5925-1-86d0-3a72-476d-c07.fixed6.kpn.net bluetoothd[1670]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down
Mar 27 07:51:51 2a02-a443-5925-1-86d0-3a72-476d-c07.fixed6.kpn.net bluetoothd[1670]: src/profile.c:connect_io() Unable to connect Hands-Free Voice gateway: connect to 00:00:AB:CD:2D:D8: Device or resource busy (16)
Mar 27 07:51:51 2a02-a443-5925-1-86d0-3a72-476d-c07.fixed6.kpn.net bluetoothd[1670]: src/profile.c:record_cb() Connecting Hands-Free Voice gateway failed: Input/output error
Mar 27 07:51:53 2a02-a443-5925-1-86d0-3a72-476d-c07.fixed6.kpn.net bluetoothd[1670]: src/profile.c:connect_io() Unable to connect Hands-Free Voice gateway: connect to 00:00:AB:CD:2D:D8: Device or resource busy (16)
Mar 27 07:51:53 2a02-a443-5925-1-86d0-3a72-476d-c07.fixed6.kpn.net bluetoothd[1670]: src/profile.c:record_cb() Connecting Hands-Free Voice gateway failed: Input/output error
I see in those lines the text kpn.net. KPN is a large Dutch internet provider which I use for my internet connection.
This is the other output:
bluetoothctl info
Device 00:00:AB:CD:2D:D8 (public)
Name: ENV-1666
Alias: ENV-1666
Class: 0x00240404
Icon: audio-headset
Paired: yes
Trusted: yes
Blocked: no
Connected: yes
LegacyPairing: no
UUID: Vendor specific (00000000-0000-0000-0099-aabbccddeeff)
UUID: Headset (00001108-0000-1000-8000-00805f9b34fb)
UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
UUID: Advanced Audio Distribu.. (0000110d-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb)
UUID: Handsfree (0000111e-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
Modalias: bluetooth:v0094p0123d1000
Affected by Policy: no
About the lists I sent yesterday you mentioned there are 2 sinks, one being the normal loudspeakers. I do have external loudspeakers connected to the laptop but they are not connected through bluetooth. Is it correct they appear in the list as well?
At the moment I am in a constant battle to have both earphones connected. But one connects while the other disconnects and vice-versa. It just goes on and on. Several months I could use the earphones without any problem and now it is a disaster, while on the Windows office laptop and on my phone (both have bluetooth switched off at the moment) they work fine. So, I don’t think it is something which is caused by the earphones themselves.
This KPN entry in the log file is the host name (output of hostname), what is remarkable to me is that it changes within the log, but that is another observation.
The output of “bluetoothctl info” looks fine to me, the differences with me are that you have additional “UUID: Vendor specific” and “UUID: PnP Information” lines.
If I look at my journal (without the headset connected) I see also the first two lines so for this problem I think they can be ignored.
That leaves:
bluetoothd[1670]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down
bluetoothd[1670]: src/profile.c:connect_io() Unable to connect Hands-Free Voice gateway: connect to 00:00:AB:CD:2D:D8: Device or resource busy (16)
For me, when the headset connects, I see also an error, but no Hands-Free Voice gateway profile but a a2dp-sink profile:
bluetoothd[3974]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for 00:1E:7C:52:4D:9A: Device or resource busy
bluetoothd[3974]: /org/bluez/hci0/dev_00_1E_7C_52_4D_9A/sep1/fd0: fd(30) ready
I think that the problem here is that somehow the “Hands-Free Voice gateway” profile is selected, but like indicated, I am no real expert here, so I think it is better to check.
You wrote the problems “started some weeks ago” and checking my journal I see it is available from 10 Jan, so I guess your computer will also still have the log.
Can you check using "sudo journalctl -g ‘(bluez.*ready|a2dp-sink)’ if you see messages still some weeks ago but no longer for recent builds?
-- Boot 397889e49c754eb7a3fbea8dc773fd8a --
-- Boot a475e96d86634cc1b55d53131139d645 --
-- Boot 0fb46efa6e28460e81a88244fb552f2d --
-- Boot 828ef0b84a9c4ce2a933812dfd4ee3e3 --
-- Boot 3b93f6fb59074698b33388213467d841 --
-- Boot 2b98dc869bb4491d98ea6936c63986fb --
-- Boot 6586c1a1f5484280bda3a1df5cdef581 --
-- Boot ae9caaef4f74431c89dcf4ffcfb2e3c6 --
-- Boot f8873e7a680b47ba9d1d431c352641b2 --
-- Boot fe1abc18bc1a44c6aec69a9d02d991c5 --
-- Boot a64b37b02b91413fb316d5cabfc92d71 --
-- Boot 3dc675aea9684644ad4f35bf260308b3 --
-- Boot e351f4b05c4a46e9ba46736174f4f03b --
-- Boot 1b0d100268e946a9a142162469eb6a14 --
-- Boot 9a636a2f51b34e5d84e53e6d7624280d --
-- Boot 08ffac2de93244259751613c38933503 --
Mar 27 08:13:13 2a02-a443-5925-1-86d0-3a72-476d-c07.fixed6.kpn.net bluetoothd[1670]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for 00:00:AB:CD:2D:D8: Device or resource busy
Mar 27 08:13:17 2a02-a443-5925-1-86d0-3a72-476d-c07.fixed6.kpn.net bluetoothd[1670]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for 00:00:AB:CD:2D:D8: Device or resource busy
Mar 27 08:15:04 2a02-a443-5925-1-86d0-3a72-476d-c07.fixed6.kpn.net bluetoothd[1670]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for 00:00:AB:CD:2D:D8: Device or resource busy
Mar 27 08:19:29 2a02-a443-5925-1-86d0-3a72-476d-c07.fixed6.kpn.net bluetoothd[1670]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for 00:00:AB:CD:2D:D8: Device or resource busy
Mar 27 08:19:35 2a02-a443-5925-1-86d0-3a72-476d-c07.fixed6.kpn.net bluetoothd[1670]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for 00:00:AB:CD:2D:D8: Device or resource busy
Mar 27 08:19:39 2a02-a443-5925-1-86d0-3a72-476d-c07.fixed6.kpn.net bluetoothd[1670]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for 00:00:AB:CD:2D:D8: Device or resource busy
Mar 27 08:19:46 2a02-a443-5925-1-86d0-3a72-476d-c07.fixed6.kpn.net bluetoothd[1670]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for 00:00:AB:CD:2D:D8: Device or resource busy
Mar 27 08:19:52 2a02-a443-5925-1-86d0-3a72-476d-c07.fixed6.kpn.net bluetoothd[1670]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for 00:00:AB:CD:2D:D8: Device or resource busy
Mar 27 08:19:59 2a02-a443-5925-1-86d0-3a72-476d-c07.fixed6.kpn.net bluetoothd[1670]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for 00:00:AB:CD:2D:D8: Device or resource busy
Mar 27 08:22:22 2a02-a443-5925-1-86d0-3a72-476d-c07.fixed6.kpn.net bluetoothd[1670]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for 00:00:AB:CD:2D:D8: Device or resource busy
Mar 27 08:22:26 2a02-a443-5925-1-86d0-3a72-476d-c07.fixed6.kpn.net bluetoothd[1670]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for 00:00:AB:CD:2D:D8: Device or resource busy
Mar 27 08:22:36 2a02-a443-5925-1-86d0-3a72-476d-c07.fixed6.kpn.net bluetoothd[1670]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for 00:00:AB:CD:2D:D8: Device or resource busy
Mar 27 08:22:40 2a02-a443-5925-1-86d0-3a72-476d-c07.fixed6.kpn.net bluetoothd[1670]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for 00:00:AB:CD:2D:D8: Device or resource busy
Mar 27 08:23:36 2a02-a443-5925-1-86d0-3a72-476d-c07.fixed6.kpn.net bluetoothd[1670]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for 00:00:AB:CD:2D:D8: Device or resource busy
Mar 27 08:23:45 2a02-a443-5925-1-86d0-3a72-476d-c07.fixed6.kpn.net bluetoothd[1670]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for 00:00:AB:CD:2D:D8: Device or resource busy
Mar 27 08:30:02 2a02-a443-5925-1-86d0-3a72-476d-c07.fixed6.kpn.net bluetoothd[1670]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for 00:00:AB:CD:2D:D8: Device or resource busy
Mar 27 08:30:09 2a02-a443-5925-1-86d0-3a72-476d-c07.fixed6.kpn.net bluetoothd[1670]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for 00:00:AB:CD:2D:D8: Device or resource busy
Mar 27 08:30:12 2a02-a443-5925-1-86d0-3a72-476d-c07.fixed6.kpn.net bluetoothd[1670]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for 00:00:AB:CD:2D:D8: Device or resource busy
Mar 27 08:30:21 2a02-a443-5925-1-86d0-3a72-476d-c07.fixed6.kpn.net bluetoothd[1670]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for 00:00:AB:CD:2D:D8: Device or resource busy
Mar 27 08:30:25 2a02-a443-5925-1-86d0-3a72-476d-c07.fixed6.kpn.net bluetoothd[1670]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for 00:00:AB:CD:2D:D8: Device or resource busy
Mar 27 08:30:32 2a02-a443-5925-1-86d0-3a72-476d-c07.fixed6.kpn.net bluetoothd[1670]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for 00:00:AB:CD:2D:D8: Device or resource busy
Mar 27 08:30:35 2a02-a443-5925-1-86d0-3a72-476d-c07.fixed6.kpn.net bluetoothd[1670]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for 00:00:AB:CD:2D:D8: Device or resource busy
Mar 27 11:17:12 2a02-a443-5925-1-86d0-3a72-476d-c07.fixed6.kpn.net sudo[32491]: jan : TTY=pts/0 ; PWD=/home/jan ; USER=root ; COMMAND=/usr/bin/journalctl -g (bluez.*ready|a2dp-sink)
Mar 27 11:19:16 2a02-a443-5925-1-86d0-3a72-476d-c07.fixed6.kpn.net sudo[3967]: jan : TTY=pts/0 ; PWD=/home/jan ; USER=root ; COMMAND=/usr/bin/journalctl -g (bluez.*ready|a2dp-sink)
It looks to me at March 20 things changed. In the original terminal output of this command it is the date the red lines appear, which you can't see here.
Is there something I need to install, or maybe uninstall (re-install)? As said before they used to work fine, great sound and then suddenly, most likely with an update of some package, things changed.
I have my Tumbleweed completely updated. Just checked and there are no updates now.
Yes, till Mar 13 things look to be running normal, one Mar 20 there are already problems, but the end result looks fine, Mar 21 there are only problems and after that no A2DP anymore.
But the sound was just as terrible as before, so I changed it again into the original way it was.
Disable the headset profile
/etc/bluetooth/main.conf
[General]
Disable=Headset
This is something I couldn’t find the file.
Is there anyone who has the same problems as I have or am I the only one? Do I miss a piece of software, do I have the wrong version, a wrong setting somewhere?
Sorry for the late response, it has been a terrible long week for me.
I tried your suggestion and booted a Leap 15.3 live version. Now the headphones work as they should. No problems in connecting to them and the sound is clear.
When I try to connect them in my installed Tumbleweed I now have something different: they do connect and after 3-4 seconds they disconnect automatically.
I open the bluetooth icon in the taskbar and try to connect and get the above mentioned situation.
I then open the settings for bluetooth and try to connect the headphones there. I get the same result, plus a message saying: br-connection-unknown
Found an Arch thread https://bbs.archlinux.org/viewtopic.php?id=270465about it but since Arch is not openSUSe I can’t use the suggested help.
sudo systemctl status --no-pager -l bluetooth
[sudo] password for root:
● bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: disabled)
Active: active (running) since Sat 2022-04-02 11:02:23 CEST; 17min ago
Docs: man:bluetoothd(8)
Main PID: 1658 (bluetoothd)
Status: "Running"
Tasks: 1 (limit: 4915)
CPU: 56ms
CGroup: /system.slice/bluetooth.service
└─1658 /usr/libexec/bluetooth/bluetoothd
Apr 02 11:02:48 2a02-a443-5925-1-fdfa-dddb-28bf-bd10.fixed6.kpn.net bluetoothd[1658]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 00:00:AB:CD:2D:D8: Connection refused (111)
Apr 02 11:02:51 2a02-a443-5925-1-fdfa-dddb-28bf-bd10.fixed6.kpn.net bluetoothd[1658]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 00:00:AB:CD:2D:D8: Connection refused (111)
Apr 02 11:07:52 2a02-a443-5925-1-fdfa-dddb-28bf-bd10.fixed6.kpn.net bluetoothd[1658]: src/profile.c:ext_connect() Hands-Free Voice gateway failed connect to 00:00:AB:CD:2D:D8: Connection refused (111)
Apr 02 11:07:52 2a02-a443-5925-1-fdfa-dddb-28bf-bd10.fixed6.kpn.net bluetoothd[1658]: src/profile.c:ext_connect() Hands-Free Voice gateway failed connect to 00:00:AB:CD:2D:D8: Connection refused (111)
Apr 02 11:07:53 2a02-a443-5925-1-fdfa-dddb-28bf-bd10.fixed6.kpn.net bluetoothd[1658]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 00:00:AB:CD:2D:D8: Connection refused (111)
Apr 02 11:07:55 2a02-a443-5925-1-fdfa-dddb-28bf-bd10.fixed6.kpn.net bluetoothd[1658]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 00:00:AB:CD:2D:D8: Connection refused (111)
Apr 02 11:08:06 2a02-a443-5925-1-fdfa-dddb-28bf-bd10.fixed6.kpn.net bluetoothd[1658]: src/profile.c:ext_connect() Hands-Free Voice gateway failed connect to 00:00:AB:CD:2D:D8: Connection refused (111)
Apr 02 11:08:06 2a02-a443-5925-1-fdfa-dddb-28bf-bd10.fixed6.kpn.net bluetoothd[1658]: src/profile.c:ext_connect() Hands-Free Voice gateway failed connect to 00:00:AB:CD:2D:D8: Connection refused (111)
Apr 02 11:08:06 2a02-a443-5925-1-fdfa-dddb-28bf-bd10.fixed6.kpn.net bluetoothd[1658]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 00:00:AB:CD:2D:D8: Connection refused (111)
Apr 02 11:08:09 2a02-a443-5925-1-fdfa-dddb-28bf-bd10.fixed6.kpn.net bluetoothd[1658]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 00:00:AB:CD:2D:D8: Connection refused (111)
[User: jan] @ [Server: 2a02-a443-5925-1-fdfa-dddb-28bf-bd10] - [Directory: ~]
For the time being at least the problem is solved. In the KDE Bluetooth settings I have removed my earphones from the list of available devices to be connected and I added them again. Now they connect and stay connected.
Also in the audio settings for the earphones I see that they use the High Fidelity Playback (A2DP sink) profile. Only the built-in microphone does’t work with this profile. When I switch to the HFP profie the microphone also works but the sound quality is what I used to have when these problems started: it’s as if I’m listening to an old radio which is not exactly set to the correct frequency of a station. In A2DP the sound is great, but no mic.