gamescope: payload 20261105.3, the shim's resolve probe clamps the core version only (gamenative-drm #55)

Merged
UT
5d ago
+1-1

What changed

GamescopePayload.VERSION 20261104.3 -> 20261105.3 (archive gamescope-gamenative-20261105.3.tzst). Nothing else in the app changes; the daemon jniLibs are unchanged.

Payload = 20261104.3 with lib/libadrenotools_gamescope.so rebuilt from https://github.com/GameNative/gamenative-drm/pull/55 (squashed to 0aa0446, not merged yet). The shim's resolve probe now only clamps the core version: it judges each core version by the exact core command names, using a bare probe device. It no longer hides extensions, it is skipped for 1.0 instances, and it logs how many ms it took.

Fixes the Honor GT (MagicOS, Android 16) Xwayland zink abort that 20261104.3 did not fix: there the probe logged "core version 1.4 resolve" while every 1.4 core name came back NULL, so apiVersion was not clamped and zink still died in its not-loaded stub. No change on devices where everything resolves.

Do not use gamescope-gamenative-20261105.1.tzst or gamescope-gamenative-20261105.2.tzst. Both are still live on the hosts. .1 carried a shim (stamp 202611050550ae024d4) that failed the RP6 no-change check: it clamped gamescope's 1.3 instance and a 1.0 Wine helper instance. .2 (stamp 202611050601569a5e0) is superseded by this pared-down shim.

Payload

Devices

DeviceCheckResult
RedMagic 6A/B against the pre-#54 shimPASS: never clamps; the probe takes 3.2-4.6 ms per process (about 15 ms per launch); time-to-window +0.10 s, inside the 2.1 s launch-to-launch noise
Honor GT (MagicOS Android 16)reporter test with an ad-hoc build20261105.2 verified by the reporter (clamp to 1.3, game runs); .3 re-verification pending

Summary by cubic

Bumps the gamescope payload to 20261105.3, shipping a rebuilt libadrenotools_gamescope.so that fixes the shim's resolve probe on Honor GT (MagicOS, Android 16). The probe now clamps the core version only, which fixes the Xwayland zink abort for devices where promoted-extension aliases resolve but the core command names come back NULL. No change where all core names resolve. The .1 archive was pulled because its shim failed the RP6 check; .2 was superseded by .3.

Rollout

  • GamescopePayloadDownloadTest fails until the archive is uploaded to both hosts; merge only after both serve gamescope-gamenative-20261105.3.tzst.

Summary by CodeRabbit

  • Updates
    • Updated the Gamescope payload to a newer version. The app continues to select the archive and check availability based on the current payload version, so the updated payload is reflected in readiness status. This change does not alter how Gamescope features are accessed.