LegionGo2Companion

Power, battery protection, gyro, haptics, lighting, buttons, screen brightness, HDR and Wi-Fi in one Steam overlay. The Legion Go 2 controls you use every day, with saved profiles and automatic recovery after wake.

Features · Requirements · Installation · Usage · How it works · Troubleshooting

Controls follow the interfaces exposed by the active kernel. Older kernels offer named EPP presets; Companion applies the closest supported preset while preserving the exact saved value for newer kernels.

1. Install Decky Loader if it is not already installed.
2. Download LegionGo2Companion-<version>.zip from Releases, when available, or build it using the instructions below.
3. Remove the overlapping standalone plugins listed below, retaining their settings.
4. In Gaming Mode, open the Quick Access Menu → Decky → Settings → Developer.
5. Choose Install Plugin from ZIP and select the archive.

The archive contains one LegionGo2Companion folder. Decky installs it with the privileges needed by the hardware controls; normal use requires no terminal commands.

Open About → Check for Updates to check the latest stable GitHub release. If a newer release has its plugin ZIP attached, Download saves it in your Downloads folder and shows the path. No public release yet, an incomplete release and a connection failure are reported separately. Checking and downloading happen only when requested; opening the menu does not contact GitHub.

Companion verifies the archive's version, size, SHA-256 digest and contents before making the completed ZIP available. Failed downloads do not replace an existing ZIP. Releases without a SHA-256 digest are not offered for download; source archives and development branches are never used as a fallback.

Install the downloaded ZIP through Decky Settings → Developer → Install Plugin from ZIP. Review your module choices afterwards: Decky's installation process can reset the gyro source, battery protection and Wi-Fi preferences. Downloading alone leaves the running plugin and all settings unchanged.

The backend checks before startup and every component request, and scans installed plugins every five seconds while running. A newly detected conflict blocks further requests and stops all module workers after an in-flight operation finishes. The frontend replaces hardware controls with a paused screen and the names of the detected plugins.

Detection uses both installation-folder names and plugin manifests, so renamed copies also count. Removing a conflict does not silently restart partially stopped modules: Check again confirms the current state, then a Decky or console restart starts a fresh instance. User profiles are kept. A plugin whose identity cannot be read safely also pauses Companion until the installation can be verified.

Companion imports TDP, vibration, display and Wi-Fi settings from their existing Decky settings folders. Existing Companion values take precedence; missing values can be filled from the old files. Importing does not modify or delete those source files.

Keep the standalone settings folders when removing their plugins. If those files have already been deleted, there is nothing to import. Companion keeps its own settings outside the installed plugin folder, so replacing the plugin files preserves them.

Open OLED Display after installation. It may ask for a display mode and offer Restart Game Mode if the installed script differs from the one gamescope has loaded.

npm ci
npm run typecheck
npm run test:frontend
npm run build      # compile the frontend into dist/
npm run package    # create LegionGo2Companion-<version>.zip

Open Legion Go 2 Companion from the Decky menu. The main page shows a short status for each hardware area; selecting one opens its controls. All Controls returns to that overview. Choosing an item from a dropdown keeps the current page open.

Open Manage Modules to turn each hardware module on or off. All modules are available by default. Disabling one stops its workers and game reports, releases its hardware controls and hides its page from the main menu. The choice survives Decky restarts and console reboots. Saved profiles and preferences return when the module is enabled again.

Lighting, remapping, battery and gyro controls restore the state they captured before taking control. Vibration returns to driver defaults. TDP returns to the balanced firmware profile; managed CPU Boost and EPP return to standard boost and balance_performance because earlier versions did not retain the original CPU policy. Wi-Fi restores its owned configuration and can briefly reconnect during the change.

OLED Display also removes its installed script. Gamescope keeps a loaded script until the session ends, so the page offers Restart Gaming Mode (closes games) when needed. If hardware restoration fails, the module stays blocked and the page shows the error with Retry Cleanup. An interrupted cleanup is retried on the next startup before that module is allowed to run, and during uninstall if Companion is not paused by a plugin conflict. Failed restoration keeps its recovery record.

Enable gives Companion control of the TDP limits. Turning it off releases that control; CPU Boost and EPP are independent controls.

Presets apply immediately. The Legion Go 2 ladder is:

The available range is checked against the firmware. In Custom, SPL sets sustained power; SPPT and FPPT add longer and shorter burst headroom above it. Apply TDP commits the slider values.

Per Game Profile stores TDP limits, CPU Boost and EPP for the running game. Separate AC Profile gives that game independent battery and charging settings for all three controls. The editing buttons select which profile you are changing; connecting the charger selects which one the backend applies. Editing an inactive profile saves its choices without changing the active profile on the hardware.

CPU Boost controls the kernel's boost setting. EPP runs from 0% towards performance to 100% towards power saving, in 10% steps. The CPU section identifies whether changes belong to the global profile, the game's battery profile or its AC profile. Choices are restored after startup, resume and power-source changes, and checked for drift.

Leaving a game, disabling its per-game profile or starting a game without a profile restores the global choices. Existing profiles without CPU values inherit the global ones until edited. New profiles start with the current choices; if no global CPU choice was saved yet, Companion records the readable baseline so it can return to it later.

Current TDP shows the limits alongside live package power. Package power is the APU reading, not the entire console's battery drain.

Choose the handle Intensity and Mode, then configure touchpad vibration separately. Test Vibration (0.5s) gives a short check of the selected handle settings.

With a game running, enable Per Game Profile to save its haptic settings. Returning to the global profile uses the global choices again. Controller reconnection and wake trigger reapplication when the driver becomes available.

Enable RGB control lets Companion manage the rings. Joystick ring lights switches their output on or off. Select an effect, then adjust the controls relevant to it:

Colour uses hue and saturation; the preview shows the current choice. Changes are saved as you make them, with slider writes grouped while you move a control. Animations run in the controller firmware.

Power button light is a separate setting. Restore lighting state from before Companion returns the captured lighting state and releases Companion's lighting control.

Enable remapping, then select an action independently for Desktop button and Page button. Choices include Steam menus, the on-screen keyboard, screenshots, window switching, navigation keys and F1-F12. Disabled makes that button produce no action.

Default restores the captured system behaviour for that button. Disabling remapping restores the mappings Companion still owns, while preserving unrelated profile entries and changes made elsewhere.

Choose a gyro source to let Companion enable reporting from the corresponding removable controller and route its motion through the existing InputPlumber service. Both controllers (average) combines the two handles; it is not the sensor inside the console body. System default releases the controls and restores the values Companion still owns. Button assignments, Steam controller identity and unrelated input filters are kept.

Start 30-second test shows native left/right gyro and touchpad readings alongside the existing virtual controller output. Rotate the device and move a finger on the touchpad while testing. Raw gyro values are diagnostic readings, not degrees per second. A stream with no packets is shown separately from a stream carrying zero values.

The test stops when the page is hidden or closed, after 30 seconds, or when the frontend stops renewing its short lease. It does not grab the controller. Reports reaching the virtual controller confirm that stage of the input path; a game's Steam Input layout must still assign gyro and touchpad actions. Body-sensor integration and firmware calibration are not enabled by this page.

Battery protection enables Lenovo's firmware-controlled Long Life mode, intended to limit charging to around 80%. This is a fixed firmware mode, with no adjustable percentage or forced discharge. Enabling it while the battery is above the limit does not immediately lower the charge level.

Turning protection off returns to the normal charging mode captured before enabling it, including Fast when it was active. Release battery control restores the captured state while it is still owned by Companion and stops automatic reapplication. The page distinguishes the saved choice from the actual charging mode and reports failed changes. The feature does not change the battery on first installation until selected by the user.

This module fixes screen brightness control in SteamOS. It also offers an HDR fix by correcting the display metadata exposed to games.

Choose a mode on first run, or use Switch Display Mode later:

Brightness slider forwards Steam's slider only when the panel is in PQ without HDR content. When Steam is already controlling HDR brightness, this part stands aside.

EDID for games corrects gamescope's published display metadata so affected games can read the panel's luminance values. Restart an already running game to let it read the updated metadata.

Prefer 5/6 GHz changes iwd's band preference system-wide. It keeps 2.4 GHz available when that is the connection the device can use; it does not pin the adapter to one band or access point.

Rescan and reconnect to 5/6 GHz makes a bounded attempt to move the current connection to a suitable higher-band access point. It briefly interrupts the connection. The page shows the actual connected band and the result, so enabling the preference is not mistaken for a completed switch.

Companion brings together the TDP, vibration, display and Wi-Fi implementations with RGB and button-remapping, gyro, diagnostic and battery pages. Each backend owns its hardware interface and settings; the Decky entry point coordinates startup, shutdown and calls from the frontend.

Button remapping reuses InputPlumber rather than installing another input service. The display fix changes the EDID copy published by gamescope, not the panel's firmware.

Settings use atomic replacement with backup/recovery handling. A failed TDP settings save attempts to restore the previous effective target, and a delayed vibration edit is rejected if its game/profile context has changed.

If neither saved settings copy can be recovered, affected controls report the problem and stop applying changes. Missing ownership information is never replaced with guessed restoration values. Keep the damaged files until a valid settings copy can be restored.

The backend continues managing saved profiles while Quick Access is closed. TDP checks for changed limits and retries failed profile transitions with backoff. RGB and remapping normally verify state once per minute; for the first 30 seconds after startup or wake they check every five seconds to catch a controller or service that appears late. Matching lighting and mappings do not need another hardware write or profile reload.

Battery and gyro choices also restore on startup and wake and check for drift once per minute. Battery changes keep a durable recovery record before writing to the kernel, so an interrupted first change retains the original charging mode. Diagnostic readers are closed outside a test; merely installing Companion does not start sampling HID reports.

If the verified InputPlumber process exits, the existing monitor tick schedules an earlier check of gyro and button mappings. Recovery still verifies the controller and ownership before applying saved choices; failed attempts use increasing retry intervals.

Wi-Fi recovery journals are stored persistently so a reboot cannot erase an unfinished transaction. Recovery stops on a conflicting external change instead of overwriting it.

Page-specific periodic status refreshes pause while Quick Access is hidden. Decky's alwaysRender keeps the selected page mounted during a native dropdown, preserving its navigation state without keeping those refresh timers running.

The main menu keeps the last received summaries when reopened. Repeated read failures or a delayed response add a small note with the age of the data; a fresh response clears it automatically. InputPlumber's version label is cached separately from live controller state, with invalidation when its executable changes.

RGB effects run on the controller. Backlight notifications are event-driven where the kernel supports them; gamescope state still needs periodic checks, with the shorter interval used by Hybrid. Background profile and recovery checks remain active because they are needed outside the menu. There is no fixed CPU percentage or battery-life claim: the cost depends on the enabled controls, mode and system build.

npm ci
npm run typecheck      # check frontend types
npm run test:frontend  # navigation and pending-setting lifecycle checks
npm test              # Python backend tests
npm run build         # compile the frontend
npm run package       # package the current build

Backend tests require Python. Linux-specific permission and symlink checks skip on Windows. Hardware calls are mocked in the unit suite; console testing is still needed for startup, resume, game transitions and native Steam UI behaviour.

The release archive includes frontend source/build inputs, license notices and the bundled pyudev source. The optional RyzenAdj executable is downloaded separately and checked against its pinned hash. See SOURCE.md for frontend rebuilding and CHANGELOG.md for version history.