Nova updates and beta releases
Stable and beta updates are separate choices. A Polaris host’s beta preference does not switch Nova to a beta, and a Nova beta does not update Polaris.
A beta is always an opt-in prerelease. It displays Nova Beta and its own version; older published betas may still say Nova Pre.
Android: install a beta
Section titled “Android: install a beta”-
Open Nova releases and choose a published release marked Pre-release. The Latest link follows stable releases and does not opt you into betas.
-
Read that beta’s requirements, then download its APK for your device:
Device Beta APK Most current phones, handhelds and ARM64 Android TV Nova-Beta-Android-arm64-v8a.apk32-bit ARM Android devices Nova-Beta-Android-armeabi-v7a.apkAndroid x86_64 devices and emulators Nova-Beta-Android-x86_64.apk -
Install the APK and open Nova Beta. Older beta releases may still say Nova Pre. This is the beta app. It uses application ID
com.papi.nova.preand installs beside stable Nova (com.papi.nova). Pair your host in the beta app; the two apps keep separate settings and pairing data.
Known limitation of 1.4.13-beta.2 and 1.4.13-beta.3: their PyroWave library is aligned for 4 KB memory pages. On an Android device with 16 KB pages that refuses that library, PyroWave still shows up as a choice and the stream fails when it starts. The other codecs do not use that library. Betas from 1.4.14-beta.1 on, including 1.5.0-beta.2, carry the aligned library; this has not been validated on a 16 KB device. Stable Nova does not enable PyroWave.
Older prereleases may use Nova-Android-… filenames. Follow the assets and notes
of the prerelease you selected; do not point the stable updater at an older beta
asset just because its filename looks the same. Public APKs have SHA-256 sidecars
on their release page.
Android: follow betas with Obtainium
Section titled “Android: follow betas with Obtainium”Keep your existing stable Nova entry. Add Nova Beta as a separate app:
- Use
https://github.com/papi-ux/novaas the source and enable Include prereleases for this entry. - Set the APK filename filter for your architecture, for example
Nova-Beta-Android-arm64-v8a\.apk$for ARM64. Use the beta app IDcom.papi.nova.preif you need to identify the installed app. - Check that Obtainium offers Nova Beta, then install or update it. Keep stable Nova’s filename filter and prerelease setting unchanged.
The changelog’s beta section also provides an ARM64 Add Nova Beta to Obtainium link with those settings. If an older beta used different asset names, update that beta entry’s filename filter before following newer builds.
Android: update a beta or return to stable
Section titled “Android: update a beta or return to stable”Install the next signed beta APK for the same architecture over the installed beta app, or
update its separate Obtainium entry. Pairing and preferences remain with that
beta app. Check the full version, including beta.N or rc.N, after updating.
If Android refuses the package, check the release notes, architecture and
signature; do not uninstall or clear app data as a routine update step.
To return to stable, open the stable Nova app and disable or remove the beta entry from Obtainium. Stable and beta app data do not transfer automatically. Uninstalling the beta app is optional and removes its own local data. Disabling prereleases in Obtainium does not convert the installed beta into stable Nova.
Nova Linux: choose an update channel
Section titled “Nova Linux: choose an update channel”Nova Linux runs on Linux desktops, laptops and handhelds, including Steam Deck.
It uses Flatpak rather than Android APKs. The Linux app ID remains
com.papi_ux.Nova.
Channel installations: Nova Linux updates itself from a signed stable or
beta channel. On Get Nova, the guided installer
installs an exact release bundle first, then Move to signed updates puts it
on the matching signed channel. You can also install a channel from the
Linux update channels page. Open
Settings → Nova → Nova Updates to check or install an update on that
installed channel. Automatic installation is optional and waits until Nova is
idle. Reopen Nova when it says the update is ready. Stable and Beta use the same
Nova app, pairing and settings. Selecting a channel is explicit; the app does not
switch channels automatically. Steam Frame stays a beta and updates from its own
aarch64/beta channel.
Updating in Game Mode: Flatpak asks once before an app updates itself, and
Steam Deck’s Game Mode cannot show that question. The guided installer’s Move
to signed updates saves that permission for Nova only and lists it in its
review. Without it, Nova says to switch to Desktop Mode and select Update Nova
once; later updates then work in Game Mode too. To withdraw the permission, run
flatpak permission-remove flatpak updates com.papi_ux.Nova. This removes only
Nova’s entry, and Flatpak asks again at the next update. Uninstalling Nova
without --delete-data keeps the entry, so run that command too if you remove
Nova.
Downloaded bundles: an ordinary .flatpak bundle may have no update feed.
Download the bundle from the intended release, verify its checksum, and install
that newer bundle with the software manager or flatpak install --user.
Current bundles are named Nova-Linux-x86_64-alpha.flatpak; older releases used
Nova-Deck-x86_64-alpha.flatpak. Use the filename attached to your release.
Existing bundle installations need a one-time channel installation before they can use the in-app feed. If you installed through the guided installer, its Move to signed updates does that and keeps your Steam entry; otherwise follow the Linux update and migration guide.
To change back to stable, use the published stable channel installer and launch
that channel explicitly. Switching channels does not mean an older build is a
safe downgrade; follow its release notes. Preserve pairing and preferences by
keeping the app data, and never use --delete-data as an update step.
For installation and Steam shortcuts, see the Nova Linux install guide.
Linux PyroWave: both x86_64 channels and the standard Linux bundle include PyroWave with a lazy device check, and the separate PyroWave bundle is retired. Keep the same app ID, installation and app data. The published 1.4.13 separate bundle remains a historical stable-release option. New codec controls and limits.
Test PyroWave
Section titled “Test PyroWave”PyroWave needs a compatible client decoder as well as a host encoder. Standard Moonlight clients cannot use it, and Polaris has no frontend switch that adds the decoder to those clients.
- Nova Android beta: with a compatible Polaris host, open a game’s Play Setup → This Game → Video Codec and select PyroWave (experimental). The choice is saved for that game on that PC; App setting returns to the codec in Nova Settings. Older builds, including v1.4.13-beta.3, the beta app named Nova Pre, do not have this Play Setup row: use Settings → Client Stream Defaults → Change codec settings → PyroWave (experimental). Auto does not select this codec, and stable Android builds do not enable it.
- Nova Linux: the standard 1.5.0 Linux package includes PyroWave, with a lazy, isolated device check. Nova 1.4.13 attached a separate codec bundle; install the standard package over it to keep your pairing and settings. The separate bundle is retired, and no separate codec update channel is offered.
In an enabled Nova Linux build, open a game’s Play Setup → Video Codec → PyroWave · Experimental. The host and the Linux device’s Vulkan decoder must both support it. Use the normal Desktop destination; PyroWave is unavailable in Spaces. Auto does not select PyroWave.
The Polaris 1.4.13 Linux packages include the host encoder, selected by the client’s request. For the first Linux test, use the supported SDR 4:2:0 profile on a fast wired local connection and confirm PyroWave in stream diagnostics. Decoder startup checks alone do not prove a streamed image, audio, input, HDR, or sustained frame rate. The Polaris PyroWave guide describes host and client requirements.
Install or leave the Linux PyroWave bundle
Section titled “Install or leave the Linux PyroWave bundle”Nova 1.4.13 only. Nova 1.4.13 attached a separate PyroWave bundle,
Nova-Linux-PyroWave-x86_64-alpha.flatpak. From 1.5.0 the standard Linux
package includes PyroWave, so there is nothing separate to install. To leave
the old bundle, install Nova 1.5.0 over it as the
Linux guide describes. It
replaces the bundle under the same app ID and keeps your pairing and settings.
Keep app data; do not use --delete-data.