* fix(proot): ship proot in the APK and run it from the native library directory
* fix(native): start rootfs programs through an APK-shipped exec loader where data files may not be executed
* fix(audio): start PulseAudio through the system linker where data files may not be executed
* feat: target Android 14 (SDK 34) so Play Protect installs DroidDeck without a warning
* fix: ask for all-files access on Android 11+, reject unloadable ELFs before exec, keep checking the proot pack
* fix: hand host scripts to the kernel, skip startup launch while all-files Settings is open
* fix: run proot from its add-on pack through Android's linker, so the APK carries no proot
* fix: declare high sampling rate sensors for controller gyro at target 34
* fix: offer the rootfs proot fallback only where Android lets proot exec its loader
* test: install the runtime's proot pack in GameFileSync fixtures
* feat(display): black frame insertion on 100 Hz and faster screens
* feat(display): black frame insertion lives in Screen effects
* test(compositor): cover black frame insertion in the render-on-commit harness
* fix(display): keep HDR and pacing intact around black frame insertion
* fix(display): gate black frame insertion on the panel's refresh, not the tick rate
BFI checked the 100 Hz minimum against g_refresh_ns, an average of the time
between handled vsync ticks. BFI presents on every tick, so under load the
ticks run late, the average fell to 95-100 Hz on a 120 Hz panel, and BFI
switched off and on again many times a second (3793 times in one session on
a Retroid Pocket Duo). That showed as uneven flicker.
Use the display mode's refresh (g_output_refresh_mhz) instead, which only
changes when the mode does.
* fix(display): offer black frame insertion for the bottom screen and while it is on
* fix(display): capture a picture, not a black refresh, while black frame insertion strobes
* fix(display): hold black frame insertion off until the last capture ends
* fix(display): keep the game composed while a capture holds black frame insertion
* test(display): a picture hold presents only pictures while black frame insertion runs
* fix(preload): Windows games run from noexec shared storage under every Proton
When mprotect(PROT_EXEC) on a private mapping is refused, libblsession
moves the pages into anonymous memory and retries, so Wine can make an
image's code sections executable on noexec mounts. FEX keeps its
existing handling.
* fix(preload): copy noexec image pages without faulting or dropping access
* fix(preload): install copied image pages with final permissions
Nexus moved its Xodus changes from patch files in xodus-nexus into a backend
fork (domsvoboda/nexus-backend, GPL-3.0). prepare.py now fetches that fork at
backend-v0.2.15 (e7884a27, same Xodus base 53ea781d, same Rust 1.99.0) and
applies the DroidDeck patches, rebased onto it:
- droiddeck-credentials, -launch-view, -library-subscriptions: same rebase as
Bannerlator's 0.2.15 update (identical patches before and after).
- droiddeck-credential-fallback, -credential-diagnostics: applied unchanged.
- droiddeck-cloud-token: session::prepare now also returns the account
snapshot; the ticket checks it like upstream's profile/social commands.
- droiddeck-licensing-device-ticket: upstream 0.2.15 already formats
delegation-compact device tickets for Store license tokens (27c335e), so only
the content licensing path is patched. Upstream now writes compact JWE
delegation tickets as t=, so the d= prefix check is replaced by the token
type, the same rule as upstream's store_license.rs.
droiddeck-xbox-ticket.patch is dropped: upstream sends compact JWE delegation
tickets to Xbox Live sign-in in a form it accepts, with tests.
Runtime: domsvoboda/nexus-runtime runtime-11.0-20261102-g76c6dd13 (was
xodus-nexus runtime-11.0-20261018). Same six modules at the same path;
xgameruntime.dll is the C++ implementation (nexus-xgameruntime 455b1ba9).
Archive sha512 from the release's .sha512sum, source sha256 from its
candidate.json, module sha256 from the extracted files. The PlayFab Game Saves
proxy is a newer build at the same path and still passes droiddeck-xbox's
export checks; its license moved to share/doc/nexus-runtime/.
DLC mounting: the C++ runtime mounts downloadable content only inside a
host-managed workspace named by XODUS_MOUNT_ROOT (src/System/Package/Mount.h
returns E_NOTIMPL without it). DroidDeck starts Wine itself
(droiddeck:prepare), so droiddeck-dlc-mount.patch (ported from Bannerlator)
creates the workspace in the launch directory for the prepare session and
reports it as mountRoot; XboxRuntime passes it in the xbox-prepare reply and
droiddeck-xbox sets XODUS_MOUNT_ROOT to its Z: path. XODUS_CONTENT_ROOTS is
unchanged and still read by the runtime.
Upstream fixes since the old pins include sign-in for some accounts, offline
play, cloud-save conflict handling, DLC mounting, duplicate token requests and
per-game fixes (Ori, AoE, MSFS, Forza Motorsport).
The session preload is also built for i386 and preloaded into every 32-bit
x86 program under FEX. There it aliased fstat64, ftruncate64, pwrite64,
fallocate64, posix_fallocate64, open64, openat64 and fcntl64 to their 32-bit
hooks, which on i386 take a different struct layout or argument size. fstat64
returned a size with garbage high bits, so libdbus rejected a valid 33-byte
/etc/machine-id as too large and aborted the program. The aliases now exist
only where off_t is off64_t; on i386 the 64-bit calls reach their own glibc
functions, keeping the open and lock hooks.
* fix(rockstar): ship the launcher service as an add-on pack, not inside the APK
* fix: ship the DiRT ws2_32 stand-in as an add-on pack and reject Windows executables in the APK
* fix(release): reject APK entries under a packed path even when the manifest omits them
* fix(dirt): fetch the ws2_32 stand-in pack once the Linux runtime is installed
* fix(desktop): serve PipeWire in Desktop mode so screen capture works
* fix(desktop): preserve shared PipeWire lifecycle
* test(desktop): exercise shared PipeWire lifecycle
* fix(desktop): start PipeWire for bottom sessions
* fix(desktop): serialize shared PipeWire bundle preparation
Concurrent Steam and bottom Desktop starts unpacked the bundle into the
same staging directory and rewrote the access settings together. Hold an
exclusive lock around unpacking and access configuration, and cover the
race plus start success and failure environment handling in tests.
* fix(desktop): replace PipeWire access fragments atomically
Write each fragment to a temporary file and rename it so running daemons and clients never read a truncated file.
* fix(desktop): isolate runtime directories in concurrent PipeWire start test
* fix: surface Battle.net's own reason when it refuses a game folder
watch() treated any "error": <nonzero> in the Agent's status JSON as fatal. The
install form carries nested errors of its own - language.error 704 when the
requested locale is not offered, game_dir.error when the folder is unusable - so
the loop ended before the install started and agent_job reported "exit 0".
A form with a non-zero game_dir.error now fails with that reason (800 reads as
"the game folder already holds a game"); otherwise the wait continues, and only
a top-level error still ends the loop.
* fix: move the form-failure regression out of the crowded test block
Keep the driver behavior unchanged; this only relocates the new regression case so
the branch can be merged with current main without a test-file conflict.
* fix: sync the agent-error change onto current main
Bring the two touched files up to the current main versions and apply the form
failure handling on top. This keeps the PR limited to the driver and its test
without pulling workflow files into the branch.
---------
Co-authored-by: visail <visail@users.noreply.github.com>
Co-authored-by: Kurt Himebauch <136133082+xXJSONDeruloXx@users.noreply.github.com>
* fix(audio): restart host after stalled wake recovery
* Serialize audio host restarts and make the stall counter race-free
* fix(audio): an overtaken restart leaves the socket alone and a sink guard only acts on its own host
---------
Co-authored-by: Kurt Himebauch <136133082+xXJSONDeruloXx@users.noreply.github.com>
* fix(game-env): keep DroidDeck's DLL overrides when a game sets its own
* fix(game-env): keep the game row when the merged DLL overrides pass 8192
---------
Co-authored-by: Kurt Himebauch <136133082+xXJSONDeruloXx@users.noreply.github.com>
* fix(graphics): fall back from unsupported auto display drivers
* refactor(graphics): drop the unused Auto recommendation lookup
* fix(graphics): repair automatic display fallback build
* test(wayland): keep Vulkan caller harness linkable
---------
Co-authored-by: Kurt Himebauch <136133082+xXJSONDeruloXx@users.noreply.github.com>
* feat(performance): add idle zram compression toggle
* Gate the idle compression toggle on memory cap support and refresh counters first
* fix(zram): retain launcher reclaim when idle compression is off
* test(memory): verify launcher-only reclaim signals
* fix(performance): keep game reclaim when focus is unknown
* fix(performance): say when to turn idle compression off and that it applies on the next session
---------
Co-authored-by: Kurt Himebauch <136133082+xXJSONDeruloXx@users.noreply.github.com>
* fix(fex): the x86 runtime is built from files inside it so FEX finds its libraries
* fix(fex): the x86 runtime keeps the permissions of the directories it is built from
* fix(fex): rebuilding the x86 runtime refreshes the Steam client links and removes read-only trees
* fix(fex): rebuilding the x86 runtime removes old trees that contain unreadable directories
* fix(fex): isolate generated rootfs files
* fix: Remote Play gets the Steam Deck controller
Steam's Remote Play client reads the controller itself from its own
streaming_client process. The input preload only exposed the virtual
Deck controller (and the DualShock 4 / DualSense pads that share its
code) to the process named steam, so in Steam Deck controller mode
streaming_client was refused /dev/hidraw16 and the stream got no input:
streaming_clien: deck: /dev/hidraw16 refused: not the Steam client
streaming_client now sees the same Deck, DualShock 4 and DualSense pads
as Steam. Each opener gets its own report stream from the read-only
ring, so the two processes do not compete for input. The Steam
Controller paths stay Steam-only: the paired controller's feature and
output slot is serialised only within one process.
Fixes#1860
* fix: Remote Play also gets the Steam Controller and touch controls
streaming_client now opens the Steam Controller pads (the app's
emulated one and a paired controller) and Steam's touch controller,
like the Steam Deck pad.
A paired controller's feature request and output slots, and the touch
controller's state, are shared with the app and written under a
seqlock that expects one writer. Their writers now also take a flock
on a lock file in the hook directory, so Steam and streaming_client
take turns. touch_state() was a template holding its own static mutex,
so each caller had a separate one; it now shares a single mutex.
The pad type and touch plug watchers run in streaming_client too, so
it gets the udev events for mode switches and replugs; those only reach
the process that injects them. Poking /dev watchers and moving event0
on the shared filesystem stay with Steam, so they happen once.
* fix: the shared slot lock fails safe and never waits forever
If the lock file cannot be opened or locked, ProcessSlotLock used to
carry on unlocked. Steam alone is still a single writer then, exactly
as before streaming_client could open these devices, so it carries on;
streaming_client now leaves the paired controller's feature and output
slots and the touch state alone instead (feature reads fail with EIO).
The first failure is logged.
The wait for the lock is now bounded: a session freeze can stop the
process holding it, and writers wait with controller_mutex held, so an
unbounded flock could stall all input in the other process. Feature
reads wait up to their 500 ms reply timeout, outputs 100 ms and touch
state 20 ms. When the deadline passes the lock is held by the other
process, so neither proceeds; the operation is skipped and logged.
* fix: Steam no longer turns motion off under its Remote Play client
Steam and streaming_client both set the Deck pad's IMU mode, and both
wrote the one word Android reads to decide whether to feed the gyro.
Steam keeps toggling its own mode during a stream, so it could switch
motion off while the Remote Play layout needed it, and the client never
re-sent an unchanged mode.
Each process now has its own word. Android reads motion while either
wants it, and ignores the Remote Play word once that process is gone.
* fix: Remote Play decides motion while Steam has set no mode
Until Steam published its IMU mode, Android reported the mode as unknown
without reading the Remote Play client's word, so a Remote Play request
to stop motion had no effect. The word that has been set now decides,
and the mode stays unknown only while neither process has set one.
The rule moves into ImuModes so it can be tested on the JVM.
---------
Co-authored-by: Kurt Himebauch <136133082+xXJSONDeruloXx@users.noreply.github.com>
* feat(compositor): pen samples drive the pointer like a mouse
Input record 13 carries the pen's state (in proximity, tip, right and
middle button) and its position in input space as 24.8 fixed point.
Hover moves the pointer, the tip holds the left button, and a record
without the in-proximity bit releases every button. Under a pointer
lock only the buttons pass. A button pressed or released mid-stroke
keeps the implicit grab on the window the stroke started in, unless
that window closed.
* feat(input): a pen moves the pointer while hovering, clicks with its tip and right-clicks with its side button
In Mouse mode (the default) a pen's hover moves the pointer, the tip
holds the left button and the side button right-clicks; Touch keeps it a
finger. The side button can send a middle click or nothing instead, and
a Bluetooth pen key counts as the side button while the pen is near.
With glasses or a program's pointer lock the pen drives the touchpad.
A hover exit followed within 50 ms by more hover or a touch keeps the
pen near, so a pen at the edge of its hover range does not flicker out,
and a hover that sends nothing for 2 s leaves proximity. On the desktop
a pen that comes near releases KWin's grab of a hardware mouse, so the
pen moves KWin's pointer. Whatever cancels touches also ends the pen,
and stylus devices no longer count as hardware mice.
* feat(input): pen mode and side button settings in the Controls tab and the session drawer
A Pen group follows the touch settings once the phone has a stylus
device or a pen event was seen, which is remembered as penSeen and kept
by a settings reset. It holds Pen (Mouse, Touch) and Side button (Right
click, Middle click, Off); Side button is hidden in Touch. Before
Android 14 a touchscreen reports the stylus source without a pen, so
there it counts only with its first pen event. The strings are
translated into all 32 languages.
* docs: describe pen input and its limits
---------
Co-authored-by: alien2003 <11610652+alien2003@users.noreply.github.com>
droiddeckctl input pen hover, tap, stroke and button register a virtual
direct pen with `adb shell uinput -` and play the gesture through it, so
Android's input reader makes the same stylus events a built-in pen does,
with pressure, tilt, distance, the eraser and both side buttons. The app
is not involved, which lets pen handling be tested without a pen.
Positions are fractions of the screen as shown, placed inside the
physical frame of the internal display viewport in dumpsys input: the
frame is smaller than the panel when `wm size` sets another aspect
ratio, and Android drops pen events outside it. The rotation and size
come from the same viewport. The values are checked before anything
runs on the device.
The script waits 1 s after registering, since uinput reads it in one go
and cannot wait for the device, and does not reset uinput's time base
after that, which would drop the first samples. Contact sends a pressure
of at least 1, because Android takes a pen at pressure 0 for a hovering
one, and a lift first moves to where it lifts, because Android's UP
repeats the last contact. A pen held still moves by one unit without
leaving the physical frame so that it keeps reporting, since the kernel
drops frames that change nothing.
Co-authored-by: alien2003 <11610652+alien2003@users.noreply.github.com>
* feat(xbox): stage the PlayFab Game Saves save-folder proxy from the Nexus runtime
Xbox titles that use PlayFab Game Saves, such as Forza Horizon 6, stop with
"Initialization Failed" E:0-17 right after sign-in. The SDK's default provider
needs Gaming Runtime save APIs that xgameruntime does not have, and its
in-process provider needs a save folder the title never passes on Windows.
xodus-nexus already builds a proxy for this into the runtime archive we pin
(scripts/runtime-compat, MIT): it keeps the title's SDK as
nexus_pgs_native.dll, sets ForceUseInprocGameSaves and passes the
PersistentLocalStorage PlayFabGameSaves folder. runtime.py now takes it and
its license from the archive, checked against runtime.lock.json, and
droiddeck-xbox stages it before each launch when the game's
PlayFabGameSave.dll has exactly the SDK's 40 exports. A game update that
brings a new SDK replaces the kept copy; anything unknown is left alone.
Unlike Nexus, no DLL override is set for the two DLLs: Wine has no builtin of
either, and forcing them native-only made Forza Horizon 6 fail with E:0-0-4.
* fix(xbox): check the whole PlayFab export table and never overwrite an unknown kept SDK
The SDK and proxy checks now also require the export address table to hold
exactly 40 functions, so a DLL with the same names plus an ordinal-only export
is no longer taken for the SDK. Before copying a new SDK to
nexus_pgs_native.dll, an existing file there must itself be a regular file
holding the SDK; an unknown file or a link is left as it is.
screencap without -d prints a warning before the PNG when it finds more
than one display, so droiddeckctl screenshot failed on foldables and
dual-screen phones. Without --display, screenshot and record now use the
physical display behind logical display 0 when there is more than one.
Co-authored-by: alien2003 <11610652+alien2003@users.noreply.github.com>
* fix(game-env): keep x64 system DLLs that only x64 code loads in ARM64 prefixes
The foreign-architecture repair treated every plain x64 DLL in system32 of
an ARM64 prefix as broken and swapped in the ARM64 builtin. ARM64EC games
load x64 DLLs fine, so this broke native-only DLLs such as the Khronos
vulkan-1.dll loader (vulkan-1=n leaves Wine nothing to load) and native
runtimes that games depend on.
An x64 DLL is now foreign only when Proton's own ARM64 programs import it,
found from the import tables of the Proton build's ARM64 executables.
Prefixes the old rule already repaired get their native copy back. This
replaces the Visual C++ runtime name list.
* fix(game-env): keep the old rule when Proton's programs cannot be read, restore the newest backup across gaps
* fix(game-env): number new backups above the highest one, treat truncated import tables as unreadable
* fix(game-env): treat an import directory outside every section as unreadable
* fix(game-env): treat truncated data directories and section tables as unreadable
* perf(game-env): index foreign DLL backups per directory
* fix(game-env): count only ARM64 Proton programs as roots, cover x64 component DLLs across launches
---------
Co-authored-by: xXJsonDeruloXx <danielhimebauch@gmail.com>
* fix(game-env): turn off Proton's tabtip unless the Steam keyboard is enabled
Proton's tabtip only opens Steam's keyboard with SteamDeck=1, but it always
runs UI Automation queries inside the focused game, and those calls crash
games that answer them (Godot 4.5 AccessKit). Game launches now add
tabtip.exe=d unless SteamDeck=1 or the user's overrides name tabtip.
* fix(game-env): match WINEDLLOVERRIDES modules split by spaces and tabs
* fix(game-env): count only tabtip.exe entries with a load order as the user's own setting
* fix(game-env): count *tabtip.exe and tabtip.exe.dll overrides as the user's own setting
* test(game-env): cover keyboard overrides during sync fallback
* fix(input): stop controller rumble when the game that started it is gone
A crashed game never sends the stop for a held rumble, so the keepalive re-armed it every 1.5 s until the session ended. A held effect now stops on the next keepalive once the process that sent it or the Steam game it started in has exited. The fake controller also stops its rumble when it's closed or the playing effect is erased, like the kernel does.
* test: read the test's own pid from /proc/self
* fix(input): track who plays rumble on each slot, check the game when a hold starts
The process that plays an effect now owns it, and only the handle currently playing on a slot sends the stop when it closes or erases its effect. A held effect records whether a game is running when it starts, and keeps checking that its sender still exists even when its start time couldn't be read.
* fix(input): only cache a running game, not its absence
A new hold claimed right after a no-game result reused it, so a game that started within the cache window was never watched.
* fix(input): treat a vanished sender of our own user as gone
Guest processes run as the app's user, so the app can always see them in /proc. If one is missing at the first lookup it already exited; only senders of another user (root-spawned guests) are left unchecked.
* fix(input): a stop only ends rumble the same process started
The fake controller's playing-handle tracking is per process, so another process closing or erasing its older effect still sent a slot-wide stop. The app now ignores a stop whose sender isn't the one behind the slot's current effect; stops from an unknown sender work as before.
---------
Co-authored-by: Tapuuk <177422350+Tapuuk@users.noreply.github.com>
* fix(ci): a test build's files outlive the catalog that names them, and a merged PR's build lasts until Preview carries it
- A new push's PR release keeps the previous push's files until the catalog names the new
ones, then five minutes more, so a download started from the old catalog still finds its APK.
The app also reloads the catalog and retries once when a test build's download fails.
- Closing a PR without merging still deletes its test build. A merged PR's build stays, and
stays listed, until the newest Preview build was built from a main holding the merge, or
three days pass (docs-only merges build no Preview). Main's build, the PR cleanup and the
sweep share one script for this.
* fix(ci): name the current push's APK in the catalog and prune nothing it still names
* fix(ci): only a Preview with every APK carries a merge or is offered
* fix(ci): publish no preview while none has every APK
* test(ci): build_catalog publishes no preview while its APKs are uploading
* fix(venus): DXVK runs on Mali GPUs without dual-source blending
DXVK requires dualSrcBlend for D3D11 and skips any GPU without it, so on
Mali through Venus no adapter was found. The Mali compatibility layer now
reports the feature and maxFragmentDualSrcAttachments 1, keeps it out of
the driver's device, turns fragment outputs decorated Index 1 into Private
variables (shader modules and inline stage code), and maps SRC1 blend
factors to source alpha in pipelines and vkCmdSetColorBlendEquationEXT.
Only active when the driver lacks the feature.
Adds a mock loader and driver test for the layer, and fetches the
layer's pinned headers for it in CI.
* build(venus): pin the Mali component with dual-source blending
* fix(epic): install the Epic Games Launcher from its Linux .deb
Epic no longer serves the Linux AppImage: the installer URL answers 404
errors.com.epicgames.launcher.app_direct_url_not_found (30003), so Install
failed for everyone. Epic now ships EpicGamesLauncher-x86_64.deb
(0.113.0+g2164614).
- The installer downloads the .deb, checks its ar magic and the CDN ETag,
and droiddeck-epic unpacks its data.tar.* member straight from the
archive.
- The .deb links WebKitGTK 4.1, JavaScriptCoreGTK 4.1 and GTK 3, which the
Steam Runtime 4 image does not ship. 32 Debian 13 amd64 packages, pinned
by SHA-256 and size (60.2 MB download, 201 MB unpacked), are unpacked
into the launcher's desktop/ folder (shared libraries only) and put on
its LD_LIBRARY_PATH. Debian 13 matches the runtime's own base, so only
sonames the runtime lacks are added. Each package falls back to
snapshot.debian.org when the deb.debian.org pool has moved on.
- WebKit starts its helper processes from its built-in
/usr/lib/x86_64-linux-gnu/webkit2gtk-4.1 path, so each launch links that
folder in the runtime to the layer's copy.
- An installed AppImage launcher keeps starting through its AppRun; the
next update check moves it to the .deb.
Closure checked offline: every ELF in the .deb and the layer resolves with
the runtime's own ld-linux-x86-64.so.2 inside a sandbox holding only the
runtime, the layer and libGLESv2 (0 missing, 0 version or undefined
symbol errors with LD_BIND_NOW).
Based on zooluis's research in #2268.
Co-authored-by: zooluis <150430329+zooluis@users.noreply.github.com>
* fix(epic): provide desktop GLib data paths
* fix(epic): keep archive symlinks from redirecting the desktop layer and icon
---------
Co-authored-by: zooluis <150430329+zooluis@users.noreply.github.com>
* feat(updates): install any kept Preview build, link builds to their PR and commit, flag stale test builds
* fix(updates): address review of the Updates tab history and test-build watch
* fix(updates): notify on switch to a followed PR, keep higher-version rebuilds installable
* fix(ci): let full reruns replace every artifact, note only expired PR builds
* fix(ci): leave the rebuild note only when the PR build is too old to rerun
* fix(ci): poll unfinished PR builds together and queue version-bump runs
* fix(ci): also rebuild PR builds that were running when the versionCode changed
* fix(ci): rebuild fork and just-finished PR builds, recheck the PR head before a rerun
* fix(ci): fail the rebuild sweep when finding candidates fails
* fix(ci): time the bump from the rebuild run's creation and scan unfinished builds of any age
* fix(ci): check the latest build of every open PR instead of scanning run history
* fix(ci): count PR builds that finish between the version push and the rebuild run
* fix(ci): use the push time from the event as the rebuild boundary
With a single GPU heap DXVK reports the whole heap as shared memory too, so games still saw ~8 GB as shared even with the cap on. Set dxgi.maxSharedMemory to the same value, like BattleNet already does.
Co-authored-by: Tapuuk <177422350+Tapuuk@users.noreply.github.com>
* fix(battlenet): a Battle.net download that stops moving ends as retryable, and a killed update comes back as an update
A job reply without a state or byte counts no longer counts as a started
download, and an Agent job that reports no change for ten minutes is
stopped with its Agent and fails with a Retry instead of waiting forever.
Updates remember their game folder in the saved queue, so one restored
after the app was closed runs agent-update on that folder instead of a
fresh install.
* fix(battlenet): a stalled job stops only the Agent it started
A game or Battle.net client running in the prefix keeps running when a
stalled Agent job is ended, and the progress test keeps the job alive
across polls with a controlled clock.
* fix(battlenet): only real progress holds off the stall timeout
The download rate and time estimate can change while no bytes move, so
the stall timer now resets only on byte counts, progress, state, phase,
pause or error.
* test(battlenet): bound the stalled-rate fake child's polls
* fix(native): drive links stored as rootfs paths reach the game library mount
* fix(native): relative drive links reach the game library mount
* fix(native): keep the path after a relative drive link as written
* fix(native): relative links that climb past the rootfs root stop at the guest root
Proton copies default_pfx/dosdevices/z: into each prefix with readlink and
symlink. The relinked target climbs as many folders as default_pfx is deep,
which is one more than a Steam prefix, so natively the kernel left the rootfs
and Z: pointed at the app's files folder. Proot stops ".." at the guest root;
the hook now does the same for links it resolves.
* fix(native): resolve drive links in prefixes stored in bind sources outside the rootfs
* fix(native): detect equal-length mount conversion for bound prefixes
* fix(session): the Steam UI on the Mali bridge stops flickering
On the Mali bridge Steam's own web helper layout makes the Deck UI footer
and overlays flicker (Mali-G78 MP14). When the browser UI is on the GPU,
default to ANGLE on Vulkan without Chromium's Vulkan compositing. Values
set by the user still win, and the software UI path is unchanged.
* fix(session): keep empty Mali bridge CEF settings as set
With "Run without proot" on, the Steam client hung about a second after
login and aborted three minutes later with "fatal stalled cross-thread
pipe". The directory cache holds its lock while it adds an inotify watch.
Without proot that call reaches the native userland hook, whose
inotify_add_watch creates a missing directory with mkdir() by name. That
mkdir resolves to the cache's own wrapper, which waits for the same lock
on the same thread. Steam's IPC threads then queue behind it.
The cache now counts the locks each thread holds. While a thread holds
one, calls that come back into the cache (opendir, the change wrappers,
created files, missing-name checks, closedir of a stream it did not open)
go straight to the next library. The same guard covers the hook's
remove(), which calls unlink() by name while the cache's remove wrapper
holds its operation lock.
* Stop searching whole libraries on every game launch and session start
The install script search ran over every library whenever any game's
manifest changed, and again on each launch. It now runs per game, only
when that game's build changes, and a launch that names its scripts
does no search at all.
A store game's shortcut walked its install folder on every scan instead
of reusing the ranking the scan keeps.
* Search a library for install scripts after the session has started, not before
* fix(session): keep deferred seeding off a running prefix and recheck old folder caches
* test(session): bound the held library search in the deferred seeding test
* fix(session): search a game again when its install script search failed
* fix(steam): share the Steam app's prefix with shortcuts of the same install
* fix(steam): prefer the matching install's save prefix
* fix(steam): tolerate an unreadable library when linking a shortcut prefix
A library folder that cannot be listed made the shortcut writer exit, so no added game was registered.
* fix(steam): repair a dangling shortcut prefix link and keep Steam library installs to their own prefix
* fix(steam): only change shortcut prefix links the importer created
* fix(steam): record a prefix link only when the importer created it
Android's FUSE daemon has no symlink or link, so those calls on a storage card return ENOSYS. The fast path read any ENOSYS from its trampoline as a seccomp trap and stopped for the whole process. It now asks again with the same call number and invalid arguments: a trap answers ENOSYS again, anything else means the call reached the kernel and only that call is repeated. Folders opened for a refused call are still closed.