My MagicMirror screen keeps turning off

[evroom]

@evroom

Talking to myself :-)

The settings for Buster are not working.
My display goes to sleep after 10 minutes.
Perhaps because it isn’t a HDMI connected monitor.

I found 2 interesting files though:

pi@raspberrypi:~ $ ls -als /home/pi/.xsession-errors
4 -rw------- 1 pi pi 2426 Aug  1 12:30 /home/pi/.xsession-errors
pi@raspberrypi:~ $ ls -als /home/pi/.cache/lxsession/LXDE-pi/run.log
20 -rw------- 1 pi pi 17988 Aug  1 12:30 /home/pi/.cache/lxsession/LXDE-pi/run.log

Also see that this file is being used, so that seems right:

/etc/xdg/lxsession/LXDE-pi/autostart

[evroom]

@evroom

This works (running for 100 minutes at the moment of posting):

$ sudo nano /etc/xdg/lxsession/LXDE-pi/autostart
@touch /home/pi/.started_etc_xdg_lxsession_LXDE-pi_autostart
@point-rpi
@xset -dpms
@xset s off
@xset s noblank

Note: the autostart file does not like comments.

Reboot:

$ sudo reboot

After reboot is finished, check:

$ ls -als /home/pi/.started_etc_xdg_lxsession_LXDE-pi_autostart

That will tell if the autostart file was used (timestamp should match reboot time).
Then check for set errors:

$ grep xset /home/pi/.cache/lxsession/LXDE-pi/run.log

It should say 3 times Launching xset, with 3 times exit 0 (for every set entry in the autostart file).

Works for Raspberry Pi 7" Touchscreen Display.

$ lsb_release -a
No LSB modules are available.
Distributor ID:	Raspbian
Description:	Raspbian GNU/Linux 10 (buster)
Release:	10
Codename:	buster

[EhsanMomeni81]

@evroom said in My MagicMirror screen keeps turning off:

sleep after 10 minutes.
Perhaps because it isn’t a HDMI connected monitor.
I found 2 interesting files though:

Wow, that’s a lot to take in. Thank you so much for your help, I’m going to try this during the week.

[EhsanMomeni81]

@evroom said in My MagicMirror screen keeps turning off:

@evroom

This works (running for 100 minutes at the moment of posting):

$ sudo nano /etc/xdg/lxsession/LXDE-pi/autostart
@touch /home/pi/.started_etc_xdg_lxsession_LXDE-pi_autostart
@point-rpi
@xset -dpms
@xset s off
@xset s noblank

I tried the code above, and it works on stretch, I screen doesn’t turn off. But my cronjob acts funny. Last night when I look at it after it was supposed to be turned off, the backlight was on but everything else was dark. Don’t really know whats going on, but I’ll take a new look tonight.

[EhsanMomeni81]

@evroom I’m stuck :(
I tried the code above, and it works, the screen doesn’t turn off, but now I can’t see the desktop, it’s black when I minimize the MM-window, and I can’t connect to my MM via VNC which I could before and that’s how I changed in the first place.

[evroom]

@EhsanMomeni81

Is here something useful ?
https://forum.magicmirror.builders/topic/1801/get-back-to-desktop
https://forum.magicmirror.builders/topic/5619/how-to-find-and-use-key-commands-in-mm-for-absolute-beginners

I personally only use VNC to “look” at the screen remotely and never use the Pi for anything else then displaying MM.
Not interested in the desktop.
I always login to the Pi using a ssh client, like for example PuTTY, or on my Mac the iTerm2.

If you use Windows, then I would recommend PuTTY.
It is small and simple.

[EhsanMomeni81]

@evroom
Thanks ever so much. I googled and found something that worked. Now everything is running as it should. Still have problems with VNC, but I installed TeamViewer, but I’m going to give ssh a shot soon. Thank you again

[TvE]

So I have also been searching a lot for an answer to this question and been wondering why it have been so difficult to find a CLI based solution to this task.

I am using the “Raspberry Pi Imager” tool (on Window$) to prepare a USB stick (or SD card) and hereafter configure everything via SSH.

I know I could just use RDP or VNC to access and thus make this change via a GUI. But that’s to annoying, hence my need for a CLI based solution

Finally I found it in this thread (thank you @evroom !)

So this is just to help others with the same search that this [1] still works on the current latest RPI OS bullseye:

pi@magicmirror:~ $ lsb_release -a
No LSB modules are available.
Distributor ID: Raspbian
Description:    Raspbian GNU/Linux 11 (bullseye)
Release:        11
Codename:       bullseye

Without this [1] change the screen goes black after 600s (10m)
Which can also be identified by the “timeout value” returned by this command.

pi@magicmirror:~ $ DISPLAY=:0 xset q
...
Screen Saver:
  prefer blanking:  yes    allow exposures:  yes
  timeout:  600    cycle:  600
...

After fixing it the value gets set to ‘0’
Right now I still see the screen after 16m (and counting…)

How to
The config change can be applied in many ways (vi, nano etc) but I prefer this method (as it can be copy-pasted or be made part of a config-script).

[1] I “just” add the three required lines to the config file:

printf "@xset -dpms\n@xset s off\n@xset s noblank" | sudo tee -a /etc/xdg/lxsession/LXDE-pi/autostart

PS.: Before I found this I also tried these solutions (which all failed to solve the problem

A. in /etc/lightdm/lightdm.conf:
xserver-command=X -s 0 dpms

B. Enable VNC as a workaround for mutter

I found (but did not try)

C. install xscreensaver and configure it to not kick in

HTH (my first post here :-)

[sdetweil]

@tve I wonder if my screensaver-off script would have done it.

see
https://github.com/sdetweil/MagicMirror_scripts

down at the bottom of the page

this is part of the install too, but the script is added in case u change your mind or need help. it checks 4 or 5 ways screensaver is done

[TvE]

@sdetweil It most likely would!

My one -file-only-edit solution have the added bonus that I know exactly what needed to be changed thus not relying on a 100+ line script.

I see that you are so kind to log what the script is doing, so you don’t leave the user in the dark (pun intended :-) ) I like that design!

I should have read your script earlier though (I read through the looong ticket regarding making the installer scripts external to MM2 and remember many of your posts!)

Actually, while browsing the MM repo I also stumbled across the exact same solution
https://github.com/MichMich/MagicMirror/wiki/Configuring-the-Raspberry-Pi#disabling-the-screensaver

Why either of those were never returned to my by google-foo I can only wonder about