On the Pocket FIT (Android 14, Adreno 750, Qualcomm 0.762.24) every Qualcomm
session failed before Steam: the bridge compares one core query between
Android's libvulkan instance and its own HAL, and Android 14's loader wraps
vkGetPhysicalDeviceProperties, so the check rejected the instance
(VK_ERROR_INCOMPATIBLE_DRIVER) although vkGetPhysicalDeviceFeatures resolved
to the same vulkan.adreno.so entry from both sides.
0012-android-loader-wrapped-queries.patch (for taowen/libhybris bc8cb358 with
wallentx's patches 0001-0011) accepts the instance when any of five core
physical-device queries resolves to the HAL's own entry. The bridge is
rebuilt with it on DroidDeck-Components.
qualcomm-runtime-r3-4b8c7f84-qa (DroidDeck-Components run 40244231868) was
built from this branch's patch series: only the Gamescope binary and its
source archive changed; Zink and the WSI layer rebuilt byte-identical to r2.
The libhybris bridge and WSI archives now come from that release, mirrored
unchanged from wallentx/DroidDeck (same SHA-256 and size; the original URLs
stay in mirrored_from).
runtime.json now records the patch series the Gamescope was built from, and
a test fails when a Gamescope patch changes without a rebuild, so the
Qualcomm Gamescope cannot silently fall behind the regular one.
On the X11 SHM path Gamescope's WSI layer is disabled, so its two
Performance mode parts (more swapchain images, the present-check cache)
cannot apply; the unpaced release and Wine's window-check cache still do.
With zero-copy every part applies. The log now says which case a session is in.
Every Qualcomm session started the driver through libhybris twice before
Steam: droiddeck-qualcomm-caps (up to 20 s) and glxinfo for the browser's
OpenGL level (up to 15 s). Both answers only change with the driver, so
they are now saved under $XDG_CACHE_HOME/droiddeck and reused while the
driver file (SHA-256), the selected driver, the bridge build, the layers
and the check script are unchanged. Gamescope's linux-dmabuf global is
still checked every session, failed or empty results are never saved, and
the log marks a reused result.
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.
0120 (nested swapchain capability fallback) and 0124 (SDL explicit refresh)
only matter for gamescope's SDL backend, which only Qualcomm sessions use.
In tools/gamescope/patches they would go into the next regular gamescope
release for every user. They now live in tools/qualcomm/gamescope-patches;
build_gamescope.py reads both folders in name order, so the Qualcomm build
applies the same series as before.
0121 and 0123 only change anything on PowerVR (vendor 0x1010) and are dropped.
0122 is renamed 0122-dmabuf-import-memory-type: it keeps the part every
vendor uses (the imported DMA-BUF's memory type must also be allowed by
vkGetMemoryFdPropertiesKHR) and drops the PowerVR-only query retry.
The full series still applies to gamescope 8f212644 (3.16.29).
The builds come from the DroidDeck-Components qualcomm-runtime release, built on ARM64 CI from this branch, so CI and fresh checkouts can stage the Qualcomm runtime without building it locally. The pins now match those Linux builds.
(cherry picked from commit 2ed529842d)
wallentx's libhybris runtime builder and patches, prebuilt bridge and WSI
releases, system-driver staging, android_wlegl buffer receiver and
Gamescope integration patches are what this backend is built on.
JeezDisReez identified turning off the image-bounds rewrite on Adreno as
the fix for the red graphics in DRAGON BALL: Sparking! ZERO.
(cherry picked from commit 09eb999a3a)
Older Adreno drivers such as the 8 Gen 2's 0.676.1 lack
VK_EXT_external_memory_dma_buf, DRM modifiers and calibrated timestamps.
They failed device creation in the WSI layer, failed Proton games on the
zero-copy path, and corrupted the Steam UI under GPU compositing.
- WSI patch 0005 makes the Wayland platform optional per device, so a
device without its extensions stays usable for X11 swapchains instead
of failing vkCreateDevice.
- droiddeck-qualcomm-caps checks DMA-BUF export and import, the swapchain
extensions and Gamescope's linux-dmabuf once per session; Proton games
use the zero-copy WSI path only when it passes and stay on X11 SHM
otherwise. The session log records the verdict.
- The Steam browser uses software compositing when Zink offers less than
OpenGL 4.0, with BL_STEAM_CEF_SOFTWARE as the manual override.
Verified on the Adreno 740 (falls back to SHM and software compositing,
UI correct) and the Adreno 840 (zero-copy and GPU compositing unchanged).
(cherry picked from commit d8d0b10cced1f21a1e9bc7dca00efd89b389adb3)
(cherry picked from commit 00775f0511)
VK_LAYER_HYBRIS_compat enables a Mali+DXVK workaround by default that
replaces the zero operand of the next OpSelect after any image sample or
fetch. On Adreno it collapses DXVK's comparison selects to constants,
which turned Sparking Zero's main-menu scene red.
(cherry picked from commit 8962b4f6f8c6d46178596dcfb02f98543135744d)
(cherry picked from commit d9c84afa8b)
Games in Qualcomm sessions now hand Gamescope LINEAR DMA-BUFs exported by
the driver instead of copying frames through X11 SHM. The ARM WSI layer is
rebuilt with its Wayland backend and the private Gamescope gains a
linux-dmabuf global without a DRM device. BL_QUALCOMM_SHM=1 keeps the
shared-memory path; Turnip sessions are unchanged.
(cherry picked from commit 1bd4c04f193f48bdaf4d4aad374010abaf48765d)
(cherry picked from commit d24b824f25)