[PLUGIN] Touch Display

To me it looks, as if the resolution of the display is not properly detected (too low).

Please post the output of

cat /var/log/Xorg.0.log

Also check for the effect of adding

framebuffer_width=800
framebuffer_height=480

to your “/boot/userconfig.txt” (reboot required).

I changed the resolution and rebooted but no change.
Here is the output of the log file (after the change of resolution):

[    44.645] 
X.Org X Server 1.20.4
X Protocol Version 11, Revision 0
[    44.646] Build Operating System: Linux 5.4.0-72-generic armv8l Raspbian
[    44.646] Current Operating System: Linux volumio 5.10.92-v7+ #1514 SMP Mon Jan 17 17:36:39 GMT 2022 armv7l
[    44.647] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=800 bcm2708_fb.fbheight=480 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000  splash 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 quiet console=ttyS0,115200 console=tty1 imgpart=/dev/mmcblk0p2 imgfile=/volumio_current.sqsh rootwait bootdelay=5 elevator=noop logo.nologo vt.global_cursor_default=0 net.ifnames=0 snd-bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 loglevel=0
[    44.648] Build Date: 04 January 2022  10:05:34AM
[    44.648] xorg-server 2:1.20.4-1+rpt4+deb10u4 (https://www.debian.org/support) 
[    44.648] Current version of pixman: 0.36.0
[    44.648] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[    44.648] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[    44.650] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Mar 22 18:39:51 2022
[    44.659] (==) Using config directory: "/etc/X11/xorg.conf.d"
[    44.659] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[    44.666] (==) No Layout section.  Using the first Screen section.
[    44.666] (==) No screen section available. Using defaults.
[    44.666] (**) |-->Screen "Default Screen Section" (0)
[    44.666] (**) |   |-->Monitor "<default monitor>"
[    44.673] (==) No monitor specified for screen "Default Screen Section".
	Using a default monitor configuration.
[    44.673] (==) Automatically adding devices
[    44.673] (==) Automatically enabling devices
[    44.673] (==) Automatically adding GPU devices
[    44.680] (==) Max clients allowed: 256, resource mask: 0x1fffff
[    44.683] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[    44.683] 	Entry deleted from font path.
[    44.687] (==) 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
[    44.687] (==) ModulePath set to "/usr/lib/xorg/modules"
[    44.687] (II) The server relies on udev to provide the list of input devices.
	If no devices become available, reconfigure udev or disable AutoAddDevices.
[    44.687] (II) Loader magic: 0x1fdf80
[    44.687] (II) Module ABI versions:
[    44.687] 	X.Org ANSI C Emulation: 0.4
[    44.687] 	X.Org Video Driver: 24.0
[    44.687] 	X.Org XInput driver : 24.1
[    44.687] 	X.Org Server Extension : 10.0
[    44.689] (--) using VT number 2

[    44.689] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[    44.689] (II) no primary bus or device found
[    44.689] (II) LoadModule: "glx"
[    44.691] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[    44.757] (II) Module glx: vendor="X.Org Foundation"
[    44.757] 	compiled for 1.20.4, module version = 1.0.0
[    44.757] 	ABI class: X.Org Server Extension, version 10.0
[    44.757] (==) Matched modesetting as autoconfigured driver 0
[    44.757] (==) Matched fbdev as autoconfigured driver 1
[    44.757] (==) Assigned the driver to the xf86ConfigLayout
[    44.757] (II) LoadModule: "modesetting"
[    44.759] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[    44.765] (II) Module modesetting: vendor="X.Org Foundation"
[    44.765] 	compiled for 1.20.4, module version = 1.20.4
[    44.765] 	Module class: X.Org Video Driver
[    44.765] 	ABI class: X.Org Video Driver, version 24.0
[    44.765] (II) LoadModule: "fbdev"
[    44.765] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[    44.768] (II) Module fbdev: vendor="X.Org Foundation"
[    44.768] 	compiled for 1.20.3, module version = 0.5.0
[    44.768] 	Module class: X.Org Video Driver
[    44.768] 	ABI class: X.Org Video Driver, version 24.0
[    44.768] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[    44.768] (II) FBDEV: driver for framebuffer: fbdev
[    44.771] (WW) Falling back to old probe method for modesetting
[    44.771] (EE) open /dev/dri/card0: No such file or directory
[    44.771] (WW) Falling back to old probe method for fbdev
[    44.771] (II) Loading sub module "fbdevhw"
[    44.771] (II) LoadModule: "fbdevhw"
[    44.772] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[    44.774] (II) Module fbdevhw: vendor="X.Org Foundation"
[    44.774] 	compiled for 1.20.4, module version = 0.0.2
[    44.774] 	ABI class: X.Org Video Driver, version 24.0
[    44.774] (II) FBDEV(0): using default device
[    44.774] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
[    44.774] (II) FBDEV(0): Creating default Display subsection in Screen section
	"Default Screen Section" for depth/fbbpp 24/32
[    44.774] (==) FBDEV(0): Depth 24, (==) framebuffer bpp 32
[    44.774] (==) FBDEV(0): RGB weight 888
[    44.774] (==) FBDEV(0): Default visual is TrueColor
[    44.774] (==) FBDEV(0): Using gamma correction (1.0, 1.0, 1.0)
[    44.775] (II) FBDEV(0): hardware: BCM2708 FB (video memory: 1500kB)
[    44.775] (DB) xf86MergeOutputClassOptions unsupported bus type 0
[    44.775] (II) FBDEV(0): checking modes against framebuffer device...
[    44.775] (II) FBDEV(0): checking modes against monitor...
[    44.775] (II) FBDEV(0): Virtual size is 800x480 (pitch 800)
[    44.775] (**) FBDEV(0):  Built-in mode "current"
[    44.775] (==) FBDEV(0): DPI set to (96, 96)
[    44.775] (II) Loading sub module "fb"
[    44.775] (II) LoadModule: "fb"
[    44.775] (II) Loading /usr/lib/xorg/modules/libfb.so
[    44.780] (II) Module fb: vendor="X.Org Foundation"
[    44.780] 	compiled for 1.20.4, module version = 1.0.0
[    44.780] 	ABI class: X.Org ANSI C Emulation, version 0.4
[    44.780] (**) FBDEV(0): using shadow framebuffer
[    44.780] (II) Loading sub module "shadow"
[    44.780] (II) LoadModule: "shadow"
[    44.781] (II) Loading /usr/lib/xorg/modules/libshadow.so
[    44.784] (II) Module shadow: vendor="X.Org Foundation"
[    44.784] 	compiled for 1.20.4, module version = 1.1.0
[    44.784] 	ABI class: X.Org ANSI C Emulation, version 0.4
[    44.784] (II) UnloadModule: "modesetting"
[    44.784] (II) Unloading modesetting
[    44.808] (==) FBDEV(0): Backing store enabled
[    44.812] (==) FBDEV(0): DPMS enabled
[    44.814] (II) Initializing extension Generic Event Extension
[    44.815] (II) Initializing extension SHAPE
[    44.815] (II) Initializing extension MIT-SHM
[    44.816] (II) Initializing extension XInputExtension
[    44.821] (II) Initializing extension XTEST
[    44.821] (II) Initializing extension BIG-REQUESTS
[    44.822] (II) Initializing extension SYNC
[    44.823] (II) Initializing extension XKEYBOARD
[    44.824] (II) Initializing extension XC-MISC
[    44.825] (II) Initializing extension SECURITY
[    44.825] (II) Initializing extension XFIXES
[    44.826] (II) Initializing extension RENDER
[    44.827] (II) Initializing extension RANDR
[    44.829] (II) Initializing extension COMPOSITE
[    44.831] (II) Initializing extension DAMAGE
[    44.832] (II) Initializing extension MIT-SCREEN-SAVER
[    44.833] (II) Initializing extension DOUBLE-BUFFER
[    44.833] (II) Initializing extension RECORD
[    44.834] (II) Initializing extension DPMS
[    44.835] (II) Initializing extension Present
[    44.836] (II) Initializing extension DRI3
[    44.836] (II) Initializing extension X-Resource
[    44.837] (II) Initializing extension XVideo
[    44.837] (II) Initializing extension XVideo-MotionCompensation
[    44.837] (II) Initializing extension SELinux
[    44.837] (II) SELinux: Disabled on system
[    44.837] (II) Initializing extension GLX
[    44.838] (II) AIGLX: Screen 0 is not DRI2 capable
[    46.175] (II) IGLX: Loaded and initialized swrast
[    46.175] (II) GLX: Initialized DRISWRAST GL provider for screen 0
[    46.175] (II) Initializing extension XFree86-VidModeExtension
[    46.176] (II) Initializing extension XFree86-DGA
[    46.177] (II) Initializing extension XFree86-DRI
[    46.180] (II) Initializing extension DRI2
[    46.490] (II) config/udev: Adding input device raspberrypi-ts (/dev/input/event0)
[    46.490] (**) raspberrypi-ts: Applying InputClass "libinput touchscreen catchall"
[    46.490] (**) raspberrypi-ts: Applying InputClass "Touch rotation"
[    46.490] (II) LoadModule: "libinput"
[    46.491] (II) Loading /usr/lib/xorg/modules/input/libinput_drv.so
[    46.529] (II) Module libinput: vendor="X.Org Foundation"
[    46.529] 	compiled for 1.20.3, module version = 0.28.2
[    46.529] 	Module class: X.Org XInput Driver
[    46.529] 	ABI class: X.Org XInput driver, version 24.1
[    46.529] (II) Using input driver 'libinput' for 'raspberrypi-ts'
[    46.529] (**) raspberrypi-ts: always reports core events
[    46.530] (**) Option "Device" "/dev/input/event0"
[    46.530] (**) Option "_source" "server/udev"
[    46.560] (II) event0  - raspberrypi-ts: is tagged by udev as: Touchscreen
[    46.561] (II) event0  - raspberrypi-ts: device is a touch device
[    46.562] (II) event0  - raspberrypi-ts: device removed
[    46.601] (**) Option "config_info" "udev:/sys/devices/platform/soc/soc:firmware/soc:firmware:touchscreen/input/input0/event0"
[    46.601] (II) XINPUT: Adding extended input device "raspberrypi-ts" (type: TOUCHSCREEN, id 6)
[    46.601] (**) Option "AccelerationScheme" "none"
[    46.601] (**) raspberrypi-ts: (accel) selected scheme none/0
[    46.601] (**) raspberrypi-ts: (accel) acceleration factor: 2.000
[    46.601] (**) raspberrypi-ts: (accel) acceleration threshold: 4
[    46.606] (II) event0  - raspberrypi-ts: is tagged by udev as: Touchscreen
[    46.607] (II) event0  - raspberrypi-ts: device is a touch device
[    46.609] (II) config/udev: Adding input device raspberrypi-ts (/dev/input/mouse0)
[    46.610] (II) No input driver specified, ignoring this device.
[    46.610] (II) This device may have been added with another device file.
[    46.631] (II) event0  - raspberrypi-ts: device removed
[    46.693] (II) UnloadModule: "libinput"
[    46.709] (==) FBDEV(0): DPMS enabled
[    46.709] (II) Initializing extension Generic Event Extension
[    46.710] (II) Initializing extension SHAPE
[    46.710] (II) Initializing extension MIT-SHM
[    46.711] (II) Initializing extension XInputExtension
[    46.712] (II) Initializing extension XTEST
[    46.713] (II) Initializing extension BIG-REQUESTS
[    46.714] (II) Initializing extension SYNC
[    46.715] (II) Initializing extension XKEYBOARD
[    46.716] (II) Initializing extension XC-MISC
[    46.716] (II) Initializing extension SECURITY
[    46.717] (II) Initializing extension XFIXES
[    46.718] (II) Initializing extension RENDER
[    46.719] (II) Initializing extension RANDR
[    46.721] (II) Initializing extension COMPOSITE
[    46.721] (II) Initializing extension DAMAGE
[    46.722] (II) Initializing extension MIT-SCREEN-SAVER
[    46.723] (II) Initializing extension DOUBLE-BUFFER
[    46.724] (II) Initializing extension RECORD
[    46.725] (II) Initializing extension DPMS
[    46.726] (II) Initializing extension Present
[    46.726] (II) Initializing extension DRI3
[    46.726] (II) Initializing extension X-Resource
[    46.727] (II) Initializing extension XVideo
[    46.728] (II) Initializing extension XVideo-MotionCompensation
[    46.728] (II) Initializing extension SELinux
[    46.728] (II) SELinux: Disabled on system
[    46.728] (II) Initializing extension GLX
[    46.729] (II) AIGLX: Screen 0 is not DRI2 capable
[    46.748] (II) IGLX: Loaded and initialized swrast
[    46.748] (II) GLX: Initialized DRISWRAST GL provider for screen 0
[    46.748] (II) Initializing extension XFree86-VidModeExtension
[    46.749] (II) Initializing extension XFree86-DGA
[    46.750] (II) Initializing extension XFree86-DRI
[    46.750] (II) Initializing extension DRI2
[    46.927] (II) config/udev: Adding input device raspberrypi-ts (/dev/input/event0)
[    46.927] (**) raspberrypi-ts: Applying InputClass "libinput touchscreen catchall"
[    46.927] (**) raspberrypi-ts: Applying InputClass "Touch rotation"
[    46.927] (II) Using input driver 'libinput' for 'raspberrypi-ts'
[    46.927] (**) raspberrypi-ts: always reports core events
[    46.927] (**) Option "Device" "/dev/input/event0"
[    46.927] (**) Option "_source" "server/udev"
[    46.935] (II) event0  - raspberrypi-ts: is tagged by udev as: Touchscreen
[    46.937] (II) event0  - raspberrypi-ts: device is a touch device
[    46.937] (II) event0  - raspberrypi-ts: device removed
[    47.000] (**) Option "config_info" "udev:/sys/devices/platform/soc/soc:firmware/soc:firmware:touchscreen/input/input0/event0"
[    47.001] (**) Option "AccelerationScheme" "none"
[    47.001] (**) raspberrypi-ts: (accel) selected scheme none/0
[    47.001] (**) raspberrypi-ts: (accel) acceleration factor: 2.000
[    47.001] (**) raspberrypi-ts: (accel) acceleration threshold: 4
[    47.005] (II) event0  - raspberrypi-ts: is tagged by udev as: Touchscreen
[    47.007] (II) event0  - raspberrypi-ts: device is a touch device
[    47.009] (II) config/udev: Adding input device raspberrypi-ts (/dev/input/mouse0)
[    47.009] (II) No input driver specified, ignoring this device.
[    47.009] (II) This device may have been added with another device file.
[    47.030] (II) event0  - raspberrypi-ts: device removed
[    47.102] (II) UnloadModule: "libinput"
[    47.112] (==) FBDEV(0): DPMS enabled
[    47.112] (II) Initializing extension Generic Event Extension
[    47.113] (II) Initializing extension SHAPE
[    47.114] (II) Initializing extension MIT-SHM
[    47.115] (II) Initializing extension XInputExtension
[    47.116] (II) Initializing extension XTEST
[    47.117] (II) Initializing extension BIG-REQUESTS
[    47.118] (II) Initializing extension SYNC
[    47.118] (II) Initializing extension XKEYBOARD
[    47.119] (II) Initializing extension XC-MISC
[    47.120] (II) Initializing extension SECURITY
[    47.121] (II) Initializing extension XFIXES
[    47.122] (II) Initializing extension RENDER
[    47.123] (II) Initializing extension RANDR
[    47.124] (II) Initializing extension COMPOSITE
[    47.125] (II) Initializing extension DAMAGE
[    47.126] (II) Initializing extension MIT-SCREEN-SAVER
[    47.127] (II) Initializing extension DOUBLE-BUFFER
[    47.127] (II) Initializing extension RECORD
[    47.128] (II) Initializing extension DPMS
[    47.129] (II) Initializing extension Present
[    47.130] (II) Initializing extension DRI3
[    47.130] (II) Initializing extension X-Resource
[    47.131] (II) Initializing extension XVideo
[    47.132] (II) Initializing extension XVideo-MotionCompensation
[    47.132] (II) Initializing extension SELinux
[    47.132] (II) SELinux: Disabled on system
[    47.132] (II) Initializing extension GLX
[    47.133] (II) AIGLX: Screen 0 is not DRI2 capable
[    47.154] (II) IGLX: Loaded and initialized swrast
[    47.154] (II) GLX: Initialized DRISWRAST GL provider for screen 0
[    47.154] (II) Initializing extension XFree86-VidModeExtension
[    47.155] (II) Initializing extension XFree86-DGA
[    47.156] (II) Initializing extension XFree86-DRI
[    47.156] (II) Initializing extension DRI2
[    47.327] (II) config/udev: Adding input device raspberrypi-ts (/dev/input/event0)
[    47.327] (**) raspberrypi-ts: Applying InputClass "libinput touchscreen catchall"
[    47.327] (**) raspberrypi-ts: Applying InputClass "Touch rotation"
[    47.327] (II) Using input driver 'libinput' for 'raspberrypi-ts'
[    47.327] (**) raspberrypi-ts: always reports core events
[    47.327] (**) Option "Device" "/dev/input/event0"
[    47.327] (**) Option "_source" "server/udev"
[    47.335] (II) event0  - raspberrypi-ts: is tagged by udev as: Touchscreen
[    47.337] (II) event0  - raspberrypi-ts: device is a touch device
[    47.338] (II) event0  - raspberrypi-ts: device removed
[    47.371] (**) Option "config_info" "udev:/sys/devices/platform/soc/soc:firmware/soc:firmware:touchscreen/input/input0/event0"
[    47.371] (**) Option "AccelerationScheme" "none"
[    47.371] (**) raspberrypi-ts: (accel) selected scheme none/0
[    47.371] (**) raspberrypi-ts: (accel) acceleration factor: 2.000
[    47.371] (**) raspberrypi-ts: (accel) acceleration threshold: 4
[    47.376] (II) event0  - raspberrypi-ts: is tagged by udev as: Touchscreen
[    47.377] (II) event0  - raspberrypi-ts: device is a touch device
[    47.379] (II) config/udev: Adding input device raspberrypi-ts (/dev/input/mouse0)
[    47.379] (II) No input driver specified, ignoring this device.
[    47.379] (II) This device may have been added with another device file.

The pictures you had posted above show Volumio’s “Classic” theme in a mode for narrow displays like on smartphones. With the display in landscape mode and with a resolution of 800x480 I would expect the UI to be shown in “desktop” mode.

I wonder why that is not the case for you. Did you modify Volumio’s css files to achieve this “mobile” mode or do you have any other plugin installed, that might change UI related files?

Yes i am using The Classic theme under “user interface layout design” in “Appearance” in Volumio. Changing to contemporary doesn’t influence the blurry screen.
Everything did work perfectly after your last help. Then it started to go wrong a week ago. At some point I installed a GPIO button plugin and suspected that to somehow influence the screen. That’s why I re flashed the SD and tried with a second one… but still no solution.

It looked perfect here last week (screen not I focus with iPhone camera):


That’s why I suspected it to be software…

Do you have another (DSI) screen you could test with your current Volumio system?

I also suggest to test the 5" Osoyoo display with Rasperry Pi OS to rule out a hardware defect.

P.S.

Did you also check the yellowish connections from the PCB to the display?

From your picture above it seems that you use a pretty long DSI cable. If that should be correct try connecting the display with a shorter DSI cable, too.

Thanks🙂 I will try to rule out if it’s a hardware issue tomorrow.
Maybe I can borrow a second Rpi from a friend to see if the problem also happens there…

I am currently using a 45 centimeter DSI cable (4.3 inch waveshare) when I use a longer one I get errors, such as no touch or black screen or stripes through the screen.
so you know.

Thanks for the feedback :slight_smile:

First I tried to use a shorter FPC cable, but that didn’t work. I accidentally use a type B ribbon cable, but the Osoyoo uses type A. Could i have damaged the screen?
I also got hold of an old RPi 2 from a friend and tried that. Still the same issue with he blurry screen (still using the old longer ribbon cable).

There were no issues the two first week of using the screen with the long cable…

No clue :man_shrugging:

Did you try another OS (e.g. Raspberry Pi OS), too?

I had at go today with the Bullseye (desktop version) Raspberry Pi OS and the OS is running fine with a standard HDMI desktop screen connected. When i connect the DSI screen the Pi won’t boot into the Pi OS (ACT_LED flashing rapidly and continuously). The multicolor image and pi logo is displayed on both screens at start up, but won’t boot into the Pi OS. Same issue with only the DSI screen connected.

I first had a power issue using a smaller PSU and both screens connected, but found another 2,5 A with no problems…
At start up the screen still looks blurry and it looks like every 2nd vertical line of the Osoyoo DSI screen is missing.

So it is properly either a screen error or a ribbon cable error. I will first try to source a new ribbon cable, but not easy to find i a Type A config…
Do you think i could be another problem maybe?

Thanks again for your kind help :slight_smile:

Yes, looks like a hardware defect to me then. I’m afraid other than replacing cables or carefully and gently wiggling the cables from the display board to the display, there’s not much you could try.

1 Like

Hallo,

I’m new to the community and read the whole thread but haven’t found my issue.
Thanks to an instruction by gvolt I got my RasPi 4 working with an 3.5 Touchscreen by Joy-iT.

Is there an opportunity to adjust the size of the thumbnails like favorites and so on, since they are too large to be displayed on the 3.5.
Only the first 4 thumbnails are in sight.

The plugins scaling-option doesn’t affect the size of the thumbnails.

Or is it possible to hide some of them, so that I can display 4 thumbnails I use the most (favorites, internetradio an spotify)?

Thanks in advance!

This is nothing the Touch Display plugin deals with, but needs adjustment in the code for the UI IMHO.

That should be possible: Under “Settings” → “Sources” → “Sources Visibility” you can select what souces should be hidden. So you could reduce the visible sources as desired.

Thanks a lot for your quick answer.
That’s judt what I was looking for.

By then I only had a look at the setting for appearence, not sources.

Problem solved!

New to the forum and hope this is the correct thread.

I am experimenting with volumio (ver 3.301) and the official RPi 7" touch screen on a RPi 4. I am trying to monitor the status of the display backlight.

I am lead to believe that this would be possible by looking at the content of either the bl_light or brightness file in /sys/class/backlight/rpi_backlight/.

This plugin appears to use a path of /sys/devices/platform/rpi_backlight/backlight/rpi_backlight

Using Cat /sys/devices/platform/rpi_backlight/backlight/rpi_backlight/brightness (or bl_light) I get either 255 (Full) for brightness and 0 (on) for bl_light. Both paths show the same result.

The values do not appear to change regardless of backlight condition.

Using the echo command to the above paths/files, I am able to dim / turn off backlight overriding the plugins command to activate it, suggesting that this plugin uses a different method.

I have also tried using the rpi-backlight libary. This returns the same result e.g. no change regardless of backlight status.

Stuck. Any help would be greatly appreciated.

1 Like

The plugin uses “/sys/devices/platform/rpi_backlight/backlight/rpi_backlight/brightness” to set brigthness.

So

cat /sys/devices/platform/rpi_backlight/backlight/rpi_backlight/brightness

should reflect the current brightness value.

Did you try to set the display’s brightness using “Brightness Settings” on the Touch Display’s config page?

There you can set two brightness values and the time of day at wich each brightness should be applied.

The time of day has to be specified using the 24-hour clock system and the time format hh:mm. If the time of day for brightness 1 should be identical with the time of day at which brightness 2 should be set, brightness will not be changed but only the brightness 1 value will be applied.

When setting the time of day have in mind that the plugin uses Volumio’s system time which might be different from your local time.

Thankyou gvolt for your prompt reply and sorry, I have confused the issue.

I am trying to monitor the status of the display backlight i.e. know when the screensaver is active.

As I was unsure if the plugin used brightness or bl_power (again I mis typed above as bl_light which added more confusion to my question), I was checking both to see which, if any changed on screensaver activation.

I used your suggestion of using the Brightness settings and can indeed read the values set there as you state from /sys/devices/platform/rpi_backlight/backlight/rpi_backlight/brightness

When I use

cat /sys/devices/platform/rpi_backlight/backlight/rpi_backlight/bl_power

I always read 0, regardless of the screen being On or in a screensaver state of Off. Clearly not the right thing to use.

I have never looked at Java before but with a bit of digging and guess work, I now believe that the plugin does not use the bl_power or brightness at all for screensaver but rather dpms via xserver, is that correct?

It looks like I was off down the wrong rabbit hole, I think I need to look at how to read the state of of dpms set, I think using the xset command. Does that sound like a sensible course to sail? xdpyinfo maybe?

Any pointers most appreciated, I am looking to use Python for the final solution as I at least have a very basic grasp of that.

Thanks in advance.

Yes.

From the CLI:

xset -d :0 q | grep Monitor

1 Like

gvolt, your a legend, that saved be going down another rabbit hole. Python written and working perfectly.

1 Like