Files
DroidDeck/app/src/main/res/xml/game_mode_config.xml
T
The412Banner 06e67cd7d5 session: run as a game — game category + game_mode_config, sustained performance mode, fastest display mode, ADPF hint session on the compositor thread, 16 KB-aligned libraries
The manifest now declares the app a game (appCategory, isGame) with a game_mode_config that
welcomes Performance mode and refuses the OS-side FPS cap and resolution downgrade — the
interventions that make a regular flagship's Big Picture crawl while a gaming phone's does not.
The session window asks for sustained performance mode and the panel's fastest mode at its size,
tells GameManager it is in gameplay, and opens a PerformanceHintManager session over the
compositor thread fed with each presented frame's interval against the panel's period. All
version-guarded (6/7/12/13); the session log carries one 'perf:' line saying what took.

The app's own libraries link with 16 KB-aligned LOAD segments (loads unchanged on 4 KB kernels).
Six prebuilt PulseAudio libraries under jniLibs are still 4 KB-only and need a rebuild.
2026-09-22 17:39:04 -04:00

16 lines
923 B
XML

<?xml version="1.0" encoding="utf-8"?>
<!--
What Android's GameManager (12+) and the OEM game services keyed to it may do to a session.
Performance mode is welcome: it is what raises the clock floor on a regular flagship the way a
gaming phone's mode does out of the box. What is refused is the two "helpful" interventions
that make a game look slow: Samsung's Game Optimizing Service and its cousins cap unknown
games' frame rate (allowGameFpsOverride) and render them at a lower resolution
(allowGameDowngrade). gamescope already owns the output size; a cap on top of Big Picture's
own pacing is exactly the low-fps-on-a-flagship symptom.
-->
<game-mode-config xmlns:android="http://schemas.android.com/apk/res/android"
android:supportsPerformanceGameMode="true"
android:supportsBatteryGameMode="true"
android:allowGameDowngrade="false"
android:allowGameFpsOverride="false" />