* 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
* 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
* Rail and second-screen icons in the Steam Deck menu's style
Solid icons throughout the rail, and Steam's glyphs where Steam has the
same place: Library is the four-square grid, Stores the price tag,
Downloads the download arrow, Settings the gear. On the second screen,
Screenshots uses Steam's Media picture and Chat its Friends people.
* Compose previews of the launcher and the in-game menu, rendered to PNGs
Debug-only previews of the launcher on each tab and the in-game menu's
pages, built from the production composables with sample state and
no-op actions, at the Duo's handheld size and in portrait.
PreviewRenderTest draws each with Robolectric's native graphics into
app/build/preview-renders/, so a UI change can be looked at without a
device, and fails on a preview that throws or draws nothing.
docs/compose-previews.md says how to run and extend them.
* Preview renders wait for store accounts before drawing
A preview case can name what the render test waits for. The Library and
Stores cases wait for store accounts, which load on a background thread,
so their PNGs never catch the loading state.
* Preview renders step the paused clock while waiting for a case to be ready
* 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>
* 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
* 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(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
* feat(boot-movie): add a Shuffle switch backed by Steam's startup movie shuffle setting
* test(boot-movie): keep unrelated settings unchanged
* fix(boot-movie): keep the Shuffle choice across reset, unreadable configs and running sessions
* fix(boot-movie): track the Shuffle baseline per Steam home and only for values staging wrote
* fix(boot-movie): adopt a Shuffle change made in the inactive Steam home before staging overwrites it
* fix(boot-movie): keep the 60 fps note under the Installed movies row
* 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>
* 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>
* Head tracking for the XREAL One, One Pro, One Pro+ and Aura
These glasses use the same USB Ethernet link and 128-byte IMU report as the
1S. XrealModel now has one model per product: the 1S keeps its tested
display-mode control, and the others switch 2D and 3D only with GET_INPUT
(0x2821) and SET_INPUT (0x2822). Display-mode set (0x275f), brightness and
the dimmer are never sent to them. The Aura's IMU reads x right, y up, z back
(about +9.8 m/s2 on y at rest), so its axes are not flipped like the rest of
the family. Recovery-mode product ids (one below each) stay excluded.
Signed-off-by: Mike Haye <84657517+mhaye20@users.noreply.github.com>
* Describe the wider XREAL support in the glasses panel and docs
The panel's help text and docs/smart-glasses-support.md named only the 1S.
They now list the One, One Pro, One Pro+ and Aura, say what was tested on
the Aura (head tracking and 2D/3D switching), and note that these models get
2D and SBS only, without brightness, dimming or display-mode set commands.
Translations still describe the 1S only.
Signed-off-by: Mike Haye <84657517+mhaye20@users.noreply.github.com>
* Docs: XREAL support is no longer 1S only
The paragraph under the support matrix still said the One and One Pro were excluded.
Signed-off-by: Mike Haye <84657517+mhaye20@users.noreply.github.com>
---------
Signed-off-by: Mike Haye <84657517+mhaye20@users.noreply.github.com>
* docs(phantom): how Android counts guest processes and why detaching cannot escape it
* docs(phantom): clarify probe permissions and batch capture
* docs(phantom): qualify probe precondition by SDK and size the limit device-wide
* docs(phantom): keep phantom discovery on for the 12L probe and raise the limit instead
* docs(phantom): warn about the CPU kill, raise the limit before the flag and restore both after the probe
* docs(phantom): restore the monitor flag before the phantom limit after the probe
* docs(phantom): restore the flag before the limit whether each is put or deleted
* fix(stores): log why a GOG cloud sync failed and stage uploads in the cache folder
* fix(stores): strip URL credentials and bound the error body in GOG cloud failure details
* fix(stores): send Galaxy's communication-service User-Agent to GOG cloud storage
GOG cloud storage now answers every list with HTTP 400 invalid_version for the bare
"GOG Galaxy" value, so uploads and downloads failed for every game. List, HEAD, GET and
PUT now identify as GOGGalaxyCommunicationService/2.0.13.27 like gogdl and Lutris, and
PUT carries the same value as X-Object-Meta-User-Agent.
* fix(stores): bound cloud list errors and verify test requests
* fix(stores): preserve cloud error classification
* 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(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
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(proot): fchdir takes the open directory's path instead of walking it again
* fix(proot): fchdir keeps trailing-period names and rechecks the binding's parent
The descriptor path now carries the same final marker the walk produced, so a directory whose name ends with a period is not truncated. The parent of the matching binding is resolved again, so a binding whose ancestor was replaced by a symlink takes the full walk as before. The check script gains a trailing-period directory.
* fix(proot): fchdir requires the binding's parent to be a directory
* 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
* fix(game-env): the VRAM cap also applies to D3D9 games
DXVK's D3D9 frontend ignores dxgi.maxDeviceMemory, so set d3d9.maxAvailableMemory to the same cap.
* fix(vram): leave DXVK's lower per-game D3D9 limits in place above the 4096 MiB default
* feat(lab): load an on-device Lab build over the installed app
* feat(lab): build Lab builds on the device and report the APK commit to agents
* fix(lab): dd-agent connects loopback adb before starting Claude Code
* feat(lab): tell the app's own agent to continue after a Lab build restart
* fix(lab): size the build heap from the device's memory
* feat(lab): keep earlier Lab builds and list them in Updates
* feat(lab): notify when DroidDeck comes back on a Lab build or turns one off
* feat(lab): estimate the time left and compile the installed commit ahead of the first build
* fix(lab): report a failed command as a failed build and update progress every five seconds
* feat(lab): a kept build for another version can be rebuilt
* feat(lab): record which installed commit the build caches are warm for
* fix(lab): the app's agent hands its builds to the app, so they outlive the agent's turn
* perf(lab): BuildConfig describes the installed base, so a Lab commit does not change it
* perf(lab): compile with the Kotlin daemon, since in-process Kotlin compiles always redo the whole app
* fix(lab): a build whose last task was up to date no longer counts as failed
* feat(lab): dd-lab-build --explain logs why tasks ran and Kotlin's build report
* fix(lab): keep a waiting build when another is staged or Lab is turned off, and never restart during a session
* fix(lab): keep the installed build's label and exact commit, and refuse AppLanguage changes
* fix(lab): setup verifies its downloads and waits for adb before preparing
* fix(agent): quote apostrophes in opened URLs and keep the sign-in pid
uplay_r2.dll speaks the same UplayDll.proto as uplay_r1.dll, but its InitReq
names the subsystems the game uses (fields 4 to 11) and its ApiContext only
creates objects for those. It copies gameInstall and storage into their
objects without checking for them, so the gameInstall droiddeck-upc always
sent crashed Prince of Persia: The Lost Crown (6145), which asks for overlay,
product and store only: an access violation reading 0x68 in
uplay_r264.dll+0xaca2 two seconds after the session.
- When the request names subsystems, gameInstall (14) is sent only with
subSystemInstall and storage (17) only with subSystemStorage, and an empty
multiplayerInit (20) is added. Requests that name none keep the old session.
- streamingReq (27) is answered: the streaming type is None, other streaming
queries are not found.
- The log records the subsystems each init asked for.
Co-authored-by: Kurt Himebauch <136133082+xXJSONDeruloXx@users.noreply.github.com>
* feat(ubisoft): sign in to Ubisoft Connect and list the owned library
* feat(ubisoft): download games natively through Demux and Ubisoft's CDN
* fix(ubisoft): show the owned games on the store page
* fix(ctl): reach the agent bridge by broadcast when the shell has no content command
* feat(ubisoft): run Ubisoft games in one prefix with Ubisoft Connect installed and the game registered
* feat(ubisoft): launch games through a native stand-in for Ubisoft Connect's local service
* feat(ubisoft): document the launcher pipes, log why owned games have no download, drop the installer after extraction
* feat(ubisoft): Steam-owned Ubisoft games install through Steam, and the launch session carries the game's application id
* feat(ubisoft): answer Denuvo activations through Ubisoft's activation service and log unanswered pipe traffic
* feat(ubisoft): report installed chunks to the game and skip add-ons the account does not own
* fix(ubisoft): the overlay stays off, Ubisoft's install steps pick Windows components, and shared-prefix games keep their own settings
* fix(ubisoft): write the manifest's registry values, and pick the game's exe over Ubisoft's installer stubs
* fix(ubisoft): stream download slices, guard the launch hook, and keep per-game components in the shared prefix
* fix(ubisoft): direct launches in the shared prefix keep their own game id
* ci(ubisoft): build the launcher service after the prepared components are verified
* fix(ubisoft): verify reused files, drop syncs from a signed-out account, and clear activation requests before launch
* fix(ubisoft): fetch again a reused file whose slices cannot be checked
* docs: research and plan for EA and Ubisoft stores
* feat(ea): EA store with sign-in, library, native downloads, updates and launch without the EA app
* perf(ea): fetch large archive records as parallel ranges
* fix(ea): register game display names
* fix(ea): license legacy EA Core games and harden the LSX endpoint
* fix(ea): run legacy Origin SDK games with a stand-in Origin process
* fix(ea): trust only the prepared game on LSX and stop stale library syncs
* fix(ea): close LSX sessions on stop and drop clients that never hand-shake
* fix(ea): require every hashed field before licensing or caching a probe
* fix(ea): trust one LSX session per launch
* fix(ea): serialize the library cache write with sign-out and rerun a skipped sync
* fix(ea): hand off library sync requests under one lock
* fix(ea): clear the sign-in before invalidating the library
* fix(ea): serialize sign-out with token refresh and with the library cache
* fix(ea): LSX trusts only verified peers, new launch closes old sessions, exit stops its own game
* fix(ea): LSX hides profile and presence from unverified peers
* fix(ea): LSX handshake has a fixed deadline and untrusted sessions yield their slot
* fix(ea): LSX never registers a client after its listener was stopped
* fix(ea): LSX evicts each untrusted session at most once
* fix(ea): LSX admission and eviction share one lock and keep the cap
* fix(ea): LSX trust promotion excludes eviction
* fix(ea): LSX launch generation guards restarts and drops results after shutdown
* fix(ea): LSX publishes launch state under the admission lock and tags accepts by generation
* fix(ea): LSX restarts rebind its listener and promotion checks the launch generation
* fix(ea): record why EA refuses a game licence in the store log
* chore(ea): log owned offers and the full licence refusal
* chore(ea): log the account's entitlements when no game licence is granted
* chore(ea): log legacy entitlements when no game licence is granted
* chore(ea): log only the refused game's own entitlements
* fix(ea): skip trial launchers flagged 1 and license games whose LSX peer Android cannot name
* fix(gog): install scripts' support files reach the prefix
A goggame-<id>.script can copy files into the prefix with supportData
actions: default INI files, Plugins.txt and other settings that mods such
as one-click editions need. Only setRegistry actions were applied, so
those games started without their configuration and ran as the base game.
droiddeck-store-launch now applies supportData after the registry, once
per script revision: copies from {app} and {supportDir} into {userdocs}
and {localappdata}, matching paths without regard to case. Links are
copied as links, paths outside those folders are refused, and existing
files are replaced only when the action asks for it.
* Keep GOG support data copies inside the game and prefix folders
* Copy linked GOG support sources as links and keep a player's own links
* docs: DroidDeck 0.7.0 release notes
* docs: add 0.7.0 release note media
* docs: drop the 30 second summary from the 0.7.0 notes
* docs: add the dual-screen Dashboard shots to the 0.7.0 notes
* docs: show the Dashboard as one stacked dual-screen image
* docs: add the swap screens GIF to the 0.7.0 notes
* docs: swap in the new Syncthing screenshot
* docs: add the HUD dock GIF to the 0.7.0 notes
* docs: add the Game Jolt screenshot to the 0.7.0 notes
* docs: show the full screen in the HUD dock GIF
* docs: merge the GPU bullets, add the no proprietary components line, put images above their bullets
* docs: add the 0.7.0 APK download button to the release notes
* docs: add the first-time contributors to the 0.7.0 notes
* docs: add KeegantheVeganat0r as a first-time contributor
* docs: add the shared Steam libraries screenshot to the 0.7.0 notes
* docs: rewrite the shared Steam libraries bullet and move it up
* docs: add the Mali support photo to the 0.7.0 notes
* docs: center 0.7.0 release media
* docs: credit The412Banner for Mali support in 0.7.0 notes
* docs: add the KDE desktop GIF to the 0.7.0 notes
* docs: add the desktop and swapped game clips to the 0.7.0 notes
* docs: use the Duo photo for the swapped screens
* docs: replace the swap screens GIF with the Duo recording
* docs: drop the swap screens GIF
* docs: keep a blank line before each release image
* docs: tweak 0.7.0 release notes
* docs: move smaller 0.7.0 items to improvements
* docs: fold the bottom-screen HUD into the Strip HUD bullet
* docs: pair the swap screens and KDE desktop media
* docs: move Game Jolt and Syncthing up in 0.7.0 features
* docs: put the swap screens and KDE desktop cluster after Mali in 0.7.0 features
* docs: reword shared Steam libraries and reorder KDE desktop bullet
* docs: add recent merged PRs to the 0.7.0 notes
* docs: auto component updates follow DroidDeck-Proton only
* docs: add input profiles, low-RAM memory, driver Auto and other recent changes to the 0.7.0 notes
* docs: add the second-screen layout editor to the 0.7.0 controller profiles notes
* docs: refresh the 0.7.0 pull request and contributor counts, mention controller profiles in the summary
* docs: 0.7.0 notes add the latest fixes and the DroidDeck-Proton, DD-Turnip and component changes
Adds the user-visible pull requests merged after the last refresh (Library
sort, runtime pack update, desktop app launches, GitHub AppImage variant,
DroidDeck-Proton default, component auto-update cleanup, UBWC and FEX preset
settings, controller navigation) and a section for what shipped in
DroidDeck-Proton 11-11.10 to 11-12.3, DD-Turnip 0.4.0 and DroidDeck-Components
since 0.6.9.
---------
Co-authored-by: maxjivi05 <maxjividen@gmail.com>
* fix(components): DXVK Auto on Adreno 6xx keeps DroidDeck-Proton on DXVK-gplasync 2.7.1
* fix(components): DXVK Auto says so when the pinned DXVK could not be installed
* fix(components): a DXVK the player picked is shown as their choice, not a failed pinned install
perf(hud): rasterize Strip graph and logo separately
Replace PR2194's whole-View software layer with a hardware-accelerated
Strip that rasterizes its graph and logo into small reusable bitmaps.
Keep the 66 ms graph invalidation cap, clear stale graph pixels, and
refresh cached logo colours when the theme changes.
Include the comparison method and six sanitized benchmark samples.
With matched Steam navigation, the hybrid averaged 12.2% less UI-thread
CPU and 34.0% lower draw p95 than the PR2194 software path. App-process
CPU averaged 5.9% lower in this run; whole-device and battery savings
are not established. Current-build physical flicker confirmation is
recorded separately from timing validation.
Validation: all 12 DroidDeckHudPanelTest checks passed; comparison APK
built and six alternating device samples completed with matched input
counts, no focus loss, thermal status 0, and no frame metric report drops.