Public Alpha Test: Audio Without Compromise - Volumio on Bookworm Begins

Volumio Development Volumio Beta Testing
, , , ,
122

Hey @JohnR,

Thank you for your report and for sharing the log - it’s helped pinpoint the issue.

What’s Happening

Your RPi 2B with USB Wi-Fi adapter is using a Ralink RT5370 chipset, which is fully supported by the rt2800usb driver - and the kernel loads it correctly.

However, the adapter was soft-blocked by RF-kill at the time Volumio tried to bring up the hotspot or wireless connection. This is evident from the log entries:

rfkill: WLAN soft blocked
wlan0: Could not connect to kernel driver
Interface initialization failed

This explains both the missing hotspot and failed Wi-Fi configuration.

What We Already Do

Volumio includes a systemd service:
volumio_rfkill_unblock.service, which runs an early script during boot to clear soft blocks.

You can verify whether it worked by running:

systemctl status volumio_rfkill_unblock.service

It should show active (exited) and contain a line like Wi-Fi is already unblocked.
If not, the unblock may have executed before the USB Wi-Fi adapter was initialized, which we’re now investigating.

What You Can Do

Manually unblock RF and confirm Wi-Fi functionality:

# Check block status
rfkill list

# Unblock everything if needed
sudo rfkill unblock wifi
sudo rfkill unblock all

# Recheck to confirm:
rfkill list

Once Wi-Fi is unblocked (Soft blocked: no), hotspot or normal wireless setup should begin working normally.

Verify the Flow

If you’re willing, please also share the output of:

# Check for interface and Wi-Fi link status
ip a
iwconfig

# Review RF state on boot
journalctl -u volumio_rfkill_unblock.service

# And for driver confirmation:
lsusb

This will help us better sequence the unblock logic for USB dongles on older boards like Pi 2B.

Thanks again for testing with this setup - it’s exactly the kind of edge case we need covered during Alpha.

Kind Regards,

123

v0.062

Fixes:

  • Extended a silver-plated invitation to USB Wi-Fi adapters that prefer to arrive fashionably late.
    (RF-kill handling improved for early startup.)

x86-specific:

  • OTA support now relies on an updated partition layout. Fresh flash is strongly recommended.
  • Onscreen keyboard prototype included - feedback welcome.
3 Likes
124

v0.062 OTA update, some touchscreen controls are non-responsive [like Pause]

http://logs.volumio.org/volumio/j3k9GBR.html

125

Hey @RedEyeNinja,

Thanks for sending the log. To help isolate the Pause button issue after the v0.062 OTA, please clarify the following:

  1. Where are you pressing Pause?

    • On the Touch Display plugin UI?
    • Inside the Now Playing plugin?
    • Or via the main web UI at http://your-volumio-ip?

  2. What type of content is playing when Pause does not respond?

    • Local files from USB or internal storage?
    • Network or NAS files?
    • Spotify?
    • Web radio?

  3. Is FusionDSP enabled when the issue occurs?

What We See in the Log

  • Touch Display plugin is active.
  • Now Playing and PeppyMeter Basic are both running.
  • Spotify plugin is installed and active.
  • Playback was last from a NAS FLAC file.
  • The Chromium UI in the Touch Display does not show JavaScript errors that may affect UI interaction.
  • There are no errors in the backend player or MPD logic, which suggests the issue is likely with input or frontend delivery.

Next Steps

To pinpoint the cause, we need to understand which layer is not receiving or processing the Pause input correctly. It could be the UI, the touchscreen rendering, or the plugin state itself.

Please test the following if possible:

  • Does Pause work from another interface, such as a browser on a separate device?
  • Does Pause work if you switch content source, for example from NAS to Spotify or Web radio?
  • Does the issue go away if you disable FusionDSP?

Let us know. These answers will help us isolate the problem to a specific layer.

Kind regards,

126
  1. It was thru the Now Playing UI with the controls at the bottom, on the touchscreen.
  2. It coul’ve been Spotify or local NAS.
  3. Yes.

However, all the issues went away after a reboot. Here’s a log of usage after reboot. I still here those loud sonic clicks once in awhile switching content.

http://logs.volumio.org/volumio/5n0TPUP.html

127

Hi @nerd ,
OTA from 0.061 to 0.062 did noch succeed - but you already said “Fresh flash is strongly recommended.” so I’ll proceed this way. Anyway here’s a log from the try OTA from 0.061 to 0.062 with a “cean” /imgpart folder (2.1GB free):
http://logs.volumio.org/volumio/7PvNadQ.html
Best regards, Robert

128

Hi @nerd ,
in V 0.062 I still get the error message “Could not connect the server” in a Tidal App when feeding Volumio via Tidal Connect. I suppose there is not yet a fix for that?

Cheers,
Robert

129

v0.062. Music scan of compilations CD’s [multiple CD folders nested within another folder] aren’t loading the actual music files and just the .cue files. This is the same after a rescan.

http://logs.volumio.org/volumio/Nco3uUb.html

130

Hey @RedEyeNinja, thanks for your report - we’re checking whether this .cue-only behavior is a regression in our custom MPD build for Bookworm (v0.24.3) or simply reflects stricter parsing behavior introduced in recent MPD versions.

From the log you shared (http://logs.volumio.org/volumio/Nco3uUb.html), we can see that the library scan indexed:

/mnt/INTERNAL/USB/Compilations/Swedish House Mafia - Paradise Again (CD1)/CD1.cue
/mnt/INTERNAL/USB/Compilations/Swedish House Mafia - Paradise Again (CD2)/CD2.cue

However, no actual audio files (e.g., .flac, .mp3) were indexed from those directories.

To investigate fully, could you please:

  1. Confirm whether this same structure and cue sheets worked as expected on Volumio 3.x (Buster)?
    If yes, could you share a log from Buster for comparison?

  2. Run the following command (or provide equivalent output) for one of the affected folders:

    ls -lh "/mnt/INTERNAL/USB/Compilations/Swedish House Mafia - Paradise Again (CD1)/"

  3. Share the FILE line(s) from the .cue sheet:

    grep FILE "/mnt/INTERNAL/USB/Compilations/Swedish House Mafia - Paradise Again (CD1)/CD1.cue"

This will help us verify whether the cue sheet references a valid file (by correct name and format) and whether MPD is failing to resolve it due to parsing changes or other configuration factors.

This is very good example and exact checks we need to master the alpha. Thanks again for your help testing.

Kind Regards,

131

Hey @RedEyeNinja,

Thanks for confirming the UI issue resolved after reboot. Regarding the “sonic clicks” you’re still hearing occasionally when switching content, these are typically caused by:

  • DAC reinitialization during sample rate or format switches
  • ALSA or DSP chain changes
  • Buffer underruns or sink resets

To isolate the cause, could you please run the following tests?

1. Reproduce Without FusionDSP

  • Disable FusionDSP.
  • Play a sequence of different content types (e.g., NAS FLAC → Spotify → Web Radio).
  • Note if the clicks still occur during these transitions.

2. Force a Single Output Format

  • Go to Playback Options → set a fixed sample rate (e.g., 44.1kHz) and disable auto resampling if available.
  • Again, switch between different tracks and sources.
  • Let us know if that reduces or eliminates the clicks.

3. Observe Specific Triggers

  • Note exactly when the clicks occur:

    • Between which sources?
    • After stopping one and starting another?
    • After any delay or immediately?

If you’re comfortable capturing logs after clicks occur, that would also help. We’re trying to narrow it down to:

  • ALSA reinit
  • FusionDSP reload
  • Format mismatch between tracks

Thanks again for helping us track this down.

Kind Regards,

132

Hey @Robert.Hecht,

Thanks for sharing the OTA log.

Just to clarify: version 0.062 introduces a new partition layout, and there is no transformation logic included in OTA for this update. While we have prototyped a partition move script, on 256MB/s storage it takes over 12 hours to complete - which makes it impractical for integration into the Volumio ecosystem.

Because of this, OTA updates from 0.061 to 0.062 are not supported. A fresh flash is strictly required to adopt the new layout introduced in 0.062 and beyond.

Let me know if you encounter any issues during or after the reflash.

Kind Regards,

133

Het @Robert.Hecht,

Regarding the TIDAL Connect issue (“Could not connect to the server”):

This behavior is currently the same across both the release and Bookworm builds. I’m checking in with the dev team to confirm the current state of this bug and whether a fix is already in progress or scheduled.

I’ll update you as soon as I have more details.

Kind Regards,

1 Like
134

Hi @nerd, is this true for any system? Because with my Raspberry Pi 3B+, the update to version 0.062 done via OTA seems to have completed successfully…

135

Raspberry Pi 3A+
New clean install of Volumio: 0.062.
I have a Volumio account Lifetime license.
After installing and entering login details on this version of Volumio: 0.062, it is not possible to use the lifetime license.

136

Hey @Ema82,

Thanks for checking. The situation with OTA to v0.062 is platform-dependent:

  • On Raspberry Pi platforms (like your 3B+), the partition layout and image size have not changed. OTA should proceed and apply cleanly - as seems to be the case for you.
  • On x86 systems, starting from v0.062 we introduced a new partition layout to support future features and improve image flexibility. This increases pressure on /imgpart, and OTA from earlier versions may silently fail due to insufficient space (especially if fallback or .part files remain).

So in summary:

  • Pi OTA to 0.062: OK
  • x86 OTA to 0.062: Manual cleanup or fresh flash strongly recommended

Let me know if you observe anything odd post-update on Pi 3B+, but so far yours looks good.

Kind Regards,

1 Like
137

Hey @tweed77,

Thanks for reporting this - but no log, no talk.

Please reproduce the issue, then send a log immediately after the failed login or license sync. From the UI:

http://<your-volumio-ip>/dev

and click “Send Log”. Share the link here so we can verify what’s going wrong during authentication or license sync.

Until then, we have no way to assist.

Kind Regards,

138

@nerd I sent a private message with a link to the log

139

Hey @tweed77,

Thanks for providing the log. No need to send them privately, logon data is removed anyway.
The system is booting cleanly, but your MyVolumio device registration is failing with:

error: Failed to add MyVolumio device: {"message":"USER_NOT_FOUND"}
error: Failed to update MyVolumio device: {"message":"DEVICE_NOT_FOUND"}

This suggests one of the following:

  • You were not logged into your MyVolumio account at the time of boot.
  • A cached or incorrect session is present (especially if reused from another Volumio setup).
  • The login was interrupted or blocked, and the backend never received a valid user token.
  • More devices connected to the account than license permitted: 6. Original post updated with screenshot after response.

Please try the following:

  1. Open the UI directly on this device, not through a bookmark or cached session.
  2. Log out of MyVolumio completely via Settings > MyVolumio > Logout.
  3. Log back in with your Lifetime account credentials.
  4. Wait 10 seconds, then reboot the system.
  5. After reboot, check again whether the subscription activates.

If this does not help, please send a new log right after login and before rebooting.

Kind Regards,

140

I sent the logs in a private message.

I logged out - then turned off - disconnected the Raspberry Pi 3B completely from the power supply.
Then after about 1 minute - I restarted the Raspberry Pi 3B.
After a few seconds I entered the data for the Volumio Lifetime License.
Now it’s ok

141

Hey @tweed77,

Great to hear the Lifetime license is now working after a full logout and power cycle.

What you experienced makes sense - I’ve seen that when testing different Raspberry Pi boards, especially during initial setup, using the same browser session across devices can cause cached MyVolumio login data to interfere with clean device registration.

The UI might still show you as logged in, but in the backend the authentication may silently fail with:

  • USER_NOT_FOUND
  • DEVICE_NOT_FOUND

This happens because the browser reuses a stale token from another system, and the new device never gets properly registered.

To avoid this in future:

  • Always start setup in a fresh browser session (e.g. incognito window).
  • Or explicitly log out of MyVolumio before switching tabs/devices.
  • A full power-off reboot after logout helps ensure a clean handshake.

Thanks again for confirming the fix.

Kind Regards,

1 Like