Read the statement by Michael Teeuw here.
MMM-EasyBack no autostart Video
-
yep, like if I’m hitting ctrl + alt + delete correct?
instead it’s ctrl shift i
-
@Darkmx-6 correct
-
Yeah I can’t get it to come up.
I’m not sure what else I can do.
-
@Darkmx-6 if u can change the startup, npm start dev opens the developers window
-
I am trying a clean install now
-
is this the start file you are talking about?
pi@raspberrypi:~ $ ls chromium_start.sh mmstart.sh package-lock.json MagicMirror node-v10.16.0-linux-armv6l pi@raspberrypi:~ $
pi@raspberrypi:~ $ sudo nano mmstart.sh GNU nano 3.2 mmstart.sh #!/bin/bash cd ~/MagicMirror node serveronly & sleep 30 xinit /home/pi/chromium_start.sh npm start dev
Is that where it goes?
Man doing this project makes me feel so dumb I need to learn more, any suggestions?
-
Oh an just to update with the clean install I had the same issue.
-
I am also now using a Raspberry Pi 3 B+
-
Well I ended up going to a static picture because I can’t think of what else to do.
-
@Darkmx-6 i don’t know where mmstart.sh came from… it is not part of the base MagicMirror solution.
the MagicMirror start script is ~/MagicMirror/installers/mm.sh
it does not run serveronly… it assumes you are running the mirror user experience ON the same machine.
i don’t know if EasyBack works on the remote client of serveronly… THAT browser would have to enable autoplay… our fix was for the electron browser running ON the same machine
edit:
ok, i see what you are doing… using chromium for the browser for some reason…so u have to disable the autoplay blocker there , from
https://developers.google.com/web/updates/2017/09/autoplay-policy-changesYou can decide to disable entirely the autoplay policy by setting the Chrome flag "Autoplay Policy" to "No user gesture is required" at chrome://flags/#autoplay-policy. This allows you to test your website as if user were strongly engaged with your site and playback autoplay would be always allowed.