A failed token refresh returned the stored access token even after it had expired, so the next request failed with a generic error instead of asking to sign in again. The stored token is now returned only while it is still valid.
The Epic docs now say that achievements are sent with Epic's launcher user agent, which the achievements service requires.
Both store modules are rewritten from a protocol-level spec: new Rust engines behind a small JNI surface (nativeCall/nativeInstall) and thin Kotlin facades, with the launcher's own user agent.
Epic: sign-in carries over, library, manifest download with byte-exact verification, assembly, uninstall, launch arguments, achievements.
Amazon: sign-in carries over, library, manifest download with per-file hash checks, path checks, executable detection from fuel.json, uninstall.
On-disk install layout is unchanged, so existing installs keep working.
Store game pages now take controller focus on their lead hero action (Install, Uninstall, Pause, Resume, Get, Buy), fall back to Back, and keep D-pad focus inside the page while it covers the library.
Space checks before Epic, GOG and Amazon installs (measured zero vs unknown), clear failure reasons with retry/clear, resume-aware checks, and safe per-file replacement so a failed or cancelled update never breaks an installed game.
Epic installs stream chunks straight into staged files in parallel (most bytes written once, a small budgeted cache for shared chunks, about 1x game size instead of 2x), pace updates by free space, and keep the lookahead, batch and bounded Java writers as hidden alternatives.
Co-authored-by: Juan Marti Mercado <[email protected]>
Co-authored-by: The412Banner <[email protected]>
* fix: desktop session: Shift no longer stays held after typing capitals on a physical keyboard
Android repeats a held key as more key presses. Those were forwarded to the
session as more wl_keyboard presses, and KWin's xkb counts every press of a
modifier, so Shift held for a few capitals took several presses and one
release and stayed held: digits typed !@#, letters stayed capital. The same
applied to Ctrl and Alt.
- the compositor no longer sends a press for a key that is already down;
releases always go through (clients repeat keys themselves from the
repeat_info it already sends)
- the app stops forwarding Android's repeat events for keyboard keys
Reported by whatsupbros with a Keychron Q7 over USB - thank you.
* Remove stale comments from statx patch
---------
Co-authored-by: The412Banner <[email protected]>
Co-authored-by: xXJsonDeruloXx <[email protected]>
* Add translations for 23 more languages and fill missing strings
* Translate the strings added in main into every language
Cardboard VR and the session drawer's component downloads in all 31
languages, the game details facts and HowLongToBeat labels in the 23 new
ones, and the reworded Components page note there.
* Add opt-in zRAM compression for the Steam client while a game runs
A "zRAM compression" toggle under Steam > Settings > Session, below
"Keep downloads running". Off by default, kept once set, and disabled
on devices without swap or with a kernel older than 5.4.
When on, the session watches for Steam's reaper. 20 s into a game the
client and its web helpers page their private anonymous memory out to
the device's zram with MADV_PAGEOUT from inside their own process
(libblsession zram.c, SIGURG), again every 5 minutes, and read every
swapped page back once the game exits. No root is needed: only a
process itself may do this without CAP_SYS_NICE. With the toggle off
nothing is installed or started.
RedMagic NP06J, Palworld: Steam's resident memory fell from ~1.7 GB to
~1.1 GB with ~560 MB in zram, available memory during play rose by
~0.5-0.8 GB, and ~2 MB was left in zram after the read-back.
* Turn zRAM compression on by default below 12 GB of RAM
Until the toggle is changed, it follows the device: on when the kernel
supports it and the device has less than 12 GB of RAM, read from the
advertised memory size on Android 14+ and from total memory before that.
Turning it off is kept.
---------
Co-authored-by: xXJsonDeruloXx <[email protected]>
* feat: add Cardboard mode with side-by-side lens-distorted eyes and 3DoF head tracking
* fix: derive the Cardboard field of view from the panel and recentre fully when far from upright
* feat: share the Cardboard head pose with the guest and add a SteamVR driver for it
* feat: run SteamVR's compositor on Turnip/KGSL with a display-extension layer and a driver-direct HMD
* feat: show SteamVR frames in Cardboard mode through a driver-side presenter and a fake direct-mode display
* feat: install and start SteamVR for Cardboard mode from the session drawer
* docs: describe Cardboard mode and the SteamVR path
* feat: drive SteamVR hands from the game pad and keep the Cardboard headset out of standby
* docs: record where the SteamVR dashboard stops
* fix: map Cardboard head tracking to the screen's axes and keep turns about the real vertical as yaw
* fix: give Cardboard its previous picture back when SteamVR stops
* fix: report sem_otime from emulated SysV semaphores so SteamVR's web helper can start
* fix: bridge SteamVR's shared semaphores across processes and keep Steam alive while SteamVR runs
* feat: present SteamVR straight to DroidDeck's compositor at panel resolution
* docs: update Cardboard VR notes for the dashboard, semaphore bridge and direct presenter
* fix: keep Wine and FEX signal handlers in the VR layer; add semaphore tracing
* fix: clear a stale SteamVR active marker on status
* fix: clear only an old SteamVR active marker
* fix: unblock SteamVR clients on Turnip and keep Steam's web helper alive across SteamVR runs
* fix: judge shared waits before a submit's own signals and on Vulkan 1.0 devices
* docs: record VR games, SteamVR Home and OpenXR results on the Thor
* docs: add Cardboard VR learnings from the Thor bring-up
* docs: add Cardboard VR screenshots from the Thor
* fix: keep the VR layer's display stand-in to SteamVR runs and clear a leftover marker at session start
* fix: report SteamVR start and stop failures from the helper's exit code
* feat(): gog & epic achievements UI
* feat(): AI-generated translations - Please get review for these
* build_local: run on macOS hosts with Docker Desktop
Two steps of tools/build_local.sh failed on a Mac:
- The uruntime staging runs on the host, where macOS's BSD install has
no -D, so `install -Dm644` stopped with "No such file or directory".
The folders are now made first and the files copied with install -m644.
- Inside the cross-compile container, Docker Desktop's VirtioFS share
now and then refuses the chmod that install -m makes (EPERM, on a
different file each run, e.g. "setting permissions for
.../droiddeck-esync: Operation not permitted"). The overlay and
desktop scripts are copied with a plain write instead. Nothing is
lost: the APK keeps no file modes, and the app sets them when it
stages the runtime.
* feat(): adjust the store
* feat(): store-achievements adjustment for UI
* feat(): translation fixes and separate hidden achievements
* Show all achievements directly on store game details
---------
Co-authored-by: xXJsonDeruloXx <[email protected]>
A game that closes as soon as it starts can be tripped by Proton's Steam
setup (steam.exe, the Steam registry entries, the Steam client bridge).
The Games page of the session drawer gets a per-game Start without Steam
switch, stored as DROIDDECK_NO_STEAM=1 in the game's environment and listed
in its profile summary.
droiddeck-game-env acts on it for a game launch only: a Proton with umu's
launch (GE-Proton, Proton-CachyOS, DroidDeck-Proton) gets UMU_ID, so it
runs umu.exe in place of steam.exe and still sets up the prefix; a Steam
game keeps its protonfixes under its own id, an added game gets 0. Any
other Proton runs the game straight in the prefix (runinprefix).
* feat: a store game's page floods out of its card onto its own hero art, and draws back from it
* fix: installs interrupted by the app closing show in Downloads with Resume and Clear
* feat: finished and interrupted downloads share the running card's art look, and the queue sits under what is running
* fix: the download queue outlives the app: queued, running and paused downloads come back after a restart
* feat: components list newest first, Steam's sheet opens on its Steam tab with offline mode, and Setup's overview drops the account group
* fix: chip selections stretch across on every move, drawn over the chips instead of behind them
* feat: with a pad the focus ring fills what it holds and is the only fill; chip rows mark their pick with a bar
* fix: the focus ring chases focus on a continuous spring per edge instead of restarting on every move
* fix: a chip selection hopping past a chip fades across instead of crawling over as a drop
* fix: the store chips' fill only shows where a pad's focus is, not on the shown store
* feat: the shown store's chip carries a bar on its foot, every chip pulses when picked, and the queue's settings live only in the cog
* fix: step-outs grow and fold in one move with no tail, keep the ring out while moving, and hand focus back to their control
* feat(profiles): add persistent per-game compatibility profiles
* fix(profiles): show Windows component overrides
Include per-game Windows component selections in the resolved profile summary so the session overlay marks those games as custom and shows the selected components.
* fix(session): detect Proton games across runtime paths
* fix(profiles): select the active Gamescope game
* fix(profiles): improve per-game reset feedback
* fix(profiles): align session components with game overrides
* fix(session): prefer selected Steam game during refresh
* fix(session): resume profile following when reopening games
* chore: keep local dev testing outside the repository
* test(session): remove local dev package path
* fix(session): preserve profiles when refresh fails
* fix(session): reject empty game profile reset scope
* perf(session): cache drawer inventory by refresh revision
* fix(profiles): align game presets and profile reset behavior
* fix(profiles): preserve originals and normalize shortcut ids
* fix(profiles): keep editor scope stable after rebase
* fix(tests): host Compose tests in both build variants
* fix(profiles): recover interrupted component selection saves
---------
Co-authored-by: Kurt Himebauch <[email protected]>
* fix: Red Dead Redemption 2 launches again, its Vulkan runtime installer is left to run
droiddeck-seed-redists marked every process in every game's install script
as already run, Red Dead Redemption 2's VulkanRT-1.1.108.0 installer
included. Steam's compat config for the game says nativevulkanloader, so
Proton loads vulkan-1.dll native only, and Khronos' loader is in the prefix
only once that installer has run. Without it the Rockstar launcher starts
RDR2.exe and it exits with STATUS_DLL_NOT_FOUND (0xc0000135) before it
opens a window.
A Vulkan runtime installer is now left out of the seeding, and a marker an
earlier seeding wrote for one comes out of each prefix and Proton template
once (dates kept), so the client runs the installer on the next launch.
The installer finishes in a few seconds under FEX.
* fix: Steam's screensaver no longer covers a running game
The client's defaults show screensavers while a game runs, after 300 s on
AC power without a button press - and a held stick or trigger is no press.
Red Dead Redemption 2's intro runs longer than that: the slideshow covered
the game, and the button that woke it reached the game too (B asked to
quit to the desktop). Customization/Screensaver/WhileInGame is seeded "0"
in config.vdf once, like the UI scale and native resolution, so turning it
back on in Settings stays the user's choice.
On the RedMagic: 18 minutes from the last button press through the intro
and riding, focus never left the game and no screensaver was created.
* fix: Rockstar's hidden launcher no longer takes cores from its game
The Rockstar Games Launcher keeps drawing its Chromium interface
(SocialClubHelper.exe: renderers, and a GPU process compositing through
DXVK) for as long as the game runs, hidden behind it - and Wine passes
Chromium's priorities on, so those threads ran above the game's (the GPU
process at nice -10), across every core. With Red Dead Redemption 2 in
front that was 1.3 to 2.5 cores under FEX for a page nobody sees.
droiddeck-launcher-cores follows gamescope's focus from the agent's
focus.json: while a game window has it, every SocialClubHelper thread runs
on the last core of the slowest cluster at nice 19; when the launcher's own
window has focus again each thread gets its own mask and priority back
(also on exit). Stopping the helpers would not hold - proot resumes a
stopped tracee. Started for Steam sessions; BL_LAUNCHER_CORES=0 turns it off.
RedMagic, RDR2 all Low, riding at the thermal limit, same spot and session:
released 46.5 fps, 1% low 27.5, p99 31.8 ms, CPU 89%, 2200 MHz;
held 48.7 fps, 1% low 32.6, p99 27.6 ms, CPU 79%, 2638 MHz.
* fix: sessions clean up what earlier ones left in /tmp
The guest's /tmp is a directory in the rootfs that no boot ever empties,
and Android ends sessions by killing them. Every session left a
/tmp/mangohud.XXXXXXXX (mktemp, never removed), and the Steam client, its
web helper, Chromium apps, dbus-run-session, AppImage runs and KDE their
own temporary files and sockets: 1,422 entries on the RedMagic.
mangoapp's config is now one fixed file rewritten each session, and the
session's first pass sweeps each kind of leftover while nothing that could
own one is running, with a single find. On the device that cleared 1,391
entries over two sessions, leaving 38.
Setup > Proton versions lists DroidDeck-Proton (The412Banner/DroidDeck-Proton) beside
GE-Proton and proton-cachyos: same aarch64 tarball pattern as GE, verified against its
sha512 file, installed by droiddeck-proton-extra (also as "droiddeck" in the session queue)
and adopted by steam-compatibility like any other extra, so it shows as
"DroidDeck-Proton <ver> (Compatible)". Its folder has a space; nothing in the install,
adopt, esync or components paths splits on it.
Update checks: each source's newest full release is looked up at app start and when the
page opens, at most every 6 h (offline keeps the last answer). A newer release shows
"Update available -> <tag>" with Update; it installs beside the old build, which stays
until removed ("Remove old ... versions"), since games are mapped to it by name.
Installed builds are ordered by their version numbers (11-9 before 11-10), not by name,
and the tag each was installed from is recorded. Prereleases and drafts are skipped.
xXJsonDeruloXx