Bluetooth - Paired but can't connect

[Birdy961]

What were your exact steps to connect using RaspiOS?

I used the RaspOS UI to make it discoverable and then scanned from my phone to find it and pair.

Once paired it allowed me to connect for audio (which is the option that doesn't show up on moOde)

---

[Birdy961]

What were your exact steps to connect using RaspiOS?

I used the RaspOS UI to make it discoverable and then scanned from my phone to find it and pair.

Once paired it allowed me to connect for audio (which is the option that doesn't show up on moOde)

---

  

Took some screenshots to show how it comes up in the bluetooth menu of my phone - through RaspOS it is shown as an audio device, whereas through moOde it isn't.

[TheOldPresbyope]

@Birdy961

I'm living out of suitcase and boxes at the moment and have no time for forensics but FYI my Google Pixel 3A phone running Android 11 has no problem pairing and connecting with our test release moOde 7.3.0. Android reports the moOde player as a connected media device and looking under device details I see that "Media audio" is enabled. (My iPad connects as well but Tim already has iOS covered.)

Yes, this is a test release and not moOde 7.2.1, but I don't recall that the Bluetooth connection aspect changed between the two.

I lean toward suspecting a difference between Samsung's version of Android/Bluetooth and Google's. Bluetooth is one of those specification which leave a lot of details up to the implementer. Again, I'm in no position to do any forensic tests so I'll return to lurking mode.

Regards,
Kent

[the_bertrum]

I have a Samsung Android and don't have any issues with Bluetooth on either the test release or 7.2.1. My pairing screens look like those above, except I have "Audio" with a switch to connect/disconnect on my moOde connection.

It could be the specifics of the phone perhaps, but it should "just work"™.

It might be flashing a fresh moOde to the SD card and trying to pair with very little else configured, just to rule out errors in the image. Failing that then we'll need to play with the information that can be gleaned from the diagnostic commands that Tim posted above.

[Tim Curtis]

Right, no changes in the Bluetooth stack since moOde 7.0.0 release which contained the RaspiOS 10.6 Bluetooth bundle plus our compile of bluez-alsa 3.0.0 w/SBC XQ which has proven to work well in the field.

We will likely bump to latest RaspiOS, Kernel and bluez-alsa when moOde 8 series is released.

[Birdy961]

@Birdy961

I'm living out of suitcase and boxes at the moment and have no time for forensics but FYI my Google Pixel 3A phone running Android 11 has no problem pairing and connecting with our test release moOde 7.3.0. Android reports the moOde player as a connected media device and looking under device details I see that "Media audio" is enabled. (My iPad connects as well but Tim already has iOS covered.)

Yes, this is a test release and not moOde 7.2.1, but I don't recall that the Bluetooth connection aspect changed between the two.

I lean toward suspecting a difference between Samsung's version of Android/Bluetooth and Google's. Bluetooth is one of those specification which leave a lot of details up to the implementer. Again, I'm in no position to do any forensic tests so I'll return to lurking mode.

Regards,
Kent

Cheers for the reply - the only thing that makes me not convinced it is the phone is that my win10 laptop had basically the same issue (not showing up as an audio device).

Hope your living situation gets better soon though, living out of boxes is never good!

[Birdy961]

Thanks all for the input on this - I have installed version 6.7.1 on which the bluetooth seems to work fine with my phone, then dowloaded 7.2.1 afresh and reflashed, bluetooth not working on that one!

I will stick to 6.7.1 for now and hopefully have more luck with version 8 when it is released!

[the_bertrum]

One last check, is your phone software up to date?

[Birdy961]

One last check, is your phone software up to date?

Yeah all up to date, laptop is as well.

[diist]

Just came here to say I have to same problem with a fresh install of 7.3.0