A TV switched on after the player boots gets a picture on Raspberry Pi 5 and x86

If your TV switches on after the player has started, for example on a power timer, the screen could stay on "No Signal" until someone rebooted the player. From Anthias 2026.08.0 the picture comes up on its own after a short wait. It affects a Raspberry Pi 5, an x86 PC or a board running the generic arm64 image, and there's nothing to set.

On those boards, a player that booted while its TV was off stayed on "No Signal" after the TV came on. The only way out was to restart the viewer container or reboot the player. Anthias 2026.07.2 added a check that restarts the viewer when a display turns up after boot, but it only acted once the display had reported its resolutions to the player. A TV that was plugged in but off at boot never got that far, so the check never fired. From Anthias 2026.08.0 it acts on any connected display that has no picture: after 60 seconds, the viewer container restarts so the display is detected again. In the project's testing on a Pi 5, the first restart brought the picture back, about 70 seconds after the display was connected.

The restarts are capped at 3 per boot. A display that never answers, such as one on a faulty cable, gets 3 attempts. Then the viewer logs that it gave up and stops restarting, so a failed screen can't keep the viewer cycling all night. The count starts over when the display comes up, when it's unplugged, or when the player reboots.

The Raspberry Pi 2, 3 and 4 images use a different display path, and this change doesn't affect them.