Oh hey, I was thinking I should check on this thread, well I’m not disappointed 
Feel free to tag me when you release this so that I can join in on the tests.
Tested on Rpi4.
Spotify connect ok
Dsp for volumio too 
A problem with multiroom makes the UI blinking :
Jun 24 16:56:01 volumio3-rpi4 volumio[936]: info: CoreCommandRouter::volumioGetVisibleSources
Jun 24 16:56:01 volumio3-rpi4 volumio[936]: info: CoreCommandRouter::executeOnPlugin: my_music , getDisabledSources
Jun 24 16:56:01 volumio3-rpi4 volumio[936]: info: CoreCommandRouter::executeOnPlugin: multiroom , getMultiroom
Jun 24 16:56:01 volumio3-rpi4 volumio[936]: error: Could not retrieve plugin audio_interface multiroom
Have you met this?
Nice 
new DSP or old one?
That seems familiar indeed – looked into it a while back and it seemed like just an empty warning!
Not new but alive
unfortunately this is not…
can you give more details please. I’d like to use the touch screen too
@ashthespy @balbuze @Darmur @ewald_harmsen @SuperBoby
Using the package below the plugin should install and run on Buster and as well on Jessie based Volumio.
Currently untested is the installation of chromium-browser on other hardware than Raspberries. Maybe someone with “other” hardware can try it (even this would still be done under Jessie).
What unfortunately does not work on Buster ATM is matchbox-keyboard automatically showing up and hiding 
As yet don’t know if the reason is related to changes in Buster or chromium-browser.
touch_display_1_1_9beta01.zip (846,9 KB)
1 Like
thank you. It installs fine. But when enabling it, the local display get black with backlight on. After a reboot, the prompt is displayed while booting, correctly rotated (90° in the plugin setting) but turns black when the UI is loaded. I installed after the official version.
If I did not misunderstand you have the display rotated by 90°. Do you have an original Raspberry 7" display or another display with a higher resolution. At least in the second case setting the GPU memory to a higher value would probably be necessary. IIRC for a resolution of 1920x1080 a GPU mem of at least 34MB was required if the display is rotated by either 90° or 270°.
If that should not help, please post the result of systemctl status -l volumio-kiosk.
Yes, I rotated the screen in plugin settings. This is the official 7"
systemctl status -l volumio-kiosk
● volumio-kiosk.service - Volumio Kiosk
Loaded: loaded (/lib/systemd/system/volumio-kiosk.service; disabled; vendor preset: enabled)
Active: active (running) since Thu 2020-06-25 06:42:31 UTC; 24min ago
Main PID: 3382 (startx)
Tasks: 19 (limit: 4547)
Memory: 20.5M
CGroup: /system.slice/volumio-kiosk.service
├─ 3382 /bin/sh /usr/bin/startx /etc/X11/Xsession /opt/volumiokiosk.sh – -nocursor
├─ 3413 xinit /etc/X11/Xsession /opt/volumiokiosk.sh – /usr/bin/X :0 -nocursor -auth /tmp/serverauth.y9NvRSD119
├─ 3414 /usr/lib/xorg/Xorg :0 -nocursor -auth /tmp/serverauth.y9NvRSD119
├─ 3460 /bin/bash /opt/volumiokiosk.sh
├─ 3484 /usr/bin/ssh-agent /opt/volumiokiosk.sh
├─ 3490 /usr/bin/openbox --startup /usr/lib/arm-linux-gnueabihf/openbox-autostart OPENBOX
├─ 3518 /usr/bin/xbindkeys -f /etc/xbindkeysrc
├─25358 /bin/bash /usr/bin/chromium-browser --simulate-outdated-no-au=Tue, 31 Dec 2099 23:59:59 GMT --disable-pinch --kiosk --no-first-run --disable-3d-apis --disable-breakpad --disable-crash-rep
├─25364 lsmod
└─25365 grep ^i915
Jun 25 06:42:31 volumio3-rpi4 startx[3382]: xorg-server 2:1.20.4-1+rpt1 (https://www.debian.org/support)
Jun 25 06:42:31 volumio3-rpi4 startx[3382]: Current version of pixman: 0.36.0
Jun 25 06:42:31 volumio3-rpi4 startx[3382]: Before reporting problems, check http://wiki.x.org
Jun 25 06:42:31 volumio3-rpi4 startx[3382]: to make sure that you have the latest version.
Jun 25 06:42:31 volumio3-rpi4 startx[3382]: Markers: (–) probed, (**) from config file, (==) default setting,
Jun 25 06:42:31 volumio3-rpi4 startx[3382]: (++) from command line, (!!) notice, (II) informational,
Jun 25 06:42:31 volumio3-rpi4 startx[3382]: (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
Jun 25 06:42:31 volumio3-rpi4 startx[3382]: (==) Log file: “/var/log/Xorg.0.log”, Time: Thu Jun 25 06:42:31 2020
Jun 25 06:42:31 volumio3-rpi4 startx[3382]: (==) Using config directory: “/etc/X11/xorg.conf.d”
Jun 25 06:42:31 volumio3-rpi4 startx[3382]: (==) Using system config directory “/usr/share/X11/xorg.conf.d”
Hm, should work. I will test again but will have the chance in about 4 hours at the earliest.
What is the content of your /boot/config.txt and /boot/userconfig.txt?
I increased the memory to 64. But no better.
cat /boot/config.txt
# Disable audio (added by raspberrypi-sys-mods)
dtparam=audio=no
initramfs volumio.initrd
#GPU_MEM=32
max_usb_current=1
dtparam=audio=on
audio_pwm_mode=2
dtparam=i2c_arm=on
disable_splash=1
hdmi_force_hotplug=1
enable_uart=1
include userconfig.txt
#### Touch Display gpu_mem setting below: do not alter ####
gpu_mem=64
and
cat /boot/userconfig.txt
dtoverlay=pi3-miniuart-bt
#### Touch Display rotation setting below: do not alter ####
display_lcd_rotate=1
display_hdmi_rotate=1@balbuze Some more questions:
Does using a rotation 0° help (probably not…)?
What is the version of the chromium-browser?
Has this been a freshly setup system? If not, did you try to install the chromium-browser manually or version 1.1.8 of the touch display plugin?
setting rotation to 0 is not better.
I installed first the plugin available in UI.
Then uninstall it and install your zip.
@ashthespy The PI never reboot using reboot from the menu. Need to power off/on
Interesting, come to think about it, I only checked the ‘Power Off’ and never tried a reboot. I won’t have access to my pi for a few days, could you tail journalctl and hit Reboot?
Ok, that’s not unexpected… just to rule out.
I suspect that’s the cause. The plugin available in the UI does not recognize Raspberry hardware due to the changed value of VOLUMIO_HARDWARE (see above) in this Buster image. In consequence the installation part for “other hardware” gets executed.
Uninstalling the plugin does not remove the packages it has installed. What you can try is uninstalling the plugin and removing the chromium-browser with sudo apt-get -y purge --auto-remove chromium-browser. I think I did this, too, when I was investigating the issue reported by @SuperBoby. But I can’t remember if that was sufficient…
If possible, it might be easier to start with a fresh Volumio system.
@ashthespy nothing really particular
Jun 25 08:51:04 volumio3-rpi4 volumio[921]: info: ___________ PLUGINS: Run onVolumioReboot Tasks ___________
Jun 25 08:51:04 volumio3-rpi4 volumio[921]: info: PLUGIN onReboot : touch_display
Jun 25 08:51:04 volumio3-rpi4 volumio[921]: info: PLUGIN onReboot : networkfs
Jun 25 08:51:04 volumio3-rpi4 sudo[16875]: volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/umount -f /mnt/NAS/musique
Jun 25 08:51:04 volumio3-rpi4 sudo[16875]: pam_unix(sudo:session): session opened for user root by (uid=0)
Jun 25 08:51:04 volumio3-rpi4 systemd[13953]: mnt-NAS-musique.mount: Succeeded.
Jun 25 08:51:04 volumio3-rpi4 systemd[1]: mnt-NAS-musique.mount: Succeeded.
Jun 25 08:51:04 volumio3-rpi4 sudo[16875]: pam_unix(sudo:session): session closed for user root
Connection to 192.168.1.83 closed by remote host.
Could it be due to the touch screen plugin?
I ran into this as well - can’t uninstall.sh script also handle removal of the installed packages? It currently removes a few config files
@ashthespy Yes, it could do. It is some kind of dead hand from the time the plugin has been created… and I did not find the time to rework this part especially check if removing the packages the plugin installs has any negative effects on the system. It should not using --auto-remove but … So uninstall.sh currently only handles additional files which are created by the plugin itself and which can be removed without any side effects to the system.
did the trick. It works now!
But the display not centered exactly. seems moved to the right.