“My emulator lags on Android” can mean four different problems: slow from the first second, fine at first but slower after a while, a smooth picture with crackling audio, or freezes only when the game reads data. Each has a different cause, and the fix for one often does nothing for the others.
This guide works from symptom to cause on Android phones, tablets and Android handhelds, using RetroArch and PPSSPP as examples. It does not cover which app or phone to pick. Menu paths, labels and defaults were checked against RetroArch 1.22.2 and PPSSPP 1.20.4, the stable releases as of September 2026; menus can move in other versions.
- Step 1: Turn on the speed readout before changing anything
- Slow from the start: remove settings load, then find the hardware ceiling
- Fine at first, slower after a while: heat and power settings
- Audio crackles: speed problem or sync problem?
- Stalls when the game reads data: storage and disc access
- RetroArch on Android: the settings that quietly add load (and the ones that don’t fix slowdown)
- Symptom cheat sheet
- A note on game files
Step 1: Turn on the speed readout before changing anything
Put a number on the screen first, so you know whether the game is really running slow and whether a change helps.
- RetroArch: Settings > User Interface > On-Screen Notifications > Notification Visibility > Display Framerate (off by default). Display Statistics sits in the same place. Notification Visibility only appears while on-screen notifications are enabled. Some libretro docs still show an older On-Screen Display path.
- PPSSPP: Settings > Graphics, under Overlay information: tick Show FPS counter and Show Speed.
The target is not “60 fps”. It is the speed of the original hardware, shown as 100% on a speed readout; the right frame rate depends on the system and the game. If speed sits around 100% and the game still feels wrong, look at frame pacing or audio rather than performance.
The most useful test needs no settings: note the numbers in one scene right after you start, then check the same scene after playing for a while. Slow from the start points to settings load. Full speed first and slower later points to heat and power. No fixed percentage or number of minutes proves either, so compare your own readings.
Slow from the start: remove settings load, then find the hardware ceiling
Remove optional load one item at a time and watch the readout after each change.
Resolution and texture upscaling
PPSSPP’s Rendering resolution (Settings > Graphics) runs from Auto (1:1) and 1x PSP to 10x PSP. On Android it defaults to 2x PSP when the screen’s long edge is at least 1000 pixels, so many phones start above native. The docs note “Setting it to higher values than 1x can affect performance, depending on your hardware”. Try 1x PSP first. Also check Upscale type and Upscale level under Texture upscaling; the in-app hint reads “CPU heavy – some scaling may be delayed to avoid stutter”. In RetroArch, 3D cores often have an internal resolution option in their core options; set it to native while testing.
Shaders, Run-Ahead and Rewind
RetroArch’s troubleshooting guide lists “Disable shaders” and “Disable Run-Ahead in the Latency options” for low frame rate, and Rewind warns about its own cost. Turn all three off for a clean test; details are in the RetroArch section below.
Frame skipping, last
PPSSPP has Frame skipping (Off or 1 to 8, Off by default) and Auto frameskip (off by default), which the docs call “Not generally recommended for use, only use on very low-power devices.” It trades smoothness for speed, so touch it last.
When nothing helps
If the game stays below 100% at native resolution with shaders, Run-Ahead and Rewind off, you have most likely reached what the chip can do for that system, and settings will not close the gap. Custom Adreno drivers (Turnip), which standalone emulators such as PPSSPP and Dolphin can load, are a separate hardware topic with no equivalent for Mali GPUs.
Fine at first, slower after a while: heat and power settings
A game that starts at 100% and slides later points toward heat. Android’s developer docs: “Devices can only maintain a high level of performance for a limited amount of time before being thermally throttled.” How long that takes depends on the device, room and workload.
What adds heat
Samsung’s summer safety guide notes that playing demanding games while charging can make a phone feel hotter, since use and charging happen together. It also warns against places that trap heat (under a blanket or pillow, in a pocket or bag), direct sunlight, parked cars, non-genuine chargers and damaged cables, and gives 0 to 35°C as the appropriate operating temperature. Unplug and move somewhere cooler before blaming settings.
Power saving modes
Make sure you are not playing in a battery saving mode. On Pixel phones, Battery Saver turns off smooth display (high refresh rate) and Extreme Battery Saver slows the CPU. Samsung’s Power saving has an optional Limit CPU speed to 70%, and switches the screen to Standard (60Hz).
Game modes and boosters
Android’s Game Mode depends on the game implementing its own optimizations or on phone-maker interventions, and an emulator is not guaranteed to count as a game, so results depend on the device and app. On Galaxy phones, Samsung says Game Booster “can only be used with game apps”, so first check whether your emulator even appears in Gaming Hub; that also decides whether options such as Pause USB Power Delivery apply.
Sustained Performance Mode
RetroArch for Android has Settings > Power Management > Sustained Performance Mode: off by default, Android 7.0 or later, and only active on devices that support it. Android describes the mode as “intended to provide a consistent level of performance for prolonged amount of time.” It favours consistency over peak speed, so test it with the readout rather than expecting a boost.
Clip-on coolers
Clip-on fans and Peltier coolers are easy to find. Peltier units can cause condensation: one maker’s FAQ advises against using its cooler over a case because the temperature difference can let water collect, while REDMAGIC calls a small amount “perfectly normal” and harmless. Follow your cooler’s instructions and never mount one over a case.
Audio crackles: speed problem or sync problem?
Crackle is often a symptom, not the cause. Watch the speed readout while it happens.
Speed below 100%
The emulator cannot produce frames, and their sound, fast enough, and audio settings will not fix that. Reduce settings load first. Frame skipping is the tool for this case; in RetroArch it is a core option. PCSX ReARMed’s Frameskip (disabled by default) is described as “Skip frames to avoid audio buffer under-run (crackling). Improves performance at the expense of visual smoothness.”
Speed holds at 100%
Then look at audio and video timing in RetroArch:
- Audio Latency (ms), Settings > Audio > Output (also under Settings > Latency). Android default: 128 ms. The libretro docs say it “perhaps unintuitively should be kept higher, not lower”, since too low a value causes stutter. If you lowered it, restore the default.
- Dynamic Audio Rate Control is already active by default and does not fix slowdown (see below).
- Threaded Video: if you enabled it, turn it off. The docs say it “is well known to interfere with smooth frame pacing and audio sync”.
On high refresh rate screens, also check VSync Swap Interval and Vertical Refresh Rate below. A high refresh rate is worth testing, but it is not automatically the cause.
Stalls when the game reads data: storage and disc access
Disc-based systems such as the PS1 read from the disc image during play, not only on loading screens, so slow storage can cause hitches mid-game. RetroArch PS1 cores offer options for this:
| Core | Option | Default | Notes |
|---|---|---|---|
| Beetle PSX HW | CD Access Method | Synchronous | Asynchronous “can reduce stuttering on devices with slow storage”; Pre-Cache loads the whole image into memory, may cause problems on low-memory devices and needs a restart |
| SwanStation | CD-ROM Read Thread | Enabled | Preload CD-ROM Image To RAM and Pre-cache CHD Images To RAM are disabled by default |
| PCSX ReARMed | CD read-ahead | 12 sectors | How far ahead the core reads |
microSD and internal storage
The SD Association states “A2 performance is available only the combination of A2 supported host and A2 supported card.”, so an A2 card alone does not guarantee A2 speed. If you have space, play the same section of a problem game from internal storage and from the card, and compare.
Slow game lists and background apps
Android’s Storage Access Framework can make library scans slow. Dolphin’s developers called it “extremely slow” for game list loading but added “this does not actually affect emulation performance.” Closing apps you are not using is sensible, and Samsung’s heat guide suggests restricting background app usage when the phone runs hot. The developer option Background process limit is documented as a testing tool for app developers, with no stated gaming benefit, so it is not a recommended fix.
RetroArch on Android: the settings that quietly add load (and the ones that don’t fix slowdown)
Several RetroArch settings sound like performance fixes. Some add load, some trade one problem for another, and some do something else entirely.
| Setting (1.22.2 path) | What it does | Load | Common mistake |
|---|---|---|---|
| Threaded Video (Settings > Video > Output), off | “Improves performance at the cost of latency and more video stuttering. Use only if full speed cannot be obtained otherwise.” | May help software-rendered cores only | Turning it on to cure stutter |
| Dynamic Audio Rate Control (Settings > Audio > Synchronization), 0.005 | A number, not a switch; corrects small timing mismatches, 0 disables it | Not a speed setting | Expecting it to fix crackle from slowdown |
| Audio Latency (ms) (Settings > Audio > Output), 128 on Android | Maximum audio latency | Not a speed setting | Lowering it |
| Run-Ahead (Settings > Latency) | Runs frames ahead to cut input lag | More frames, more CPU | Treating it as free |
| Rewind Support (Settings > Frame Throttle > Rewind), off | Lets you step back in time | “a severe performance hit when playing.” | Leaving it on |
| Shaders (Quick Menu > Shaders) | Post-processing such as CRT effects | Heavy shaders cost more on high resolution screens | Assuming old games make them free |
| Sustained Performance Mode (Settings > Power Management), off | Android-only; asks for consistent performance | Not a peak boost | Treating it as turbo |
| Frameskip (core options) | Skips drawing frames | Less load, less smooth | Looking in main settings, which only have Fast-Forward Frameskip |
Threaded Video
In 1.22.2 it is not applied when a core renders through the GPU, so it only affects software-rendered cores. It also makes RetroArch ignore Vertical Refresh Rate, per that setting’s description. Development builds after 1.22.2 rewrite this setting, so read the description in your own version.
Dynamic Audio Rate Control
Its description: “Helps smooth out imperfections in timing when synchronizing audio and video.” At the default it adjusts within about half a percent either way, far too little to cover a game running well below full speed. Leave it at the default.
120Hz screens
VSync Swap Interval (Settings > Video > Synchronization, default 1): “‘Auto’ sets factor based on core-reported frame rate, providing improved frame pacing when running e.g. … 60 fps content on a 120 Hz display.” Vertical Refresh Rate (Settings > Video > Output) is “Used to calculate a suitable audio input rate.” and can be taken from Estimated Screen Refresh Rate. Check these alongside the phone’s own refresh rate setting. Automatic Refresh Rate Switch does not appear on Android, and RetroArch’s Game Mode setting is Linux-only; desktop guides that mention them do not apply here.
Symptom cheat sheet
| What you notice | Speed readout | Try first | Skip |
|---|---|---|---|
| Slow from the first minute | Below 100% from the start | Native resolution; shaders, Run-Ahead, Rewind off | Dynamic Audio Rate Control |
| Slower after a while | 100% early, lower later in the same scene | Unplug, cooler spot, power saving off | Background process limit |
| Crackle with slowdown | Below 100% | Cut settings load; frame skipping last | Lowering Audio Latency |
| Crackle at full speed | Around 100% | Default Audio Latency; Threaded Video off | Frame skipping |
| Hitches in disc-based games | Short dips mid-play | CD access core options; compare storage | Assuming only loading screens matter |
| Game list slow to appear | Normal in game | Nothing in-game | Emulation settings |
In short: measure first, change one thing at a time, and match the fix to the symptom.
A note on game files
Use game data and BIOS files you dumped yourself from discs, cartridges and consoles you own, and do not download game or BIOS files shared online without the rights holder’s permission. Rules on backups differ by country, and in the United States even personal backups are not clearly settled. This is general information only, and this is not legal advice; for your own situation, ask a qualified lawyer where you live.
コメント