This one turned out bigger than I anticipated, so here’s a disclaimer first:
*** THIS IS A BIG RELEASE THAT CAN TAKE UP TO 25 MINUTES TO INSTALL ***
With that being said, there are a few highlights in this release:
Bluetooth support. Finally you can use you XL as a bluetooth endpoint.
HAT auto-detection. For those HAT’s that support this (more and more) your HAT will be automatically confgured.
Make Alsa DAPM toggable. In the last release DAPM was disabled, but for some users this caused issues. So with this setting this can be toggled while the default behaviour (Alsa DAPM enabled) is as before 3.015.
Furthermore some ‘under the hood’ polish, where probably the main thing that stands out is the size of the image which has been trimmed. And with that also installation time, as over time there were more packages being downloaded during installation which takes considerable time in places where internet speed is not optimal.
There is also a change in deliverables: in stead of providing both images for ‘regular’ RoPieee and XL, you now will find only ‘regular’ RoPieee images (and obviously you can upgrade to XL from within RoPieee). And I’ve been starting to use a proper CDN for delivery, which means that there are no more “slow download” reports for RoPieee images.
As usual here’s the complete changelog:
NEW: auto detection of HAT’s (for those HAT’s that support detection)
NEW: option to enable/disable Alsa DAPM
NEW: support for the MERUS Amp HAT
NEW: [RoPieeeXL] support for acting like a bluetooth endpoint (pi4 only for now)
NEW: [RoPieeeXL] hardware mixer support for IQaudIO devices
NEW: [RoPieeeXL] Squeezelite: support for DoP
FIX: WiFi stability issues
IMPROV: support Hewbrew characters on display
IMPROV: [RoPieeeXL] update Librespot
IMPROV: [RoPieeeXL] update upmpdcli
IMPROV: make webpage survive an update
IMPROV: make webpage behave better on small(er) screens
I suspected there should be a configuration option for bluetooth under “Advanced”. There seems to be one, according to the guide, 1i). Unfortunately, I don’t have any. Tried Chrome and Firefox, cleared the cache.
Raspberry Pi 4 Model B Rev 1.4
Upgraded from the previous release.
Works on both Raspberries like a champ. Saw temperature falling from 40 C to 38 C on one unit and the other from 51 C to 48 C under identical conditions. Cool… and a big thank you.
Works with my other Raspberry Pi 4 Model B Rev 1.1.
I checked that bluetooth is ok with the 1.4 pi, though. Enabled BT in the 1.1 pi and put the card into the other one, could connect my phone.
I’m having some trouble updating my RPi3, which is connected on WiFi. (My other RPi2 on ethernet updated with no issue in a total of about 5 minutes.)
I saw the Update Available notification, Downloaded the update (took about 1-2 minutes), and restarted to update (after banner turned blue) all as prompted on the status page. The Pi came back online fairly quickly, but is sill on version 3.020.
Interestingly, there is stall a pink banner across the top “Update is being downloaded…” which has been there for about 30 min. It appears something has gone wrong along the way with the update. Here is the feedback identifier: 0cacbd328d841018
You’re on wifi, and I see an issue with bringing up the interface. Normally this resolves itself after a few seconds, but in this case the updater thinks it can do it’s work (and it can’t).
Few things you can do:
switch to cable just for the update
switch to internal wifi for the update (I see you’re using an external USB dongle)
Which endpoint do you use? The new UPnP software provides both an endpoint for UPnP and for OpenHome. Make sure you are connect to the UPnP one and not the OpenHome version.
Hi Harry,
I have another issue with the other pi testing bluetooth.
Connected my phone, I see the Ropieee on the BT panel, however don’t see any profiles as I have for the other connection, typically Stereo Audio and Phone Calls.
DAPM is only meant for HAT’s, so forget about USB.
This is basically power management for IC’s involved. In reality this means that, depending on if DAPM is enabled, outputs on HAT’s (SPDIF/COAX) get disabled after a period of time when there is no audio signal.
By default this was disabled, so output’s stay enabled. I received a report from someone with a specific DAC (forgot about type/model) that was not capable of switching inputs (so from OPTICAL to COAX for example) if there was still a signal on the selected input. Hence I enabled DAPM, but this had an unwanted side effect for some other users (resulting in devices being powered down because the input signal went away).
Anyways, hence the switch. If you never had to deal with this before (because, for example, you use USB) then forget it about
