It’s not enabling or disabling Now Playing that leads to this, it’s how you access the screens.
If you click here
… the keyboard doesn’t show when using any subsequent screens.
However if you go via Go to Artist/Album it appears properly in all subsequent screens
Hey @ClaesM,
I am not sure how can I help, perhaps Now Playing plugin’s creator?
Is or was there a version of Touch Plugin where onscreen keyboard worked in Now Playing plugin? Not sure about relation between these two plugins.
Kind Regards,
Hey @nerd
I haven’t used onscreen keyboard with Now Playing plugin on Volumio 4.xxx, first time 2 days ago.
I know it worked on Volumio 3.xxx when I tried it then.
I guess that it’s some incompability in Now Playing plugin so I disabled it for know.
Best Regards / C
Hi,
just like this:
# Set device scope
[all]
# Enable display vc4 autodetection
display_auto_detect=1
# Add touchscreen-specific overlays
# # dtoverlay=rpi-ft5406. -- In many versions of Volumio, the rpi-ft5406 driver is already built into the kernel and activates automatically
dtoverlay=vc4-kms-v3d
dtoverlay=vc4-kms-dsi-7inch
# Ensure backlight control works
gpio=18=op,dh
Psychic skills will help, based on your hardware description and lack of full logs.
Hi everyone! And thanks to all your work with this topic. I have been reading for days trying to find a working solution for my own case but I am growing desperate since so many things have changed since the very first post.
I have a Raspberry Pi 3 with a Waveshare 3.5 inch SPI touchscreen mounted via GPIO. It is the 480x320 model which has been referenced a couple of times in the thread.
When I flashed the current version of Volumio to my mSD card, I managed to proceed with the plugin installation via web interface but the screen stayed white (or black). I tried going back to an older Volumio version which uses kernel 5.x - but there, it already fails at the plugin installation in the web interface with the chromium dependency error. I tried changing the repository as mentioned but it also didn’t help.
So, could someone give me instructions from scratch on how to properly get this working nowadays? Thank you so much!
I don’t know which display you are using, but it happened to me with a WaveShare 7" DSI display. Somehow, the system thinks there is an additional HDMI display. I solved it disabling HDMI with these 2 lines in userconfig.txt:
disable_hdmi=1
dtoverlay=vc4-kms-v3d,nohdmi
I hope it helps.
Regards.
Angel
Thank you Angel, your hint actually helped me for the first time ever to get a display on my touchscreen! It showed the “Volumio - The Music Player” animation after bootup. However, it did not get any further and then suddenly restarted with only a black screen again. The web interface shows “cannot start xserver”, how can this be solved?
Hi did a factory reset on volumio 4.071 and updated to 4.072 on RPI5.
Now the Touch Display plugin fails to install. During installation I get this error (under 4.071 all went ok):
Downloading plugin at https://plugins.volumio.workers.dev/pluginsv2/downloadLatestStable/touch_display/volumio/bookworm/armhf
END DOWNLOAD: https://plugins.volumio.workers.dev/pluginsv2/downloadLatestStable/touch_display/volumio/bookworm/armhf
Creating install location
Unpacking plugin
Checking that the plugin is suitable for this version of Volumio The plugin can be used with this version of Volumio
Checking for duplicate plugin
Copying plugin to location
Installing necessary utilities
Re-synchronizing package index files from their sources
Hit:1 Index of /raspbian bookworm InRelease
Hit:2 Index of /debian bookworm InRelease
Ign:3 https://deb.nodesource.com/node_20.x bookworm InRelease
Err:4 https://deb.nodesource.com/node_20.x bookworm Release
404 Not Found [IP: 172.66.150.169 443]
Reading package lists…
Running apt-get update failed
Plugin failed to install!
Cleaning up…
Hi @pjorgenunes
We identified the issue last night and it’s already being addressed.
Recent changes from NodeSource caused bookworm and buster to no longer be recognized as valid distribution names.
It’s not related to V4.072, also earlier images are generating the same error.
Thank you for your quick feedback.
Is there any way of installing it manually?
No need just upgrade to the latest Volumio version via OTA, as it has been fixed.
Hi
due to another issue with V3 I thought I would give V4 a try but its failing to install the touch plugin
http://logs.volumio.org/volumio/7SLVNbX.html
volumio@volumio:~$ cat /etc/os-release
PRETTY_NAME=“Raspbian GNU/Linux 12 (bookworm)”
NAME=“Raspbian GNU/Linux”
VERSION_ID=“12”
VERSION=“12 (bookworm)”
VERSION_CODENAME=bookworm
ID=raspbian
ID_LIKE=debian
HOME_URL=“http://www.raspbian.org/”
SUPPORT_URL=“http://www.raspbian.org/RaspbianForums”
BUG_REPORT_URL=“http://www.raspbian.org/RaspbianBugs”
VOLUMIO_BUILD_VERSION=“3a3cfe435f8bb2bc94a920662e91a4ef35bc8e7c”
VOLUMIO_FE_VERSION=“35f8f4439f0076a62fefa72fd80b70701b3d6cbd”
VOLUMIO_FE3_VERSION=“bcca17b6b6b26edfb999e6fd7da1b222a88a61d2”
VOLUMIO_BE_VERSION=“8bcc10c3dbcbcb349e9887dc0527d54876b32688”
VOLUMIO_ARCH=“arm”
VOLUMIO_VARIANT=“volumio”
VOLUMIO_TEST=“FALSE”
VOLUMIO_BUILD_DATE=“Tue Dec 2 11:51:19 UTC 2025”
VOLUMIO_VERSION=“4.072”
VOLUMIO_HARDWARE=“pi”
VOLUMIO_DEVICENAME=“Raspberry Pi”
VOLUMIO_HASH=“e5001581b220b096097cf8f46a54d4f1”
volumio@volumio:~$ cat /proc/cpuinfo | grep -i revision
CPU revision : 3
CPU revision : 3
CPU revision : 3
CPU revision : 3
Revision : c03111
volumio@volumio:~$ cat /proc/cpuinfo | grep -i model
model name : ARMv7 Processor rev 3 (v7l)
model name : ARMv7 Processor rev 3 (v7l)
model name : ARMv7 Processor rev 3 (v7l)
model name : ARMv7 Processor rev 3 (v7l)
Model : Raspberry Pi 4 Model B Rev 1.1
I keep getting the same issue and already done a factory reset.
Are you sure you updated your Volumio to 4.073 (05-12-2025) Hotfix release?
Please paste screenshot from: System Settings → System Version
Kind regards,
@pjorgenunes : same problem as you. I built the download link as they are everytime built on the same model and it works :
https://updates2.volumio.org/pi/volumio/4.073/Volumio-4.073-2025-12-05-pi.zip
Regards
Awesome, thanks. I will just flash the card and test it 
Hey @pjorgenunes,
I genuinely do not understand what specific problem you are reporting here.
Are you saying:
Countless users have successfully switched to beta.
So what exactly is the blocker? “I think I’m stuck” is not actionable information. Either OTA works and you have not configured the release channel correctly, or OTA is broken and we need logs to investigate. There is no third option where we guess what you meant.
If OTA genuinely fails after switching to the test channel, provide a log link from http://volumio.local/dev so we can actually investigate. If you simply did not know how to switch channels, the documentation link was already given - read it and follow the steps.
I cannot help further without knowing which of these scenarios applies to you.
Kind Regards,
