Moode 8.2.2 (arm 64) bluetooth issues

[audioDrax]

Hi all,

New to the forum and moode in general, been using it since 24th Oct. A nice bit of kit so far but having some trouble with bluetooth headphones.


Using moode 8.2.2 bluetooth playback not working after connecting Sony WF-1000XM4 headphones.

Turned on bluetooth, paired and connected fine to the headphones, and changed to bluetooth playback mode.
Volume was changed slowly from 0-100%.
headphone disconnect after about 30 secs or everytime the volume is changed or menu selected.

No sound is outputted via the bluetooth headphones.

I came from volumio as their bluetooth is behind a paid wall, I have not tested these headphones with that player but I have used them on tablet, phone and PC all without issue and working as expected.

The Pi is a 4, with khadas Tone Board DAC via USB, this output mode works perfectly with Moode.

Is there something I am missing with bluetooth setup? I have been through and changed every setting I can with no change in the output audio (or lack of) via bluetooth.

I appreciate the help.

Thanks

[Tim Curtis]

Reboot and post the startup log and status of the Bluetooth daemon after the issue occurs.

Code:

moodeutl -l

systemctl status bluetooth

Disconnections can be caused by weak signal strength which can result if the Pi is in a metal enclosure,

[audioDrax]

Reboot and post the startup log and status of the Bluetooth daemon after the issue occurs.

Code:

moodeutl -l

systemctl status bluetooth

Disconnections can be caused by weak signal strength which can result if the Pi is in a metal enclosure,

moodeutl -l output;

Code:

20221105 171922 worker: --
20221105 171922 worker: -- Start moOde 8 series
20221105 171922 worker: --
20221105 171922 worker: Successfully daemonized
20221105 171924 worker: File check (OK)
20221105 171924 worker: Session vacuumed
20221105 171924 worker: Session loaded
20221105 171924 worker: Debug logging (OFF)
20221105 171924 worker: --
20221105 171924 worker: -- Audio debug
20221105 171924 worker: --
20221105 171924 worker: ALSA cards: (0:b1 | 1:Headphones | 2:Control | 3:empty
20221105 171924 worker: MPD config: (2:Khadas Tone Control | mixer:(Khadas Tone       Control ) | card:2)
20221105 171925 worker: ALSA mixer actual (Khadas Tone Control )
20221105 171925 worker: ALSA Khadas Tone Control volume set to (0%)
20221105 171925 worker: --
20221105 171925 worker: -- System
20221105 171925 worker: --
20221105 171926 worker: Host      (moode)
20221105 171926 worker: moOde     (8.2.2 2022-10-23)
20221105 171926 worker: RaspiOS   (11.5)
20221105 171926 worker: Kernel    (5.15.61-v8+ #1579)
20221105 171926 worker: Platform  (Pi-4B 1.2 2GB)
20221105 171926 worker: ARM arch  (aarch64, 64-bit)
20221105 171926 worker: MPD ver   (0.23.5)
20221105 171926 worker: CPU gov   (ondemand)
20221105 171926 worker: USB boot  (enabled)
20221105 171926 worker: File sys  (expanded)
20221105 171926 worker: HDMI port (Off)
20221105 171926 worker: Sys LED0  (On)
20221105 171926 worker: Sys LED1  (On)
20221105 171926 worker: --
20221105 171926 worker: -- Network
20221105 171926 worker: --
20221105 171926 worker: eth0 adapter exists
20221105 171926 worker: eth0 check for address (No)
20221105 171926 worker: eth0 address not assigned
20221105 171926 worker: wlan0 adapter does not exist
20221105 171926 worker: apd0 router mode (Off)
20221105 171926 worker: No active network interface
20221105 171926 worker: --
20221105 171926 worker: -- Software update
20221105 171926 worker: --
20221105 171926 worker: Automatic check (Off)
20221105 171926 worker: --
20221105 171926 worker: -- Audio config
20221105 171926 worker: --
20221105 171926 worker: MPD conf update skipped (USB device)
20221105 171926 worker: ALSA card number (2)
20221105 171926 worker: MPD audio output (Khadas Tone Control)
20221105 171926 worker: Audio formats (S16_LE, S32_LE, SPECIAL, DSD_U32_BE)
20221105 171926 worker: ALSA mixer name (Khadas Tone Control )
20221105 171926 worker: MPD mixer type (hardware)
20221105 171927 worker: Hdwr volume controller exists
20221105 171927 worker: Max ALSA volume (100%)
20221105 171927 worker: ALSA output mode (Default: plughw)
20221105 171927 worker: ALSA loopback (Off)
20221105 171927 worker: Reset renderer active flags
20221105 171927 worker: CamillaDSP (off)
20221105 171927 worker: --
20221105 171927 worker: -- File sharing
20221105 171927 worker: --
20221105 171927 worker: SMB file sharing (Off)
20221105 171927 worker: NFS file sharing (Off)
20221105 171927 worker: --
20221105 171927 worker: -- MPD startup
20221105 171927 worker: --
20221105 171927 worker: MPD started
20221105 171927 worker: MPD accepting connections
20221105 171927 worker: MPD output 1 ALSA Default (On)
20221105 171927 worker: MPD output 2 ALSA Bluetooth (Off)
20221105 171927 worker: MPD output 3 HTTP Server (Off)
20221105 171927 worker: MPD crossfade (off)
20221105 171927 worker: MPD ignore CUE files (yes)
20221105 171927 worker: --
20221105 171927 worker: -- Music sources
20221105 171927 worker: --
20221105 171927 worker: USB sources
20221105 171927 worker: No drives found
20221105 171927 worker: NAS sources
20221105 171927 worker: 192.168.0.19
20221105 171935 worker: Try (mount -t cifs "//192.168.0.19/music" -o username="P      i",password="",rsize=61440,wsize=65536,iocharset=utf8,ro,noserverino,dir_mode=07      77,file_mode=0777 "/mnt/NAS/192.168.0.19")
20221105 171935 worker: Err (mount error(113): could not connect to 192.168.0.19      Unable to find suitable address.)
20221105 171935 worker: Mount all submitted
20221105 171935 worker: --
20221105 171935 worker: -- Feature availability
20221105 171935 worker: --
20221105 171935 worker: Source select (available)
20221105 171935 worker: Source select (source: MPD)
20221105 171935 worker: Source select (output: Khadas Tone Control)
20221105 171943 worker: Bluetooth (available: started)
20221105 171943 worker: AirPlay renderer (available)
20221105 171943 worker: Spotify renderer (available)
20221105 171943 worker: Squeezelite (available)
20221105 171943 worker: RoonBridge renderer (not installed)
20221105 171943 worker: Multiroom sender (available)
20221105 171943 worker: Multiroom receiver (available)
20221105 171943 worker: UPnP renderer (available)
20221105 171943 worker: DLNA server (available)
20221105 171943 worker: GPIO button handler (available)
20221105 171943 worker: Stream recorder (n/a)
20221105 171943 worker: --
20221105 171943 worker: -- Other
20221105 171943 worker: --
20221105 171943 worker: USB volume knob (Off)
20221105 171943 worker: Shellinabox SSH started
20221105 171943 worker: USB auto-mounter (udisks-glue)
20221105 171943 worker: Saved MPD vol level (0)
20221105 171943 worker: Preamp volume level (0)
20221105 171943 worker: MPD volume level (100) restored
20221105 171943 worker: ALSA Khadas Tone Control volume (100%)
20221105 171943 worker: Auto-play (On)
20221105 171943 worker: Auto-playing id (39)
20221105 171943 worker: CoverView toggle (-off)
20221105 171943 worker: On-screen keyboard (Off)
20221105 171943 worker: Library scope (all)
20221105 171943 worker: Maintenance interval (360 minutes)
20221105 171943 worker: Screen saver activation (Never)
20221105 171943 worker: Session permissions (OK)
20221105 171943 worker: Mount monitor (Off)
20221105 171943 worker: Watchdog started
20221105 171943 worker: Ready

systemctl status bluetooth output;

Code:

bluetooth.service - Bluetooth service
    Loaded: loaded (/lib/systemd/system/bluetooth.service; disabled; vendor pr>
    Active: active (running) since Sat 2022-11-05 17:19:43 GMT; 5h 44min ago
      Docs: man:bluetoothd(8)
  Main PID: 1048 (bluetoothd)
    Status: "Running"
     Tasks: 1 (limit: 2137)
       CPU: 155ms
    CGroup: /system.slice/bluetooth.service
            └─1048 /usr/libexec/bluetooth/bluetoothd

Nov 05 17:19:43 moode bluetoothd[1048]: Endpoint registered: sender=:1.11 path=>
Nov 05 17:19:43 moode bluetoothd[1048]: Failed to set privacy: Rejected (0x0b)
Nov 05 17:19:43 moode bluetoothd[1048]: Endpoint registered: sender=:1.11 path=>
Nov 05 17:19:43 moode bluetoothd[1048]: Endpoint registered: sender=:1.11 path=>
Nov 05 17:19:43 moode bluetoothd[1048]: Endpoint registered: sender=:1.11 path=>
Nov 05 17:19:43 moode bluetoothd[1048]: Endpoint registered: sender=:1.11 path=>
Nov 05 17:19:43 moode bluetoothd[1048]: Endpoint registered: sender=:1.11 path=>
Nov 05 23:01:31 moode bluetoothd[1048]: Endpoint registered: sender=:1.11 path=>
Nov 05 23:01:51 moode bluetoothd[1048]: /org/bluez/hci0/dev_88_C9_E8_37_3D_4D/f>
Nov 05 23:02:35 moode bluetoothd[1048]: /org/bluez/hci0/dev_88_C9_E8_37_3D_4D/s>
lines 1-21/21 (END)...skipping...
● bluetooth.service - Bluetooth service
    Loaded: loaded (/lib/systemd/system/bluetooth.service; disabled; vendor preset: enabl>
    Active: active (running) since Sat 2022-11-05 17:19:43 GMT; 5h 44min ago
      Docs: man:bluetoothd(8)
  Main PID: 1048 (bluetoothd)
    Status: "Running"
     Tasks: 1 (limit: 2137)
       CPU: 155ms
    CGroup: /system.slice/bluetooth.service
            └─1048 /usr/libexec/bluetooth/bluetoothd

Nov 05 17:19:43 moode bluetoothd[1048]: Endpoint registered: sender=:1.11 path=/org/bluez/>
Nov 05 17:19:43 moode bluetoothd[1048]: Failed to set privacy: Rejected (0x0b)
Nov 05 17:19:43 moode bluetoothd[1048]: Endpoint registered: sender=:1.11 path=/org/bluez/>
Nov 05 17:19:43 moode bluetoothd[1048]: Endpoint registered: sender=:1.11 path=/org/bluez/>
Nov 05 17:19:43 moode bluetoothd[1048]: Endpoint registered: sender=:1.11 path=/org/bluez/>
Nov 05 17:19:43 moode bluetoothd[1048]: Endpoint registered: sender=:1.11 path=/org/bluez/>
Nov 05 17:19:43 moode bluetoothd[1048]: Endpoint registered: sender=:1.11 path=/org/bluez/>
Nov 05 23:01:31 moode bluetoothd[1048]: Endpoint registered: sender=:1.11 path=/org/bluez/>
Nov 05 23:01:51 moode bluetoothd[1048]: /org/bluez/hci0/dev_88_C9_E8_37_3D_4D/fd0: fd(30) >
Nov 05 23:02:35 moode bluetoothd[1048]: /org/bluez/hci0/dev_88_C9_E8_37_3D_4D/sep1/fd1: fd>
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
lines 1-21/21 (END)

The Pi does live in a Flirc full aluminium case, the area I am testing it is about 2 feet away from the headphones. The wifi is the same distance away and works well with full signal strength; although I disabled that and use a wired connection for network.

thanks

[Tim Curtis]

It's best to get a baseline with the settings at their shipped defaults so try turning on WiFi and also take the board out of the case to be sure.

If the issue still occurs then it's possible there is a compatibility problem between that particular headphone device and Pi/Linux/Bluetooth.

[audioDrax]

It's best to get a baseline with the settings at their shipped defaults so try turning on WiFi and also take the board out of the case to be sure.

If the issue still occurs then it's possible there is a compatibility problem between that particular headphone device and Pi/Linux/Bluetooth.

I'll try reinstalling the OS tomorrow and see what I can achieve.

[audioDrax]

Tried a fresh install, and also removing from the case with no change. Will look at other music players and maybe a bluetooth dongle as people have had luck with those on other players

[Tim Curtis]

Tried a fresh install, and also removing from the case with no change. Will look at other music players and maybe a bluetooth dongle as people have had luck with those on other players

Try PiCorePlayer. The PcP crew does a great job with their software.

[TheOldPresbyope]

@audioDrax

Have you updated the firmware on your WF-1000XM4s? at least to 1.3.0 and preferably to the latest which seems to be 1.4.2?

Among benefits of the updated firmware listed by Sony are

Improves the stability of Bluetooth connection and music playback

Updating is specifically mentioned in their support section as pertaining to issues with Windows 10 which suggests to me it might pertain also to Linux.

I'm amazed at the amount of technology baked into these tiny earbuds. 

My full-size Sennheiser noise-cancelling wireless headphones have performed well against either the on-board RPi bluetooth transmitter or my Creative Tech USB BT-W2 adapter but the Sennheiser has different internal technology so it's not a straight comparison.

All Bluetooth audio products must support the SBC codec. If you choose to get an external Bluetooth adapter try to find one that also supports the additional ALAC codec present in the WF-1000XM4. If you still have young ears you should be able to hear the difference. (By comparison, the Creative Tech BT-W2 and newer support the additional aptX codec present in my Sennheiser.)

Regards,
Kent

[audioDrax]

Tried a fresh install, and also removing from the case with no change. Will look at other music players and maybe a bluetooth dongle as people have had luck with those on other players

Try PiCorePlayer. The PcP crew does a great job with their software.

I already downloaded piCorePlayer and will give it a whirl today. Thanks

[audioDrax]

@audioDrax

Have you updated the firmware on your WF-1000XM4s? at least to 1.3.0 and preferably to the latest which seems to be 1.4.2?

Among benefits of the updated firmware listed by Sony are

Improves the stability of Bluetooth connection and music playback

Updating is specifically mentioned in their support section as pertaining to issues with Windows 10 which suggests to me it might pertain also to Linux.

I'm amazed at the amount of technology baked into these tiny earbuds. 

My full-size Sennheiser noise-cancelling wireless headphones have performed well against either the on-board RPi bluetooth transmitter or my Creative Tech USB BT-W2 adapter but the Sennheiser has different internal technology so it's not a straight comparison.

All Bluetooth audio products must support the SBC codec. If you choose to get an external Bluetooth adapter try to find one that also supports the additional ALAC codec present in the WF-1000XM4. If you still have young ears you should be able to hear the difference. (By comparison, the Creative Tech BT-W2 and newer support the additional aptX codec present in my Sennheiser.)

Regards,
Kent

Thanks Kent. I will look into this and see what version I have on them.