Pin Gamescope with the Steam client again outside Qualcomm sessions

The Qualcomm port stopped pinning Gamescope to the Steam client's cores for
every session. Outside Qualcomm sessions Gamescope does not copy frames
through X11 SHM, and a user who restricts the client's cores still expects
Gamescope on them, as since #152. Only Qualcomm sessions skip it now.
This commit is contained in:
The412Banner committed 2026-10-25 23:14:04 +00:00
1 parent 18735361d7
commit 563dff6d75
2 files changed
+7 -2

No files matched your search

@@ -1213,7 +1213,12 @@ BUSCONF
for _d in /proc/[0-9]*; do
{ IFS= read -r -d '' _c && { IFS= read -r -d '' _c1 || _c1=; }; } < "$_d/cmdline" 2>/dev/null || continue
case $_c in FEX|*/FEX|FEXInterpreter|*/FEXInterpreter) _c=$_c1 ;; esac
case $_c in *steamwebhelper*|*steamrtarm64/steam|*steamrt64/steam) ;; *) continue ;; esac
case $_c in
*steamwebhelper*|*steamrtarm64/steam|*steamrt64/steam) ;;
# Qualcomm sessions copy every frame through X11 SHM inside Gamescope; the client's cores starve it.
*gamescope*) [ "${DROIDDECK_SYSTEM_QUALCOMM:-0}" != 1 ] || continue ;;
*) continue ;;
esac
_t=("$_d"/task/*)
_p=${_d#/proc/}
[ "${_bl_pinned[$_p]:-}" = "${#_t[@]}" ] && client_single_core_matches "$BL_CLIENT_CPUS" "${_t[@]}" && continue