[PLUGIN] Touch Display

miklau · June 24, 2025, 6:35pm

Thanks for the quick reply.

Can’t explain what happened, but after three more reboots I was able to store the settings and now have a working screen🙂

I am running a 3b+ and the screen is very similar to this one without the casing and has a Wisecoco sticker on the back: 8.8” HDMI

Next step is to install the now playing plugin and restore my old settings.

Have a great day.

Gelo5 · June 24, 2025, 7:15pm

I have the same screen. Just set the TouchDisplay to rotate 90 degrees. userconfig - empty
(RPI5).
ps. only the boot screen (logo) is rotated during startup

Ritger · June 25, 2025, 3:14am

Hello all,

I recently installed Volumio on my Raspberry Pi 4 with 2 GB of RAM. I also have a waveshare 5.5 inch AMOLED display connected via HDMI. When I try to install the Display Touch plugin I get the following error:
Downloading plugin at https://plugins.volumio.workers.dev/pluginsv2/downloadLatestStable/touch_display/volumio/buster/armhf END DOWNLOAD: https://plugins.volumio.workers.dev/pluginsv2/downloadLatestStable/touch_display/volumio/buster/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 Get:1 https://deb.nodesource.com/node_14.x buster InRelease [4584 B] Get:2 http://raspbian.raspberrypi.org/raspbian buster InRelease [15.0 kB] Get:3 http://archive.raspberrypi.org/debian buster InRelease [54.2 kB] Err:2 http://raspbian.raspberrypi.org/raspbian buster InRelease Undetermined Error [IP: 93.93.128.193 80] Get:4 https://deb.nodesource.com/node_14.x buster/main armhf Packages [786 B] Get:5 http://archive.raspberrypi.org/debian buster/main armhf Packages [400 kB] Fetched 460 kB in 1s (358 kB/s) Reading package lists... Reading package lists... Building dependency tree... Reading state information... 0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded. Installing graphical environment Reading package lists... Building dependency tree... Reading state information... Installation of xinit failed Plugin failed to install! Cleaning up... Removing dependencies Reading package lists... Building dependency tree... Reading state information... Reading package lists... Building dependency tree... Reading state information... Reading package lists... Building dependency tree... Reading state information... Reading package lists... Building dependency tree... Reading state information... Reading package lists... Building dependency tree... Reading state information... Reading package lists... Building dependency tree... Reading state information... Reading package lists... Building dependency tree... Reading state information... Package 'chromium-browser' is not installed, so not removed 0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded. Reading package lists... Building dependency tree... Reading state information... Package 'openbox' is not installed, so not removed 0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded. Reading package lists... Building dependency tree... Reading state information... Deleting /opt/volumiokiosk.sh Deleting /data/volumiokiosk Deleting /data/volumiokioskextensions Deleting /lib/systemd/system/volumio-kiosk.service Enabling login prompt Done Removing plugin directory /data/plugins/user_interface/touch_display Removing temporary directory /tmp/touch_display-ZPcSjpCk78 An error occurred while installing the plugin Error

Can anyone help?

Wheaten · June 25, 2025, 5:17am

@Ritger

Please read this topic, as the possible solution is mentioned multiple times.
like: [PLUGIN] Touch Display - #1423 by gvolt

proteinklumpen · July 2, 2025, 8:28pm

Hello everyone,

I just got into the topic of volumio and need some assitance with my setup. I bought a raspberry pi 5 with the waveshare 7" touch display.
This one to be specific:

I installed volumio (version 3.816) and the touch display plugin (version 3.5.1). The visuals are working via HDMI. My problem is that the touch display doesn’t work. I really tried to get this on my own and read almost the whole discussion in this community but couldn’t fix it. Here are some further information:

cat /boot/config.txt

### DO NOT EDIT THIS FILE ###
### APPLY CUSTOM PARAMETERS TO userconfig.txt ###
initramfs volumio.initrd
gpu_mem=128
gpu_mem_256=32
gpu_mem_512=32
gpu_mem_1024=128
max_usb_current=1
[pi5]
usb_max_current_enable=1
[all]
include volumioconfig.txt
include userconfig.txt

#### Volumio i2s setting below: do not alter ####
dtoverlay=hifiberry-digi-pro

cat /boot/userconfig.txt

# Add your custom config.txt options to this file, which will be preserved during updates
hdmi_group=2
hdmi_mode=87
hdmi_cvt 1024 600 60 6 0 0 0
hdmi_drive=1

Can somebody help me troubleshoot this?

Thanks in advance

RedEyeNinja · July 4, 2025, 2:35pm

Pi5 8gb and Pi4 8gb, both on 4.014 beta, updated to 3.5.5 stable and both crashed on boot, unrecoverable…needed to reflash.

gvolt · July 4, 2025, 7:22pm

I can’t replicate it. On a Pi4 (2GB) with a new Volumio system (4.014beta), I first installed version 3.5.2 of the plugin and then clicked the “Update” button that appears for the Touch Display plugin. This installed the plugin version 3.5.5, after which I restarted Volumio without any problems.

Wheaten · July 4, 2025, 7:42pm

Same here. no issues

proteinklumpen · July 6, 2025, 10:38pm

I was actually able to fix it myself. At first I thought it was a compatibility problem with the touch plugin, because I have seen a lot of posts about this. It wasn’t. Here is how I troublehooted it:

Possible Troubleshooting Steps

Check if kernel registers inputdevice. Search for “input: … as /devices/…”

dmesg | grep -i input

Check if usb-device is listed

lsusb

Check if X11 rejects the touch inputs or not.

cat /var/log/Xorg.0.log | grep -i touch

It should look something like this if it works

bash-5.0# cat /var/log/Xorg.0.log | grep -i touch
[  1063.986] (**) WaveShare WS170120: Applying InputClass "libinput touchscreen catchall"
[  1063.986] (**) WaveShare WS170120: Applying InputClass "Touch rotation"
[  1064.050] (II) event0  - WaveShare WS170120: is tagged by udev as: Touchscreen
[  1064.050] (II) event0  - WaveShare WS170120: device is a touch device
[  1064.080] (II) XINPUT: Adding extended input device "WaveShare WS170120" (type: TOUCHSCREEN, id 6)
[  1064.142] (II) event0  - WaveShare WS170120: is tagged by udev as: Touchscreen
[  1064.142] (II) event0  - WaveShare WS170120: device is a touch device```

Check if driver is installed. Search for “hid_multitouch”

lsmod | grep hid

Check if the kernel-event-subsystem of your device gets the inputs via “evtest”

sudo apt-get install evtest
evtest

Select your device. It opens up a “listener” and shows any traffic coming from this device. I didn’t recevice any on my PI 5. So my issue was way deeper than the Volumio touch display plugin.

Solution
My Waveshare 7" HDMI touchscreen was detected by Volumio and listed correctly in lsusb and dmesg, but the touch functionality didn’t work — evtest showed no input events. The issue was resolved by adding hdmi_force_hotplug=1 and config_hdmi_boost=10 to /boot/userconfig.txt, which forced proper HDMI initialization and allowed the touch controller to fully activate.

Cause
The Raspberry Pi detected the touchscreen’s USB interface and loaded the appropriate drivers, but the touch controller didn’t send any input events because the HDMI signal wasn’t properly initialized during boot. Many touchscreen controllers require an active HDMI handshake to fully power up or exit standby; by default, if no display is detected, the Pi disables HDMI output, preventing the controller from completing its initialization.
Adding hdmi_force_hotplug=1 forces the Pi to enable HDMI even without a detected display, and config_hdmi_boost=10 strengthens the signal to ensure stable communication — together, these settings triggered proper HDMI activation, allowing the touch controller to start correctly and send events to the system.

GROMIK · July 9, 2025, 8:05am

Good morning,
I’m asking for help getting my Waveshare 12.3 Dsi display working with Volumio.
Has anyone managed to get this working?
I should mention that the display works with PI OS on a Raspberry Pi 5, but Volumio won’t even start the display.

Wheaten · July 9, 2025, 8:11am

Hi,

Which Volumio version are you running, don’t state latest?

Do you see the boot logo?
Your using it on a rpi5?

output of:
cat /boot/config.txt
cat /boot/userconfig.txt

GROMIK · July 9, 2025, 8:16am

The latest version of Volumio.
I can’t see anything on the screen, it’s black.
I’m using a Raspberry Pi 5.
I’ve tried the userconfig settings from the manufacturer’s website, but to no avail.

Wheaten · July 9, 2025, 8:19am

Please provide the answers and output as requested. When not I can’t provide any support.

GROMIK · July 9, 2025, 8:34am

Sorry, I’m using a translator

Volumio VERSION: 3.819

config.txt

### DO NOT EDIT THIS FILE ###
### APPLY CUSTOM PARAMETERS TO userconfig.txt ###
initramfs volumeio.initrd
gpu_mem=128
gpu_mem_256=32
gpu_mem_512=32
gpu_mem_1024=128
max_usb_current=1
[pi5]
usb_max_current_enable=1
[all]
include volumeioconfig.txt
include userconfig.txt

userconfig.txt

dtoverlay=vc4-kms-v3d
DSI1 Use
dtoverlay=vc4-kms-dsi-waveshare-panel-v2-test,12_3_inch_a_4lane
#DSI0 Use
#dtoverlay=vc4-kms-dsi-waveshare-panel-v2-test,12_3_inch_a_4lane,dsi0

Link: https://www.waveshare.com/wiki/12.3-DSI-TOUCH-A

Wheaten · July 9, 2025, 8:50am

Moved the topic to the correct post.

Did you install anything related to this display, as the dtoverlay is already present in /boot/overlays
vc4-kms-dsi-waveshare-panel-v2.dtbo

If yes, please perform a factory reset and only add to /boot/userconfig.txt:
dtoverlay=vc4-kms-dsi-waveshare-panel-v2

And see if that shows the bootlogo.

GROMIK · July 9, 2025, 8:57am

I analyzed the /boot/overlays file and indeed didn’t find “vc4-kms-dsi-waveshare-panel-v2.dtbo”

Wheaten · July 9, 2025, 9:18am

Can you add to /boot/userconfig.txt:
display_auto_detect=1

So it should exactly look like this:

display_auto_detect=1
dtoverlay=vc4-kms-v3d
#DSI1 Use
dtoverlay=vc4-kms-dsi-waveshare-panel-v2-test,12_3_inch_a_4lane
#DSI0 Use
#dtoverlay=vc4-kms-dsi-waveshare-panel-v2-test,12_3_inch_a_4lane,dsi0

GROMIK · July 9, 2025, 10:50am

I can’t install the waveshare 12.3 driver because the kernel version doesn’t match, via ssh of course

Wheaten · July 9, 2025, 11:00am

Then try if this one will do the trick, if not you might try to download the beta version of volumio.
vc4-kms-dsi-waveshare-panel-v2.zip (1.1 KB)

cd ~
wget https://community.volumio.com/uploads/short-url/rOCwRS6008AMhAZXZ7Tz6k3UfAX.zip
miniunzip rOCwRS6008AMhAZXZ7Tz6k3UfAX.zip
rm rOCwRS6008AMhAZXZ7Tz6k3UfAX.zip
sudo cp vc4-kms-dsi-waveshare-panel-v2.dtbo /boot/overlays/

Gelo5 · July 9, 2025, 11:05am

This is your config.txt?

### DO NOT EDIT THIS FILE ###
### APPLY CUSTOM PARAMETERS TO userconfig.txt ###
initramfs volumeio.initrd
gpu_mem=128
gpu_mem_256=32
gpu_mem_512=32
gpu_mem_1024=128
max_usb_current=1
[pi5]
usb_max_current_enable=1
[all]
include volumeioconfig.txt
include userconfig.txt

Why is it like this:
initramfs volumeio.initrd
include volumeioconfig.txt ?
Shouldn’t it be like this?
initramfs volumio.initrd
include volumioconfig.txt

These are just my observations, maybe that’s how it should be?
Regards