mirror of
https://github.com/Droid-Deck/DroidDeck.git
synced 2026-11-21 05:46:03 +00:00
feat: x86-64 client follows DroidDeck-Components' fex.json; fuller x86-64 session logs (#1053)
FEX builds can reach devices without an app release: while the x86-64 client is selected the app reads DroidDeck-Components' fex.json (directly, on its own thread, not in Offline Mode) and a session passes that build to droiddeck-steam-x64, which installs it only once its sha256 matches and its programs load, keeping the replaced files aside until the installed copy loads too; it keeps a working installed build otherwise and falls back to the build it pins. FEX is built and published by Components' build-fex.yml on its single fex release; this repository's build-fex.yml only checks the build. x86-64 session logs name the FEX build and its source, the rootfs and the client's builds, report the rootfs download in tenths, and say in one line when the web helper's GPU process keeps exiting, with x86 glxinfo and vulkaninfo through FEX. Settings shows the FEX build installed.
This commit is contained in:
1 parent
798386d02a
commit
292295ba30
12 files changed
+488
-58
No files matched your search
@@ -139,6 +139,27 @@ the timeline, then lessons and backlog. Companion to the README (what the app *d
|
||||
FEX uses). With the device's libxxhash hidden, r4 failed with the reported error and r5 loaded.
|
||||
Mirrored in DroidDeck-Components (#5); the app moves to fex-2610-r5 and an installed r4 is replaced
|
||||
at the next x86-64 start.
|
||||
- Merged as 7d21ba22.
|
||||
- **FEX from the catalog**: FEX builds may need to follow user reports faster than app builds, so the
|
||||
app now reads Components' `fex.json` (directly, kept between starts) and passes it to the session; a
|
||||
build is installed only once its sha256 matches and its programs load, the installed one stays while it
|
||||
loads, and the build pinned in the script remains the first-start default. **Session logs** for the
|
||||
x86-64 client now name the FEX build and its source, the rootfs and the client's builds, report the
|
||||
rootfs download in tenths instead of a progress bar (one report's log ended in hundreds of bar lines),
|
||||
and, when the web helper's GPU process keeps exiting (a report from an Adreno 840: the menus never
|
||||
appeared), say so in one line with x86 `glxinfo`/`vulkaninfo` through FEX. Settings shows the FEX
|
||||
build installed. FEX is now built and published by DroidDeck-Components' `build-fex.yml` from this
|
||||
repository's `tools/fex`, replacing the archive on its single `fex` release and recording the version
|
||||
in `fex.json`; this repository's `build-fex.yml` only checks the build. Tests: `test_fex_select.py`,
|
||||
`FexCatalogTest`.
|
||||
Components' first build there published `2610-r6` (run 39104443888). Device (Pocket FIT, r4
|
||||
installed): the app read `fex.json`, and the next x86-64 start logged `downloading FEX (fex-2610-r6)`
|
||||
then `FEX ready (fex-2610-r6, catalog)` a second later, with the rootfs and client lines; the client
|
||||
came up on it.
|
||||
- Review of #1053: an install keeps the files it replaces aside until the installed copy loads and puts
|
||||
them back otherwise (a failed copy could leave a partly replaced FEX marked as the new one;
|
||||
`test_fex_install.py`), and the catalog is read on its own thread, not before the library scan, and
|
||||
not in Offline Mode.
|
||||
|
||||
## 2026-10-15 - `feat/x86-64-steam-client`: SD card library, ARM parity, org main, Counter-Strike 2
|
||||
|
||||
|
||||
Reference in new issue
Block a user