[PLUGIN] Touch Display

Adjusting brightness should work as long as you don’t have V1.0 of the official 7" display. On screens of this old revision, brightness values below 128 simply turn the screen off, while values above 127 turn it on.

Apart from that, on the config page of the plugin it is possible to define two different brightness values (“Brightness 1” and “Brightness 2”) and to specify the time of day at which each brightness value should be set (e.g. a higher brightness value in the daytime starting at 6:00 and a lower brightness at the night-time starting at 21:00). The time of day values need to follow the 24-hour clock system and the time format hh:mm. If both time of day settings should be identical, the screen brightness will not be changed but only brightness 1 will be applied.

Regarding the time values be aware that the plugin uses the system time. The system time might deviate from the local time and can only be changed from the command line currently.

What are your settings for “Brightness 1”, “Brightness 2” and their start times on the plugin’s config page?

Ok, I don’t know why it wasn’t working before when I had two separate brightness values entered to start at different times. But I decided to make start time the same for each, and then adjusting Brightness 1 started to work. And then I changed it back to two brightness values starting at different times and that now works too.

hey i would like to get volumio 2.907 to run with touchdsisplay but i can’t do it… when i try it with volumio3.xx everything works

Received SIGRTMIN+20 from PID 1506 (plymouthd).
Started Show Plymouth Reboot Screen.
[2022/02/20 19:32:01.889520,  0] ../source3/winbindd/winbindd.c:266(winbindd_sig_term_handler)
Got sig[15] terminate (is_parent=1)
[2022/02/20 19:32:01.889725,  0] ../source3/winbindd/winbindd.c:266(winbindd_sig_term_handler)
Got sig[15] terminate (is_parent=0)
[2022/02/20 19:32:01.892315,  0] ../source3/winbindd/winbindd.c:266(winbindd_sig_term_handler)
Got sig[15] terminate (is_parent=0)
[2022/02/20 19:32:01.896990,  0] ../source3/winbindd/winbindd.c:266(winbindd_sig_term_handler)
Got sig[15] terminate (is_parent=0)
Stopped LSB: start Winbind daemon.
Stopping the Winbind daemon: winbind.
error: touch_display: Xserver unix domain socket cannot be determined.
error: touch_display: Xserver unix domain socket cannot be determined.
error: touch_display: Xserver unix domain socket cannot be determined.
error: touch_display: Xserver unix domain socket cannot be determined.
xinit: unexpected signal 15
volumio-kiosk.service: main process exited, code=exited, status=1/FAILURE
Stopped Volumio Kiosk.
Unit volumio-kiosk.service entered failed state.

Please post the output of

cat /var/log/Xorg.0.log

What screen (brand and exact model name) are you using?

hey good evening, at the moment the ui doesn’t even work via HDMI. I haven’t gotten to the display yet

pure volumio 2.907 installation and then only touch plugin tries to install, on volumio 3.178 everything is ok

cat /var/log/Xorg.0.log

[ 30.573]
X.Org X Server 1.18.4
Release Date: 2016-07-19
[ 30.573] X Protocol Version 11, Revision 0
[ 30.573] Build Operating System: Linux 4.4.26-v7+ armv7l Raspbian
[ 30.573] Current Operating System: Linux volumio2 4.19.118-v7l+ #1311 SMP Mon Apr 27 14:26:42 BST 2020 armv7l
[ 30.573] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 cma=64M bcm2708_fb.fbwidth=1824 bcm2708_fb.fbheight=984 bcm2708_fb.fbswap=1 smsc95xx.macaddr=DC:A6:32:51:22:DC vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 splash quiet plymouth.ignore-serial-consoles dwc_otg.fiq_enable=1 dwc_otg.fiq_fsm_enable=1 dwc_otg.fiq_fsm_mask=0xF dwc_otg.nak_holdoff=1 console=ttyS0,115200 kgdboc=ttyS0,115200 console=tty1 imgpart=/dev/mmcblk0p2 imgfile=/volumio_current.sqsh elevator=noop rootwait bootdelay=5 logo.nologo vt.global_cursor_default=0 loglevel=0 snd-bcm2835.enable_compat_alsa=1 snd_bcm2835.enable_headphones=1
[ 30.573] Build Date: 11 November 2016 11:59:59AM
[ 30.573] xorg-server 2:1.18.4-2+rpi1 (Debian -- Support)
[ 30.573] Current version of pixman: 0.32.6
[ 30.573] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 30.573] Markers: (–) probed, () from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 30.573] (==) Log file: “/var/log/Xorg.0.log”, Time: Sun Feb 20 21:42:10 2022
[ 30.577] (==) Using config directory: “/etc/X11/xorg.conf.d”
[ 30.577] (==) Using system config directory “/usr/share/X11/xorg.conf.d”
[ 30.580] (==) No Layout section. Using the first Screen section.
[ 30.580] (==) No screen section available. Using defaults.
[ 30.580] (
) |–>Screen “Default Screen Section” (0)
[ 30.580] () | |–>Monitor “”
[ 30.584] (==) No device specified for screen “Default Screen Section”.
Using the first device section listed.
[ 30.584] (
) | |–>Device “Allwinner A10/A13 FBDEV”
[ 30.584] (==) No monitor specified for screen “Default Screen Section”.
Using a default monitor configuration.
[ 30.584] (==) Automatically adding devices
[ 30.584] (==) Automatically enabling devices
[ 30.584] (==) Automatically adding GPU devices
[ 30.587] (==) Max clients allowed: 256, resource mask: 0x1fffff
[ 30.589] (WW) The directory “/usr/share/fonts/X11/cyrillic” does not exist.
[ 30.589] Entry deleted from font path.
[ 30.591] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
built-ins
[ 30.591] (==) ModulePath set to “/usr/lib/xorg/modules”
[ 30.591] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 30.591] (II) Loader magic: 0x636f20
[ 30.591] (II) Module ABI versions:
[ 30.591] X.Org ANSI C Emulation: 0.4
[ 30.591] X.Org Video Driver: 20.0
[ 30.591] X.Org XInput driver : 22.1
[ 30.591] X.Org Server Extension : 9.0
[ 30.593] (–) using VT number 2

[ 30.593] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[ 30.593] (II) no primary bus or device found
[ 30.594] (II) LoadModule: “glx”
[ 30.597] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 30.635] (II) Module glx: vendor=“X.Org Foundation”
[ 30.635] compiled for 1.18.4, module version = 1.0.0
[ 30.635] ABI class: X.Org Server Extension, version 9.0
[ 30.635] (==) AIGLX enabled
[ 30.635] (II) LoadModule: “fbturbo”
[ 30.635] (II) Loading /usr/lib/xorg/modules/drivers/fbturbo_drv.so
[ 30.638] (II) Module fbturbo: vendor=“X.Org Foundation”
[ 30.638] compiled for 1.18.4, module version = 0.5.1
[ 30.638] Module class: X.Org Video Driver
[ 30.638] ABI class: X.Org Video Driver, version 20.0
[ 30.638] (II) FBTURBO: driver for framebuffer: fbturbo
[ 30.642] (WW) Falling back to old probe method for fbturbo
[ 30.643] (II) Loading sub module “fbdevhw”
[ 30.643] (II) LoadModule: “fbdevhw”
[ 30.643] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[ 30.644] (II) Module fbdevhw: vendor=“X.Org Foundation”
[ 30.644] compiled for 1.18.4, module version = 0.0.2
[ 30.644] ABI class: X.Org Video Driver, version 20.0
[ 30.645] (II) FBTURBO(0): using /dev/fb0
[ 30.645] (II) FBTURBO(0): Creating default Display subsection in Screen section
“Default Screen Section” for depth/fbbpp 24/32
[ 30.645] (==) FBTURBO(0): Depth 24, (==) framebuffer bpp 32
[ 30.645] (==) FBTURBO(0): RGB weight 888
[ 30.645] (==) FBTURBO(0): Default visual is TrueColor
[ 30.645] (==) FBTURBO(0): Using gamma correction (1.0, 1.0, 1.0)
[ 30.645] (II) FBTURBO(0): hardware: BCM2708 FB (video memory: 7011kB)
[ 30.645] () FBTURBO(0): Option “fbdev” “/dev/fb0”
[ 30.645] (
) FBTURBO(0): Option “SwapbuffersWait” “true”
[ 30.645] (II) FBTURBO(0): processor: Unknown
[ 30.645] (II) FBTURBO(0): checking modes against framebuffer device…
[ 30.645] (II) FBTURBO(0): checking modes against monitor…
[ 30.645] (–) FBTURBO(0): Virtual size is 1824x984 (pitch 1824)
[ 30.645] (**) FBTURBO(0): Built-in mode “current”
[ 30.645] (==) FBTURBO(0): DPI set to (96, 96)
[ 30.645] (II) Loading sub module “fb”
[ 30.645] (II) LoadModule: “fb”
[ 30.645] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 30.649] (II) Module fb: vendor=“X.Org Foundation”
[ 30.649] compiled for 1.18.4, module version = 1.0.0
[ 30.649] ABI class: X.Org ANSI C Emulation, version 0.4
[ 30.649] (==) Depth 24 pixmap format is 32 bpp
[ 30.661] (II) FBTURBO(0): using backing store heuristics
[ 30.667] (II) FBTURBO(0): can’t load ‘g2d_23’ kernel module
[ 30.667] (II) FBTURBO(0): failed to enable the use of sunxi display controller
[ 30.667] (II) FBTURBO(0): No sunxi-g2d hardware detected (check /dev/disp and /dev/g2d)
[ 30.667] (II) FBTURBO(0): G2D hardware acceleration can’t be enabled
[ 30.667] (II) FBTURBO(0): enabled fbdev copyarea acceleration
[ 30.667] (==) FBTURBO(0): Backing store enabled
[ 30.672] (==) FBTURBO(0): DPMS enabled
[ 30.672] (II) FBTURBO(0): failed to enable hardware cursor
[ 30.672] (II) FBTURBO(0): no 3D acceleration because the driver has been compiled without libUMP
[ 30.672] (II) FBTURBO(0): if this is wrong and needs to be fixed, please check ./configure log
[ 30.673] (==) RandR enabled
[ 30.689] (II) SELinux: Disabled on system
[ 30.694] (II) AIGLX: Screen 0 is not DRI2 capable
[ 30.694] (EE) AIGLX: reverting to software rendering
[ 31.520] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
[ 31.522] (II) AIGLX: Loaded and initialized swrast
[ 31.522] (II) GLX: Initialized DRISWRAST GL provider for screen 0
[ 31.687] (II) FBTURBO(0): using backing store heuristics
[ 31.693] (II) FBTURBO(0): can’t load ‘g2d_23’ kernel module
[ 31.693] (II) FBTURBO(0): failed to enable the use of sunxi display controller
[ 31.693] (II) FBTURBO(0): No sunxi-g2d hardware detected (check /dev/disp and /dev/g2d)
[ 31.693] (II) FBTURBO(0): G2D hardware acceleration can’t be enabled
[ 31.693] (II) FBTURBO(0): enabled fbdev copyarea acceleration
[ 31.694] (==) FBTURBO(0): DPMS enabled
[ 31.694] (II) FBTURBO(0): failed to enable hardware cursor
[ 31.694] (II) FBTURBO(0): no 3D acceleration because the driver has been compiled without libUMP
[ 31.694] (II) FBTURBO(0): if this is wrong and needs to be fixed, please check ./configure log
[ 31.694] (==) RandR enabled
[ 31.707] (II) SELinux: Disabled on system
[ 31.709] (II) AIGLX: Screen 0 is not DRI2 capable
[ 31.709] (EE) AIGLX: reverting to software rendering
[ 31.714] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
[ 31.716] (II) AIGLX: Loaded and initialized swrast
[ 31.716] (II) GLX: Initialized DRISWRAST GL provider for screen 0

Are you using the screen you mentioned here?

it’s not my setup, everything works for me thank you. this is from my friend who prefers to stay with 2.xxx he only uses hdmi to tv. sound does not work but IU surface

Ok, what is the brand and model name of his HDMI display?

In case there has been a download problem during the installation of the Touch Display plugin: Did you already try to uninstall and re-install the plugin?

samstug tv 55zoll

I’ve uninstalled/installed it more times with a restart after each action

What are the outputs of

chromium-browser -version

and

systemctl status -l volumio-kiosk.service

?

volumio@volumio2:~$ chromium-browser -version
-bash: chromium-browser: command not found
volumio@volumio2:~$ systemctl status -l volumio-kiosk.service
● volumio-kiosk.service - Volumio Kiosk
Loaded: loaded (/lib/systemd/system/volumio-kiosk.service; disabled)
Active: active (running) since Sun 2022-02-20 22:14:16 UTC; 8min ago
Main PID: 1160 (startx)
CGroup: /system.slice/volumio-kiosk.service
├─1160 /bin/sh /usr/bin/startx /etc/X11/Xsession /opt/volumiokiosk.sh – -nocursor
├─1184 xinit /etc/X11/Xsession /opt/volumiokiosk.sh – /usr/bin/X :0 -nocursor -auth /tmp/serverauth.9nxgUExXhn
├─1186 /usr/lib/xorg/Xorg :0 -nocursor -auth /tmp/serverauth.9nxgUExXhn
├─1249 /bin/bash /opt/volumiokiosk.sh
├─1266 /usr/bin/ssh-agent /opt/volumiokiosk.sh
├─1271 /usr/bin/openbox --startup /usr/lib/arm-linux-gnueabihf/openbox-autostart OPENBOX
├─1625 /usr/bin/pulseaudio --start
├─1814 /bin/sh /usr/bin/start-pulseaudio-x11
└─1816 /usr/bin/xprop -root -spy

Feb 20 22:14:16 volumio2 startx[1160]: Markers: (–) probed, (**) from config file, (==) default setting,
Feb 20 22:14:16 volumio2 startx[1160]: (++) from command line, (!!) notice, (II) informational,
Feb 20 22:14:16 volumio2 startx[1160]: (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
Feb 20 22:14:16 volumio2 startx[1160]: (==) Log file: “/var/log/Xorg.0.log”, Time: Sun Feb 20 22:14:16 2022
Feb 20 22:14:16 volumio2 startx[1160]: (==) Using config directory: “/etc/X11/xorg.conf.d”
Feb 20 22:14:16 volumio2 startx[1160]: (==) Using system config directory “/usr/share/X11/xorg.conf.d”
Feb 20 22:14:16 volumio2 startx[1160]: modprobe: FATAL: Module g2d_23 not found.
Feb 20 22:14:18 volumio2 pulseaudio[1625]: Unable to contact D-Bus: org.freedesktop.DBus.Error.Spawn.ExecFailed: /usr/bin/dbus-launch terminated abnormally without any error message
Feb 20 22:14:19 volumio2 pulseaudio[1625]: Unable to contact D-Bus: org.freedesktop.DBus.Error.Spawn.ExecFailed: /usr/bin/dbus-launch terminated abnormally without any error message
Feb 20 22:14:19 volumio2 pulseaudio[1625]: org.bluez.Manager.GetProperties() failed: org.freedesktop.DBus.Error.UnknownMethod: Method “GetProperties” with signature “” on interface “org.bluez.Manager” doesn’t exist

At least chromium-browser has not been installed and also has probably not been downloaded successfully. This could be e.g. because of DNS problems or Volumio’s data partition has not been fully expanded and therefore there is not enough space to install chromium-browser.

You may check disk space with

df -h

Look for the line starting with “overlayfs”.

typically 16gb

Volumio Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
volumio@volumio2:~$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mmcblk0p2 2.2G 487M 1.6G 24% /imgpart
/dev/loop0 355M 355M 0 100% /static
overlay 13G 557M 12G 5% /
devtmpfs 1.9G 0 1.9G 0% /dev
tmpfs 2.0G 68K 2.0G 1% /dev/shm
tmpfs 2.0G 4.7M 2.0G 1% /run
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 2.0G 0 2.0G 0% /sys/fs/cgroup
tmpfs 2.0G 44K 2.0G 1% /tmp
tmpfs 2.0G 0 2.0G 0% /var/spool/cups
tmpfs 20M 24K 20M 1% /var/log
tmpfs 2.0G 0 2.0G 0% /var/spool/cups/tmp
/dev/mmcblk0p1 61M 57M 3.4M 95% /boot
tmpfs 396M 0 396M 0% /run/user/1000
volumio@volumio2:~$

Looks good. So probably a download problem as mentioned above.

yes no plan what I do wrong. get no picture from the HDMI on Volumio 2.xxx

IMHO you need to somehow make it so that the download of the additional software like chromium-browser - which happens during the installation of the plugin - is successful. To me this appears to be the culprit here.

chromium-browser is running in this time, but maybe I can also get Rotary Encoder KY-040 to run on the volumio 3.xxx then I would switch

I can’t follow, could you rephrase this statement:

I got the chromium browser up and running now. hdmi output still no picture. normally nothing has to be in the config or

Could please post the outputs of

cat /var/log/Xorg.0.log

and

systemctl status -l volumio-kiosk.service

again? Or maybe better PM me to not to clutter this thread too much with logs etc.