Volumio 4 Feedback Thread

Help and Support Help
227

The same in my case with 4.071. Installed new system with 4.071 - it seems that disconnecting cable when RPI is working make wifi active :slight_smile:

228

Hey @AndrewHeard,

You are comparing fundamentally incompatible systems. This is not pears versus apples - this is comparing a steam engine to a smartwatch.

The timeline you are spanning:

Let me lay out what has changed between ā€œVolumio 2ā€ and ā€œVolumio 4ā€ so the scope is clear:

Debian Releases:

  • Debian 8 Jessie: April 2015
  • Debian 9 Stretch: June 2017
  • Debian 10 Buster: July 2019
  • Debian 11 Bullseye: August 2021
  • Debian 12 Bookworm: June 2023

Volumio 2 ran on Jessie/Stretch era base. Volumio 3 ran on Buster. Volumio 4 runs on Bookworm. You are spanning three to four major Debian generations.

Kernel evolution:

  • Kernel 4.9.x: December 2016 (Stretch era)
  • Kernel 4.19.x: October 2018 (Buster initial)
  • Kernel 5.10.x: December 2020 (Bullseye era)
  • Kernel 6.1.x: December 2022 (Bookworm initial)
  • Kernel 6.6.x: October 2023 (Volumio 3 late backport for Pi 5 support)
  • Kernel 6.12.x: November 2024 (Volumio 4 current)

Your boot time comparison spans approximately 8 years of Linux kernel development and 4 major Debian releases. Each kernel major version adds drivers, security subsystems, hardware abstraction layers, and initialization requirements. Each Debian release updates systemd, adds services, and increases baseline complexity.

This was explained extensively in the Alpha test thread (April 2025) and Beta test thread (September 2025). Neither you nor @marcinmarcin participated in those testing phases where these architectural realities were documented and discussed.

Why 175 seconds on your Pi 3B+:

The Raspberry Pi 3B+ has a Cortex-A53 quad-core at 1.4GHz with 1GB RAM shared with GPU. This hardware was released in March 2018 and designed when kernel 4.x was current. Running Bookworm with kernel 6.12.x on it means:

  1. Initial overlayfs mount and storage resize operations are heavier under modern kernel
  2. Systemd service chain is longer and more complex than 2017-era init
  3. Kernel 6.12.x has substantially more subsystems to initialize than kernel 4.9.x
  4. RAM constraints force pressure during boot when modern services compete for memory
  5. USB 2.0 storage interface bottlenecks all I/O operations

SD card class does not meaningfully change this. You tested Samsung EVO Plus 2 versus SanDisk Ultra - both are fast cards. The bottleneck is not sequential read speed. The bottleneck is random I/O during systemd service initialization and the sheer volume of work the modern kernel must complete before handing off to userspace.

Supported does not mean Performance Guaranteed:

Volumio maintains support for older single-board computers including the Raspberry Pi 3B+ to ensure users are not abandoned. Support means the system will boot, function correctly, and receive updates. It does not mean performance parity with newer hardware. Once boot completes and processes are loaded into memory, audio playback and UI responsiveness operate normally - the Pi 3B+ handles runtime workloads adequately. Boot time is the price paid for running a modern OS on legacy hardware.

What would actually help:

Moving to a Raspberry Pi 4 with 2GB or 4GB RAM would reduce boot time significantly - not because of RAM for audio playback, but because:

  • Cortex-A72 cores are substantially faster for boot operations
  • USB 3.0 allows faster storage access if using USB boot
  • More RAM means less pressure during initialization
  • Hardware is contemporary with Bookworm expectations

Your concern about HAT clearance with a heatsink is solvable. GPIO extender/stacker headers exist specifically for this purpose - they raise the HAT above the Pi 4 heatsink. HiFiBerry DAC Plus is fully compatible with Pi 4.

Power supply concerns are valid. Pi 4 does require 3A minimum. Your 18650x2 UPS arrangement would need evaluation.

Regarding migration of Favorites and Web Radios:

This should have been documented more prominently. The data files from V2 were not directly compatible with V4 database structure. Manual recreation was the practical path for most users.

Regarding @marcinmarcin and Single Network Mode:

This is Volumio architectural behavior, not a bug in 4.071. Volumio operates with only one network interface active at a time by design. When ethernet is connected, WiFi is disabled. When ethernet is disconnected, WiFi should re-enable.

The claim that ā€œSingle Network Mode management is failing to switch WiFi back onā€ needs investigation with proper logs. If this is a reproducible problem, it requires a log link from http://volumio-IP/dev showing the issue occurring. Without evidence, it cannot be assessed or escalated.

Both of you: if you want issues investigated, provide logs per the help request guidelines. Observations without evidence cannot and will not be actioned.

Kind Regards,

3 Likes
229

@nerd I made a card with pi imager using file 4.071 - wifi is working (enabled by default) and if ethernet cable is disconnected it connect to wifi
but I prepared card using balena etcher - in this case wifi is disabled by default and there is no possibility to enable it (strange - I made second card because first one seems working quite slowly) Send a log from system made with balena - wifi not working
edit - installed 4.071 on second card with imager - still wifi disabled and no option to enable itā€¦ its crazyā€¦ is possible that this could be sd card related?
edit2 - made 3rd card - wifi is enabled after installation, and connect with my routerā€¦

230

Balena is not recommended.
We have seen a lot of issues with it, hence Volumio stepped away from Balena and advises RaspBerry Pi Imager.

2 Likes
231

@nerd
Yes, but WiFi only re-enables if the ethernet is disconnected while Volumio is running. WiFi does not work if the ethernet is disconnected after shut down.
This results in it being impossible to reconnect unless an ethernet connection is available.

1 Like
232

Thanks nerd for all the info. Where did I write I was complaining? I wasnā€™t my intention. We all bring different motivations, experience, and passion to this forum. Two other users kindly suggested a faster SD card, and that an RPi4 wouldnā€™t help much; that was my interpretation. Any of the changes suggested would require almost total scrapping of an otherwise functional device; it just wonā€™t fit in the existing space, and hard to justify extra cost. Please appreciate from a non-technical users point of view, and the rest of my bemused family, no one notices this difference between a steam engine and smartwatch - we turn it on, it eventually plays the radio and excellent quality music - that is the basis of my ā€œcomparisonā€. My setup was working fine since Y2021, so as they say ā€œif it ainā€™t broke, donā€™t fix itā€, but I was very excited when I read the V4 announcement. The update to the Android Volumio app forced my hand because suddenly it couldnā€™t connect to the player (now sorted). Yes I was unaware of alpha & beta testing but Iā€™ve spent 2 days to get to this point. A migration guide with suggested levels of hardware, and how to maintain favorites & ā€œlast 100ā€ would be very useful. Thatā€™s all cool. Thanks for your time.

233

Hi @Newbiggen
I tried and indeed thereā€™s no switchover to wifi when the ethernet cable is disconnected after power off. Furthermore the hotspot fallback didnā€™t work. I also tried entering my wifi password whilst still wired, but that made no difference.

234

Hi @AndrewHeard

Not sure where your info regarding the rPi4 is coming from, but itā€™s not true.
Using a rPi4, booting form USB, I get the device up and running in less then a minute, this is including driving the display.
The rPi4 will perform smoother when running Volumio, but if it is worth the investment in your case, I canā€™t tell.
But for running basic Volumio the rPi3 still perform.

235

Iā€™m running 2 Raspberry Pi 3B+ units, I upgraded one about two weeks ago, it has been a better experience overall than with V3.x
I just upgraded the second one today and Iā€™m hoping it too will be a better experience (it connects to the usb\music share on the first for itā€™s music source).
I also donā€™t think it is noticeably slower to boot than it was with V3.x

236

Hi @pwstereo

a rPi3 on Bookworm boots indeed slower. Please read this post for the explanation.

But good too here your positive feedback.

237

On Pi4 boots also slower. But I think its not very important. My 1 problem with no possiibility to enable wifi is card related - only on one card. On two other cards wifi is enabled and connect if I disconnect lan cable when volumio is running.

2nd problem is with tidal connect - when aac file will be on playlist and should start playing - volumio stops and disappear from connect list on my phone. Helps to disable and enable Tidal connect from sources or to restart volumiio.

238

Hey @nerd @Volumio

Volumio Version: 4.071
Hardware: Raspberry Pi 5
DAC: Both without dac connected and with TEAC UD- 501 connected.

I think something must be done with wireless setup/ function.
When I connect rPi5 to mains it often hangs before fully loading. I hangs when loading touch display 2. I canā€™ connect to rPi5 with SSH either so itā€™s hard to send a log.
I have to restart and sometimes up to three times before it works. Same with rPi 4
I would recommend some rework with Wireless setup and function.

If connected with ethernet it works withot problems.

Best Regards/ C

Additional Information

239

All,

I just downloaded a new volumio img (Volumio-4.071-2025-11-17-pi.img) from the website. Put it on the sd-card and started my pi.
Volumio doesnā€™t start :frowning: but in the log I see following (strange) messages:

Nov 30 10:04:15 volumio volumio[3062]: error: Cannot start Volumio Streaming Daemon
Nov 30 10:04:15 volumio volumio[3062]: error: Failed initialization of streaming services: Error: Error: Command failed: /usr/bin/sudo systemctl restart volumio-streaming-daemon.service
Nov 30 10:04:15 volumio volumio[3062]: Failed to restart volumio-streaming-daemon.service: Unit volumio-streaming-daemon.service not found.

If I do

volumio@volumio:~$ sudo systemctl status volumio                         
ā— volumio.service - Volumio Backend Module
     Loaded: loaded (/lib/systemd/system/volumio.service; enabled; preset: enabled)
    Drop-In: /etc/systemd/system/volumio.service.d
             ā””ā”€override.conf
     Active: active (running) since Sun 2025-11-30 10:04:00 UTC; 4min 42s ago
   Main PID: 3062 (node)
      Tasks: 62 (limit: 4915)
        CPU: 15.435s
     CGroup: /system.slice/volumio.service
             ā”œā”€3062 /usr/bin/node /volumio/index.js
             ā”œā”€3091 /bin/bash /volumio/app/plugins/system_controller/network/network_monitor.sh
             ā”œā”€3124 /usr/bin/node /volumio/app/plugins/miscellanea/albumart/serverStartup.js 3001 /data/albumart
             ā”œā”€3142 /usr/bin/node /volumio/app/plugins/miscellanea/albumart/serverStartup.js 3001 /data/albumart
             ā”œā”€3144 /usr/bin/node /volumio/app/plugins/miscellanea/albumart/serverStartup.js 3001 /data/albumart
             ā”œā”€3145 /usr/bin/node /volumio/app/plugins/miscellanea/albumart/serverStartup.js 3001 /data/albumart
             ā””ā”€3868 sleep 10

Nov 30 10:04:35 volumio volumio[3062]:  [Metrics]  CommandRouter:  34s 661.64ms 
Nov 30 10:04:35 volumio volumio[3062]: info: CoreCommandRouter::volumiosetStartupVolume
Nov 30 10:04:35 volumio volumio[3062]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam
Nov 30 10:04:35 volumio volumio[3062]: info: CoreCommandRouter::executeOnPlugin: system , getConfigParam
Nov 30 10:04:35 volumio volumio[3062]: info: CoreCommandRouter::Close All Modals sent
Nov 30 10:04:35 volumio volumio[3062]: info: CoreCommandRouter::Close All Modals sent
Nov 30 10:04:36 volumio volumio[3062]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , checkAudioDeviceAvailable
Nov 30 10:04:36 volumio volumio[3062]: info: CoreCommandRouter::executeOnPlugin: i2s_dacs , getI2sStatus
Nov 30 10:04:36 volumio volumio[3062]: info: CoreCommandRouter::executeOnPlugin: system , versionChangeDetect
Nov 30 10:04:42 volumio volumio[3062]: info: BOOT COMPLETED
volumio@volumio:~$

Output as expected.
Can anybody help me get going ā€¦

TIA!,
Arjan

240

Hey @athoopen,

Your post contains a contradiction that needs clarification. You state ā€œVolumio doesnā€™t startā€ but then show systemctl output proving volumio.service is active and running with ā€œBOOT COMPLETEDā€ in the log.

Regarding the streaming daemon error - this is expected behavior on a fresh install without a MyVolumio subscription. The volumio-streaming-daemon.service is a MyVolumio Premium/Superstar feature for remote streaming capability. On systems without an active subscription, the streaming_services plugin attempts to initialize this daemon but fails because the service unit file is not installed. This is a non-fatal warning, not a system failure.

Your system appears to be running normally based on the evidence you provided.

Before investigating further, I need proper details per community guidelines:

The snippet you provided shows only a few lines. Full logs are required for proper investigation.

Kind Regards,

241

@nerd

The problem was that the UI did not start, not in the app, not in the browser.
I downloaded the newest version since the current one was on a sd-card which became faulty (I use volumio for years). All my links etc are saved links etc.

The fault I made was that I use https://ā€¦ to get to volumio. After changing this to http://ā€¦ Iā€™ve get the welcome screen in my browser.

I like to apologize, I should have checked this before adding the question to the forum.

Keep on the good work, my family and I enjoy it!

Greetings and thanks from Holland,
Arjan

1 Like
242

I havenā€™t used Volumio in a while, but I donā€™t know what you guys did with Volumio 4. Itā€™s simply amazing. A simple Raspberry Pi 3 connected to a modified Singxer SU-1 via a DDDAC sounds far better than all my other equipment, and that includes some serious gear. My recently purchased Auralic Aries S1 plus an external Aries S1 PSU is completely outperforming it. Iā€™m a bit baffled.
So software does affect the sound.

I just wanted to mention this.

1 Like
243

Hey @nerd @volumio

Raspberry Pi 5, Volunio 4.071 wifi
After every restart (when it maybe is fully restarted) I have to login to MyVolumio and it take sometimes pretty log time. IsnĀ“t it possible to have login done during startup?

log: http://logs.volumio.org/volumio/VthrlgB.html

Best Regards / C

244

Still waiting for at least a forecast as to when the fix for the dongle will be released.
Thanks

245

Hello all Volumio users and @volumio
I have previously written about my problems with Wifi and Wifi setup. Not when ethernet is connected

  1. When first setting up Volumio wizard, I had to go back and re-enter my username and password 3-4 times before Volumio could connect to the internet. Really frustrating.
  2. Restarting Volumio has taken a very long time and sometimes Volumio has not finished loading. Restart again and hope for the bestā€¦
  3. If my rPi4 -5 has been unplugged from power overnight and then been plugged in to power next morning, the first startup of Volumio has not worked without a manual restart. Even then a new startup is required, sometimes multiple times. I have always had to log in to MyVolumio again.

Iā€™ve been searching for a solution for a while and I found this:

https://github.com/volumio/volumio-os/pull/281

I decided that I want to test this approach and solution but of course I needed some help. Anyway, I got help and now Wifi works perfectly. No problems starting Volumio and loading time is much faster.
Simply brilliant. Thanks @nerd for this solution.

I recommend this for everyone with similar problems.

Best Regards / C

1 Like
246

Thanks @nerd for this.

Given how important this piece of the architecture is, we need some time to review, test and deploy this fix. Bear with us, we are on it

1 Like