I often control Max2play/Jivelite with SqueezePlay (on Windows) or Squeeze Commander (on a mobile phone). I often play Internet radio. I use screensaver which makes screen black and turns off illumination after 10s of inactivity. The problem is that when I press the pause („||“) on Squeeze Commander or SqueezePlay, then LCD illumination activates on max2play and screen displays black screen (with illumination). Furthermore it stays illuminated forever (until I do some tricks). It is inconvenient as power consumption of raspberry multiplies and illumination system wears out. Please help or correct software.
In above scenario to turn off the LCD illumination I have to tap on LCD/touchscreen, which brings on the displayed context and after 10s screen illumination is automatically turned off (which is good).

I don’t know where to find Audioplayer debug log (in GUI or in shell, and where is it?)
I use squeezelite+jivelite on max2play and I control it using Squeezeplay/Windows or Squeeze Commander/Android.

Below I include „Debug Informationen“ from Audioplayer card in my max2play web interface.

Note that I have just written a working workaround as a script in bash (autostarted in /etc/rc5.d – /etc/init.d) which every 5 seconds checks if the screen is all blank/black. If the screen is all blank/black, then the script turns off LCD illumination. If not, it turns illumination on. I use xwd to dump the current screenshot to file. Then my script compares current dump file with black screen file dumped earlier. I use diff to compare files.

So it is no longer an urgent issue for me, however I would appreciate if you provide a more subtle solution.

Below I include „Debug Informationen“ from Audioplayer card in my max2play web interface.

We checked the situation with a fresh setup again and a simple update in Jivelite (pre-compiled by Max2Play) solves the issue. You also have to make sure that the Screensaver settings are set to „blank screen“ when off and when paused. This should get the trick done.

Nonetheless, we appreciate the DIY solution and will continue to link to it if other users experience similar issues. Thanks for your detailed contributions and for pointing out this problem.