Anthias 2026.07.3 | Screenly

Anthias 2026.07.3: Screen rotation turns content the same way on every board

Thu, 16 Jul 2026 00:00:00 +0000

From Anthias 2026.07.3, each "Screen rotation" choice turns the picture the same way on every board. "Portrait (90°)" turns it a quarter turn clockwise and "Portrait, inverted (270°)" a quarter turn anticlockwise, and images, web pages, video and streams all turn together.

Before, the direction depended on the board. A 32-bit Raspberry Pi 2 or 3 turned video clockwise for "Portrait (90°)", while a Raspberry Pi 3 running the 64-bit image, a Pi 4, a Pi 5, a PC and generic arm64 boards turned the picture anticlockwise for the same setting.

If you have a portrait screen on a Raspberry Pi 3 running the 64-bit image, a Pi 4, a Pi 5, a PC or a generic arm64 board such as the Rock Pi 4: after upgrading to Anthias 2026.07.3, the picture shows upside down. In the web interface, open Settings and, under "Display & playback", switch "Screen rotation" from "Portrait (90°)" to "Portrait, inverted (270°)", or the other way round. If you set it through the API, swap screen_rotation between 90 and 270. "Landscape (0°)" and "Landscape, inverted (180°)" look the same as before, and a 32-bit Raspberry Pi 2 or 3 needs no change.

Images and web pages on a 32-bit Raspberry Pi 2 or 3

On a Raspberry Pi 2 or 3 running a 32-bit image, only video followed "Screen rotation", as the 2026.05.1 entry that introduced the setting described. Images and web pages stayed upright whatever you picked. From Anthias 2026.07.3 they turn at 90°, 180° and 270°, in the same direction as video.

Rotated video on these boards still played at only a few frames per second in this release. Anthias 2026.07.4 brought 180° up to full speed.

Video on a 64-bit Raspberry Pi 3

On a Raspberry Pi 3 running the 64-bit image (pi3-64), video ignored "Screen rotation" and stayed upright while images and web pages turned. That started when Anthias 2026.07.2 brought hardware video to this board. Video now turns with everything else.

At 180°, video still plays at full frame rate. This board's video hardware can't turn a picture by a quarter, so at 90° and 270° video plays through a software path instead: about 9 to 10 frames per second for 1080p in the project's testing. For portrait video, a Raspberry Pi 4 or 5 is the better board.

Anthias 2026.07.3: Anthias container images come with signed build provenance

Thu, 16 Jul 2026 00:00:00 +0000

This is for people who check where software comes from before they run it, such as a security team. Nothing changes on your screens and you don't need to do anything, but you can now confirm with 1 command that the software on a player was built by the Anthias project itself.

An Anthias player runs 3 containers, server, viewer and redis, pulled from GitHub Container Registry, with a copy of each image on Docker Hub. From Anthias 2026.07.3, every one of those images, for every board, is published with a signed build provenance attestation. It records the repository, workflow and commit that built the image, so you can check that an image came from the Anthias build before you run it.

Check an image with the GitHub CLI:

gh attestation verify \
 oci://ghcr.io/screenly/anthias-server:<short-hash>-<board> \
 --repo Screenly/Anthias

<board> is one of pi2, pi3, pi3-64, pi4-64, pi5, x86 or arm64. A release's short hash is in the docker-tag file attached to its GitHub release: for 2026.07.3 it's a782add. Put anthias-viewer or anthias-redis in place of anthias-server to check the other 2.

The latest-<board> tags point at the same images and pass the same check. So does the Docker Hub copy, oci://docker.io/screenly/anthias-server:<short-hash>-<board>, because the attestation belongs to the image itself rather than to one registry.

Images built for earlier releases have no attestation. The disk images on the release page aren't covered either: check those against the .sha256 file published next to each one.

Anthias 2026.07.3: The Anthias boot splash shows on a Raspberry Pi 2

Thu, 16 Jul 2026 00:00:00 +0000

On a Raspberry Pi 2 installed with the install script, the screen showed plain text on black while the board booted, not the Anthias splash. The boot splash only waited 8 seconds for a display to appear, and on the Pi 2 the project tested, the display came up about 14 seconds into boot. By then the splash had settled on text. It now waits up to 30 seconds, so the Anthias splash appears.

The fix arrives when you upgrade with bin/run_upgrade.sh, which runs the installer again, and takes effect at the next reboot. Players installed from a disk image or Raspberry Pi Imager run balenaOS, which the installer doesn't set up, so this change doesn't touch them.

For contributors

The wait is DeviceTimeout=30 in the Plymouth config the splashscreen Ansible role installs. Plymouth reads its theme and settings from the copy in the initramfs, so the role now rebuilds the initramfs once, after every file is in place, instead of partway through.

Anthias 2026.07.3: App settings use your browser's date and time pickers, and other improvements

Thu, 16 Jul 2026 00:00:00 +0000

Fixes

Anthias 2026.07.3 reports itself as 2026.07.3 in System Info. The previous release reported itself as 2026.07.1.

Improvements

An app setting that holds a date, a time or both, like the Timer app's "Target date & time", opens your browser's date and time picker instead of a text box you had to type an ISO 8601 value into. It's there when you add an app and when you edit one.
The install guide and the website's get-started page recommend Raspberry Pi Imager for most people. The one-line install script is marked as advanced, and the guide shows how to download it and read it before you run it.
The hardware table on the website's get-started page lists the Raspberry Pi 3 Model A+ as not recommended: its 512 MB of RAM is too little for Anthias. Pick a board with at least 1 GB, a Pi 3 Model B or newer.

For contributors

The SBOM workflow adds an SBOM for the website's dependencies, alongside the JavaScript and Python ones, and runs for release tags only. Each SBOM is still uploaded to sbomify and attested, and is now filed under its Anthias release there.
Dependabot uses the uv ecosystem for Python, so uv.lock is updated together with pyproject.toml, and it no longer proposes Django major upgrades in the grouped Python update.
Dependencies updated, including yt-dlp and Ansible.