Pisound App fails to connect via Bluetooth

Pisound Support
1

Hello there !

I just bought a pisound, and i’m very happy with it, all is working very good except the mobile app.

I already try a lot of things (i’m not a programmer but i know some tricks as long as it is 20 years i use linux).

So what i try :

  • standard procedure
  • fresh install with no update
  • fresh install with all the update (apt get update && apt get upgrade)
  • on a fresh install, make the change in the bluetooth.service to avoid the ‘Sap driver initialization failed’ error
  • try little others things without success (reinstall pisound, restart the phone, starting by pairing the phone then make the update on the pisound, restarting pisound, try to control manually the bluetooth with bluetoothctl, try to save the /usr/bin/pisound-ctl, try to use a monitor with HDMI cable , etc etc … )

I can pairing the pisound with my phone on a fresh install without module and update, but the app don’t see anything (the circle is turning and turning …). The app got all the authorisations, it can make what it want ! When the pairing works, it says that it is for sound. And when i update the pisound (apt update && apt upgrade) i can’t pairing anymore.

Modep works as expected, i can make some pedalboard and use them, the sound is very good.
I don’t try Orac because i want the app to work before i try something.

So i’m really out of idea and i really want the app to work as i want to use ModeP (thanks a lot the modep Team !) and Orac (Thanks a lot the Thechnobear !)

So here is my config :

  • samsoung A40
  • android 11 with all the update
  • raspberry 4+ 8go

and here is the result of the commands :

apt show pisound-ctl

Package: pisound-ctl
Version: 1.03-10
Priority: optional
Section: sound
Maintainer: Blokas Labs <hello@blokas.io>
Installed-Size: unknown
Depends: libc6 (>= 2.19), libstdc++6 (>= 4.9.2), libgcc1 (>= 1:4.9.2-10), libdbus-1-3 (>= 1.8.2), git (>= 1:2.1.4), osc2midi (>= 1.0-1), pd-blokas (>= 0.1.1-3), pisound-ctl-scripts-common (>= 1.03-6), mec-blokas (>= 0.1.1-2)
Recommends: pisound-ctl-scripts-system (>= 1.03-6)
Suggests: blokas-puredata-patches (>= 1.0), pisound-ctl-scripts-puredata (>= 1.03-6)
Download-Size: 256 kB
APT-Manual-Installed: yes
APT-Sources: http://apt.blokas.io rpi/main armhf Packages
Description: Bluetooth service for Pisound companion mobile app.
 See https://blokas.io/pisound for more information.

N: There are 11 additional records. Please use the '-a' switch to see them.

dmesg > dmesg.log
dmesg.log (33.5 KB)

journalctl -u bluetooth > bluetooth.log

-- Journal begins at Tue 2022-05-17 14:32:17 BST, ends at Sat 2024-03-23 18:25:28 GMT. --
May 17 14:32:28 patchbox systemd[1]: Condition check resulted in Bluetooth service being skipped.
May 17 14:32:35 patchbox systemd[1]: Starting Bluetooth service...
May 17 14:32:36 patchbox bluetoothd[702]: Bluetooth daemon 5.55
May 17 14:32:37 patchbox systemd[1]: Started Bluetooth service.
May 17 14:32:37 patchbox bluetoothd[702]: Starting SDP server
May 17 14:32:38 patchbox bluetoothd[702]: Bluetooth management interface 1.21 initialized
May 17 14:32:42 patchbox bluetoothd[702]: profiles/sap/server.c:sap_server_register() Sap driver initialization failed.
May 17 14:32:42 patchbox bluetoothd[702]: sap-server: Operation not permitted (1)
May 17 14:32:42 patchbox bluetoothd[702]: Failed to set privacy: Rejected (0x0b)
Mar 23 17:10:16 patchbox bluetoothd[702]: Endpoint registered: sender=:1.30 path=/MediaEndpoint/A2DPSink/sbc
Mar 23 17:10:16 patchbox bluetoothd[702]: Endpoint registered: sender=:1.30 path=/MediaEndpoint/A2DPSource/sbc
Mar 23 17:10:16 patchbox bluetoothd[702]: src/profile.c:ext_start_servers() RFCOMM server failed for Headset unit: rfcomm_bind: Address already in use (98)
Mar 23 17:56:05 patchbox bluetoothd[702]: Terminating
Mar 23 17:56:05 patchbox bluetoothd[702]: Endpoint unregistered: sender=:1.30 path=/MediaEndpoint/A2DPSink/sbc
Mar 23 17:56:05 patchbox systemd[1]: Stopping Bluetooth service...
Mar 23 17:56:05 patchbox bluetoothd[702]: Endpoint unregistered: sender=:1.30 path=/MediaEndpoint/A2DPSource/sbc
Mar 23 17:56:05 patchbox bluetoothd[702]: Stopping SDP server
Mar 23 17:56:05 patchbox bluetoothd[702]: Exit
Mar 23 17:56:05 patchbox systemd[1]: bluetooth.service: Succeeded.
Mar 23 17:56:05 patchbox systemd[1]: Stopped Bluetooth service.
Mar 23 17:56:06 patchbox systemd[1]: Starting Bluetooth service...
Mar 23 17:56:06 patchbox bluetoothd[12807]: Bluetooth daemon 5.55
Mar 23 17:56:06 patchbox systemd[1]: Started Bluetooth service.
Mar 23 17:56:06 patchbox bluetoothd[12807]: Starting SDP server
Mar 23 17:56:06 patchbox bluetoothd[12807]: Bluetooth management interface 1.21 initialized
Mar 23 17:56:06 patchbox bluetoothd[12807]: profiles/sap/server.c:sap_server_register() Sap driver initialization failed.
Mar 23 17:56:06 patchbox bluetoothd[12807]: sap-server: Operation not permitted (1)
Mar 23 17:56:06 patchbox bluetoothd[12807]: Failed to set privacy: Rejected (0x0b)
Mar 23 17:56:06 patchbox bluetoothd[12807]: Endpoint registered: sender=:1.30 path=/MediaEndpoint/A2DPSink/sbc
Mar 23 17:56:06 patchbox bluetoothd[12807]: Endpoint registered: sender=:1.30 path=/MediaEndpoint/A2DPSource/sbc
Mar 23 18:13:48 patchbox systemd[1]: Stopping Bluetooth service...
Mar 23 18:13:48 patchbox systemd[1]: bluetooth.service: Succeeded.
Mar 23 18:13:48 patchbox systemd[1]: Stopped Bluetooth service.
-- Boot e1118c30cd1a4041a9bd03e753828723 --
Mar 23 18:13:59 patchbox systemd[1]: Condition check resulted in Bluetooth service being skipped.
Mar 23 18:14:06 patchbox systemd[1]: Starting Bluetooth service...
Mar 23 18:14:06 patchbox bluetoothd[649]: Bluetooth daemon 5.55
Mar 23 18:14:06 patchbox systemd[1]: Started Bluetooth service.
Mar 23 18:14:06 patchbox bluetoothd[649]: Starting SDP server
Mar 23 18:14:06 patchbox bluetoothd[649]: Bluetooth management interface 1.21 initialized
Mar 23 18:14:07 patchbox bluetoothd[649]: profiles/sap/server.c:sap_server_register() Sap driver initialization failed.
Mar 23 18:14:07 patchbox bluetoothd[649]: sap-server: Operation not permitted (1)
Mar 23 18:14:07 patchbox bluetoothd[649]: Failed to set privacy: Rejected (0x0b)
Mar 23 18:14:13 patchbox bluetoothd[649]: Endpoint registered: sender=:1.26 path=/MediaEndpoint/A2DPSink/sbc
Mar 23 18:14:13 patchbox bluetoothd[649]: Endpoint registered: sender=:1.26 path=/MediaEndpoint/A2DPSource/sbc

journalctl -u pisound-ctl > pisound-ctl.log
pisound-ctl.log (33.0 KB)

sudo systemctl status bluetooth

● bluetooth.service - Bluetooth service
     Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
     Active: active (running) since Sat 2024-03-23 18:14:06 GMT; 18min ago
       Docs: man:bluetoothd(8)
   Main PID: 649 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 4915)
        CPU: 99ms
     CGroup: /system.slice/bluetooth.service
             └─649 /usr/libexec/bluetooth/bluetoothd

Mar 23 18:14:06 patchbox systemd[1]: Starting Bluetooth service...
Mar 23 18:14:06 patchbox bluetoothd[649]: Bluetooth daemon 5.55
Mar 23 18:14:06 patchbox systemd[1]: Started Bluetooth service.
Mar 23 18:14:06 patchbox bluetoothd[649]: Starting SDP server
Mar 23 18:14:06 patchbox bluetoothd[649]: Bluetooth management interface 1.21 initialized
Mar 23 18:14:07 patchbox bluetoothd[649]: profiles/sap/server.c:sap_server_register() Sap driver initialization f>
Mar 23 18:14:07 patchbox bluetoothd[649]: sap-server: Operation not permitted (1)
Mar 23 18:14:07 patchbox bluetoothd[649]: Failed to set privacy: Rejected (0x0b)
Mar 23 18:14:13 patchbox bluetoothd[649]: Endpoint registered: sender=:1.26 path=/MediaEndpoint/A2DPSink/sbc
Mar 23 18:14:13 patchbox bluetoothd[649]: Endpoint registered: sender=:1.26 path=/MediaEndpoint/A2DPSource/sbc
...skipping...
● bluetooth.service - Bluetooth service
     Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
     Active: active (running) since Sat 2024-03-23 18:14:06 GMT; 18min ago
       Docs: man:bluetoothd(8)
   Main PID: 649 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 4915)
        CPU: 99ms
     CGroup: /system.slice/bluetooth.service
             └─649 /usr/libexec/bluetooth/bluetoothd

Mar 23 18:14:06 patchbox systemd[1]: Starting Bluetooth service...
Mar 23 18:14:06 patchbox bluetoothd[649]: Bluetooth daemon 5.55
Mar 23 18:14:06 patchbox systemd[1]: Started Bluetooth service.
Mar 23 18:14:06 patchbox bluetoothd[649]: Starting SDP server
Mar 23 18:14:06 patchbox bluetoothd[649]: Bluetooth management interface 1.21 initialized
Mar 23 18:14:07 patchbox bluetoothd[649]: profiles/sap/server.c:sap_server_register() Sap driver initialization f>
Mar 23 18:14:07 patchbox bluetoothd[649]: sap-server: Operation not permitted (1)
Mar 23 18:14:07 patchbox bluetoothd[649]: Failed to set privacy: Rejected (0x0b)
Mar 23 18:14:13 patchbox bluetoothd[649]: Endpoint registered: sender=:1.26 path=/MediaEndpoint/A2DPSink/sbc
Mar 23 18:14:13 patchbox bluetoothd[649]: Endpoint registered: sender=:1.26 path=/MediaEndpoint/A2DPSource/sbc
~

It would be fantastic if the app could work, so here i’m waiting for your help !!
Let’s make it working together !

Thanks a lot the Blokas Team, this is really a nice hardware !!

cheers,
jubal

2

Mmmm i just that this topic is mark as resolve maybe i start an another one, let me know what you prefer.

3

and i forgot this command

sudo systemctl status pisound-ctl

● pisound-ctl.service - Bluetooth service for Pisound companion app.
     Loaded: loaded (/usr/lib/systemd/system/pisound-ctl.service; enabled; vendor preset: enabled)
     Active: active (running) since Sat 2024-03-23 18:13:58 GMT; 33min ago
   Main PID: 452 (pisound-ctl)
      Tasks: 14 (limit: 4915)
        CPU: 20.642s
     CGroup: /system.slice/pisound-ctl.service
             ├─452 /usr/bin/pisound-ctl
             ├─903 /bin/sh /usr/bin/mec /etc/mec-blokas.json
             ├─907 osc2midi pisound-ctl 127.0.0.1 60986
             └─909 mec-app /etc/mec-blokas.json

Mar 23 18:15:05 patchbox pisound-ctl[909]: mec api initialise
Mar 23 18:15:05 patchbox pisound-ctl[909]: mecapi_proc start
Mar 23 18:15:05 patchbox pisound-ctl[909]: MecApi::MecApi
Mar 23 18:15:05 patchbox pisound-ctl[909]: MecApi_Impl::init
Mar 23 18:15:05 patchbox pisound-ctl[909]: KontrolDevice initialise
Mar 23 18:15:05 patchbox pisound-ctl[909]: KontrolDevice::init
Mar 23 18:15:05 patchbox pisound-ctl[909]: mec_app running
Mar 23 18:15:05 patchbox pisound-ctl[909]: kontrol device : listening on 6050
Mar 23 18:15:05 patchbox pisound-ctl[909]: KontrolDevice::init - complete
Mar 23 18:15:08 patchbox pisound-ctl[909]: KontrolDevice::new client 127.0.0.1 : 58413 KA = 5
4

Is this the entire log?

This line seems fishy:

Mar 23 17:10:16 patchbox bluetoothd[702]: src/profile.c:ext_start_servers() RFCOMM server failed for Headset unit: rfcomm_bind: Address already in use (98)

It may indicate a conflict between Pisound CTL and some audio headset?

Are you using any other Bluetooth devices with the Pi?

5

I’m having the same issue today
Upgrading my pisound to RPi4

  • fresh install
  • updates via the patchbox terminal app
  • BT device can be seen by PC and Smartphone when enabled, but not by pisound app

Something weird in the log, the date was wrong at first. I tried connecting from outside the app this might be visible in the log. The pisound app did not discover the RPi4 with Pisound:

May 17 14:32:26 patchbox systemd[1]: Condition check resulted in Bluetooth service being skipped.
May 17 14:32:37 patchbox systemd[1]: Starting Bluetooth service...
May 17 14:32:40 patchbox bluetoothd[821]: Bluetooth daemon 5.55
May 17 14:32:40 patchbox bluetoothd[821]: Starting SDP server
May 17 14:32:40 patchbox systemd[1]: Started Bluetooth service.
May 17 14:32:40 patchbox bluetoothd[821]: Bluetooth management interface 1.21 initialized
May 17 14:32:42 patchbox bluetoothd[821]: profiles/sap/server.c:sap_server_register() Sap driver initialization failed.
May 17 14:32:42 patchbox bluetoothd[821]: sap-server: Operation not permitted (1)
May 17 14:32:42 patchbox bluetoothd[821]: Failed to set privacy: Rejected (0x0b)
Mar 26 10:03:25 patchbox bluetoothd[821]: Endpoint registered: sender=:1.49 path=/MediaEndpoint/A2DPSink/sbc
Mar 26 10:03:25 patchbox bluetoothd[821]: Endpoint registered: sender=:1.49 path=/MediaEndpoint/A2DPSource/sbc
Mar 26 10:03:25 patchbox bluetoothd[821]: src/profile.c:ext_start_servers() RFCOMM server failed for Headset unit: rfcomm_bind: Address already in use (98)
Mar 26 10:06:40 patchbox bluetoothd[821]: Endpoint unregistered: sender=:1.49 path=/MediaEndpoint/A2DPSink/sbc
Mar 26 10:06:40 patchbox bluetoothd[821]: Endpoint unregistered: sender=:1.49 path=/MediaEndpoint/A2DPSource/sbc
Mar 26 10:06:40 patchbox bluetoothd[821]: Terminating
Mar 26 10:06:40 patchbox bluetoothd[821]: Stopping SDP server
Mar 26 10:06:40 patchbox systemd[1]: Stopping Bluetooth service...
Mar 26 10:06:40 patchbox bluetoothd[821]: Exit
Mar 26 10:06:40 patchbox systemd[1]: bluetooth.service: Succeeded.
Mar 26 10:06:40 patchbox systemd[1]: Stopped Bluetooth service.
-- Boot a4fa390bed0b45fdb811652aae494064 --
Mar 26 10:06:52 patchbox systemd[1]: Condition check resulted in Bluetooth service being skipped.
Mar 26 10:06:59 patchbox systemd[1]: Starting Bluetooth service...
Mar 26 10:07:00 patchbox bluetoothd[1043]: Bluetooth daemon 5.55
Mar 26 10:07:00 patchbox systemd[1]: Started Bluetooth service.
Mar 26 10:07:00 patchbox bluetoothd[1043]: Starting SDP server
Mar 26 10:07:00 patchbox bluetoothd[1043]: Bluetooth management interface 1.21 initialized
Mar 26 10:07:00 patchbox bluetoothd[1043]: profiles/sap/server.c:sap_server_register() Sap driver initialization failed.
Mar 26 10:07:00 patchbox bluetoothd[1043]: sap-server: Operation not permitted (1)
Mar 26 10:07:00 patchbox bluetoothd[1043]: Endpoint registered: sender=:1.23 path=/MediaEndpoint/A2DPSink/sbc
Mar 26 10:07:00 patchbox bluetoothd[1043]: Endpoint registered: sender=:1.23 path=/MediaEndpoint/A2DPSource/sbc
Mar 26 10:07:00 patchbox bluetoothd[1043]: Failed to set privacy: Rejected (0x0b)
Mar 26 10:15:09 patchbox bluetoothd[1043]: Endpoint unregistered: sender=:1.23 path=/MediaEndpoint/A2DPSink/sbc
Mar 26 10:15:09 patchbox bluetoothd[1043]: Endpoint unregistered: sender=:1.23 path=/MediaEndpoint/A2DPSource/sbc
Mar 26 10:15:09 patchbox systemd[1]: Stopping Bluetooth service...
Mar 26 10:15:09 patchbox bluetoothd[1043]: Terminating
Mar 26 10:15:09 patchbox bluetoothd[1043]: Stopping SDP server
Mar 26 10:15:09 patchbox bluetoothd[1043]: Exit
Mar 26 10:15:09 patchbox systemd[1]: bluetooth.service: Succeeded.
Mar 26 10:15:09 patchbox systemd[1]: Stopped Bluetooth service.
-- Boot c3c7a07d31494f40bd5a1976fb291cea --
Mar 26 10:15:24 patchbox systemd[1]: Condition check resulted in Bluetooth service being skipped.
Mar 26 10:15:31 patchbox systemd[1]: Starting Bluetooth service...
Mar 26 10:15:31 patchbox bluetoothd[866]: Bluetooth daemon 5.55
Mar 26 10:15:31 patchbox systemd[1]: Started Bluetooth service.
Mar 26 10:15:31 patchbox bluetoothd[866]: Starting SDP server
Mar 26 10:15:31 patchbox bluetoothd[866]: Bluetooth management interface 1.21 initialized
Mar 26 10:15:31 patchbox bluetoothd[866]: profiles/sap/server.c:sap_server_register() Sap driver initialization failed.
Mar 26 10:15:31 patchbox bluetoothd[866]: sap-server: Operation not permitted (1)
Mar 26 10:15:31 patchbox bluetoothd[866]: Endpoint registered: sender=:1.22 path=/MediaEndpoint/A2DPSink/sbc
Mar 26 10:15:31 patchbox bluetoothd[866]: Endpoint registered: sender=:1.22 path=/MediaEndpoint/A2DPSource/sbc
Mar 26 10:15:31 patchbox bluetoothd[866]: Failed to set privacy: Rejected (0x0b)
Mar 26 10:32:00 patchbox bluetoothd[866]: src/profile.c:ext_io_disconnected() Unable to get io data for Headset unit: getpeername: Transport endpoint is not connected (107)

And the other output:

patch@patchbox:~ $ sudo systemctl status pisound-ctl
● pisound-ctl.service - Bluetooth service for Pisound companion app.
     Loaded: loaded (/usr/lib/systemd/system/pisound-ctl.service; enabled; vendor preset: enabled)
     Active: active (running) since Tue 2024-03-26 10:15:23 GMT; 34min ago
   Main PID: 489 (pisound-ctl)
      Tasks: 14 (limit: 4915)
        CPU: 13.195s
     CGroup: /system.slice/pisound-ctl.service
             ├─489 /usr/bin/pisound-ctl
             ├─959 /bin/sh /usr/bin/mec /etc/mec-blokas.json
             ├─963 mec-app /etc/mec-blokas.json
             └─964 osc2midi pisound-ctl 127.0.0.1 53409

Mar 26 10:15:32 patchbox pisound-ctl[963]: mec api initialise
Mar 26 10:15:32 patchbox pisound-ctl[963]: mecapi_proc start
Mar 26 10:15:32 patchbox pisound-ctl[963]: MecApi::MecApi
Mar 26 10:15:32 patchbox pisound-ctl[963]: MecApi_Impl::init
Mar 26 10:15:32 patchbox pisound-ctl[963]: KontrolDevice initialise
Mar 26 10:15:32 patchbox pisound-ctl[963]: KontrolDevice::init
Mar 26 10:15:32 patchbox pisound-ctl[963]: mec_app running
Mar 26 10:15:32 patchbox pisound-ctl[963]: kontrol device : listening on 6050
Mar 26 10:15:32 patchbox pisound-ctl[963]: KontrolDevice::init - complete
Mar 26 10:15:52 patchbox pisound-ctl[963]: KontrolDevice::new client 127.0.0.1 : 47579 KA = 5
patch@patchbox:~ $
6

I have the same line in my output. No other devices connected, also not to my smartphone.
I even tried connecting with a fresh smartphone that never had any other Bluetooth device connected to it. Same result

7

I got rid of the SAP (SIM Access Protocol) error by disabling that in the bluetooth service, but it does not seem to be related

This issue though seems to be related, but I tried everything mentioned there without luck

I also manually enabled “discover nearby devices” as the app did not ask this permission… but still no luck

image
image627×1072 50.8 KB

8

What is the output of lsb_release -a?

I tried reproducing the problem, but it’s working just fine for me.

I do receive some of the same errors in bluetooth.service journactl log, but not the RFCOMM address is in use one:

Mar 26 16:11:52 patchbox systemd[1]: Condition check resulted in Bluetooth service being skipped.
Mar 26 16:11:56 patchbox systemd[1]: Starting Bluetooth service...
Mar 26 16:11:56 patchbox bluetoothd[844]: Bluetooth daemon 5.55
Mar 26 16:11:56 patchbox systemd[1]: Started Bluetooth service.
Mar 26 16:11:56 patchbox bluetoothd[844]: Starting SDP server
Mar 26 16:11:56 patchbox bluetoothd[844]: Bluetooth management interface 1.22 initialized
Mar 26 16:11:56 patchbox bluetoothd[844]: profiles/sap/server.c:sap_server_register() Sap driver initialization failed.
Mar 26 16:11:56 patchbox bluetoothd[844]: sap-server: Operation not permitted (1)
Mar 26 16:11:56 patchbox bluetoothd[844]: Endpoint registered: sender=:1.19 path=/MediaEndpoint/A2DPSink/sbc
Mar 26 16:11:56 patchbox bluetoothd[844]: Endpoint registered: sender=:1.19 path=/MediaEndpoint/A2DPSource/sbc
Mar 26 16:11:56 patchbox bluetoothd[844]: Failed to set privacy: Rejected (0x0b

So the above log lines don’t impact operation of pisound-ctl.

9

Yes, tanks for the answer ( and sorry for the Multiple reply i made in the other thread)

I give you the output this evening

Thanks again !

10

I wiped SD card again, did everything without updating again. Just to test if the stock OS image would work
then I switched to the non RT-kernel, just to test, but I get the exact same issues
I then switched back to the RT kernel (on RPi4 -4Gb)
Then I updated again…

This is my output

Last login: Tue Mar 26 14:26:38 2024
patch@patchbox:~ $ lsb_release -a
No LSB modules are available.
Distributor ID:	Raspbian
Description:	Raspbian GNU/Linux 11 (bullseye)
Release:	11
Codename:	bullseye
patch@patchbox:~ $ uname -a
Linux patchbox 5.15.36-rt41-v7l+ #1 SMP PREEMPT_RT Mon May 9 12:16:02 EEST 2022 armv7l GNU/Linux
patch@patchbox:~ $
11

Mmm now you are pointing this, i see that it was not the entire log,
So here is the full result :

bluetoot.log (18.5 KB)

And i’m not using any other bluetooth device.

and here the result of lsb_release -a

No LSB modules are available.
Distributor ID: Raspbian
Description:    Raspbian GNU/Linux 11 (bullseye)
Release:        11
Codename:       bullseye

thanks for your help !

12

By the way, every time you reflash the OS on Raspberry Pi, it gets some new system finger print, making previous pairing remembered by your phone no longer valid.

Make sure to manually unpair (forget / remove the device from the Bluetooth devices settings screen), before trying to pair via the app again.

So far I haven’t been able to reproduce the problem.

At the same time I’m working on updating the Patchbox OS image, so it would make sense to focus on getting this working on the new image, once it’s out, as there’s going to be big changes to various software and drivers anyway.

3 Likes
13

Ok, if you can’t reproduce the problem, i understand that you can’t help us !

And yes i made the unpair/pair trick a lot of time, but doesn’t change anything.

And for sure if you are working on a new PatchBox OS image, don’t worry about my problem, like you said, we will see this with the new image. I just hope it doesn’t come from my phone !!

So thanks for your help, and have a good day !

14

I tried multiple phones, including one that was not paired before. I “forgot” the pairing before I tried again

If it could help, I could set up remote Ssh access to my pisound

15

I installed the new Patchbox OS image.

Same behaviour

I can see and pair from the bluetooth settings of my phone, or from the patchbox OS bluetooth icon in the taskbar(topright)
but not from the android app

16

What happens exactly when you attempt to pair through the App?

17

The app keeps showing the spinning wheel, but no device ever shows up

18

This is while scanning for nearby devices? Did you enable the discoverable mode by holding down the button for 1-2 seconds? The LEDs on Pisound should keep blinking for about 3 minutes while the discoverable mode is on.

1 Like
19

Just wanted to add that I’m having the same problem - I’ve had patchbox/pisound for a few months and it never worked, but I didn’t dig deep until the past week.

I start pairing mode using the button and then using the app, I hit scan and it continually shows the searching wheel animation and never finds anything

Here’s everything I tried:

  • Held the button down to initiate pair mode - the LEDs were blinking for a while indicating pairing
  • SSHed in and managed bluetooth through the patchbox command and started pair mode manually (same result…blinking for awhile to indicate pairing
  • Turned on “allow location” in the app
  • Tried my Pixel 8 Pro, my wife’s Pixel 8, and my now ancient Chromebook - none of them can find
  • Re-flashed my SD card to do a new Patchbox install
  • Re-flashed again when I saw there was a beta release of Patchbox from 4/4/2024
  • Re-flashed yet again without installing MODEP (as I saw in other threads this was a potential culprit)
  • Tried a USB Bluetooth dongle on top of what was already in my Pi (though I wasn’t very scientific, so I’m not sure if it was actually attempting to use the new one)
  • Reviewed my logs and definitely saw a line that said “Failed to set mode: Rejected” like mentioned here BLE connection fail - bluetoothd[575]: Failed to set mode: Rejected (0x0b) · Issue #35 · RPi-Distro/pi-bluetooth · GitHub. I tried various solutions that replace some of the bluetooth startup utils (I think they were all shell scripts). None of them solved it for me even though various folks on Stack Overflow and Github said it worked for them

Additionally, my Pixel 8 Pro finds Patchbox in my bluetooth devices list just fine when it’s in pairing mode, and I can pair it this way, but it really doesn’t seem to help with the app finding Patchbox.

Oh and I’m on a Pi 4 if that makes a difference

20

I did some more digging.

patch@patchbox:~ $ sudo patchbox-config 
2024-06-06.11:52:13: Setting Discoverable prop of /org/bluez/hci0 to true
Error: GDBus.Error:org.bluez.Error.Failed: Not Powered
bluetooth_supported=1
bluetooth_service_active_state=active
bluetooth_service_sub_state=running
bluealsa_service_active_state=inactive
bluealsa_service_sub_state=dead
hciuart_service_active_state=inactive
hciuart_service_sub_state=dead
bluetooth_soft_blocked=yes
bluetooth_hard_blocked=no

Press any key to continue...

note the bluetooth_soft_blocked=yes line

digging some more

patch@patchbox:~ $ hciconfig hci0 up
Can't init device hci0: Operation not permitted (1)
patch@patchbox:~ $ sudo hciconfig hci0 up
Can't init device hci0: Operation not possible due to RF-kill (132)

I can get past the no-powered problem.
by running

patch@patchbox:~ $ rfkill unblock all
patch@patchbox:~ $ sudo hciconfig hci0 up
patch@patchbox:~ $ bluetoothctl
Agent registered
[bluetooth]# power on
Changing power on succeeded

Then asking the status from patchbox-config changes the softblocked line


patch@patchbox:~ $ sudo patchbox-config 
2024-06-06.12:02:57: Setting Discoverable prop of /org/bluez/hci0 to true
bluetooth_supported=1
bluetooth_service_active_state=active
bluetooth_service_sub_state=running
bluealsa_service_active_state=inactive
bluealsa_service_sub_state=dead
hciuart_service_active_state=inactive
hciuart_service_sub_state=dead
bluetooth_soft_blocked=no
bluetooth_hard_blocked=no

Press any key to continue..

but that does not help me connecting the app to it…

I do hope this gives some insights
RPi4 4Gb with regular kernel

I switched to console mode, trying to eliminate the possibility that some graphical applet was interfering with the bluetooth, but i get the exact same results


Pisound Button Version: 1.16
Pisound Hardware Version: 1.1
Pisound Server Version: 1.03
Pisound Firmware Version: 1.03
Pisound Serial Number: PS-XXXXX

Linux patchbox 6.6.20+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.6.20-1+rpt1 (2024-03-07) aarch64

I also deleted the pisound app, removed the data, rebooterd my phone and reinstalled pisound, granting access to bluetooth & nearby devices/location… no progress