Video keeps its sound after a reboot, and other fixes

Large backups restore through the API on boards with 1 GB of RAM, uploads to a full disk say so, and a balena device carries out a reboot even while its supervisor restarts.

July 8, 2026

Fixes

• On the images with the Qt 6 viewer (the 64-bit Raspberry Pi 3, Pi 4, Pi 5, x86 and arm64), video could play without sound after a reboot or a restart of the viewer container. It has sound after a reboot now.
• Restoring a backup through /api/v1/recover or /api/v2/recover no longer loads the whole backup into memory, so a large backup restores on a board with 1 GB of RAM, such as a Raspberry Pi 3, instead of running it out of memory. The restore in Settings > Backup & restore already worked this way.
• Uploading to a device whose disk is full now says the disk is full and suggests deleting assets you no longer use. Through the API, file_asset answers with a 507 response. Before, the upload failed with an error that didn't say why.
• Chunked uploads to file_asset that arrive out of order are put together correctly. The Content-Range header has to be in the form bytes <start>-<end>/<total>, with a known total. A header that isn't gets a 400 response.
• Reboot and shutdown on a balena device keep trying for up to 2 minutes while the balena supervisor is down or restarting, as it is right after an update. Before, they gave up after a few seconds and the device didn't reboot or shut down.
• The "Update available" notice on the System Info page, and up_to_date in the API's info endpoint, compare your version with the newest Anthias release. When the newest release on GitHub was something else, such as a WebView toolchain release, the check stopped updating.
• The installer no longer stops to ask for a sudo password when your user already has passwordless sudo, as the first user on Raspberry Pi OS does. Unattended installs used to hang at Ansible's BECOME password: prompt.
• On a device with no CEC adapter, such as an x86 PC, the "Display Power (CEC)" card on the System Info page shows "Not available" instead of "CEC error". So does display_power in the v2 info endpoint.

Improvements

• The 64-bit Raspberry Pi 3 image (pi3-64) ships the Raspberry Pi build of ffmpeg, like the Pi 4, Pi 5 and arm64 images, so H.264 video is decoded by the Pi 3's hardware decoder instead of its CPU. Video on that image could still show a black screen until Anthias 2026.07.2.
• The web view on the 32-bit Raspberry Pi 2 and Pi 3 images is built on Qt 5.15.19, up from 5.15.14.
• On x86, the "Device model" card on the System Info page shows the board on one line and the CPU on the next, and drops suffixes such as "Corporation" from the maker's name.
• The footer of the web interface has "Star on GitHub" and "Review on G2" links. After you add an asset to a device with at least 3 enabled assets of your own, a card asks whether you're enjoying Anthias, with the same 2 links. "Maybe later" hides it for 90 days, following either link hides it for good, and the choice is saved on the player, so it holds in every browser.
• The guide to moving assets to Screenly walks through the Migrate to Screenly page in Settings, with no SSH or script.
• The Anthias website and install docs point to Raspberry Pi Imager as the quickest way to install on any Raspberry Pi, the Pi 5 included, under Other specific-purpose OS > Digital signage and kiosks > Anthias. The get-started page lists the 64-bit Raspberry Pi 3 as supported instead of in maintenance.

For contributors

• bun run test runs TypeScript unit tests with bun test, starting with how the Apps tab builds an app's address and name.
• bin/rebuild_qt5_toolchain.sh builds Qt 5.15.19, keeps the QtWebEngine build to MAKE_CORES parallel jobs so it doesn't run the build machine out of memory, and reads CI's public build cache.
• Error reports to Sentry leave out expected events: an upload that isn't a valid backup, a failed YouTube or video download, a device with no working DNS, a jump to an asset that was deleted or is still processing, and the background worker briefly losing Redis.