@zdenek Hello, what did you fix in Google Maps Traffic code?
Have same issue…
@zdenek Hello, what did you fix in Google Maps Traffic code?
Have same issue…
Today even install does not run :-(
Entpacken von nodejs (14.18.2-deb-1nodesource1) über (12.22.5~dfsg-2~11u1) …
dpkg: Fehler beim Bearbeiten des Archivs /var/cache/apt/archives/nodejs_14.18.2-deb-1nodesource1_armhf.deb (–unpack):
Versuch, »/usr/share/doc/nodejs/api/fs.html« zu überschreiben, welches auch in Paket nodejs-doc 12.22.5~dfsg-2~11u1 ist
dpkg-deb: Fehler: »einfügen«-Unterprozess wurde durch Signal (Datenübergabe unterbrochen (broken pipe)) getötet
Fehler traten auf beim Bearbeiten von:
/var/cache/apt/archives/nodejs_14.18.2-deb-1nodesource1_armhf.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
Edit using - PI OS - Buster now runs as before:
When I fresh start MM:
pi@raspberrypi:~/MagicMirror $ free -h
total used free shared buff/cache available
Mem: 1,8Gi 291Mi 982Mi 195Mi 598Mi 1,3Gi
Hello,
I’m using MM since years but since last year it is crashs more and more. Freeram, restart every 6h and similar already help but seems to get worse.
I use only
Google Maps
ImageslideShow
iFrame for Videostream (this seems to impact heavy)
HW itseld is not really used on CPU, but RAM is always running out.
Do you suggest a different OS or are 4GB of PI4 simple not enough for that? Since RAM is fairly empty after restart I assume only trashed full over time.
Also restart via PM2 does not really empty it…
bottom 110% was first try, but cutted away parts on left side :-( even if there was space… Margin 0, if not other issues will come - works fine as mirror is anyhow bigger…
After removing frame margin from main.css body, works fine!!
@hango - Big thanks for super fast reply!!
body {
margin: 0px;
position: absolute;
height: calc(100% - 0px);
width: calc(100% - 0px);
Screen appears THANKS, but whole display is having a offset of approx 10% moved to right… (left black bar, right gutted away…)
bottom: 110%; works for right side, but left side is cutted.
ist that something that is driven maybe by config or main.css?
Hello,
I tried your proposal in custom.css.
For -90deg as written works fine.
For 90deg again black screen.
(edit: 0deg , 180deg, -270deg result in black screen)
Hello,
when do I need to run npm install?
Only one or also when I download modules from git afterwards?
I recall that this was asked inside modules folder sometimes in past or only once in MagicMirror folder is enough?
BR
Hello,
based on that showcase here
[Showcase] (https://forum.magicmirror.builders/topic/9707/save-performance-when-rotating-screen-e-g-on-raspberry-pi/12)
I tried to rotate screen. So post it here again in Troubleshooting, as showcase is not right place for support I assume.
Iam struggeling on my PI3 to rotate by 90deg to right. Monitor has 1920x1080.
Doing it I see only black screen at any other position than -90deg!!
At -90deg screen is there only upside done…
As I need to change to 90deg or -270deg I got only black screen (also 180deg even) …
So I changed config.txt to:
display_hdmi_rotate=0
framebuffer_width=1920
framebuffer_height=1080
& custom.css to:
body {
margin: 0;
position: absolute;
transform: rotate(90deg);
transform-origin: top left;
width: 100vh;
height: 100vw;
object-fit: cover;
top: 100vh;
visibility: visible;
}
What is missing/wrong?
transform: rotate(90deg);
transform-origin: top right;
works at least see have screen, but only half screen is used, so no option…