Hi,

I'm pretty new to Linux and the raspberry so bare that in mind.

I have my raspberry pi4 and I'm trying to connect it to my van radio system to output the audio through the vans speakers. It used to work fine with an old Raspbian image. But since installing Kali I've got a connection problem.

I can pair up the device using the GUI and see the device called Media-Nav. It will also connect for a few seconds but then disconnects.

So decided to ditch the GUI, and use the command line tool thingy to see whats happening. Below are the logs:-

kali@kali:~$ bluetoothctl
Agent registered
[bluetooth]# show
Controller AA:AA:AA:AA:AA:AA (public)
Name: kali
Alias: kali
Class: 0x003c0000
Powered: yes
Discoverable: no
DiscoverableTimeout: 0x0000003c
Pairable: yes
UUID: Message Notification Se.. (00001133-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb)
UUID: OBEX Object Push (00001105-0000-1000-8000-00805f9b34fb)
UUID: Message Access Server (00001132-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
UUID: IrMC Sync (00001104-0000-1000-8000-00805f9b34fb)
UUID: Vendor specific (00005005-0000-1000-8000-0002ee000001)
UUID: Headset (00001108-0000-1000-8000-00805f9b34fb)
UUID: Headset AG (00001112-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
UUID: Phonebook Access Server (0000112f-0000-1000-8000-00805f9b34fb)
UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb)
UUID: Device Information (0000180a-0000-1000-8000-00805f9b34fb)
UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
UUID: Audio Source (0000110a-0000-1000-8000-00805f9b34fb)
UUID: OBEX File Transfer (00001106-0000-1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0537
Discovering: no
Roles: central
Roles: peripheral
Advertising Features:
ActiveInstances: 0x00 (0)
SupportedInstances: 0x05 (5)
SupportedIncludes: tx-power
SupportedIncludes: appearance
SupportedIncludes: local-name
[bluetooth]# agent KeyboardOnly
Agent is already registered
[bluetooth]# power on
Changing power on succeeded
[bluetooth]# scan on
Discovery started
[CHG] Controller AA:AA:AA:AA:AA:AA Discovering: yes
[NEW] Device C0:84:7D:46:28:5D Nextbase522GW-285d
[bluetooth]# paired-devices
Device C8:02:10:6A:F0:68 MEDIA-NAV
[bluetooth]# connect C8:02:10:6A:F0:68
Attempting to connect to C8:02:10:6A:F0:68
[CHG] Device C8:02:10:6A:F0:68 Connected: yes
Connection successful <-LOOK IT CONNECTS FOR A FEW SECONDS AND THEN DISCONNECTS
[CHG] Device C8:02:10:6A:F0:68 ServicesResolved: yes
[CHG] Device C8:02:10:6A:F0:68 ServicesResolved: no <-A FEW SECONDS LATER IT SAYS SERVICESRESOLVED: NO AND CONNECTED NO
[CHG] Device C8:02:10:6A:F0:68 Connected: no
[NEW] Device 39:92:1F:6E:46:75 39-92-1F-6E-46-75
[DEL] Device 39:92:1F:6E:46:75 39-92-1F-6E-46-75
[bluetooth]# connect C8:02:10:6A:F0:68 <-SO I TRIED TO CONNECT AGAIN BUT GOT FAILED ERROR THIS TIME
Attempting to connect to C8:02:10:6A:F0:68
Failed to connect: org.bluez.Error.Failed


Also tried sudo cat /var/log/syslog | grep -i protocol

Mar 31 14:50:12 kali kernel: [ 0.158550] NET: Registered protocol family 16
Mar 31 14:50:12 kali kernel: [ 0.303086] NET: Registered protocol family 2
Mar 31 14:50:12 kali kernel: [ 0.305171] NET: Registered protocol family 1
Mar 31 14:50:12 kali kernel: [ 0.618327] NET: Registered protocol family 17
Mar 31 14:50:12 kali kernel: [ 1.340508] NET: Registered protocol family 10
Mar 31 14:50:12 kali kernel: [ 4.906385] NET: Registered protocol family 31
Mar 31 14:50:12 kali kernel: [ 4.989145] Bluetooth: HCI UART protocol H4 registered
Mar 31 14:50:12 kali kernel: [ 4.989754] Bluetooth: HCI UART protocol Three-wire (H5) registered
Mar 31 14:50:12 kali kernel: [ 4.990574] Bluetooth: HCI UART protocol Broadcom registered
Mar 31 14:50:12 kali kernel: [ 5.455619] Bluetooth: BNEP filters: protocol multicast
Mar 31 14:50:12 kali kernel: [ 5.483714] NET: Registered protocol family 38
Mar 31 14:50:26 kali lightdm[706]: Error opening audit socket: Protocol not supported
Mar 31 14:50:31 kali systemd[717]: Starting Virtual filesystem service - Media Transfer Protocol monitor...
Mar 31 14:50:31 kali systemd[717]: Started Virtual filesystem service - Media Transfer Protocol monitor.
Mar 31 15:56:54 kali kernel: [ 0.158601] NET: Registered protocol family 16
Mar 31 15:56:54 kali kernel: [ 0.303365] NET: Registered protocol family 2
Mar 31 15:56:54 kali kernel: [ 0.305451] NET: Registered protocol family 1
Mar 31 15:56:54 kali kernel: [ 0.614464] NET: Registered protocol family 17
Mar 31 15:56:54 kali kernel: [ 1.346143] NET: Registered protocol family 10
Mar 31 15:56:55 kali kernel: [ 5.952867] NET: Registered protocol family 31
Mar 31 15:56:55 kali kernel: [ 6.245808] Bluetooth: HCI UART protocol H4 registered
Mar 31 15:56:55 kali kernel: [ 6.247123] Bluetooth: HCI UART protocol Three-wire (H5) registered
Mar 31 15:56:55 kali kernel: [ 6.248072] Bluetooth: HCI UART protocol Broadcom registered
Mar 31 15:56:56 kali kernel: [ 6.809173] Bluetooth: BNEP filters: protocol multicast
Mar 31 15:56:56 kali kernel: [ 6.834083] NET: Registered protocol family 38
Mar 31 15:57:08 kali lightdm[707]: Error opening audit socket: Protocol not supported
Mar 31 15:57:15 kali systemd[718]: Starting Virtual filesystem service - Media Transfer Protocol monitor...
Mar 31 15:57:15 kali systemd[718]: Started Virtual filesystem service - Media Transfer Protocol monitor.
kali@kali:~$


Can anyone help?

Thanks

Hi and welcome to LQ.

Yes we can help, and all the answers will include "Don't use Kali - it's not meant for that".

Seriously.

See this page on the Kali site and this page on LQ.

3 members found this post helpful.

I really hate to bust your bubble, but you ditched an OS (raspbian) where sound worked perfectly for you, and replaced it with a pen test system (kali) where you cannot get sound (or more specifically bluetooth) to work.
Kali is not designed to be an entertainment system but is specifically designed for penetration testing. The fact that it can run on the pi is a plus. For you to configure it to use in that manner is a matter of digging deep into the nuts and bolts where few people go.

Have you searched for previous problems with kali and bluetooth? If not, please do. There may be some informative nuggets there. If you have, then what have you found and what have you tried beyond asking this question?

Install Raspberry PI OS, either the 32bit arm or the arm64.
Everything just works. I was using my monitor speakers to play an audiobook from my phone just last night.