Commit Graph
811 Commits
Author SHA1 Message Date
The412Banner 49f1ceaadc x86-64 client: run native Linux games, 32-bit preloads, no Deck flags
- DroidDeck direct: a compatibility tool the x86 client gets in its own
  compatibilitytools.d, running a native Linux game with Valve's scout
  library runtime under FEX instead of the Steam Linux Runtime container
  (pressure-vessel, which needs bwrap). Left 4 Dead 2 (BL_X64_DIRECT_APPS)
  is mapped to it in the x86 config while that client is not running.
- The session shim and the controller reader are also built for i386 and
  preloaded through glibc's $LIB, so 32-bit games get them too.
- The runtime's bin/ on the client's PATH (steam-runtime-launch-client).
- No -steamdeck -steamos3 for the x86 client yet: its SteamOS audio
  manager aborts on the runtime's PulseAudio 13 (pa_operation_get_state).
2026-10-02 18:16:17 -04:00
The412Banner 2d2ffd9d05 Progress log: x86-64 client controllers, online, Play-button choice 2026-10-02 17:28:49 -04:00
The412Banner 05d74c8a1f Steam session: choose the ARM64 or the x86-64 client
A Steam setting (Client > Steam client: ARM64, the default, or x86-64
under FEX, experimental) sent as BL_STEAM_CLIENT_ARCH. With x86_64 the
session starts Valve's x86-64 client through bannerlator-steam-x64 in its
own home instead of steamrtarm64/steam, so the Play button gets every fix
the session has (system bus and NetworkManager stand-in, gamescope, Deck
and Big Picture UI, stale locks, branch sync, restart loop, stop watcher,
logs, core pinning); what is only for the arm64 client (ARM64 Proton and
its mapping, redist seeding, Decky, the steamclient.so probes) is skipped.
bannerlator-steam-x64 gains --prepare and --exec for that; its own library
replaces the shared steamapps link.
2026-10-02 17:28:00 -04:00
The412Banner cb2334da4e bannerlator-steam-x64: the app's FEX preset for the client
The client ran on FEX's defaults (half-barrier TSO, full-precision x87).
Use the app's default game preset, PERFORMANCE_TSO (WinNative's), as the
FEX_* variables both FEX builds read; values already set win.
2026-10-02 17:24:24 -04:00
The412Banner 8a89387ef8 x86-64 client: the session's fixes for the arm64 client
From an audit of bannerlator-session against bannerlator-steam-x64:
- a system bus and the NetworkManager stand-in when none is up, stopped
  with the client: the client showed no connection on the desktop
- stale .crash/steam.pid/htmlcache Singleton* cleared before a start
- package/beta matched to -clientbeta before every start (rc=42 loop)
- BL_CLIENT_CPUS re-pinning of the client and its web helper every 5 s
- pathcache.c and perms.c also recognise steamrt64 (the path cache saved
  most of the arm64 client's start-up; the write override covers its
  self-update)
2026-10-02 16:59:56 -04:00
The412Banner 47e528102d x86-64 client: the controller reader for x86 programs
The session's pads exist for a guest program only through libfakeinput
(the FAKE_EVDEV_* rings), which was built for arm64 alone, so the x86
client saw no controller. Build it natively for x86-64 too, stage it, and
preload it through the FEX rootfs next to the session shim.
2026-10-02 16:52:53 -04:00
The412Banner 1d90448924 Progress log: the x86-64 Steam client under FEX (2026-10-02) 2026-10-02 16:52:01 -04:00
The412Banner 131ba72ee5 x86-64 client: hide the tracer only from tier0's status reads
Hiding it from the whole x86 web helper got it past tier0 (message loop,
BrowserCreated) but then Chromium trapped on the status descriptor it
opened itself, now a memfd copy - which is the other reason the shim
leaves the web helper alone. With BL_WEBHELPER_HIDE_TRACER=1 only opens
called from libtier0_s.so get the copy; Chromium's get procfs.
2026-10-02 16:28:43 -04:00
The412Banner b2e3a3a5ea x86-64 client: hide proot's tracer from the web helper too
Traced per process through FEXServer: every x86 web helper read
/proc/self/status (the string sits in libtier0_s.so) and died of SIGTRAP
right after. proot is a tracer, so tier0 believes a debugger is attached
and breaks into it with int3 on the first failed assertion. The arm64
build only issues a stray svc there, which is why the session shim leaves
the arm64 web helper reading the real TracerPid. BL_WEBHELPER_HIDE_TRACER=1,
set by bannerlator-steam-x64, serves the x86 one TracerPid 0 as well.
2026-10-02 16:17:55 -04:00
The412Banner 254e1db969 bannerlator-steam-x64: BL_FEXSERVER_LOG for pid-tagged FEX logs
A diagnostic: FEX's file log is opened without O_APPEND, so each process
overwrites the last. Through a foreground FEXServer every line carries
the pid and tid it came from.
2026-10-02 16:14:31 -04:00
The412Banner 34e7191e02 bannerlator-steam-x64: BL_FEX picks the FEX build that runs the client
For diagnostics: a DEBUG_STRACE build traces the client and everything it
starts.
2026-10-02 15:49:32 -04:00
The412Banner 5dfa6f43ed bannerlator-steam-x64: webhelper on Wayland
On X11 Chromium sets up GBM on the render node Xwayland hands out over
DRI3 even with the GPU disabled, loops on KMS dumb-buffer ioctls against
the KGSL device, and never creates the SteamUI browser; the client
restarted it every 10 s. Without a GPU, Chromium's Wayland backend draws
to shared-memory buffers.
2026-10-02 15:46:35 -04:00
The412Banner 2ff30ab4bb bannerlator-steam-x64: no DRI3 for x86 Mesa
Hiding /dev/dri was not enough: Xwayland hands the render node out over
DRI3, and llvmpipe then loops on KMS dumb-buffer ioctls against the KGSL
device. LIBGL_DRI3_DISABLE=1 presents through plain X.
2026-10-02 15:44:41 -04:00
The412Banner aa27921dee bannerlator-steam-x64: hide the GPU node from x86 programs
x86 Mesa and the Vulkan loader still enumerated /dev/dri, found the
session's KGSL node and looped on it (KMS dumb-buffer ioctls), and the
webhelper never brought a browser up; the client restarted it every
10 s. FEX resolves paths in the rootfs first, so an empty /dev/dri there
leaves llvmpipe and lavapipe.
2026-10-02 15:43:52 -04:00
The412Banner 581a7d1557 bannerlator-steam-x64: software GL and the rootfs's Vulkan for the x86 client
The desktop exports zink over the arm64 Turnip ICD (GALLIUM_DRIVER,
MESA_LOADER_DRIVER_OVERRIDE, VK_ICD_FILENAMES); x86 Mesa found no driver
and the client died on glXChooseVisual. Clear them and use llvmpipe.
2026-10-02 15:31:02 -04:00
The412Banner e07e436857 bannerlator-steam-x64: SteamRT libraries only where the rootfs has none
LD_LIBRARY_PATH beats the system folders regardless of order, so the
platform's own older libc.so.6 shadowed the rootfs's (GLIBC_2.38 not
found). Keep only the libraries the rootfs lacks.
2026-10-02 15:29:19 -04:00
The412Banner e0348adc02 bannerlator-steam-x64: soname links for the SteamRT platform libraries
Valve's platform runtime files carry each library under its full version
only; pressure-vessel makes the soname links when it builds a container.
Link them into a folder of our own and run the rootfs's ldconfig -n there,
so libgtk-x11-2.0.so.0 and the rest resolve.
2026-10-02 15:28:46 -04:00
The412Banner a7b4d79c15 bannerlator-steam-x64: the SteamRT platform libraries after the rootfs's
steamui.so needs GTK 2 (libgtk-x11-2.0.so.0), which the SteamRT container
provides and FEX's Ubuntu 24.04 rootfs does not. Append Valve's own
steamrt3c platform library directories to the client's library path,
after the rootfs.
2026-10-02 15:27:38 -04:00
The412Banner ae96d7fdaf bannerlator-steam-x64: stay out of pressure-vessel, restart on request
After its self-update the x86 client re-executes itself in the SteamRT
container through pressure-vessel-wrap, which needs bwrap. The FEX rootfs
with the client's steamrt64 libraries is the container here, as proot is
for the arm64 client: set the client's recursion guard. Restart on exit
code 42 the way steam.sh does.
2026-10-02 15:26:34 -04:00
The412Banner e5145bfad5 x86-64 client: System V IPC shim for x86 programs, and staging
The x86 client stops at start on a tier0 assertion: semget answers ENOSYS,
as Android kernels have no System V IPC (traced with a DEBUG_STRACE FEX).
The session shim that gives the arm64 client its semaphores is now also
built as native x86-64 and preloaded through the FEX rootfs's own
ld.so.preload. SessionFiles stages it and bannerlator-steam-x64 into
installed runtimes.
2026-10-02 15:16:24 -04:00
The412Banner b3c54e6cda FEX build: optional diagnostic CXXFLAGS
A workflow_dispatch input passes extra CXXFLAGS (e.g. -DDEBUG_STRACE for a
syscall trace) into the build; such builds stay artifacts and are never
published under a release tag.
2026-10-02 15:08:49 -04:00
The412Banner a6a11cad54 bannerlator-steam-x64: answer the SteamRT3 client's namespace probe
The x86 client carries pressure-vessel and will not start when
steam-runtime-check-requirements cannot create a user namespace; no
Android app can, and proot is the container here as it is for the arm64
client, which has no such probe. STEAM_RUNTIME_STEAMRT points it at
Valve's runtime linked file by file, with only that probe replaced.
2026-10-02 15:05:49 -04:00
The412Banner 615539dcd3 bannerlator-steam-x64: start steamrt64/steam the way the session starts the arm64 client
Through steam.sh, steam-runtime-check-requirements' bwrap probe needs user
namespaces, which proot does not have. Run the SteamRT3 client directly
with STEAM_RUNTIME=1 and its own library folders, after the ~/.steam
links steam.sh would make, as bannerlator-session does for steamrtarm64.
2026-10-02 15:04:48 -04:00
The412Banner b121a89c8b bannerlator-steam-x64: start Valve's 64-bit SteamRT3 client
The legacy ubuntu12_32 path in steam.sh refuses to start without user
namespaces (steam-runtime-check-requirements, exit 71). On the beta branch
STEAM_FORCE_CLIENT=steamrt64 makes steam.sh run steamrt64/steam directly,
the x86 twin of the arm64 client the session already runs.
2026-10-02 15:03:46 -04:00
The412Banner d7b7193cbd bannerlator-steam-x64: run FEX without the proot fast path
With libblfastpath loaded into FEX, every i386 program died with SIGILL
(FEX's fatal trap) before logging was up, and steam.sh reported the
32-bit libc.so.6 missing. Bisected on device: the session's other two
preloads are harmless; PROOT_FP_OFF=1 lets i386 ld.so run.
2026-10-02 15:01:28 -04:00
The412Banner ca166c670e bannerlator-steam-x64: FEX fex-2609-r2 2026-10-02 14:43:48 -04:00
The412Banner 42aa7692dc FEX: fall back to openat inside the rootfs when openat2 is missing
Our proot answers openat2 with ENOSYS. FEX opened every rootfs path with
openat2(RESOLVE_IN_ROOT) and only fell back on EXDEV, so in a session
every x86 file lookup missed the rootfs and hit the arm64 guest: bash
under FEX could not find libtinfo. GetEmulatedFDPath already follows
absolute symlinks inside the rootfs, so a plain openat relative to the
rootfs fd is the same lookup. The rootfs also gets an empty
ld.so.preload, so the guest's arm64 preloads are not tried.
fex-2609-r2
2026-10-02 14:38:37 -04:00
The412Banner 5786ddf81f bannerlator-steam-x64: no early FEX run, stop a stale FEXServer
FEX processes take the rootfs from FEXServer. The version probe started
one before FEX_ROOTFS was set, and later clients inherited its empty
rootfs. Still not enough on its own on the device: under investigation.
2026-10-02 14:04:13 -04:00
The412Banner ec3243a997 bannerlator-steam-x64: a finished rootfs download is not a failure
curl -C - on a complete file gets 416, which set -e turned into an abort.
The Ubuntu 24.04 image is 525 MB, not 850.
2026-10-02 13:58:23 -04:00
The412Banner d5ef1c832a Opt-in x86-64 Steam client under FEX
The arm64 Linux client never runs VAC: TF2 and L4D2 are refused by VAC
servers and no client log mentions VAC, because VAC modules are x86 code.
bannerlator-steam-x64 installs Valve's x86-64 client, FEX and FEX's
Ubuntu 24.04 x86 rootfs, and runs the client unchanged under FEX in a
home of its own, sharing only steamapps with the arm64 client. The arm64
client stays the default; the desktop menu gets an experimental entry.
2026-10-02 13:56:22 -04:00
The412Banner 61ea96a9e8 Build FEX for the runtime
The x86-64 Steam client experiment needs FEX inside the guest, and neither
Arch Linux ARM nor FEX publishes a Linux arm64 binary. Built in the same
Arch Linux ARM container as gamescope, without thunks, tuned for generic
armv8-a, with the runtime's own unsquashfs alongside to unpack FEX's x86
rootfs image.
fex-2609-r1
2026-10-02 13:51:26 -04:00
The412Banner ed2160c137 VAC diagnostics: an attempt to connect is not a connection
Left 4 Dead 2 logs "Connecting to", retries, and refuses a VAC server with
a "Connection Blocked: Please remove plug-ins" dialog that never reaches
the console. Counting the attempt as reaching a server would have reported
an insecure game as connected. Only "Connected to" counts now; an attempt
alone is reported as not connected, naming the dialog to look for.
2026-10-02 12:37:37 -04:00
The412Banner c9fb19b0cd Restart the client once for a title mapped while it runs
The client reads config.vdf once, as it starts. A title installed during a
session got its per-app ARM64 Proton entry from the compat beat, but the
running client kept its own pick: native for a Linux build, which then sat
on "Downloading content (0%)" waiting for Steam Linux Runtime 2.0 and FEX
it can never run here (Left 4 Dead 2), or proton-stable for a Windows one.

The beat now runs the compat pass with --live, which notes titles it maps
while the client runs. Once each has finished installing and no game is
running, the session restarts the client through the existing restart-once
marker. Once per title and three times per session at most. The mapping is
re-applied before the client starts again, since it writes config.vdf back
from memory as it exits.
2026-10-02 12:30:34 -04:00
The412Banner 9a6558d8b3 VAC diagnostics: game console + vac.txt in the session logs
A Source-engine game says whether it started VAC-secure only in its own
console, which reaches a file only with -condebug. With the new Setup
toggle on (off by default), the launch wrapper adds -condebug to Source
and Source 2 titles and notes each launch; at the end of the session each
console.log written during it is copied, scrubbed, into vac/ and vac.txt
quotes the game's secure/insecure lines, any VAC lines in the client's
logs and which client builds are on disk. No connection to a server is
reported as inconclusive rather than guessed.
2026-10-02 11:17:56 -04:00
Kurt Himebauch ec016f85bc Merge pull request #142 from Droid-Deck/xXJSONDeruloXx-patch-1
Update README.md
2026-10-02 01:55:28 -04:00
Kurt Himebauch c2c812deaa Update README.md 2026-10-02 01:55:15 -04:00
Kurt Himebauch eec3428f78 Merge pull request #141 from Droid-Deck/release/0.3.0
Release 0.3.0: version bump, Deck mode for everyone, release notes and media, Updates page fix
0.3.0
2026-10-02 01:39:31 -04:00
xXJSONDeruloXx 4a5e4b76e3 ci: publish the GitHub release from the Release APKs run, with the notes from docs/releases 2026-10-02 01:34:41 -04:00
xXJSONDeruloXx 43f952b2fb discord link and cleanup 2026-10-02 01:32:12 -04:00
xXJSONDeruloXx 0d86bec34d docs: drop the unused overlay GIF and the 'as above' it left behind 2026-10-02 01:16:04 -04:00
xXJSONDeruloXx 47a6f29ad7 docs: in-game GIF for the faster-in-games highlight 2026-10-02 01:15:25 -04:00
xXJSONDeruloXx 84834f180e docs: GPU drivers shot with DD-Turnip in use 2026-10-02 01:03:16 -04:00
xXJSONDeruloXx bfd445618a docs: dual-screen Deck controller and Stop GIFs, Deck mode for everyone in the 0.3.0 notes 2026-10-02 00:59:48 -04:00
xXJSONDeruloXx eddfd37b93 feat: move every install to Deck mode once, so updated installs get it too 2026-10-02 00:59:48 -04:00
xXJSONDeruloXx d7341863bf docs: show added apps on the Desktop page in the 0.3.0 notes 2026-10-02 00:49:37 -04:00
xXJSONDeruloXx 2f51be7b5a docs: 0.3.0 release notes with screenshots and GIFs 2026-10-02 00:47:35 -04:00
xXJSONDeruloXx fbc0014d14 fix: say Can't install, not Update available, for a build Android would refuse 2026-10-02 00:47:35 -04:00
xXJSONDeruloXx 46df6171fc release: 0.3.0 2026-10-02 00:47:35 -04:00
Kurt Himebauch 761b62914f Merge pull request #140 from Droid-Deck/chore/ui-cleanups
UI cleanup for 0.3.0: motion, focus ring, copy and game environment editor
2026-10-02 00:22:26 -04:00
Kurt Himebauch 91b0299f77 Merge branch 'main' into chore/ui-cleanups 2026-10-02 00:18:04 -04:00