[solved] Cant connect via Bluetooth

Cannot connect. App does not detect anything.
Updated all the packages (apt), used all the options (no sap, etc)

Using a Samsung 10.

Thanks for your help.

Hey, what is the output of this command:

sudo systemctl status pisound-ctl

Did you turn on discoverable mode on the Raspberry Pi? This can be easily done by holding the Pisound’s button down for 3-4 seconds (count the blinks). Then it will remain discoverable for 180 seconds, and keeps the MIDI LEDs will blink for that duration.

First, thanks for your reply!

Yes, I’ve turned discovery on. I’ve turned on vía software ($patchbox->bluetooth) and hardware (pressing buttons). Both in desktop and console mode.

The device is not shown, neither in the app or the phone bluetooth screen.

Thanks again for your help

Can you please post the output of the command here? What is the Raspberry Pi version you’re using?

Raspberry Pi 3B

output of the command

patch@patchbox:~ $ sudo systemctl status pisound-ctl
\u25cf pisound-ctl.service - Bluetooth service for Pisound companion app.
Loaded: loaded (/lib/systemd/system/pisound-ctl.service; enabled; vendor preset: enabled)
Active: active (running) since Sat 2021-03-20 23:10:37 GMT; 1 day 17h ago
Main PID: 419 (pisound-ctl)
Tasks: 14 (limit: 2199)
Memory: 7.5M
CGroup: /system.slice/pisound-ctl.service
\u251c\u2500419 /usr/bin/pisound-ctl
\u251c\u2500913 /bin/sh /usr/bin/mec /etc/mec-blokas.json
\u251c\u2500917 osc2midi pisound-ctl 127.0.0.1 38735
\u2514\u2500919 mec-app /etc/mec-blokas.json

Mar 20 23:11:09 patchbox pisound-ctl[419]: mec api initialise
Mar 20 23:11:09 patchbox pisound-ctl[419]: mecapi_proc start
Mar 20 23:11:09 patchbox pisound-ctl[419]: mec_app running
Mar 20 23:11:09 patchbox pisound-ctl[419]: MecApi::MecApi
Mar 20 23:11:09 patchbox pisound-ctl[419]: MecApi_Impl::init
Mar 20 23:11:09 patchbox pisound-ctl[419]: KontrolDevice initialise
Mar 20 23:11:09 patchbox pisound-ctl[419]: KontrolDevice::init
Mar 20 23:11:09 patchbox pisound-ctl[419]: kontrol device : listening on 6050
Mar 20 23:11:09 patchbox pisound-ctl[419]: KontrolDevice::init - complete
Mar 20 23:11:12 patchbox pisound-ctl[419]: KontrolDevice::new client 127.0.0.1 : 40051 KA = 5

additional info

sudo systemctl status bluetooth
\u25cf bluetooth.service - Bluetooth service
Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
Active: active (running) since Sat 2021-03-20 23:10:43 GMT; 1 day 17h ago
Docs: man:bluetoothd(8)
Main PID: 555 (bluetoothd)
Status: “Running”
Tasks: 1 (limit: 2199)
Memory: 1.9M
CGroup: /system.slice/bluetooth.service
\u2514\u2500555 /usr/lib/bluetooth/bluetoothd --compat --noplugin=sap

Mar 20 23:10:42 patchbox systemd[1]: Starting Bluetooth service…
Mar 20 23:10:43 patchbox bluetoothd[555]: Bluetooth daemon 5.50
Mar 20 23:10:43 patchbox systemd[1]: Started Bluetooth service.
Mar 20 23:10:43 patchbox bluetoothd[555]: Starting SDP server
Mar 20 23:10:43 patchbox bluetoothd[555]: Excluding (cli) sap
Mar 20 23:10:43 patchbox bluetoothd[555]: Bluetooth management interface 1.14 initialized
Mar 20 23:10:43 patchbox bluetoothd[555]: Failed to set privacy: Rejected (0x0b)
Mar 20 23:10:43 patchbox bluetoothd[555]: Endpoint registered: sender=:1.7 path=/org/bluez/hci0/A2DP/SBC/Source/1
Mar 20 23:10:43 patchbox bluetoothd[555]: Endpoint registered: sender=:1.7 path=/org/bluez/hci0/A2DP/SBC/Source/2

I’ve just checked on Raspberry Pi 3B, it worked just fine. The bluthoothd command line was not modified from original, this is the output I got:

patch@patchbox:~ $ sudo systemctl status bluetooth
● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
   Active: active (running) since Tue 2021-03-23 08:37:11 GMT; 15min ago
     Docs: man:bluetoothd(8)
 Main PID: 528 (bluetoothd)
   Status: "Running"
    Tasks: 1 (limit: 2062)
   CGroup: /system.slice/bluetooth.service
           └─528 /usr/lib/bluetooth/bluetoothd

Mar 23 08:37:11 patchbox systemd[1]: Starting Bluetooth service...
Mar 23 08:37:11 patchbox bluetoothd[528]: Bluetooth daemon 5.50
Mar 23 08:37:11 patchbox systemd[1]: Started Bluetooth service.
Mar 23 08:37:11 patchbox bluetoothd[528]: Starting SDP server
Mar 23 08:37:11 patchbox bluetoothd[528]: Bluetooth management interface 1.18 initialized
Mar 23 08:37:11 patchbox bluetoothd[528]: Sap driver initialization failed.
Mar 23 08:37:11 patchbox bluetoothd[528]: sap-server: Operation not permitted (1)
Mar 23 08:37:11 patchbox bluetoothd[528]: Endpoint registered: sender=:1.8 path=/org/bluez/hci0/A2DP/SBC/Source/1
Mar 23 08:37:11 patchbox bluetoothd[528]: Endpoint registered: sender=:1.8 path=/org/bluez/hci0/A2DP/SBC/Source/2
Mar 23 08:37:11 patchbox bluetoothd[528]: Failed to set privacy: Rejected (0x0b)
patch@patchbox:~ $ uname -a
Linux patchbox 5.10.11-v7+ #1399 SMP Thu Jan 28 12:06:05 GMT 2021 armv7l GNU/Linux

By the way, the App must ask for location permission - did you grant that permission? If not, Bluetooth on Android won’t work. See here for why it’s required: https://blokas.io/pisound/docs/pisound-app/#why-is-the-location-permission-required

Yes, location permissions are granted.
Just reinstalled the app. No change.

But I have just made an interesting finding…
Patchbox is not visible from my phone…but I can see it in my PC bluetooth, so definitely and luckily is not a bluetooth problem, but an app/samsung issue

Uninstall - reboot phone - install - reboot phone - worked!!

1 Like