[PROBLEM] Issue with Blutooth in 4.1

[Dileas]

Hello,

Looking for some help with setting up Bluetooth on a clean install of Moode 4.1 on a Pi 3 Model B with an IQ Audio Dac+ and IQ Audio Pi Amp+.

Most things seem to work fine with the exception of the Bluetooth.  On the Bluetooth config page the run command  is not enabled, although on the System Config page the Bluetooth is enabled.


When I run "systemctl status bluetooth" the following is returned.

Loaded: loaded (/lib/systemd/system/bluetooth.service; disabled; vendor preset: enabled)
   Active: inactive (dead)
Condition: start condition failed at Wed 2018-04-11 12:16:42 BST; 4h 28min ago
           └─ ConditionPathIsDirectory=/sys/class/bluetooth was not met
     Docs: man:bluetoothd(8)


Very much a beginner with the Moode, Linux and the Pi, so would be grateful for advice as to how to proceed and sort out the Bluetooth.

Thanks

[TheOldPresbyope]

Hello,

Looking for some help with setting up Bluetooth on a clean install of Moode 4.1 on a Pi 3 Model B with an IQ Audio Dac+ and IQ Audio Pi Amp+.

Most things seem to work fine with the exception of the Bluetooth.  On the Bluetooth config page the run command  is not enabled, although on the System Config page the Bluetooth is enabled.


When I run "systemctl status bluetooth" the following is returned.

Loaded: loaded (/lib/systemd/system/bluetooth.service; disabled; vendor preset: enabled)
   Active: inactive (dead)
Condition: start condition failed at Wed 2018-04-11 12:16:42 BST; 4h 28min ago
           └─ ConditionPathIsDirectory=/sys/class/bluetooth was not met
     Docs: man:bluetoothd(8)


Very much a beginner with the Moode, Linux and the Pi, so would be grateful for advice as to how to proceed and sort out the Bluetooth.

Thanks

@Dileas

Go to the Audio Config page and set "Bluetooth speaker" on. Then run systemctl again. You should see your service running.

Regards,
Kent

[Dileas]

Hello,

Looking for some help with setting up Bluetooth on a clean install of Moode 4.1 on a Pi 3 Model B with an IQ Audio Dac+ and IQ Audio Pi Amp+.

Most things seem to work fine with the exception of the Bluetooth.  On the Bluetooth config page the run command  is not enabled, although on the System Config page the Bluetooth is enabled.


When I run "systemctl status bluetooth" the following is returned.

Loaded: loaded (/lib/systemd/system/bluetooth.service; disabled; vendor preset: enabled)
   Active: inactive (dead)
Condition: start condition failed at Wed 2018-04-11 12:16:42 BST; 4h 28min ago
           └─ ConditionPathIsDirectory=/sys/class/bluetooth was not met
     Docs: man:bluetoothd(8)


Very much a beginner with the Moode, Linux and the Pi, so would be grateful for advice as to how to proceed and sort out the Bluetooth.

Thanks

@Dileas

Go to the Audio Config page and set "Bluetooth speaker" on. Then run systemctl again. You should see your service running.

Regards,
Kent

Hi Kent,

Thanks for that, my problem now resolved.

Regards
Dileas

[dbrgn]

I'm also having issues with Bluetooth in Moode 4.1 when trying to use Moode as an audio sink.

I previously used Moode 4.0 on a Raspi Zero W, where connecting worked without a problem.

Now on Moode 4.1 on a Raspi 3 B+, I can pair my phone with the Raspberry Pi, but Moode does not advertise itself as audio device. When showing the device in Android, it is not listed as audio device, so I can't send any audio to it.

If I try to connect from Moode *to* the phone, then I get this log in the bluetoothd journal:

Apr 16 18:40:00 moode bluetoothd[843]: a2dp-source profile connect failed for 84:CF:BF:88:CA:16: Protocol not available

My phone (FP2D) is trusted and paired:

Code:

$ sudo /var/www/command/bt.sh -l | grep FP2D
** 84:CF:BF:88:CA:16 FP2D
$ sudo /var/www/command/bt.sh -p
** Paired devices
**
** 84:CF:BF:88:CA:16 FP2D
**

But as I wrote, I cannot connect to it as an audio device. Restarting both Moode and the phone didn't help.

Any ideas?

[dbrgn]

I also just tried it with the Nexus 10 Android tablet - same result.

Here's a screenshot from the phone. "Grundig 2012" is Moode, it's just listed as bluetooth device without any profiles. The UE Boom in contrast is shown as device with audio and phone profiles.

[Tim Curtis]

Very odd.

Try removing all pairings on moOde and then on one of your devices remove the moOde pairing. Then Reboot moOde and turn Bluetooth OFF/ON on your device.

Then re-pair and see if that solves the problem.

-Tim

[TheOldPresbyope]

I also just tried it with the Nexus 10 Android tablet - same result.

Here's a screenshot from the phone. "Grundig 2012" is Moode, it's just listed as bluetooth device without any profiles. The UE Boom in contrast is shown as device with audio and phone profiles.

@dbrgn

Running the app "Bluetooth Profiles Scanner" on my Nexus 9 tablet (Android 7.1.1), I see the two moOde r41 players I currently have running are advertising both the Advanced Audio Distribution Audio Profile (A2DP) and the Audio/Video Remote Control Profile (AVRCP). In the Bluetooth devices screen on the tablet, I see (under the gear icons) the paired players can be used for media audio.

Having said this, using the same Bluetooth source and settings, my installation of the released version of r41 doesn't seem to be playing the Bluetooth stream while an earlier r41beta version does, so I think you may be on to something.

Will investigate tonight. I know the beta and released versions have different versions of the Bluetooth stack but I haven't looked into the specifics.

Regards,
Kent

[Tim Curtis]

Hi Kent,

For reference, I just ran a clean-slate test using iPhone, iPad and an ANKER SoundCore speaker with release 4.1 on Pi-3B, 3B+ and a 0W. The only issue I ran into was that I had to turn Bluetooth OFF/ON on my iPhone in order for it to see the 0W, otherwise no issues with discovery, pairing, connecting and playing music.

Email me if you run into issues tonight :-)

-Tim

[dbrgn]

I'll try to test it later this week

[Tim Curtis]

Hi Kent,

For reference, I just ran a clean-slate test using iPhone, iPad and an ANKER SoundCore speaker with release 4.1 on Pi-3B, 3B+ and a 0W. The only issue I ran into was that I had to turn Bluetooth OFF/ON on my iPhone in order for it to see the 0W, otherwise no issues with discovery, pairing, connecting and playing music.

Email me if you run into issues tonight :-)

-Tim

Hey Kent,

Bluetoothctl util can be used to see what Bluetooth profiles a particular paired device supports. The device needs to be paired but not connected.

Examples showing support for "Advanced Audio Distribu.." (A2DP) profile for both Anker SoundCore Speaker and iPhone.

Code:

pi@rp3:~ $ sudo bluetoothctl
Agent registered
[bluetooth]# info XX:XX:XX:XX:XX:XX
Device XX:XX:XX:XX:XX:XX (public)
        Name: Anker SoundCore
        Alias: Anker SoundCore
        Class: 0x00240404
        Icon: audio-card
        Paired: yes
        Trusted: yes
        Blocked: no
        Connected: no
        LegacyPairing: no
        UUID: Headset                   (00001108-0000-1000-8000-00805f9b34fb)
        UUID: Audio Sink                (0000110b-0000-1000-8000-00805f9b34fb)
        UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
        UUID: Advanced Audio Distribu.. (0000110d-0000-1000-8000-00805f9b34fb)
        UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
        UUID: Handsfree                 (0000111e-0000-1000-8000-00805f9b34fb)
[bluetooth]# 

[bluetooth]# info YY:YY:YY:YY:YY:YY
Device YY:YY:YY:YY:YY:YY (public)
        Name: Tim's iPhone
        Alias: Tim's iPhone
        Class: 0x007a020c
        Icon: phone
        Paired: yes
        Trusted: yes
        Blocked: no
        Connected: no
        LegacyPairing: no
        UUID: Vendor specific           (00000000-deca-fade-deca-deafdecacafe)
        UUID: Service Discovery Serve.. (00001000-0000-1000-8000-00805f9b34fb)
        UUID: Audio Source              (0000110a-0000-1000-8000-00805f9b34fb)
        UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
        UUID: Advanced Audio Distribu.. (0000110d-0000-1000-8000-00805f9b34fb)
        UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
        UUID: NAP                       (00001116-0000-1000-8000-00805f9b34fb)
        UUID: Handsfree Audio Gateway   (0000111f-0000-1000-8000-00805f9b34fb)
        UUID: Phonebook Access Server   (0000112f-0000-1000-8000-00805f9b34fb)
        UUID: Message Access Server     (00001132-0000-1000-8000-00805f9b34fb)
        UUID: PnP Information           (00001200-0000-1000-8000-00805f9b34fb)
        Modalias: bluetooth:v004Cp6D00d0A30
[bluetooth]# 

-Tim