I have been trying to set this up proper and got it working. Correct view on screen, right rotation, able to play etc. Everything worked. Then I tried to add some support for Bluetooth speaker, but then the touch part stopped working.
Did a reflash and set up everything again, screen is on and I can see the player, but the touch part is not working.
Then your issue can only be solved by changes to the plymouth theme Volumio uses during the boot process. Possibly you could create your own plymouth theme with lettering adapted to the portrait format.
Please post the full contents of the following four files from your /boot partition after the problem occurs (after second reboot when the touchscreen stops working):
cmdline.txt
config.txt
volumioconfig.txt
userconfig.txt
Also, include a link to the Volumio debug log. You can generate it from the UI under http://<your-volumio>/dev section. This will help verify the kernel boot messages, display probing, DRM/KMS initialization, and whether the touch input device is being detected correctly.
The sequence you described suggests that either the KMS overlay is not being applied early enough during boot, or the Touch Display plugin might be altering something in X11 or the framebuffer assignment that disables the touch device on the next reboot.
Once we have those four files and the debug log, we can analyze whether the issue is caused by boot parameter ordering, the plugin reconfiguring something incorrectly, or a driver failing to initialize on second boot.
If it turns out to be related to plugin behavior, we can then suggest a workaround or file an issue for plugin maintainers.
I discovered this morning one thing. If my RPi4 is powered off, at first startup touch function is working. When I performed a reboot, then touch function is not working. So I have a solution that is not robust but that work. A simple reboot did not do the same than a reboot with a power supply stop and start
### 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
#### Volumio i2s setting below: do not alter ####
dtoverlay=hifiberry-digi-pro
/boot/volumioconfig.txt
### DO NOT EDIT THIS FILE ###
### APPLY CUSTOM PARAMETERS TO userconfig.txt ###
[cm4]
dtoverlay=dwc2,dr_mode=host
otg_mode=1
[pi5]
dtoverlay=vc4-kms-v3d-pi5
# dtparam=uart0_console # Disabled by default
dtparam=nvme
dtparam=pciex1_gen=2
[all]
arm_64bit=0
dtparam=audio=on
audio_pwm_mode=2
dtparam=i2c_arm=on
disable_splash=1
hdmi_force_hotplug=1
force_eeprom_read=0
/boot/userconfig.txt
# Add your custom config.txt options to this file, which will be preserved during updates
display_auto_detect=1
dtoverlay=vc4-kms-v3d-pi4,nohdmi
dtoverlay=vc4-kms-dsi-ili9881-7inch
#### Touch Display rotation setting below: do not alter ####
display_lcd_rotate=1
display_hdmi_rotate=1
Your analysis is correct. This is a hardware-level power conflict between the Touch Display V2 and the HiFiBerry Digi2 Pro when both are drawing power from the Raspberry Pi GPIO header.
The Digi2 Pro uses the 5V rail from the GPIO header and can be sensitive to voltage dips. The official 7-inch Touch Display also draws a significant amount of current from the same 5V rail, especially during panel initialization and backlight activation.
Your workaround, powering the Touch Display V2 externally, is valid and electrically safe. It removes the load from the Pi’s 5V rail and allows the Digi2 Pro to initialize consistently.
This is not something that can be fixed purely in software. The I2S interface and ALSA kernel drivers expect stable enumeration during boot. If the DAC fails to initialize due to power instability, no software layer can recover it afterward.
Let us know if it remains stable after more testing. Good catch.
Hello,
Some aditional information after a few days …
The alsa error was due to a lack a patience from my side. I just have to wait some seconds to have alsa started ! It was reported in a couple of posts !
In adition I found also that part at the pihut webstore in order to plug the screen directly to USB port and not on the GPIO pins from the hifiberry. Very usefull for a very small price ! (search : “USB Power Breakout for Raspberry Pi Touch Display 2”)
