It’s not the default because if there are any problems preventing the system from booting up you will never see them and have no idea what is going wrong.
The default is “auto” mode, where no messages will be displayed if no errors occur, but messages will be switched on if there is an error during startup such as a service failing to start or a disk failing to mount.
Unfortunately auto mode will also switch on messages if services take “too long” to start. Unfortunately “too long” is not measured in seconds but seems to be based upon whether a slow service is delaying other services, and we have a couple of services in OSMC like http-time (which sets the system time from an http request) and the bluetooth firmware uploader on the Vero which take about 10-11 seconds to complete under normal operation and this sometimes provokes systemd to switch into displaying startup messages.
There doesn’t seem to be any easy way to turn off message display for slow services but still leave it enabled for failed services but we are continuing to investigate this - just like you we would like the boot screen to be clean unless there are actual errors that matter.
Thanks for the explanation DBMandrake. I’m assuming that Bluetooth firmware uploader is in Vero builds only?? Maybe the reason I see them on my Pi2 is because of the extra Samba server and FTP servers I have installed.
I’m sure you guys will figure out the best way to handle it, like always. No worries, just something that (me thinks) cries Beta/debug. Reminds me of past jailbreaks on my phone running code injection, lolz.