Don‘t forget to go to the target module directory before installing!

cd MMM-Tronity

Ralf

@robertybob yes, screen rotation is still possible via CLI/terminal…

edit “/usr/share/dispsetup.sh”
eg:

sudo nano /usr/share/dispsetup.sh

there you will find an if clause at the beginning:

if ! raspi-config nonint is_pi || raspi-config nonint is_kms ; then
if xrandr --output HDMI-1 --primary --mode 2560x1440 --rate 59.951 --pos 0x0 --rotate left --dryrun>
xrandr --output HDMI-1 --primary --mode 2560x1440 --rate 59.951 --pos 0x0 --rotate left

the word after “rotate” defines the rotation :-)

NO rotation = “normal”, rest is obvious.
You must change this in both occurances.

In same statement you define the resolution for the screen, as well - after “mode”(given example 2560x1440)

HTH

Regards,
Ralf

@wuermchen which fork are you using?
There was a newer implementation, I guess last year.
This version resolved the sticky caller-window (at least for me).

Good luck,
Regards,
Ralf

@robertybob said in Can´t rotate my display:

Mine looks a little different :(

OK, that’s bad…
(It’s a Pi5, right?).

The complete content of my dispsetup.sh is as follows:

#!/bin/sh
if ! raspi-config nonint is_pi || raspi-config nonint is_kms ; then
if xrandr --output HDMI-1 --primary --mode 2560x1440 --rate 59.951 --pos 0x0 --rotate left --dryrun>
xrandr --output HDMI-1 --primary --mode 2560x1440 --rate 59.951 --pos 0x0 --rotate left
fi
fi
if [ -e /usr/share/tssetup.sh ] ; then
. /usr/share/tssetup.sh
fi
if [ -e /usr/share/ovscsetup.sh ] ; then
. /usr/share/ovscsetup.sh
fi
exit 0

If I interpret your line correctly, you are using the Wayland-Window-Manager?
(wlandr => wayland … ???).
My box is a Pi4B, no wayland.
I’ve seen elsewhere that the Pi5 can be forced to use X11 again - than the above should work directly.
Otherwise you may give it a try to put your code into the dispsetup.sh?

Here I found the description of your commandlines above. Unfortunately there is no description how to get this pesistent…

In Addition I just found a hint in Raspberry-Forum
There a guy stated:

sudo nano .config/wayfire.ini

-> scrolled down and changed the output section as below:

[output:HDMI-A-1]
mode = 1920X1080@60000
position = 0,0
transform = 90

May this is the right way with wayland…

Regards,
Ralf

@robertybob said in Can´t rotate my display:

Raspberry Pi 3 :)

May this in combination with bookworm?
Sam acknowledged my assumption a posting above…

• back to X11 …

Regards,
Ralf

@sdetweil :-)
OK good move…
But the startup-command is generated by your install-script, so this is the result of the “auto-start”…
In the meantime I’ve figured out that may X11 is - in priciple - may the better choice for me because I might remember that MMM-Pir ( :-) ) had issues with wayland in context of screen-off …

@rkorell said in MMM-Universal-Pir - Desparately seeking right command:

“DISPLAY=:0.0 xrandr --output HDMI-1 --off” / “DISPLAY=:0.0 xrandr --output HDMI-1 --primary --mode 2560x1440 --rate 59.951 --pos 0x0 --rotate left”

these are the right commands and are working now!

(If one was not too blonde to switch the commands …)
My fault - I’ve entered the on comand to the off parameter …
Sorry!

Regards,
Ralf

@sdetweil As I wrote initially “npm run start:wayland” doesn’t work …
(despite wayland configured).
And the “stored” auto-start option npm run start:x11 DOES work - for whatever reason.

VNC was really sluggish on this, performance a nightmare so - see above marked as “solution” I switched back to x11 and all is working fine.

In the meantime I’ve also managed to get MMM-Pir to work by idenitfying and correcting two errors in Bugsounet’s code …

Warm regards,
Ralf

@mischag
This definitely sounds like a system not a MagicMirror problem.
You didn’t provide system information, so it’s hard to say anything.
What Pi? What OS? What screen?

I recently upgraded a (really old) Pi 2B and the (until upgrade) smoothly running touch didn’t work anymore - clearly caused by OS-upgrade.
The newer version introduced a completely different (touch) screen handling (without any warning, hint or message regarding this fact).
The axes and x-y positionings were mirrored. Your description sounds like that…

Regards,
Ralf

@sdetweil said in How to Swipe between pages:

sadly MagicMirror forum search stinks

:-)
what I’m using regularly and works pretty well is external search via Google with limitation to site forum.mgicmirror.builders …
Astonishing…

Regards,
Ralf