Files
DroidDeck/tools/linuxfs/overlay/usr/bin/steamos-update
The412Banner 2fb79735c3 Deck mode made safe, a client-branch choice, and a battery the client can see
Deck mode passes -steamdeck alone: -steamos3 opted the install into the steamdeck_stable
branch and started the restart loop Bannerlator hit on device (38996ea1). The SteamOS helpers
the client calls in that mode - the two Armada found it needs under steamos-polkit-helpers and
the three under /usr/bin - are staged from the apk as no-op stubs. The client branch on disk is
kept in step with the one forced on the command line, and an update that cannot install stops
the session after three restarts instead of looping for ever.

The Steam cog gets a Client branch row: public beta (every session so far) or Steam Deck
public beta, the channel Armada bootstraps from.

The client reads /sys/class/power_supply/BAT<n>/; Android's supply is called battery and laid
out differently, so the Quick Access Menu had no battery. BatteryComponent writes BAT0 and BAT1
from Android's battery API every five seconds - status, percentage, charge, energy, power and
time to empty - into a directory bound over /sys/class/power_supply.
2026-09-23 09:11:54 -04:00

9 lines
370 B
Bash
Executable File

#!/bin/sh
# What the Steam client calls in Deck mode to look for a SteamOS update. There is no SteamOS
# here: the answer is "no update", which is exit 7 in SteamOS's convention, and the client moves
# on. --supports-duplicate-detection is a capability probe and answers yes. Staged from the apk.
case "${1:-}" in
--supports-duplicate-detection) exit 0 ;;
esac
exit 7