# RPi 4 Bluetooth Connection Fail \[solved, possibly\]

**URL:** <https://community.blokas.io/t/rpi-4-bluetooth-connection-fail-solved-possibly/2674>\
**Category:** Mobile App\
**Created:** [January 29, 2021, 3:53pm UTC](https://community.blokas.io/t/rpi-4-bluetooth-connection-fail-solved-possibly/2674 "2021-01-29T15:53:28Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![soxsa](https://community.blokas.io/letter_avatar_proxy/v4/letter/s/ce7236/32.png) [@soxsa](https://community.blokas.io/u/soxsa)\
**Post date:** [January 29, 2021, 3:53pm UTC](https://community.blokas.io/t/rpi-4-bluetooth-connection-fail-solved-possibly/2674/1 "2021-01-29T15:53:28Z")

</div>

I get a ‘Connection Error’ when trying to connect from the Scan page of the Mobile App to the Raspberry Pi 4. When I try it manually, I get the ‘Protocol not available’ message.

![bluetooth fail 2](https://community.blokas.io/uploads/default/original/2X/3/3ab1b783c5732d30702a34e7d11b4edfb15479a6.png)

Here’s the bluetooth status, showing all running. Using `bluetoothctl` I can see the device trying to connect, made sure it’s trusted.

Any ideas?

![bluetooth status](https://community.blokas.io/uploads/default/original/2X/7/790d615803d5da9a4f519f15f72774c8fa0f6175.png)

---

<div class="post-metadata">

**Author:** ![Giedrius](https://community.blokas.io/letter_avatar_proxy/v4/letter/g/6a8cbe/32.png) [@Giedrius](https://community.blokas.io/u/Giedrius)\
**Post date:** [January 29, 2021, 4:03pm UTC](https://community.blokas.io/t/rpi-4-bluetooth-connection-fail-solved-possibly/2674/2 "2021-01-29T16:03:48Z")

</div>

What is the output of:

```auto
sudo systemctl status pisound-ctl

```

?

You may inspect its log by running:

```auto
sudo journalctl -u pisound-ctl

```

---

<div class="post-metadata">

**Author:** ![soxsa](https://community.blokas.io/letter_avatar_proxy/v4/letter/s/ce7236/32.png) [@soxsa](https://community.blokas.io/u/soxsa)\
**Post date:** [January 29, 2021, 4:06pm UTC](https://community.blokas.io/t/rpi-4-bluetooth-connection-fail-solved-possibly/2674/3 "2021-01-29T16:06:08Z")

</div>

> [@Giedrius](#):
>
> `sudo systemctl status pisound-ctl`

![image](https://community.blokas.io/uploads/default/original/2X/1/1ac7094e77cf9f60658082943dad797382be8569.png)

I’ve tried this with a couple of phones, sames result. I should mention that I’m running remote-desktop server. I tried with ssh, same result.

Also I don’t have my pisound card yet, it’s delayed due to ‘Brexit’ 😱 But I was guessing that wasn’t necessary at this point?

---

<div class="post-metadata">

**Author:** ![soxsa](https://community.blokas.io/letter_avatar_proxy/v4/letter/s/ce7236/32.png) [@soxsa](https://community.blokas.io/u/soxsa)\
**Post date:** [January 29, 2021, 4:10pm UTC](https://community.blokas.io/t/rpi-4-bluetooth-connection-fail-solved-possibly/2674/4 "2021-01-29T16:10:44Z")

</div>

The last lines of the log…

 ![image](https://community.blokas.io/uploads/default/original/2X/1/1747b77700bf1e44bdbaa85d983a926c88ffddec.png)

---

<div class="post-metadata">

**Author:** ![soxsa](https://community.blokas.io/letter_avatar_proxy/v4/letter/s/ce7236/32.png) [@soxsa](https://community.blokas.io/u/soxsa)\
**Post date:** [January 29, 2021, 4:15pm UTC](https://community.blokas.io/t/rpi-4-bluetooth-connection-fail-solved-possibly/2674/5 "2021-01-29T16:15:06Z")

</div>

Can the app connect over WiFi instead? That would do for me.

---

<div class="post-metadata">

**Author:** ![Giedrius](https://community.blokas.io/letter_avatar_proxy/v4/letter/g/6a8cbe/32.png) [@Giedrius](https://community.blokas.io/u/Giedrius)\
**Post date:** [January 29, 2021, 10:11pm UTC](https://community.blokas.io/t/rpi-4-bluetooth-connection-fail-solved-possibly/2674/6 "2021-01-29T22:11:30Z")

</div>

The server runs only if Pisound is attached, so you’ll have to wait for it to get delivered. 🙂

---

<div class="post-metadata">

**Author:** ![soxsa](https://community.blokas.io/letter_avatar_proxy/v4/letter/s/ce7236/32.png) [@soxsa](https://community.blokas.io/u/soxsa)\
**Post date:** [January 30, 2021, 8:07am UTC](https://community.blokas.io/t/rpi-4-bluetooth-connection-fail-solved-possibly/2674/7 "2021-01-30T08:07:18Z")

</div>

Ah ha 🙂

---

<div class="post-metadata">

**Author:** ![soxsa](https://community.blokas.io/letter_avatar_proxy/v4/letter/s/ce7236/32.png) [@soxsa](https://community.blokas.io/u/soxsa)\
**Post date:** [February 3, 2021, 1:12pm UTC](https://community.blokas.io/t/rpi-4-bluetooth-connection-fail-solved-possibly/2674/8 "2021-02-03T13:12:29Z")

</div>

Yes, with the pisound attached, the mobile app does connect. I still see that protocol error pop up btw. I find the app keeps disconnecting, but could well be my phone. I’m not planning to use it for control that much anyway. The plan is more midi-controller knob-twiddling.

---

<div class="post-metadata">

**Author:** ![Giedrius](https://community.blokas.io/letter_avatar_proxy/v4/letter/g/6a8cbe/32.png) [@Giedrius](https://community.blokas.io/u/Giedrius)\
**Post date:** [February 3, 2021, 2:13pm UTC](https://community.blokas.io/t/rpi-4-bluetooth-connection-fail-solved-possibly/2674/9 "2021-02-03T14:13:57Z")

</div>

We’ve seen these unexpected disconnects happen when some bluetooth related system libraries out of date.

Another reason could be, if you’re using the realtime kernel, that the libraries are actually too new for the kernel. Unfortunately there’s been no good updates to the RT branches yet on the RPi Foundation’s kernel tree.

---

<div class="post-metadata">

**Author:** ![soxsa](https://community.blokas.io/letter_avatar_proxy/v4/letter/s/ce7236/32.png) [@soxsa](https://community.blokas.io/u/soxsa)\
**Post date:** [February 3, 2021, 2:53pm UTC](https://community.blokas.io/t/rpi-4-bluetooth-connection-fail-solved-possibly/2674/10 "2021-02-03T14:53:34Z")

</div>

OK, as I say not a major thing for me. I’ll try with a different phone anyway.

Not for now, but if one day the mobile app could be made to connect via wifi that would be a good thing IMO. I’ve no idea if that’s an easy or difficult thing for you, of course. I often find BT behaves oddly at times, I think that’s the common experience.

---

<div class="post-metadata">

**Author:** ![soxsa](https://community.blokas.io/letter_avatar_proxy/v4/letter/s/ce7236/32.png) [@soxsa](https://community.blokas.io/u/soxsa)\
**Post date:** [February 18, 2021, 1:04pm UTC](https://community.blokas.io/t/rpi-4-bluetooth-connection-fail-solved-possibly/2674/11 "2021-02-18T13:04:34Z")

</div>

Update, after reading around, people were reporting bluetooth dropouts on standard Raspbian, with BT keyboards for instance. A suggested fix was to copy the firmware from the latest OS update (the one at the end of 2020).

Files in `/lib/firmware/brcm`

I did that on my patchbox OS (keeping a copy of course) and indeed after a reboot, my phone has a stable connection from the patchbox app to the pisound.

Not saying this is a definitive fix, it’s a hack, but working at the moment.

---

<div class="post-metadata">

**Author:** ![soxsa](https://community.blokas.io/letter_avatar_proxy/v4/letter/s/ce7236/32.png) [@soxsa](https://community.blokas.io/u/soxsa)\
**Post date:** [February 18, 2021, 1:27pm UTC](https://community.blokas.io/t/rpi-4-bluetooth-connection-fail-solved-possibly/2674/12 "2021-02-18T13:27:05Z")

</div>

A quick go with the app - it’s very cool 😄

Controlling the parameters from a phone, yes it’s handy but fiddly in a live situation. But I didn’t know about the MIDI learn feature - now that is really good!!!

---

<div class="post-metadata">

**Author:** ![Kasper\_Jordaens](https://community.blokas.io/user_avatar/community.blokas.io/kasper_jordaens/32/968_2.png) [@Kasper\_Jordaens](https://community.blokas.io/u/Kasper_Jordaens)\
**Post date:** [February 9, 2023, 9:28am UTC](https://community.blokas.io/t/rpi-4-bluetooth-connection-fail-solved-possibly/2674/13 "2023-02-09T09:28:35Z")

</div>

> [@soxsa](#):
>
> A suggested fix was to copy the firmware from the latest OS update

Could you elaborate on how to do this?
