android: disable the A52 vblank time-grid fps limiter patch
Moves 0050-A52-fps-limit-on-the-vblank-time-grid.patch out of android/patches/gamescope/ into android/patches/disabled/, where android/build-gamescope.sh does not apply it.
With the patch gone, the non-VRR frame-rate limit counts compositor wakeups again (steamcompmgr_should_vblank_window, vblank_idx % nVblankDivisor) instead of releasing on the vblank time grid. That equals every Nth vblank only while no wakeup is ever late: CVBlankTimer::GetNextVBlank steps to the next vblank after now, so a wakeup landing more than one vblank late skips the vblanks in between and vblank_idx never counts them. The finer the session grid, the sooner a wakeup is late — a sub-millisecond scheduling delay already cost a whole vblank — so each late wakeup held the next release a vblank longer and the cap read below its target: the 18-21 ms frames with the CPU and the GPU idle that #22 measured at 54 of 60. The launcher no longer passes a fine grid, which is why the patch is disabled rather than merely unapplied.
One file, a rename, so re-enabling is the reverse move. The VRR path is untouched either way, and no other patch depends on it.
Paired changes
- GameNative app — https://github.com/utkarshdalal/GameNative/pull/2313: ships this build as payload
20261101.1.
With A52 out of the payload, the limiter the app drives is the compositor's own divisor-based
one; the app-side cap and frame generation are unchanged by this rename.