Common handheld problems & fixes

Quick answers to the issues new Android and PC handheld owners hit most. Start with the simplest fix and change one thing at a time.

Games stutter, especially the first time

Most first-run stutter is shader compilation and gets better as the shader cache fills. Enable asynchronous shaders if the emulator offers it, use a higher performance mode, and on Snapdragon devices try a different GPU driver. Close background apps.

Black screen when a game starts

Check the BIOS/firmware/keys the emulator needs are installed and match what it expects. Try the other graphics backend (Vulkan vs OpenGL), switch back to the system GPU driver or a previous custom driver, and clear the shader cache. Confirm your game dump isn't corrupted.

Controller not detected or buttons wrong

Open the emulator's input/controller settings and select the built-in controller, then remap. Make sure the device's controller mode (e.g. Xbox vs Nintendo layout toggle) is what you expect. For Bluetooth pads, re-pair after a reboot. In Winlator/GameHub, check the container's input settings.

Games run slowly

Lower the resolution scale first, then turn off extras like heavy filters. Use a higher performance mode. Check the compatibility database for settings that worked on your device. Some games are simply too heavy for some chips.

Audio crackles or stutters

Audio crackle usually means the game isn't hitting full speed, so fix performance first. Try increasing the audio buffer/latency setting or switching audio backend in the emulator.

Winlator or GameHub crashes

Change one setting at a time: try a different graphics driver, a different DXVK/VKD3D version, and lower in-game settings. Make sure the game has the Windows dependencies it needs (e.g. Visual C++ runtimes) installed in the container. Try a fresh container if one got broken. Our Winlator/GameHub guide.

Custom GPU driver won't install or work

Custom drivers like Turnip only work on Qualcomm Adreno GPUs, and you need a build for your Adreno generation. Install the release .zip as-is (don't extract it), from the emulator's driver manager. If a game breaks, switch back to the system driver. Driver guide.

Device gets hot or battery drains fast

Higher performance modes and resolution scales use more power. Lower them for lighter games, cap frame rate where possible, and on PC handhelds lower TDP. Don't block the vents, and use a quality charger.

Emulator says BIOS or keys are missing

Point the emulator to the folder where your dumped files are, and check the file names match what its documentation asks for. Overclocked can't provide these files; dump them from your own hardware.

Emulator or frontend can't see my games

On Android, grant the app storage/folder access to your ROMs folder and re-scan. Check games are in the right per-system subfolder for your frontend.

Still stuck? Look up your game in the compatibility database, or submit a report once you get it working to help others.

New here? Start with Start Here or the glossary.