FEX_THUNKS=1 (build-fex.yml 'thunks' input) builds FEX's host thunks: the
arm64 half against the runtime's graphics dev packages, the x86 and i686
guest halves with clang against a sysroot of Arch Linux x86_64 and
multilib packages unpacked by pacman (not run). With them an x86 program's
Vulkan, GL, X11, Wayland and DRM calls reach the runtime's own libraries -
Turnip and Mesa on the GPU - instead of llvmpipe.
- DroidDeck direct: a compatibility tool the x86 client gets in its own
compatibilitytools.d, running a native Linux game with Valve's scout
library runtime under FEX instead of the Steam Linux Runtime container
(pressure-vessel, which needs bwrap). Left 4 Dead 2 (BL_X64_DIRECT_APPS)
is mapped to it in the x86 config while that client is not running.
- The session shim and the controller reader are also built for i386 and
preloaded through glibc's $LIB, so 32-bit games get them too.
- The runtime's bin/ on the client's PATH (steam-runtime-launch-client).
- No -steamdeck -steamos3 for the x86 client yet: its SteamOS audio
manager aborts on the runtime's PulseAudio 13 (pa_operation_get_state).
The session's pads exist for a guest program only through libfakeinput
(the FAKE_EVDEV_* rings), which was built for arm64 alone, so the x86
client saw no controller. Build it natively for x86-64 too, stage it, and
preload it through the FEX rootfs next to the session shim.
The x86 client stops at start on a tier0 assertion: semget answers ENOSYS,
as Android kernels have no System V IPC (traced with a DEBUG_STRACE FEX).
The session shim that gives the arm64 client its semaphores is now also
built as native x86-64 and preloaded through the FEX rootfs's own
ld.so.preload. SessionFiles stages it and bannerlator-steam-x64 into
installed runtimes.
A workflow_dispatch input passes extra CXXFLAGS (e.g. -DDEBUG_STRACE for a
syscall trace) into the build; such builds stay artifacts and are never
published under a release tag.
The x86-64 Steam client experiment needs FEX inside the guest, and neither
Arch Linux ARM nor FEX publishes a Linux arm64 binary. Built in the same
Arch Linux ARM container as gamescope, without thunks, tuned for generic
armv8-a, with the runtime's own unsquashfs alongside to unpack FEX's x86
rootfs image.
Preload library answers stat/open/access/readlink in-process via a
trampoline page proot 0014 lets through seccomp. On by default with a
Performance toggle; also sets GLIBC_TUNABLES rseq=0 and malloc top_pad.
* feat: add an Updates page that installs Stable, Nightly or test builds in-app
* style: put update channels on the left and the build on one line
* style: make the update card read like a system updater
* feat: expand update notes, show the build beside the title, fit with button hints
* style: check for updates with the refresh icon Components uses
* Add ownership-aware Steam game folder imports
* Fix Steam title lookup and installed game manifests
---------
Co-authored-by: MaxsTechReview <6025299+maxjivi05@users.noreply.github.com>
DROIDDECK_CI_TOKEN never existed, so PR Release Publish skipped its
upload, and a personal token would expire and belong to one person. Both
workflows now mint a token of the org's DroidDeck CI Publisher app,
installed on DroidDeck-CI only with Contents: write (its ID in the
DROIDDECK_CI_APP_ID variable, its key in DROIDDECK_CI_APP_KEY). No
fallback: a main build without them fails its announce job.
Run artifacts need a GitHub sign-in to download. Each signed main build
is now also a prerelease main-<sha> of the public DroidDeck-CI (all
variants and their SHA-256s; the last 10 kept, PR releases untouched),
and the Discord post links its standard apk and the release. Without
DROIDDECK_CI_TOKEN the post links the run's artifacts as before.
A job after the signing of a main build posts to the Discord's builds
channel: the merged PR (or the commit), and a link to the run's signed
apks. The channel's webhook URL is the DISCORD_BUILDS_WEBHOOK secret;
without it the job posts nothing and passes.
main's build signed only the standard package, so the pubg, antutu and
ludashi variants existed only after a manual Release APKs run. The build job
now reads the variant list from tools/release/variants.txt, as release.yml
does, and main's signing job signs all of them.
Cemu never showed a frame on DroidDeck: its Getting Started dialog blocked
every first launch (the folder picker cannot reach ROMs), the session's
controller helper aborted it, and the desktop's Vulkan renderer drew no
cursor. With the Turnip KGSL fix in the driver and the haptic-optional
Cemu in the catalog, this makes the app side complete:
- bannerlator-pad-defaults seeds Cemu's settings.xml once: the Wii U games
folder, Vulkan, and Cubeb audio on the default device for both the TV
and the GamePad speaker at full volume (Wipeout 3 plays through the
GamePad; Cemu's own default is 20 %).
- The Cemu tile launches full screen (-f).
- libfakeinput.so is preloaded into every session process and exported its
static C++ runtime (~7000 symbols); programs unwound through it and
aborted (shadPS4 in pthread_exit, Cemu's controller thread). Link with
--exclude-libs,ALL, and fail the build if the runtime leaks out again.
- On the Vulkan and GLES desktops the pointer worked but no cursor was
drawn: wlroots hands the cursor to the app's compositor, which draws
none. WLR_NO_HARDWARE_CURSORS=1 makes labwc composite it itself.
Device-tested on the FIT: Super Mario 3D World in-game at 35-37 fps with
sound, Deus Ex HR DC and Wipeout 3 launch with sound; RPCS3, Dolphin and a
Steam session (FlatOut) unchanged on the same driver.
After a pull request's Build APK run succeeds, its APK is published as the
pr-<number> prerelease in Droid-Deck/DroidDeck-CI, named
DroidDeck-PR.<number>-<commit>.apk, with release notes taken from the pull
request. New commits to the same pull request replace its APK. Pull requests
from forks are resolved by head owner, branch and commit.
A pull request's build is signed only with the committed testkey, so every CI
build installs over the last; the publish checks the certificate against it
and refuses anything else.
Needs a DROIDDECK_CI_TOKEN secret: a fine-grained token with Contents
read/write on Droid-Deck/DroidDeck-CI. Without it the run skips with a warning.