Installed the pi 4 today.

Was getting up to 4 days on the 02W without it crashing, so will need to give it a week to know for sure.

Thanks for the tips, will take a look tomorrow to see how would do it via CSS.

Why would you recommend doing it via CSS? Turning the headers on and off as a config option feel more intuitive to me compared to using CSS to surpress them.

Although moving to 64 bit made it more stable, still found it was going blank after a few days requiring the mm container restarted.

Think the Zero 2W was too under powered for what I was trying to do. So have upgraded to a Pi 4.

I have two instances of the module, and I only want to hide the header on one instance. If I use CSS, wouldn’t it hide it for both?

I use the MMM-CalendarExt3 module, and decided for my configuration wanted to display it without the header (in week view).

Made the following modifications to make it into an option to turn the header on and off.

Sharing it here as haven’t looking into how to contribute via git…

--- MMM-CalendarExt3.js.org	2025-08-09 22:19:40.792525741 +1200
+++ MMM-CalendarExt3.js	2025-08-09 22:22:25.620897641 +1200
@@ -82,7 +82,7 @@
     skipDuplicated: true,
     monthIndex: 0,
     referenceDate: null,
-
+    showHeader: true, 
     customHeader: false // true or function
   },
 
@@ -755,7 +755,7 @@
       config: options,
       range: [boc, eoc]
     })
-    makeDayHeaderDom(dom, options, { boc, eoc })
+    if (options.showHeader) makeDayHeaderDom(dom, options, { boc, eoc })
     makeWeekGridDom(dom, options, targetEvents, { boc, eoc })
     if (options.displayLegend) displayLegend(dom, targetEvents, options)
     if (options.customHeader) customHeaderDom(dom, options, { boc, eoc })

Moving to 64bit looks like might have helped. Up for 18 hours since rebuilding so far with my full calendar configuration.

Observation - took about 30 min to boot through displaying the calendar. Load average getting up to 20.0+ during boot, assume swapping a lot via the slow SD card interface. So although looks more stable, much slower performance.

@sdetweil said in MM Screen goes blank 5-20min after starting (was stable on 2.31) - Pi Zero 2W running MagicMirrorOS:

sdetweil
3 minutes ago

@karsten13 he should examine use and adjust as required…

As @karsten13 noted, defaults to 1024 on a 2W (have done first boot post imaging). Will give it a go at 2048, likely a bit oversized.

@sdetweil said in MM Screen goes blank 5-20min after starting (was stable on 2.31) - Pi Zero 2W running MagicMirrorOS:

Away
sdetweil
3 minutes ago

@scottwalsh the 64bit version takes about 500m more memory than the 32 bit version…

Thanks for the tip, what’d you recommend as a min swap size? Will just try it off the SD card to start (as don’t have a USD at hand).

@karsten13 said in MM Screen goes blank 5-20min after starting (was stable on 2.31) - Pi Zero 2W running MagicMirrorOS:

You did not write which OS you are using, 32-bit or 64-bit. The 32-bit is more resource-saving

Hadn’t checked, until now. Have been using the 32-bit version.
Will reimage with the 64-bit version and see if it is more stable.

Did note the following error from the labwc container about four hours after starting it in the above example errors, so suspecting is part of it.

So I guess how can I troubleshoot/avoid this event.
And/or have the mm container reconnect after this occurs.

wlr-randr errors "failed to connect to display" so killing container.