GameCore 3.5.4 — config editor and resolution override

Two features in this release: a config editor for the games that keep their settings in a file, and a per-game render resolution.

Config editor

Some games keep their graphics and control settings in a plain config file in their own shared-storage directory, and changing a value there is the only way to reach a setting the game's own menu does not offer. GameCore can now browse and edit those files.

• It stays inside the game's own Android/data/<package>/files directory. A path guard refuses anything that tries to climb out of it, and it never touches the game's code or its private storage.
• Every write is shown to you line by line before it happens. You see exactly which lines change, and nothing is written until you confirm.
• The file is staged and then committed whole, atomically, so an interrupted write cannot leave a half-rewritten config behind.
• The original is backed up automatically before the first edit. You can also take named checkpoints as you go and restore any of them later.
• If the game updates its config file behind you, the editor says so rather than quietly writing over the new version.
• A one-time notice before your first edit, and it needs Shizuku.

Resolution override

• A per-game render resolution, set as a scale of the display's native size and applied through wm size when the game comes to the front.
• Cleared and the display put back exactly as it was when the game leaves — the same restore rule every other profile field follows.
• Lowering it can lift frame rate on a GPU-bound game, at the cost of sharpness. It is per game, off unless you set it, and it asks once for confirmation the first time because it reshapes the whole display while the game runs.
• An in-game status chip shows while an override is active, so a changed resolution is never a mystery. Needs Shizuku.

Also in this build

These have been in the source since 3.5 but have never shipped in a release until now:

• A pinned magnifier — a loupe that shows the centre of the screen enlarged. A crop-and-scale of one capture frame, parked so it can never magnify itself. No detection, no tracking, no aim logic.
• Panel macros — a named, ordered set of overlay actions you already have, fired in sequence by one tap.
• Config backup and restore — export every configuration store to one file and restore it later. Configuration only; your recorded sessions are never written into it and a restore cannot overwrite them.
• Profile transfer — share game profiles as a file, presets and all, recreating what is missing and matching-then-remapping what already exists.
• Profile suggestions — a starting profile derived only from what a game was measured doing, with a sentence behind every field. A game with thin history gets no suggestion rather than a guess.
• Per-sample export — one row per sample, the raw time series behind a graph, as CSV or JSON. Blank, never zero, for a reading a sample never took.

Notes

• Database schema 13, migrated in place. Your profiles, sessions and Aim Lab runs carry over.
• Five new elevated commands (ls, stat, cp, mv, rm -f), all bounded to one game's own config directory and enumerated by the command test alongside every other one.
• No new Android permissions.
• The README's account of what the app can run with elevated authority has been brought up to date, including the config editor's writes.

versionCode 22 · versionName 3.5.4 · minSdk 26 · targetSdk 34