← All guidesPC games

Winlator vs GameHub Lite vs GameNative: play PC games on your Android handheld

Last verified · Overclocked guides

Which Windows-game app to pick, how to set up a container, and the DXVK, FEX/Box64 and resolution settings that actually raise FPS.

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?

Step-by-step: first container

  1. Install the app from its official GitHub or store page. Give storage permission when asked.
  2. 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.
  3. Screen size: 1280x720 on 7xx/8xx chips, 960x540 on Adreno 6xx.
  4. Graphics driver: Turnip for 6xx/7xx, an a8xx/Gen8 build or Qualcomm v8xx for 8xx (driver guide).
  5. DXVK: start with 2.4.1 (prereg or gplasync builds) for DX9-11 games. DX12 games need VKD3D and are much heavier.
  6. FEX preset: Performance. If a game crashes, try Compatibility, or switch to a Box64 container.
  7. Install or download the game (GameNative/GameHub: from your Steam library; Winlator: run the installer you bought, e.g. from GOG).
  8. Make a shortcut, then set per-game overrides there so one game's tweaks don't break the others.

Squeeze out more FPS

Common fixes

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