Winlator vs GameHub Lite vs GameNative: play PC games on your Android handheld
Which Windows-game app to pick, how to set up a container, and the DXVK, FEX/Box64 and resolution settings that actually raise FPS.
⚖ Play legal. Dump keys, firmware, BIOS and games from consoles and copies you own. Overclocked never hosts or links to keys, firmware, BIOS, ROMs or game files, and we don't say where to find them. Only download apps and drivers from their official pages.
Running Windows games on an ARM handheld takes two translation layers: the CPU code goes through FEX or Box64, and the graphics through DXVK/VKD3D → Vulkan. Three apps package this up. Here's how to choose one and set it up properly.
Which app?
- GameNative (open source): signs in to your own Steam account and installs games you own. The easiest start, and it supports Lossless Scaling frame gen if you own that app.
- GameHub Lite: a community build of GameHub with the tracking removed. A simple, curated driver list and Steam support.
- Winlator (Bionic forks such as Ludashi): the most control (custom drivers, components, environment variables). Best for tinkerers and GOG installers.
Step-by-step: first container
- Install the app from its official GitHub or store page. Give storage permission when asked.
- Create a container. Pick Proton 10 arm64ec (uses FEX) as your default. Use an x86_64 container with the Box64 preset on Intermediate for game installers and very old games.
- Screen size: 1280x720 on 7xx/8xx chips, 960x540 on Adreno 6xx.
- Graphics driver: Turnip for 6xx/7xx, an a8xx/Gen8 build or Qualcomm v8xx for 8xx (driver guide).
- DXVK: start with 2.4.1 (prereg or gplasync builds) for DX9-11 games. DX12 games need VKD3D and are much heavier.
- FEX preset: Performance. If a game crashes, try Compatibility, or switch to a Box64 container.
- Install or download the game (GameNative/GameHub: from your Steam library; Winlator: run the installer you bought, e.g. from GOG).
- Make a shortcut, then set per-game overrides there so one game's tweaks don't break the others.
Squeeze out more FPS
- Lower the in-game resolution before the container resolution.
- Cap at 30-40 FPS. Steady beats spiky, and it keeps the device cooler.
- Prefer the DX11 mode if a game offers DX11 and DX12.
- Set the handheld to its high-performance mode with an active fan profile.
- Frame generation only helps when you're already at 45+ FPS (frame gen guide).
Common fixes
- .NET errors: install Wine Mono from the container's start menu (Winlator).
- Old game won't open: try the env var
MESA_EXTENSION_MAX_YEAR=2003. - Stutter on first play: that's shader compilation, and it fades after the first run. gplasync DXVK builds help.
Compat reports: GameNative → Compat reports: Winlator → Compat reports: GameHub →
Shortcut: get a driver + settings recommendation for your exact device. Open the setup wizard
More guides
Custom GPU drivers on Android handhelds: Turnip vs Qualcomm, explainedDriversEden setup on Android handhelds: first boot to per-game tuningSwitchDay-one setup for a new Android handheld (Odin 3, Retroid Pocket 6, Thor and more)SetupES-DE vs Daijishō vs Beacon: pick and set up an Android frontendFrontendsFrame generation on Android handhelds: when it helps and how to turn it onPerformance