SteamOS for ARM 64 is HERE! Armada Ultimate Guide! Features, Gameplay, & Dual Boot!

Technological concepts & product features highlighted

• Installing SteamOS on ARM64 handhelds: The video focuses on running SteamOS on ARM-based gaming handhelds, specifically using Armada SteamOS.
• Armada vs. Rocknix: Armada’s defining difference from Rocknix is that it boots directly into the SteamOS game mode UI.
• Fully working KDE desktop (Linux desktop mode): Armada includes a functional KDE desktop environment, enabling “mild productivity” and access to apps like Firefox and other desktop software.
• Update channel / experimental status:
  • Armada targets the beta update channel by default.
  • Uses OTA updates, but is described as experimental / not widely tested.
• System stack & hardware/graphics details (Linux/ARM specifics):
  • Mentions running Fedora (Armada variant).
  • Uses Linux kernel 7.x (auto-sub title mentions “Linux kernel 7.”).
  • ARM64 CPU clock around 3.5 GHz, with Mesa 4.6 and 7 GB VRAM (device described as having 16 GB RAM total).
  • Performance/feel is said to resemble Valve SteamOS, but the distribution similarity is described as more like Bazzite.
• Desktop utilities & launcher tuning:
  • Deck/Tweak tooling preinstalled: “Deck Loader” comes with an Armada plugin (Armato Control, per subtitles).
  • Per-game performance profiles & tuning, including:
    • Custom effects presets
    • Fan curve
    • CPU underclocking
    • Performance adjustments per game via presets.
• Gameplay/performance benchmarking examples:
  • TMNT Splintered Fate: ~100 FPS in smaller areas; generally smooth with no complaints. Emphasis is on battery friendliness and playability for travel.
  • Shadow of Mordor (more demanding):
    • Cannot consistently lock at 60 FPS without tradeoffs.
    • “Balanced/custom” settings achieve mid-40 FPS hovering—playable and smooth.
    • Using a performance profile can reach ~60 FPS, but fans become loud, so the speaker prefers quieter settings.
    • Uses internal storage for better performance; dips to high-30s in heavier areas but remains around 40–45 FPS most of the time.
  • Once Upon a Katamari: Mostly 60 FPS, with dips (around 80–90/100 FPS in the world, with dips depending on scene complexity). Reported as enjoyable and smooth, using “balanced” power and an effects preset.
• Battery-life and portability messaging: ARM handhelds are described as having incredible battery life, and the speaker positions these devices as portable/tinkering machines rather than direct replacements for a desktop gaming rig.

---

Guides / tutorials included (key steps)

1. Dual-boot setup concept (Android + Armada/SteamOS)

The video demonstrates dual booting Android with Armada, using either:

• SD card installation (simpler; keeps Android intact)
• Internal storage installation (faster; requires more advanced steps and can affect Android data)

---

2. Armada installation to SD card (with custom bootloader requirement)

Prerequisites

• Install a custom bootloader so the device can boot into Linux/Armada.
• Requires running a root script from Android.

Critical warning: the script must match the device’s SoC model—using the wrong one may brick the device.

Downloads

• The instructions point to Armada GitHub releases and downloading a preview build (example date mentioned).

Flash process

• Write the image to an A2-speed SD card (recommendation: 64GB+).
• Use tools like Balena Etcher (or Rufus) to flash.

Booting into SD-based Linux/SteamOS

• Use the bootloader menu (navigate with volume keys).
• Select the device model (example includes Odin 3).
• Switch boot mode to Linux, then boot.
• SteamOS onboarding:
  • Downloads updates
  • Enables login via QR code

---

3. Internal storage installation (for better performance + advanced management)

• Installing Armada to internal storage requires using an “Armada installer” from KDE desktop mode.
• Warning: it factory resets Android, potentially deleting Android apps/data.

Partitioning concept

• Example allocation: more space for Armada (e.g., ~403GB) while keeping some for Android (e.g., ~32GB).

SD card workaround formatting and storage integration

• Install GParted on Armada.
• Format SD as BTRFS (example: GPT partition table + BTRFS filesystem).
• Use a SteamOS-mount tool (cloned from GitHub) to mount SD content.
• Change ownership so the SteamOS user can access the SD.
• In Steam client (desktop mode), add/mount the SD storage so it appears in game mode.

---

4. Workflows for uninstalling Armada

• Boot to bootloader (keep volume down while powering).
• Use ADB / fastboot to erase/remove Armada-related installations:
  • Example uses a fastboot erase command (noted as misnamed in tooling but used to erase Armada).
• Reinstall/remediate using an SD card live environment.
• In desktop mode, use Armada Installer → “remove and restore Android.”
• After removal, switching boot mode back to Android returns the device to Android (described as similar to a factory reset on the Android side).

---

Key review/analysis takeaways (tone and conclusions)

Big strengths of Armada (as framed by the speaker)

• Boots straight into SteamOS game mode.
• KDE desktop is functional and useful (including Firefox).
• Strong device tuning via per-game profiles and loader plugins.
• Smooth gameplay in demonstrated titles, with acceptable frame rates depending on tuning.

Main limitations/risks

• Software is preview/experimental, beta-channel based.
• Bootloader script must match SoC or risk bricking.
• Internal installation may factory reset Android.

---

Main speakers/sources

• Speaker: Inovision (primary presenter of the walkthrough, demos, and installation steps)
• Primary source referenced: Armada GitHub (releases, scripts, and download links)
• Supporting community tooling/projects mentioned:
  • SteamOS-mount-tool (GitHub repo)
  • Deck Loader / Armato Control (Armada plugin mentioned)
  • Rocknix team tooling (referenced indirectly in uninstall command behavior)