Thanks @volpone - great comments!
Completely understandable. I use my Raspberry Pi touch screen as a browser client only since I have the Node.js instance running on the same Virtual Machine as my Roon Server. In addition to the sound quality concerns, the fast ethernet connection tends to get overrun with Hi-Res files, too. The gigabit Ethernet connection on the Odroid C2 or the Asus Tinkerboard is one of many areas that these boards beat out the Raspberry Pi.
But since a lot of folks do want to use DietPi as a Roon endpoint, I wanted to make sure they were covered too.
I have not yet implemented this because it was not really a feature that I wanted. The trend over the last few years on desktop systems has been to allow the screen to go to power save mode.
Doing some searches on how to do it and it seems like disabling power save mode in a web browser is possibleā¦ Let me do some more research and if I can implement it, I will add it as an optional configuration item in settings.
In the mean time, you can make the timeout longer than a minute if you wish, though. In the User Configuration section, the line that says xset dpms 60 60 60 & is what sets the 1 minute time out. The values are in seconds. You can set it to never turn off the display by using xset -dpms & instead.
Theoretically this could be done with something like XScreensaver. But once again, the trend over the last few years on desktop systems has been phasing out screen savers and instead letting the monitor go into power save mode. As a result, many screen savers are no longer actively developed.
Perhaps another way would be to turn off the power saving mode entirely and put a clock in the āNot Playingā section of the app. But I would still need to preserve a way to switch zones and a clock may not look right on a full desktop or in portrait mode.
This one is really in the weeds. And as you may have noticed, there is not an option for this in the āDisplay Optionsā program. Since the guide I wrote was intended to be as entry level as possible, I intentionally left out the section on screen brightness. After reading the following, do you think I should add it?
In a nutshell, setting the screen brightness on the Raspberry Pi with a Raspberry Pi touchscreen is possible via a pseudo file under the /sys pseudo file system. To see the current brightness setting, run:
cat /sys/class/backlight/rpi_backlight/brightness
where ā0ā is off (0%) and ā255ā is as bright as possible (100%).
Other displays use other locations so these instructions will not work on different displays.
You can set the brightness to a different value by switching to the root user and using a command like:
echo 128 > /sys/class/backlight/rpi_backlight/brightness
This will set the screen brightness to 50%.
But that may or may not stay set after a reboot.
If it does not stay set, you can create a file under /etc/tmpfiles.d to set it for you at boot time. Once you determine which brightness you want (128 in this example):
nano /etc/tmpfiles.d/rpi_backlight.conf
With the contents:
w /sys/class/backlight/rpi_backlight/brightness - - - - 128
Then save and exit.
The recommended way is to use a Chrome extension like this.
Unfortunately, this is very inconsistent right now because the app uses iFrames. One of the road map items for a future release is to stop using iFrames so that the linked extension works correctly.
