Steam Frame beta
Steam Frame is a native 2D streaming target for Nova Linux, in beta. It uses the Frame’s ARM64 hardware directly; it is not the Android APK, a new XR interface, or Steam Frame Verified support.
If the installer says Steam is running, Nova is already installed and works without a Steam entry. The installer won’t add the entry while Steam is open, and it never closes Steam: exit Steam completely with Steam menu ▸ Exit or its tray icon ▸ Exit Steam, in Desktop Mode on a Steam Deck or Steam Frame, since Game Mode always has Steam running. Then choose Check again (Steam is closed now), or open the installer again and choose Add to Steam only. Move to signed updates works with Steam left open and keeps your Steam entry.
The alpha in the bundle name, Flatpak branch and folder names below is a
compatibility identifier, not the build’s maturity.
What the Frame beta was checked for
Section titled “What the Frame beta was checked for”- A short functional check. On a Frame, H.264, HEVC and PyroWave each streamed 1920×1080 at a requested 60 fps with picture, sound and working controllers. That is not a performance result.
- How each codec reaches the screen. H.264 and HEVC decode through Frame’s V4L2 decoder and copy each frame through the CPU. PyroWave decodes with Vulkan and hands frames over as DMA-BUF.
- Untested. Rates above 60 fps, long sessions, color and clarity. Immersive XR and HDR are separate work.
- Runtime. Those checks used an isolated installation with a pinned KDE Platform 6.10 runtime. A fresh install of the current Flathub runtime with the commands below has not been tested.
Install it apart from other Nova builds
Section titled “Install it apart from other Nova builds”Download both files from the same release on Nova Releases. Then, in a terminal on the Frame or over SSH, run these from the download folder:
export FLATPAK_USER_DIR="$HOME/.local/share/nova-frame-alpha-flatpak"sha256sum -c Nova-Linux-aarch64-frame-alpha.flatpak.sha256flatpak remote-add --user --if-not-exists flathub https://dl.flathub.org/repo/flathub.flatpakrepoflatpak install --user --arch=aarch64 flathub org.kde.Platform//6.10flatpak install --user --arch=aarch64 --bundle ./Nova-Linux-aarch64-frame-alpha.flatpakFLATPAK_USER_DIR lasts for that terminal only. Set it again before any later
flatpak command for the Frame beta, including removal.
To launch it:
- Save the launcher script from the Steam Frame
guide
as
~/nova-frame-alpha.sh, and make it executable. - Add the launcher to Steam as its own non-Steam entry, separate from any other Nova shortcut. Give it a gamepad Steam Input layout and a Game Resolution of 1920×1080.
- Pair the Frame beta with your PC, then choose 1920×1080 at 60 fps. The device default is 1280×800.
The Frame beta keeps its pairing, settings and cache in its own frame-alpha
folders, and other Nova builds on the device keep theirs. They all share the
~/.var/app/com.papi_ux.Nova data folder, so never uninstall any Nova with
--delete-data. The same guide covers removal.
Earlier 90 fps development runs
Section titled “Earlier 90 fps development runs”Before the Frame beta download, development builds were run toward a 1080p at 90 fps target. These are not results for the Frame beta download.
| Path | Development evidence | Limit |
|---|---|---|
| H.264 | A 15-minute 1080p90 run, with real decoded frames | About 89.3 decoded/submitted frames per second and 85.5 app compositions per second, with delivery drops and decoder refusals; the 90 fps target did not pass |
| HEVC | A real picture and an interrupted run of about ten minutes | No completed, matched 90 fps soak; later display-rate changes are a separate run |
| PyroWave | Owner-observed 1080p60 picture, audio and controls | Clarity/color concerns and the 90 fps soak remain open |
App compositions, decoded frames and display presentation are different measurements. They should be read together rather than turning any one counter into a “90 fps verified” badge.
Before you try it
Section titled “Before you try it”Keep a working client available, start at 1920×1080 and 60 fps, and check the actual codec, decoder and display cadence. PyroWave needs its own Vulkan feature support and considerably more network bandwidth than HEVC.
The Linux guide explains the native client’s controls. PyroWave in the beta separates decoder support, capture paths and bandwidth advice. None of these pages promises XR support or all-codec 90 fps acceptance on Frame.