[PROBLEM] Autoplay after start

[fiorello]

Thanks for clarification!

Situation here is as follows (moOde 6.7.1 2020-07-22, Pi-Zero W 512MB v1.1, Sandisk microSDHC, 16GB, U1, UHS-I):

Code:

pi@moode:~ $ systemd-analyze blame
         10.638s dhcpcd.service
         10.577s dev-mmcblk0p2.device
          4.295s rc-local.service
          3.463s systemd-timesyncd.service
          3.314s nmbd.service
          3.264s keyboard-setup.service
          3.174s smbd.service
          3.079s networking.service
          2.936s systemd-udev-trigger.service
          2.868s nginx.service
          2.529s raspi-config.service
          2.528s winbind.service
          2.515s systemd-logind.service
          2.495s php7.3-fpm.service
          1.907s rng-tools.service
          1.698s sysstat.service
          1.698s systemd-journald.service
          1.677s systemd-rfkill.service
          1.654s avahi-daemon.service
          1.637s systemd-fsck@dev-disk-by\x2dpartuuid-2fed7fee\x2d01.service
          1.566s ssh.service
          1.411s alsa-restore.service
          1.283s systemd-update-utmp.service
          1.169s wpa_supplicant.service
          1.132s systemd-fsck-root.service
          1.065s rsyslog.service
           897ms user@1000.service
           880ms systemd-remount-fs.service
           868ms systemd-tmpfiles-setup.service
           856ms run-rpc_pipefs.mount
           805ms dev-mqueue.mount
           794ms kmod-static-nodes.service
           704ms systemd-sysctl.service
           695ms systemd-modules-load.service
           652ms systemd-user-sessions.service
           637ms sys-kernel-debug.mount
           609ms systemd-journal-flush.service
           608ms systemd-sysusers.service
           522ms rpi-eeprom-update.service
           499ms systemd-random-seed.service
           449ms fake-hwclock.service
           441ms rpcbind.service
           402ms udisks.service
           393ms systemd-udevd.service
           311ms systemd-update-utmp-runlevel.service
           258ms nfs-config.service
           218ms console-setup.service
           182ms systemd-tmpfiles-setup-dev.service
           161ms user-runtime-dir@1000.service
           161ms boot.mount
           132ms sys-kernel-config.mount
            96ms ifupdown-pre.service
pi@moode:~ $ systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.
                                                                                                                                                                               
multi-user.target @41.725s
+-smbd.service @38.528s +3.174s
  +-winbind.service @35.918s +2.528s
    +-nmbd.service @32.533s +3.314s
      +-network-online.target @32.228s
        +-network.target @32.181s
          +-dhcpcd.service @21.521s +10.638s
            +-basic.target @21.084s
              +-sockets.target @21.074s
                +-avahi-daemon.socket @21.048s
                  +-sysinit.target @20.985s
                    +-systemd-timesyncd.service @17.495s +3.463s
                      +-systemd-tmpfiles-setup.service @16.525s +868ms
                        +-local-fs.target @16.485s
                          +-boot.mount @16.289s +161ms
                            +-systemd-fsck@dev-disk-by\x2dpartuuid-2fed7fee\x2d01.service @14.605s +1.637s
                              +-dev-disk-by\x2dpartuuid-2fed7fee\x2d01.device @12.610s
pi@moode:~ 

So, what is the conclusion? Pi-Zero W not suited as moOde player?