* feat(display): zero-copy presentation toggle and compositor display buffers
Adds a Zero-copy presentation switch under Steam Settings, Display,
Session Display (on by default), and a display-buffer allocator in the
compositor: a Vulkan driver that states displayBuffers asks it for the
memory of the images it exports, so frames presented through the nested
compositor are gralloc buffers that go on the display layer without a
copy. Compressed buffers are offered only where the device's allocator
matches the layout the drivers render to; everything else stays on the
copy path.
The private buffer protocol is renamed to droiddeck-ahb-v1.
* fix(display): zero-copy frames keep the full refresh rate
Two buffers set on the game layer inside one refresh replaced each other, and a frame that slipped into the next refresh made the compositor hold and drop the on-time frame behind it. The layer now queues buffers, and a refresh takes a second frame when the one before it took none. The pacing tool no longer counts its dump time in the frame rate.
* Keep cropped scenes on the display layer and pace layer frames evenly
Accept any in-bounds source crop for the display layer and map the draw
geometry the same way the copy path does. Time layer frames against the
display's frame timeline, and when the game's rate is a steady whole
fraction of the refresh rate show each frame a fixed number of refreshes
after the last so uneven arrivals no longer reach the screen.
* List zero-copy in the settings map
* Hold display buffers until the display releases them
A buffer the game or gamescope rendered straight into went back to its
client as soon as the next one was latched, with the display's release
fence attached to the dma-buf. The KGSL driver does not wait on that
fence, so the client could draw into a buffer the panel was still
reading. Display buffers now wait for the release fence before the
release event, and gamescope composites only into output images the
host has released.
* Keep the game picture copy-free when an overlay has no display layer
When the display cannot give a second layer of its own to an overlay,
the compositor tells gamescope how many planes it can show directly.
gamescope then composes its overlays into the game picture, which still
reaches the display without a copy.
* feat(session): the panel refresh rate follows the session's frame rate
The session learns the panel's refresh rates and reports the refresh rate and
frame rate it wants. The panel moves to the highest rate the frame rate divides
evenly, frame generation counts at its output rate, and a panel whose rate the
system holds offers only that rate.
* feat(session): the panel follows a frame rate the game holds on its own
The compositor reports the game's frame rate once a second. A rate that
holds for three seconds and divides a panel rate becomes the content
rate when neither the app's limit nor the session's limiter is setting
the pace, so a game capped in its own settings gets a panel rate its
frames divide into. A rate that was dropped has to hold twice as long
before it is used again.
* Show generated frames on the game's display layer
With frame generation on, the game's own frames stay on their display
layer untouched and each generated frame is placed on the same layer
between them, timed across the game's frame interval. The compositor
pass is kept when effects, HDR routing or a cursor need it, or when the
panel cannot show the multiplied rate.
* Keep scaling, generated frames and HDR on the display layer
A scaler or frame generation with zero-copy on now draws once into the
display layer instead of falling back to the copied surface. HDR output
goes to the layer when the panel supports it; on a panel without HDR the
picture is tone-mapped on the same path, and the toggle is labelled to
match what the panel can do.
* Spread a frame limit the refresh rate does not divide evenly across refreshes
* Cover the spare-tick and panel-rate paths in the compositor source tests
* Pin the gamescope build with the display-plane, release, refresh and limiter patches
* Give the layer and terminal-caller harnesses the black fill state they compile against
* feat(display): switch HDR during a session without restarting the app
The compositor now offers HDR whenever the device can present it, and the
HDR setting only decides whether the session uses it. Both HDR switches set
gamescope's hdr_enabled, the compositor's HDR output and zero-copy for the
running session. gamescope patch 0139 lets hdr_enabled change after start.
The 'Restart the app to apply.' hint is removed from every locale.
* Remake the output images in the new format when HDR is switched during a session
* Pin the gamescope build that switches HDR during a session
* Apply a saved HDR opt-out at session start and keep HDR retries with their session
* Serialise the HDR output switch with the gate opening
* feat(display): keep the client's HDR setting and the session's in step
The session publishes its HDR state with the other device controls and the
client helper applies it to the client's own display setting. A change made in
the client is reported back and goes through the same switch the drawer and
Session Display use, so all three always show one value.
* fix(desktop): keep the display-buffer socket when the runtime directory is cleared
The desktop launcher removed everything in the runtime directory except the
compositor's Wayland socket, which took the display-buffer socket with it, so
no desktop program could ask for display buffers and every frame was copied.
* fix(display): the client's HDR setting follows the session in every client mode
The bridge only ran when a variable nothing sets was present, so the client's
HDR setting and the session's never met. It now runs whenever the session
publishes an HDR state, and a client that has no such setting is asked again
only every ten seconds.
* fix(display): harden display-buffer hand-off, layer fallbacks and HDR sync
- Stop closing a buffer handle's descriptor the allocator still owns, and free an allocation whose reply could not be sent.
- Rebuild the advertised buffer formats when zero-copy is switched during a session.
- Fall back to the copy path when a layer buffer cannot be allocated, and hide the game layer when it is skipped for a frame.
- Keep a release fence that has not signalled instead of rendering into a buffer the display still reads.
- Ignore a refresh-target reset from a client that does not own the target.
- Restart the content-rate measurement after a pause, clear it when the game stops, and lengthen engagement only for a rate that was released before.
- Compare colour conversions by their values, and read padded cursor buffers at their row width.
- Use the running session's mode for the HDR and zero-copy settings, probe the display before screen effects are pushed, retry a held panel mode, and ignore callbacks after the activity is destroyed.
- Write a newer HDR value while an earlier write is settling, and reapply the value after the bridge is reinstalled.
* fix(epic): start Epic titles that check their parent under an EpicGamesLauncher.exe stand-in
Rockstar's launcher only accepts an Epic copy of GTA V when a process
named EpicGamesLauncher.exe started it. DroidDeck's Epic client is a
Linux program, so the launcher logged "Epic Games Launcher not detected
as parent process", failed to relaunch through Epic and showed the game
as unowned.
- tools/epic-launcher: a small Windows EpicGamesLauncher.exe that starts
the game with the rest of its own command line, unchanged, waits for
it and returns its exit code. It ships as the epic add-on pack.
- The Epic .droiddeck-launch.bat runs the game through it for Epic
titles known to need it (GTA V, GTA V Enhanced, RDR2, RDR, GTA SA DE,
Returnal, Phantom Blade: Executioners), or for any Epic game whose
per-game environment sets DD_EPIC_PARENT=1; DD_EPIC_PARENT=0 turns it
off. Those titles also start without Steam's SteamAppId. Without the
staged stand-in the game starts directly, as before.
- Steam launch options now reach Epic games (%*).
- The launch hook fetches the pack when such a title finds it missing.
- Rockstar's launcher found no Social Club SDK in the prefix and ran
Social-Club-Setup.exe /silent, which never exits under Wine. For Epic
titles that carry a Rockstar SDK installer, the hook now extracts the
SDK from the launcher's own Redistributables copy (the version the
launcher compares against) or, before the launcher is installed, from
the game's copy, and registers it. It re-extracts when that installer
changes and leaves the Rockstar Games Launcher key alone, so PlayGTAV
still installs the launcher on first start.
* fix(epic): fetch the parent stand-in exactly when the game will use it; keep Cargo output out of source digests
The launch hook runs before droiddeck-game-env applies per-game
variables, so it now resolves DD_EPIC_PARENT through
droiddeck-game-env's own apply_config and game_id: an unlisted title
with DD_EPIC_PARENT=1 fetches the pack, a listed title with
DD_EPIC_PARENT=0 no longer waits for it.
runtime_inputs no longer hashes the target directory beside a Cargo.toml
under its source paths, so a local cargo build of a Windows helper does
not fail verify(). tools/epic-launcher gets the same .gitignore as the
other helpers.
* fix(epic): a DD_EPIC_PARENT in the game's sidecar env decides the stand-in fetch too
The .bat sets the sidecar's env before it reads DD_EPIC_PARENT, so that
value overrides the game environment there; the launch hook now gives it
the same precedence when deciding whether to fetch the pack.
* test(epic): keep an inherited DD_EPIC_PARENT out of the launch hook tests
---------
Co-authored-by: MaxsTechReview <maxjividen@gmail.com>
* fix(display): read linear client frames at their row pitch when the driver has no explicit modifier layouts
* fix(display): keep row-pitch copied client frames eligible for layer presentation
* fix(display): order the readback layout change after the staging copy
* fix(display): skip the modifier import query when the driver lacks VK_EXT_image_drm_format_modifier
* test(display): the compositor's source-extracting tests follow the linear dma-buf helpers
vkp_image_destroy now frees through destroy_image_objects, render_impl stages
linear dma-bufs and the external-image release asks foreign_image; the two
tests that compile these functions out of vk_present.c extract or stub them,
with the image's new buffer fields in their fakes.
---------
Co-authored-by: Kurt Himebauch <136133082+xXJSONDeruloXx@users.noreply.github.com>
Since #1593 every process except the Steam client gets DroidDeck's udev
answers through dlsym. Steam's Remote Play client, streaming_client, is
an SDL3 program: for each input node it treats as a joystick, SDL3 asks
udev_device_get_driver for the device that udev_device_new_from_devnum
returned. The preload answered new_from_devnum with its own handle for a
virtual pad but did not answer get_driver, so the real libudev read the
handle as its own and streaming_client crashed before the stream opened.
It reaches that call whenever it can stat a pad node: the Xbox 360 pad,
Steam's own uinput gamepads, and since #2033 the pads it reads.
streaming_client now keeps the real libudev like the Steam client, and a
virtual pad answers get_driver with no driver, so other SDL3 programs no
longer crash on it.
* fix(input): Steam finds a DualShock or DualSense chosen mid-session
Android lets an app open a uevent netlink socket but not join its multicast
groups, and libudev joins none when no udev daemon runs, so the udev
monitors Steam's SDL opens heard nothing and the pad switch's add and remove
events reached no one. SDL only noticed a new PlayStation pad when the old
one happened to fail a read. A monitor left without a subscription is now
swapped for the session's stand-in under the same descriptor, so it
receives the injected events.
* test(preload): stub the udev monitor bind hook in the CDP guard build
* fix(session): remove the keep-top guard from other displays
#2763 put a transparent KeepTopActivity on every other display while a
session was on top, so lmkd killing that display's home could not move focus
off the session. A/B on a 12 GB AYN Thor (Android 13) and a Retroid Pocket
Duo (Android 16) found no case where it kept a session alive: with steady
pressure the bottom home (stock launcher or Cocoon) was killed up to 400
times per run without taking focus, and a burst big enough to matter makes
lmkd kill the session at adj 0 with or without the guard.
Its side effects were real:
- Android's ActivityRecordInputSink made the bottom screen ignore touch
(worked around in #2910 by stepping aside on touch).
- Cocoon tracks each display's top activity, so it could not suspend or
resume DroidDeck cleanly.
- The Thor's Game Assistant gives every app with an activity on top of the
bottom display that display's volume, so DroidDeck's audio followed the
bottom screen's volume slider.
Removes KeepTopActivity, the focus bounce and light pause, the memory
pressure trigger and their tests. onPause runs its departure cleanup every
time again.
tools/memory_guard_ab.py gains a burst mode, reads oom_score_adj without
su (lmkd kills the root manager app and su can then open its request screen
over the game), handles Android 13 dumps, a hung stop and a session that
does not start. docs/development/memory-guard-ab.md has the Thor results.
* test(session): the guard A/B fill mode starts its counter again, and a pressure run with no completed run fails
* test(session): the burst seed is rebuilt unless it is exactly 256 MiB
* test(session): the guard A/B burst takes its last partial chunk, and only a hog run that finished counts
The proot pack pin check failed on GitHub-hosted runners for PRs that do
not touch proot. The hosted image puts the latest upstream zstd (1.5.7)
in /usr/local/bin, while the self-hosted runners use zstd 1.5.5, and
zstd -19 output differs between those versions for identical tar input.
tools/packs/build.sh now compresses every pack with the zstd version
pinned in tools/packs/zstd/release.env: the system zstd when it is that
version, otherwise the checksum-verified upstream release built once
into the pack input cache.
* fix(session): the bottom screen takes touch again while a game runs
Since #2763, a transparent KeepTopActivity covers every other display while a
session is on top. Its window is NOT_TOUCHABLE, but Android gives a
translucent activity alone in its task an ActivityRecordInputSink that eats
every touch on that display (ENABLE_TOUCH_OPAQUE_ACTIVITIES, on for this
target SDK). With the dual-screen panel closed, the bottom screen's launcher,
Cocoon or any other app could not be touched until the session ended, and
the guard stayed over it after Home/PiP as well.
- The guard now takes touches itself: a touch removes it from that display.
- It comes back when the session is top-resumed again, or after 5 s if the
session kept the top spot (the user touched the bottom screen once and
stayed in the game).
- Stopping or entering PiP removes the guards; PiP keeps the session at adj
50 with or without them, so they protected nothing there.
A/B on a Retroid Pocket Duo (Android 16, Cocoon as bottom home): the guard
is on top in every state it was on top on main, except the 5 s after a
bottom touch and PiP. Under lmkd pressure (kills down to adj 50, bottom
home killed 14-31 times per run) neither build lost the top spot.
* test(session): A/B tool for the keep-top guard on rooted dual screens, with Duo findings
* test(session): the guard A/B tool stops on a failed session start and cleans up an interrupted pressure run
Components > Proton gains an Experimental builds card that installs a Proton build from a .zip, lists it as Experimental-<name> and removes it with its stored and unpacked originals and selections. Replacing a build keeps its user settings and is safe to interrupt.
Co-authored-by: maxjivi05 <maxjividen@gmail.com>
* feat(ubisoft): keep Denuvo game tokens per account and product until the game invalidates them
* feat(ubisoft): sync cloud saves through Ubisoft's cloud save service
* fix(xbox): turning cloud saves off passes the offline mode the game save runtime reads
* fix(ubisoft): Ubisoft games list their shared prefix, so they get a saves and cloud tab
* feat(ea): sync cloud saves through EA's cloud sync service
* fix(ea): sync at EA launch and exit, keep one rule snapshot, and check the cloud copy under the write lock
* fix(ubisoft): exact slot versions, scoped save export, and a Denuvo cache bound to its account
* fix(ea): fresh rules per sync, checksums required, backup before restore, and sign-in shown on the saves tab
* fix(ubisoft): launch-time sync on the shared prefix, saves scoped to the game, and Denuvo bound to each launch's account
* fix(ea): back up only the saves a restore replaces, refuse truncated manifests, and need a master title id
* fix(ubisoft): treat a slot whose bytes changed since the last sync as a conflict before uploading over it
* fix(ea): one resolved save folder per sync, refuse case collisions, and walk each folder once
* fix(ubisoft): sync only identified slots, keep live saves and backups safe, and tie a pending eviction to its account
* fix(cloud): a forced download fetches every saved conflict and keeps the ones it could not write
* test(ea): keep the cloud save cases in EaTest
* fix(ubisoft): report only written slots, keep drift conflicts, read whole headers, and never rename a named eviction
* fix(ea): keep real save folders in the inventory, back up any restored file, refuse duplicate or malformed cloud listings
* fix(cloud): commit Ubisoft slots one at a time and stop on a newer cloud write, name skipped and blocked slots, keep unsent conflicts
* fix(ubisoft): acknowledge an invalidation only once its marker is published and never serve a kept token after it
* fix(cloud): a cloud request the launcher cannot write still starts the game and keeps the exit upload
* fix(cloud): scope Ubisoft sync state to the account and product, compare alike slots, keep committed progress, and name partial slots
* fix(ea): ask for sign-in after a rejected refresh, upload saves reached through folder aliases
* fix(cloud): a launch that stops waiting for the cloud download claims it back, so no save is written once the game starts
* fix(ubisoft): name the account in an invalidation marker and never hold the token lock across a pipe write
* fix(ea): only invalid_grant asks for sign-in again, and case collisions count only among synced saves
* test(epic): let the launcher's ask doubles take the claim flag
* fix(ea): apply save rules in their order, match bare patterns inside the save folder, and resolve LocalLow and install folders
* fix(ubisoft): stamp a fresh identifier into a new save that has none, so it can sync
* fix(ubisoft): answer a burn ticket request as unavailable instead of leaving the game waiting
* fix(cloud): read EA manifests with the XML parser, clear conflicts whose sides match, and bound the claim and stall tests
* feat(xbox): install MSIXVC2 packages from their encrypted content boxes
* feat(xbox): run a package's custom install actions once per prefix
* fix(xbox): launch the program a launcher menu names instead of the menu
* fix(xbox): check free space before an MSIXVC2 install starts
* fix(xbox): keep a forwarded launch path relative when the install folder is reached through a link
* fix(xbox): rebuild the MSIXVC2 patch on the final legacy install
* fix(xbox): keep a backup whose release fails, and test an interrupted restore
* fix(xbox): verify resumed msixvc2 files, contain writes, decode install action arguments
* fix(xbox): keep one completion record per msixvc2 file, never follow a linked install state
* fix(xbox): drop a torn msixvc2 completion record before appending to it
* fix(xbox): repair a torn msixvc2 record from its tail instead of rereading it
* fix(game-env): run Kingdom Come: Deliverance II at D3D12 feature level 12_0
* fix(game-env): restore feature level 12_2 and shader model 6_9 for Kingdom Come: Deliverance II
* feat(xbox): install legacy EAppx titles through Windows Update
A legacy Store title does not ship as MSIXVC. It ships as an encrypted
EAppx bundle, which streaming rejects, so the store could list the game
and never install it.
Accept EAPPX and EAPPXBUNDLE beside MSIXVC, carry the format through the
catalogue, the install record and the cached library, and dispatch
legacy-install for those formats.
Two backend patches do the work:
- droiddeck-legacy-packages.patch lets the plan, license and extract
verbs handle a legacy package, and expands a bundle in place (nesting
bounded at three), decrypting each inner EAppx with the same keys.
- droiddeck-legacy-install.patch adds legacy-install: resolve,
license, download, extract, hoist AppxManifest.xml to the game root.
Resolution asks the Xbox content service first and Windows Update
second, because some legacy products return no files from the content
service at all. The WU endpoint needs no Xbox credential but chains to
Microsoft's ECC Product Root CA 2018, which Android's CA bundle does
not carry, so that one public root is pinned for those requests.
The manifest reader accepts AppxManifest.xml as well as
MicrosoftGame.config, since a legacy package carries only the former.
Running it against a real title exposed four things that only show up at
full size:
- A licence names a key by its 16-byte content id, while a bundle header
names it as a (content id, package id) pair. Reading the 16-byte id
yields a different pair, so a complete key file reported every key
missing and no bundle could be opened. Keys are now aligned against
the header's own ids before the header is judged.
- Windows Update answers with several updates whose PackageContentId
differs from the bundle's own. Licensing used to take the first and
fail with content-http 400; every candidate is now tried in order,
preferring the one the container is named after.
- A container already in .xodus-container is reused rather than fetched
again, so a failed run does not cost another download of tens of
gigabytes. The space preflight no longer counts a container twice for
the same reason.
- A bundle that carries add-on packages unpacks each into its own
folder, leaving the manifest one level down. Hoisting lifts the
largest folder that holds a manifest, so the game still lands at the
root beside its add-ons.
Unpacking now reports bytes written, so the install bubble fills while a
package is decrypted instead of holding a single unchanging word.
* fix(xbox): unpack a legacy package across cores and report the bytes
Unpacking one title ran as a single thread on a saturated core at about
40 MB/s. Files sit at independent offsets, so each worker now opens its own
handle and takes every Nth file, with a 1 MiB read buffer in place of the
8 KiB default that turned one 64 KiB block into eight reads. Measured on the
Forza Horizon 4 bundle, writes went from 40 MB/s to about 200 MB/s.
Two things the first full-size run exposed:
- The container was deleted only after the whole nested tree was unpacked,
so a title that holds its package as one member held the archive and the
decrypted copy at once. On this device that runs out of space partway
through the second stage. The container is now deleted once its members
are on disk, which frees the archive before they are decrypted.
- A bundle member is written as a single file, so a counter that advances
when a file finishes stays at zero for the whole of the longest stage.
The reported figure now also follows the growth of the destination while
that is the case, and never moves backwards when the container is freed.
Progress is exact during the per-file stage: each file's declared length is
added as it lands, instead of walking the whole destination every tick.
* docs(xbox): record the completed legacy install
The evidence section said a finished legacy install and its decrypted
contents were unverified, because the first run was still unpacking when it
was written. That install has now completed on the same device: the
85,219,173,025-byte container produced 79.3 GB at the game root with
AppxManifest.xml and the package DLLs directly beneath it, and the launcher
lists the title as installed.
It also records what unpacking costs, since that decided the change: one
thread held a core at 100% for about 40 MB/s and four reach about 200 MB/s,
and releasing each container once its members are on disk is what keeps the
peak footprint at one package rather than the archive plus its contents.
The launch is not part of this evidence, and the entry says so.
* fix(xbox): place the 64-bit framework beside a legacy title
A Windows Update framework category lists one package per architecture under
identifier-only names. The first package was unpacked, which on this device was
the x86 build, so a 64-bit title got 32-bit DLLs and every load failed with
STATUS_INVALID_IMAGE_FORMAT. Candidates are unpacked now and only the one whose
manifest declares ProcessorArchitecture="x64" is kept.
The framework folder was also never created, so a finished download failed at the
move with "no such file or directory".
unzip.rs belongs to this patch: legacy-install calls it and the recipe left it out,
so a rebuild from the pinned source could not compile.
* feat(xbox): report a UWP entry point at launch
An unpacked package can name a COM class as its entry point instead of
Windows.FullTrustApplication. That class is a UWP application, which expects the
app model to activate a view; Wine has no host for it, so the launch died inside
the loader with no explanation. The launch now reads the entry point and reports
uwp-entry-point, and full-trust packages are unaffected.
Forza Horizon 4 is such a package: its manifest names Forza.App. Its frameworks
are installed and the loader is clean before that point.
* fix(xbox): report why a launch was refused
A failed prepare replaced the backend message with a fixed sign-in hint, so a title
that was not installed or a runtime that refused all read as a bad account. The
reason is kept, with paths and URLs dropped, and written to the store log.
* fix(adb): dismiss the keyboard on Search and Go
Search and Go were terminal IME actions but were not handled, so focus stayed in
the field and the keyboard covered the results it had just fetched.
* fix(xbox): keep a cache row without a legacy format plain
Decoding added a format key with an empty value to every cached title, so a
library restored from storage no longer matched the one that was saved.
* test(ui): match the manifest message a legacy package reports
The message covers both a MicrosoftGame.config and an AppxManifest, so the
assertion follows the text the content dialog now prints.
* fix(xbox): refuse to start a title that needs the Windows app model
A legacy package that names an entry point other than
Windows.FullTrustApplication is a UWP application. Wine has no app-model
host, so starting its executable crashes inside the loader and the launch
looks like nothing happened. Read the entry point from the manifest the
installer already parses and stop the Play action with a message instead.
Forza Horizon 4 names Forza.App, so it installs and reports as installed
but cannot be started here yet.
* fix(xbox): dispatch on the container format of the chosen package
The catalogue records the format of the first installable desktop package, and
the picker only replaced the content id. An offer that lists MSIXVC and a legacy
container would then hand the legacy id to streaming, or the streamed id to
legacy-install, and the install failed after resolution had succeeded.
The choice now carries its own format and the catalogue value only fills a gap.
* fix(xbox): keep an extraction reason that the sanitizer rewrote
The extraction sanitizer replaces anything outside letters, digits, space, dot,
underscore and dash with a question mark, so a reason such as "(os error 28)"
arrived as "?os error 28?" and the allowlist dropped the line. The failure then
showed only the stage code, with no cause.
Add that replacement character to the class the allowlist accepts.
* fix(xbox): print the reason a launch was refused
The account channel sends a reason with a refusal, and the guest replaced it
with a fixed sign-in message, so a title that was never installed still read as
a bad account. The guest now shows the reason it was given, and a token holding
a path is dropped whole instead of having its slashes removed and its directory
names kept.
* build(xbox): leave RUST_TEST_THREADS unset when the host has no value
The recipe always passed the variable, empty when the host had none, and the
pinned test harness rejects an empty count. On an ARM64 host that runs cargo
test, so the default local build failed before compiling.
* fix(xbox): rebuild the backend patches from the tree that ran
The two patches in this branch were not the ones the verified install ran, and
one of them did not compile. `unzip.rs` inflates deflated entries but the
dependency that provides the inflater was never added, so `prepare.py` produced
a tree that failed at `flate2::read::DeflateDecoder`. Anything else missing fell
into the same gap: the install stage reported no bytes, so the bar held one
value for the whole unpack, and a container a stopped run had finished was
downloaded again.
Rebuilt from the patched source, and fixed the defects a review of the patch
found:
- Unpacking reports bytes again: the workers count each file's declared length,
and for the single-file bundle member the folder's growth stands in, which is
what the device run showed.
- A finished container is reused, so a retry after a failure past the download
does not spend hours fetching it again. The space preflight counts it as
reclaimable, since the retry truncates it first.
- An install over a folder that already has a manifest replaces the old files
instead of leaving the new package nested and reporting success. A first
install still refuses to merge into an existing target.
- The manifest search looks at the depth a nested bundle writes, not only one
level down.
- `withdraw_libraries` removes only the DLLs `copy_libraries` recorded copying,
so a framework replacement cannot delete a library the title owns.
- ZIP64 sizes and offsets stay `u64`; truncating them to `u32` read the wrong
local header past 4 GiB.
- The extraction checks the blockmap length against the footer's before writing,
which the crate only does when asked.
- The container being unpacked is never treated as a nested member, so
`extract-eappx title.eappx .` no longer re-enters and deletes its own input.
- `flate2` is declared and the lock is updated.
`prepare.py` reproduces this from a pristine checkout and `cargo test` passes on
it.
* fix(xbox): apply the legacy install patch over the Nexus 0.2.15 backend
* fix(xbox): install only the newest x64 build of a legacy title and size the space check at its real peak
* fix(xbox): install a store package that is a plain archive instead of an XVD
* fix(xbox): refuse a package entry that ends before its recorded size
* fix(xbox): credit only complete staged containers toward the free space a legacy install needs
* fix(xbox): bound each package entry to its data and check ZIP64 decoded sizes
* fix(xbox): refuse duplicate package names and clear an unfinished download before measuring space
* fix(xbox): bound package entries by the next header and stage a plain package until it validates
* fix(xbox): hold the install folder lock through a legacy install
* fix(xbox): fall back to an older build when Microsoft refuses the newest one a license
* fix(xbox): keep the registered device across sign-out
* feat(xbox): explain device-limit and license refusals, with a link to manage devices
* fix(xbox): locate each build only once licensed, roll back a failed package swap, report the final license answer
* fix(xbox): skip trial and preorder packages, read runtime behavior, keep licensing timeouts
* fix(xbox): keep a failed package swap recoverable, size bundles up front, report key-write and framework errors cleanly
* fix(xbox): drop a pending manifest check on any newer launch, keep committed backups out of restores, match the app-model order
* fix(xbox): cancel pending launch checks on a new intent, remember entries a rollback could not remove
* fix(xbox): clear the removal list before a restore moves old files back
---------
Co-authored-by: TimmyCraft <46533729+TimmyTurner51@users.noreply.github.com>
* fix(game-env): per-game DROIDDECK_GAME_TU_DEBUG reaches the game
game_gpu() ran on the inherited environment before apply_config() added
the entries from game-environment.json, so a DROIDDECK_GAME_TU_DEBUG
(or DROIDDECK_GAME_MESA_NO_ERROR) set for one game was passed through
unchanged and TU_DEBUG was never set. apply_config() now returns its
result through game_gpu(), so a per-game value is applied the same way
as one from the session.
* fix(game-env): a game's own TU_DEBUG still wins over a shared prefixed one
Resolve the prefixed GPU keys inside the shared entries and inside the
game's entries separately, before the game's entries are laid over the
shared ones. A game's plain TU_DEBUG (or its removal with null) now
beats a shared DROIDDECK_GAME_TU_DEBUG, and a prefixed value set for one
game still applies.
* fix(game-env): keep a plain TU_DEBUG over the prefixed key in the same profile
---------
Co-authored-by: zdennisz <15849186+zdennisz@users.noreply.github.com>
Co-authored-by: maxjivi05 <maxjividen@gmail.com>
* ci: fail the checks gate when store engine tests fail
* test(ci): expect store-tests in the checks gate
---------
Co-authored-by: Tapuuk <177422350+Tapuuk@users.noreply.github.com>
* fix(compositor): hold releases from synchronized subsurfaces until the parent commits
gamescope's Wayland backend moves layers between synchronized subsurface
planes and commits the parent last. Each child commit was applied at once,
so a buffer leaving one plane could be released before the next plane took
it, and gamescope then logged "Compositor released us but we were not
acquired". A buffer attached again also dropped its queued release, and the
buffer trace records every attach.
* fix(compositor): hold a synchronized release at its sync boundary and recheck holds on set_desync
---------
Co-authored-by: maxjivi05 <maxjividen@gmail.com>
* ci: install the arm64 C library headers the verified components cross-compile against
* ci: cross-compiling component recipes install the arm64 C library headers
* fix(effects): keep upscaling and sharpening at panel size with frame generation on
* fix(effects): stub sharpening query in the terminal callers probe
Building the full APK locally on an x86_64 Linux host (rootful Docker, no
Docker Desktop) failed in the Xbox backend step and could not be rerun:
- The xodus-cli tests re-execute their own arm64 test binary, which needs an
aarch64 binfmt handler on the host. Without one the child runs through
/bin/sh ("Syntax error: & unexpected"). build-local.sh now checks for the
handler up front and prints the one-line fix.
- msixvc's streaming tests give each request 40 ms. Under qemu with the whole
suite in parallel they time out (28/30 pass in parallel, 30/30 serially),
so they run with one test thread when emulated. Native arm64 is unchanged.
- The backend container runs as root, so with rootful Docker its outputs in
the repo and the cache were root-owned and the next build_local.sh could not
remove them. The container now hands them back to the calling user on exit.
- README lists the missing requirements: Go, a host C compiler, both MinGW-w64
compilers (i686 with DWARF-2 exceptions; Homebrew's SJLJ build cannot link
Rust's i686-pc-windows-gnu) and the arm64 binfmt handler.
Verified with a full tools/build_local.sh run on SteamOS (x86_64): all three
backend test suites pass and the APK is release-signed.
* fix(xbox): log and show why an Xbox launch could not be prepared
* fix(xbox): hand Xodus a launch folder the Linux guest can see
---------
Co-authored-by: Zeratullo <8460122+Zeratullo@users.noreply.github.com>
* chore: consistent code branding
* fix: carry legacy overrides, queues and live sync rows across the rename
* fix: keep queued legacy overrides on a failed rename and separate merged queue entries
#2780 committed 21 empty libdroiddeck-pipewire.lock files whose names are
mangled Windows temp paths. test_pipewire_helper runs the POSIX helper
under sh; on Windows it received a C:\Users\...\Temp path, so the helper's
"$dir.lock" landed in the working directory. The helper needs a POSIX
shell, flock and Unix sockets, so skip the test on Windows.
* fix: initialize Proton prefix before install scripts
* game-env: start Proton first only for a new prefix
* fix: wait for new prefix wineserver before seeding
* game-env: find wineserver in either Proton layout
* fix(steam): skip redist seeding when wineserver wait fails
* fix(steam): probe new prefixes only when Proton has no template prefix
* fix(steam): check the active Proton prefix template before seeding
* fix(steam): use effective environment for redist seeding
* fix(desktop): keep the bundled PipeWire paths out of Plasma so the desktop draws
* fix(desktop): let the screencast portal use KWin so Sunshine can capture the desktop
* fix(proot): /proc/<pid>/root reads as the guest root so portals accept callers
* fix(nativeguest): /proc/<pid>/exe of another guest program names that program, not the loader
* fix(nativeguest): trust another process's program only when it is mapped there, and read all of its environment
* fix(nativeguest): accept versioned glibc loaders, and wait for the test program to run
* feat: adopt game folders in added Steam libraries
* Share the appmanifest builder between steam-library and steam-games
* steam: load the shared compatibility module once per run
* Guard unreadable game folders during library adoption
---------
Co-authored-by: Kurt Himebauch <136133082+xXJSONDeruloXx@users.noreply.github.com>
* fix: move zram page-out off signal thread
* fix: drain pending zram requests
* Time the async and inline page-out runs on the same workload
* fix(zram): keep pageout worker responsive under load
* test(zram): synchronize signal delivery before fixture shutdown
* test(zram): compare matched single-request timings
* test(zram): correct single request timing control
* test(zram): calibrate single request timing together
* test(zram): fail the timed run when the acknowledgement never arrives
* fix(fex): supply current Wayland libraries in the shared runtime
* fix(fex): provide current FreeType runtime libraries
* fix(fex): fall back when provider links are broken
* fix(fex): require ffi for provider Wayland libraries
* fix(fex): keep Wayland cursor with its provider client
* fix(fex): preserve cursor compatibility and refresh runtime cache
* fix(fex): provide current GBM runtime libraries
* fix(rockstar): serve launcher pipes named by the executables beside a protected game
* fix(rockstar): skip unreadable executables beside a game instead of failing the launch
* test(rockstar): exercise case-insensitive sibling pipe name dedupe
* fix(rockstar): show the launcher service log in the session log after a Rockstar game exits
* fix(store): run the store exit hook when the session ends a store game
* fix(session): read the compressed client back when it is in front of a running game
* fix(session): keep the client compressed while focus is unknown
A missing or unreadable focus.json no longer counts as the client in front
of the game, so the readback timer starts only on a confirmed focus change.
* fix(session): invalidate focus snapshots after collection failures
* fix(session): retry focus snapshot publication
* fix(fex): GL thunk passes X errors to the program instead of exiting
* fix(fex): raise forwarded X errors on the program connection without swapping its handler
* fix(fex): release the host display lock while a forwarded X error runs the program's handler
* test(fex): cover X error forwarding with real Xlib locks under Xvfb
* test(fex): verify GLX context fallback with a valid config
* test(fex): probe GLX headers before compiling harness
* fix(ci): wait out the API rate limit in build validation
* fix(ci): skip rate-limit sleep retries on status POSTs
* fix(ci): detect status POSTs via --method without changing api() call signature
* Add integer scaling mode
* Fix integer scaling view-space input bounds
* Improve integer scaling tolerance
* Add Fit and Auto scaling toggle to session drawer
* Translate Fit and Integer scaling labels
* Clarify integer scaling cropping hint
* Update integer scaling hint across translations
* Fix integer scaling settings and translations
* Fix controller input for integer scaling
* Complete integer scaling hint translations
* Fix integer scaling hint translations
* Restore XML declaration quote style
* Use double quotes in XML declarations
* Add missing norugeuingz translatisn
* fix: include math.h for roundf integer scaling
* fix: link math library in Vulkan caller tests
* Fix integer scaling translations
* Fix Italian integer scaling string
* Fix Italian scaling hint apostrophe