HiFiBerryOS RP2: Spotify not visible

Max Mustermann

May 27, 2020 13:09

None

I just tried to use HiFiBerryOS on my RPi 2B with a DAC+ Pro. Unfortunately I cant select Spotify as source at hifiberry.local and the device is also not selectable in the Spotify app. Is this a known issue?

Date Votes

24 comments

0

HiFiBerry team May 27, 2020 13:30

The Pi2 isn't tested by us. It might be a bug or a compatibility problem. You can login and check

systemctl status spotify

Comment actions Permalink
0

Max Mustermann May 27, 2020 13:42

systemctl status spotify gives:

● spotify.service - Spotify connect
Loaded: loaded (/usr/lib/systemd/system/spotify.service; enabled; vendor preset: enabled)
Active: inactive (dead)
Condition: start condition failed at Wed 2020-05-27 15:25:05 CEST; 14min ago
└─ ConditionPathExists=/etc/features/arm7 was not met

May 27 15:25:05 hifiberry systemd[1]: Condition check resulted in Spotify connect being skipped.

Comment actions Permalink
0

HiFiBerry team May 28, 2020 13:20

Ok, the Pi2 isn't recogniozed as "supported". I'm not sure if this has been changed already with the latest release. Try upgrading to 20200527 and check with this version.

Comment actions Permalink
0

Max Mustermann May 28, 2020 16:17

I upgraded to 20200527 today, systemctl status spotify now gives:

● spotify.service - Spotify connect
Loaded: loaded (/usr/lib/systemd/system/spotify.service; disabled; vendor preset: enabled)
Active: inactive (dead)

Comment actions Permalink
0

HiFiBerry team May 28, 2020 16:18

Can you enable it in the GUI?

Comment actions Permalink
0

Roie Geron June 06, 2020 19:49

I have been able to enable Spotify connect on RP2 by remark the following line from

/usr/lib/systemd/system/spotify.service

edit it using vi or nano

# ConditionPathExists=/etc/features/arm7

Remak the line and then reboot the RP2 .

you should see it on the devices list in your Spotify application although it will not be shown in the HIFIBerryOS GUI.

Comment actions Permalink
0

HiFiBerry team June 06, 2020 19:59

Ok, looks like the Pi2 didn't get the ARM7 feature. We'll fix this in the next release.

Comment actions Permalink
0

HiFiBerry team June 06, 2020 20:26

To fix this, we need an identification of the Pi2. Can you please post the output ouf the following command:

cat /proc/device-tree/model

Comment actions Permalink
0

Roie Geron June 07, 2020 04:05

# cat /proc/device-tree/model
Raspberry Pi 2 Model B Rev 1.1

Comment actions Permalink
0

HiFiBerry team June 07, 2020 05:20

Thanks, we'll include this in the next release.

Comment actions Permalink
1

Olsen October 10, 2020 22:37

This doesn't seem to have been fixed in 20200908. I've got the same Pi Model as Roie (Raspberry Pi 2 Model B Rev 1.1) but Spotify is only available after applying Roie's fix. It would be great if you could fix it!

Comment actions Permalink

Olsen October 12, 2020 20:28

..I think this patch should do it:

$ diff -u4 reconfigure-players reconfigure-players-orig 
--- reconfigure-players 2020-10-12 22:10:52.055002540 +0200
+++ reconfigure-players-orig    2020-10-12 22:09:37.924245059 +0200
@@ -117,14 +117,8 @@
   FEATURES="$FEATURES bluetooth"
   return
  fi
 
- if [[ $modelname == *"Pi 2 Model B Rev 1.1" ]]; then
-  PIMODEL="2"
-  PIVERSION=2
-  return
- fi
-
  if [[ $modelname == *"Pi 2 Model B" ]]; then
   PIMODEL="2"
   PIVERSION=2
   FEATURES="$FEATURES arm7"

0

HiFiBerry team October 13, 2020 06:24

This has been included already in the September release:
https://github.com/hifiberry/hifiberry-os/blob/master/buildroot/package/hifiberry-tools/reconfigure-players

Comment actions Permalink
0
Olsen October 13, 2020 08:06
I started with September release on my Pi2 and had to comment out the line
```
ConditionPathExists=/etc/features/arm7
```
within /usr/lib/systemd/system/spotify.service to get Spotify connect running. /etc/features/arm7 doesn't exist on the Pi2. Therefore I assume
```
FEATURES="$FEATURES arm7"
```
is not correct for the Pi2.
Comment actions Permalink
0

HiFiBerry team October 13, 2020 08:08

Try removing /etc/hifiberry.state and reboot

Comment actions Permalink
0

Olsen October 13, 2020 08:48

Ok, I reverted /usr/lib/systemd/system/spotify.service to the original version, deleted /etc/hifiberry.state and rebooted. Spotify is neither available through the web gui nor via an official Spotify client within the same network.

/etc/hifiberry.state looks like this:

# cat /etc/hifiberry.state
CURRENT_PIMODEL=unknown
CURRENT_MIXER_CONTROL="Digital"
CURRENT_CARD="DAC+ Pro"
CURRENT_HW="card 0"
CURRENT_HW_SHORT=0
CURRENT_SYSNAME="HiFiBerry"
CURRENT_PLAYERS=""
CURRENT_HATINFO="HiFiBerry DAC+"
CURRENT_FEATURES="pi bluetooth bin boot data dev etc home lib lib32 libexec library library.bak linuxrc lost+found lost_found media mnt opt proc root run sbin srv sys tmp usr var"
CURRENT_DSPTYPE=""
PIVERSION=
#

I think it doesn't work because my Pi model string is "Raspberry Pi 2 Model B Rev 1.1" which doesn't match on [[ $modelname == *"Pi 2 Model B" ]]. And even if it would match, arm7 seems to be wrong for this revision of the Pi2 (there is no /etc/features/arm7).

I'm on 20200908 with a direct installation (no update).

Comment actions Permalink
0

HiFiBerry team October 13, 2020 08:54

Ok, I see. This is a Pi that doesn't feature an ARM7 command set. It's interesting to see that spotifyd is running at all as it should not. As it is not supposed to work at all, we won't include a patch to enable this on this Pi model. It might just break with the next release.

You can create a file /etc/hifiberry/arm7.feature to enable it.

However, as I said it might just break in any new release and we won't guarantee that it will will on a non-ARM7 Pi in future releases.

Comment actions Permalink
0
Olsen October 13, 2020 09:37
All Pi2 models are at least arm7 ! According to Wikipedia the first version (this is what i have) contains a Cortex-A7 (arm7). Newer models of the Pi2 contain a Cortex-A53 (arm 8). See https://en.wikipedia.org/wiki/Raspberry_Pi#Specifications

The error is the missing '*' at the end of the [[ $modelname == *"Pi 2 Model B" ]] -> it doesn't match on "Raspberry Pi 2 Model B Rev 1.1" -> no arm7 feature -> no Spotify connect.

I added the '*' at the end: [[ $modelname == *"4 Model B"* ]], removed /etc/hifiberry.state and rebooted. Afterwards HifiBerry is available as a Spotify connect player. I think you can safely enable this for the Pi2.

The only flaw is that Spotify is not available in the HifiBerry web gui. I don't know why...

/etc/hifiberry.state looks good now:
```
 
CURRENT_PIMODEL=2
CURRENT_MIXER_CONTROL="Digital"
CURRENT_CARD="DAC+ Pro"
CURRENT_HW="card 0"
CURRENT_HW_SHORT=0
CURRENT_SYSNAME="HiFiBerry"
CURRENT_PLAYERS=""
CURRENT_HATINFO="HiFiBerry DAC+"
CURRENT_FEATURES="pi arm7 bluetooth bin boot data dev etc home lib lib32 libexec library library.bak linuxrc lost+found lost_found media mnt opt proc root run sbin srv sys tmp usr var"
CURRENT_DSPTYPE=""
PIVERSION=2
#
```
Comment actions Permalink
0

HiFiBerry team October 13, 2020 12:31

You're right. I misread this. We'll add this fix in the next release.

Comment actions Permalink
0

Olsen October 13, 2020 13:59

Thanx! :)

Comment actions Permalink
0

Olsen October 22, 2020 14:25

The Pi 2 still isn't recognized correctly with 20201022. There is a Typo in reconfigure-players:

actual: *"

if [[ $modelname == *"Pi 2 Model*" ]]; then

should be: "*

if [[ $modelname == *"Pi 2 Model"* ]]; then

Comment actions Permalink
0

HiFiBerry team October 22, 2020 14:29

Just a few more releases and we'll get it working ;-)

Comment actions Permalink
0

Olsen October 22, 2020 14:32

... which causes Spotify to be disabled

Comment actions Permalink
0

Olsen October 22, 2020 14:33

yes, it's getting really close to perfect for the Pi 2 now! ;-)

Comment actions Permalink

Please sign in to leave a comment.