QWASARVOID DESK / FIELD PORTAL
GETTING STARTED

INSTALL · NAVIGATE · UNDERSTAND

Manual

Install the published package, learn the controls and check the firmware compatibility notes.

01 PACKAGE PATH10 NAVIGATION ICONS01 FORGE SCREEN REFERENCE
01 / INSTALLATION

Install

Do not install from the repository source ZIP. The release asset is the packaged application intended for the muOS archive installation flow.

HANDHELD INSTALL / MUOSCHECKLIST Q—01
  1. 01
    Open the official releases

    Choose the published .muxapp asset from the repository Releases page.

    Browse GitHub Releases ↗
  2. 02
    Copy the package to the archive path

    Place the downloaded package in SD1/ARCHIVE/.

  3. 03
    Install with the native archive manager

    On the handheld, open Applications → Archive Manager and install the package.

  4. 04
    Launch from Applications

    Keep the installed application directory and launcher names intact. Existing installs use Void-Desk/ and mux_launch.sh.

PUBLISHED BASELINELatest published handheld package: v10.2.0v10.5.4-NEXUS is development work under review; v12 is a blueprint, not an installer.
02 / NEXUS VISUAL VOCABULARY

Navigation icons

These PNGs are the existing menu and hub symbols from the repository. They identify destinations; they do not depict complete application screens.

Workshop navigation icon
WORKSHOP
Settings navigation icon
SETTINGS
The Forge hub icon
THE FORGE
Start Session navigation icon
START SESSION
RT Toolbox navigation icon
RT:TOOLBOX
Netsphere navigation icon
NETSPHERE / UPLINK
muOS apps navigation icon
muOS APPS
Media Vault navigation icon
MEDIA VAULT
Info navigation icon
INFO
End navigation icon
END
03 / REAL SCREEN REFERENCE

THE FORGE

This is the actual THE FORGE application screen capture. It is deliberately kept separate from the hub icon shown above.

CAPTURE / THE FORGE MENUAPPLICATION SCREEN
Actual THE FORGE application screen capture
Asset distinction
forge-menu.png is the screen capture. the_forge.png is the navigation icon.
04 / FIRMWARE MATRIX

Compatibility

Firmware family is only one part of controller resolution. Device model and controller GUID must be evaluated together.

Firmware linePositionPolicy
2606.0 AndromedaCURRENT TARGETValidate exact device and controller GUID combinations.
2601.0 JacarandaLEGACYKeep a separate legacy profile family.
2601.1 Funky JacarandaLEGACY VARIANTDo not merge metadata until equivalence is proven.
2612 SupernovaIN DEVELOPMENTPreview only until official release and device tests.
Unknown / otherUNVERIFIEDGeneric safe baseline plus manual calibration.
!

Controller safety — never infer a certified physical mapping from CI or a graphics screenshot. The profile key is firmware release + device model/board + SDL controller GUID.

QWASAR / QUICK NAVIGATION

Quick navigation

CTRL + K OPEN · ↑ ↓ NAVIGATE · ENTER OPEN · ESC CLOSE