mirror of
https://github.com/Droid-Deck/DroidDeck.git
synced 2026-11-19 04:46:08 +00:00
fix: read droiddeck-env from ps (#413)
This commit is contained in:
1 parent
6eda278d9b
commit
5954ac58f8
4 files changed
+42
-14
No files matched your search
@@ -61,7 +61,7 @@ Why the current choices were made, from the history:
|
||||
|
||||
All runs on the AYN Thor (SD 8 Gen 2, Adreno 740, 1920x1080 top panel), Deck mode on, Force
|
||||
fullscreen off, with a spike build of `feat/steam-native-output`. Each run sets
|
||||
`Download/droiddeck-env` and starts the session with
|
||||
`Android/data/com.droiddeck.launcher/files/droiddeck-env` and starts the session with
|
||||
`am start -n com.droiddeck.launcher/.SessionActivity --es mode steam [--es steamUrl ...]`.
|
||||
|
||||
### Run 1: baseline (Resolution = Match screen, 1920x1080)
|
||||
@@ -181,7 +181,7 @@ game. `--xwayland-count 2` and `STEAM_MULTIPLE_XWAYLANDS=1` went through `Downlo
|
||||
## Two Xwayland servers by default (`feat/steam-dual-xwayland`)
|
||||
|
||||
Steam sessions now start gamescope with `--xwayland-count 2` and `STEAM_MULTIPLE_XWAYLANDS=1`.
|
||||
`BL_XWAYLAND_COUNT=1` in `Download/droiddeck-env` goes back to one. The session script's
|
||||
`BL_XWAYLAND_COUNT=1` in `Android/data/com.droiddeck.launcher/files/droiddeck-env` goes back to one. The session script's
|
||||
root-window requests that are meant for the game (the drawer's live Force fullscreen,
|
||||
`GAMESCOPE_FORCE_WINDOWS_FULLSCREEN`, and the resume watcher's `GAMESCOPE_RESTORE_FOCUS_WINDOW`)
|
||||
go to both displays, `$DISPLAY` and `STEAM_GAME_DISPLAY_0`. gamescope reads both per server, so
|
||||
@@ -222,7 +222,7 @@ reason "Force game windows fullscreen" existed. What it still did was make any g
|
||||
Resolution differs from what it draws fight it (runs 4 and 5). The switch is gone from Steam
|
||||
settings (Games) and the session drawer (Display), along with its preference, the
|
||||
`BL_GAMESCOPE_FORCE_FULLSCREEN` flag, the `~/.droiddeck-fill` live watcher and the device report
|
||||
line. `BL_GAMESCOPE_ARGS=--force-windows-fullscreen` in `Download/droiddeck-env` still passes the
|
||||
line. `BL_GAMESCOPE_ARGS=--force-windows-fullscreen` in `Android/data/com.droiddeck.launcher/files/droiddeck-env` still passes the
|
||||
flag for an experiment.
|
||||
|
||||
Device check (Thor): Alan Wake's American Nightmare with its 1280x720 Game Resolution runs on `:1`
|
||||
|
||||
@@ -81,7 +81,7 @@ $R/usr/lib/ld-linux-aarch64.so.1 --library-path $R/usr/lib $R/usr/bin/xprop -dis
|
||||
nothing.
|
||||
- To test gamescope with a candidate binary without rebuilding the apk, put it in the rootfs (for
|
||||
example `/opt/gstest/gamescope`, owned by the app's uid) and add
|
||||
`PATH=/opt/gstest:/usr/local/bin:/usr/bin:/bin` to `Download/droiddeck-env`. The session log's
|
||||
`PATH=/opt/gstest:/usr/local/bin:/usr/bin:/bin` to `Android/data/com.droiddeck.launcher/files/droiddeck-env`. The session log's
|
||||
first lines name the gamescope that ran. Remove the line afterwards: the app stages its own
|
||||
gamescope over `/usr/local/bin` at every session start.
|
||||
- Never `pkill -f <pattern>` inside `su -c '…'`: the pattern matches that shell's own command line.
|
||||
|
||||
Reference in new issue
Block a user