Forum Replies Created
-
Posted in: Allo USB Bundle
-
12. Dezember 2019 at 0:07 #47756
Hello
What I have noticed is that if I connect the Raspi4 through an ethernet cable eth0 with fixed IP, the Spotify Connect autostart does NOT work.
But, if I connect the Raspi4 through WIFI and DHCP ( wlan0 ) then Spotify Connect autostart works fine.
Maybe someone could discover why is that
11. Dezember 2019 at 22:57 #47755Hello
I have reinstalled max2play from scratch, update it, intalled only the bluetooth module, done apt-get update + apt-get upgrade and the bluealsa module does not work:#### Bluetooth Installation ####
#### Bluetooth Dongle ####
hci0: Type: Primary Bus: UART
BD Address: DC:A6:32:0E:42:8A ACL MTU: 1021:8 SCO MTU: 64:1
UP RUNNING
RX bytes:7822 acl:0 sco:0 events:486 errors:0
TX bytes:20354 acl:0 sco:0 commands:486 errors:0#### BLUEALSA ERROR ####
● bluealsa.service – Start Bluealsa for Bluetooth on Alsa (not compatible with Pulseaudio)
Loaded: loaded (/etc/systemd/system/bluealsa.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Wed 2019-12-11 21:52:16 CET; 2s ago
Process: 2011 ExecStartPre=/bin/rm -Rf /var/run/bluealsa (code=exited, status=0/SUCCESS)
Process: 2012 ExecStartPre=/usr/bin/killall bluetoothd (code=exited, status=0/SUCCESS)
Process: 2013 ExecStartPre=/bin/systemctl start sys-subsystem-bluetooth-devices-hci0.device (code=exited, status=0/SUCCESS)
Process: 2014 ExecStartPre=/bin/hciconfig hci0 down (code=exited, status=0/SUCCESS)
Process: 2015 ExecStartPre=/bin/systemctl start bluetooth (code=exited, status=0/SUCCESS)
Process: 2017 ExecStartPre=/bin/sleep 5 (code=exited, status=0/SUCCESS)
Process: 2018 ExecStart=/usr/bin/bluealsa -p a2dp-sink -p a2dp-source (code=exited, status=127)
Main PID: 2018 (code=exited, status=127)#### BLUEALSA RUNNING ####
0/var/log/syslog
Dec 11 21:56:22 max2play systemd[1]: Started Start Bluealsa for Bluetooth on Alsa (not compatible with Pulseaudio).
Dec 11 21:56:22 max2play bluealsa[2952]: /usr/bin/bluealsa: error while loading shared libraries: libsbc.so.1: cannot open shared object file: No such file or directory
Dec 11 21:56:22 max2play systemd[1]: Started „Bluetooth speaker for Bluealsa“.
Dec 11 21:56:22 max2play systemd[1]: bluealsa.service: Main process exited, code=exited, status=127/n/a
Dec 11 21:56:22 max2play systemd[1]: bluealsa.service: Failed with result ‚exit-code‘.
Dec 11 21:56:22 max2play bluealsa-aplay[2953]: /usr/bin/bluealsa-aplay: ../../utils/../src/shared/ctl-client.c:105: Connecting to socket: /var/run/bluealsa/hci0
Dec 11 21:56:22 max2play bluealsa-aplay[2953]: /usr/bin/bluealsa-aplay: BlueALSA connection failed: No such file or directory
Dec 11 21:56:22 max2play systemd[1]: bluealsa_aplay.service: Main process exited, code=exited, status=1/FAILURE
Dec 11 21:56:22 max2play systemd[1]: bluealsa_aplay.service: Failed with result ‚exit-code‘.
Dec 11 21:56:23 max2play systemd[1]: bluealsa_aplay.service: Service RestartSec=100ms expired, scheduling restart.
Dec 11 21:56:23 max2play systemd[1]: bluealsa_aplay.service: Scheduled restart job, restart counter is at 25.
Dec 11 21:56:23 max2play systemd[1]: Stopped „Bluetooth speaker for Bluealsa“.7. Dezember 2019 at 23:54 #47714I already run version 2.51 which is the latest stable release
6. Dezember 2019 at 19:12 #47708Hello
I will abandon the Shairport path and will focus on connecting through Bluetooth, which it does neither work, I have started another thread to handle the bluetooth issue.
Best6. Dezember 2019 at 19:11 #47707Hi Heiner
It is a 1x HiFiBerry DAC+ bundle Pi 4 bought on 4th november 2019 so I assume is the latest one, shall I run any command to give you more detailed info?
I only have the Spotify Connect module installed.
Best
-
