Getting 90-120 FPS in Android emulators

High frame rates in an Android emulator come from three things lining up: a high FPS target in the emulator, matching in-game graphics settings, and hardware that can actually push it. BRUTAL helps with all three — and is honest about the last one, because no tool can give you frames your GPU and monitor can't deliver.

Step 1: Set the emulator's FPS target

The single biggest lever is the emulator's own frame-rate cap. Many emulators default to 60 FPS. Open Game profiles, pick your game, and set Target FPS to 90 or 120 in the detail panel. When you Apply Profile, BRUTAL writes that FPS value where it finds a setting it knows in the emulator's config file (on BlueStacks, the Nougat 64-bit instance).

For GameLoop specifically, this writes fps in the genuine AowConfig.ini; for BlueStacks it sets the high-FPS config keys; for LDPlayer it edits the instance config's FPS field. If the emulator hasn't created its config yet, launch it once and re-apply.

Step 2: Match the in-game frame-rate option

Setting the emulator to 120 FPS isn't enough if the game itself is capped at 60. Inside the game, choose the highest frame-rate mode the profile lists for your tier — for example a battle royale's "Ultra Extreme (120 FPS)" mode, or a MOBA's high-frame-rate mode with FPS Unlock on. The in-game settings list in each Game Profile spells out exactly which option to pick. Both caps (emulator and game) must be high for high FPS to actually happen.

Step 3: Use a vendor-appropriate renderer

The right graphics API matters. BRUTAL recommends a renderer based on your GPU: OpenGL+ or DirectX+ for NVIDIA, Vulkan for AMD, OpenGL+ for Intel. Set this in your emulator's graphics settings to match the recommendation shown in the profile — the wrong renderer can leave performance (and FPS) on the table.

Step 4: Let BRUTAL handle the system side

Applying a profile already raises the emulator's CPU and I/O priority (IFEO) and prioritises the game's network ports. For Pro users, Guardian goes further while it detects a running emulator: it elevates the emulator's priority live, forces a 0.5 ms timer, disables Windows power throttling (EcoQoS), locks a working-set minimum, and demotes background bloatware. Together these keep the emulator fed so it can sustain a higher frame rate.

Be honest about your ceiling

This is the part other "FPS unlockers" skip. Two hard limits apply:

• Your monitor's refresh rate. A 60 Hz monitor can only display 60 frames per second — rendering 120 just causes screen tearing, not a smoother picture. You need a 120 Hz+ display to actually see 120 FPS.
• Your hardware tier. Each tier (LOW / MID / HIGH / ULTRA) can realistically sustain so much. If you pick an FPS above what your monitor or hardware can do, BRUTAL shows a warning explaining exactly why and recommends a sustainable value.

If you're frequently warned, the recommended number is your honest sweet spot. Lowering in-game effects (shadows, anti-aliasing) buys headroom toward higher FPS before you hit the GPU wall.

How to use it (quick recipe)

1. Confirm your emulator is detected on the Emulators page.
2. In Game Profiles, set Target FPS to 90 or 120 and Apply.
3. Set the matching renderer in the emulator's graphics settings.
4. In the game, select the highest frame-rate mode from the profile's in-game list.
5. Turn the FPS overlay on (Ctrl+Shift+F) to verify the real frame rate (for GameLoop on Windows 11 it counts the game's own frames; for other emulators it shows the display's rate, labelled DISPLAY).

Common issues / troubleshooting

• I set 120 but still get 60. Both caps must be raised — check the in-game frame-rate setting too, not just the emulator. Also confirm your monitor is 120 Hz; a 60 Hz panel caps what you can see at 60.
• The config wasn't written. Launch the emulator once so it creates its config, then re-apply. BRUTAL won't write an orphan file the emulator ignores.
• FPS is choppy at 120. Your hardware tier may not sustain it — heed the warning, drop to the recommended FPS, and lower shadows/anti-aliasing/effects in-game.
• The overlay says DISPLAY or reads near my refresh rate. That is the display's rate, shown on Windows 10 and for emulators BRUTAL doesn't measure yet (BlueStacks, LDPlayer, MuMu, Nox and MEmu); with GameLoop on Windows 11 it counts the game's own frames, windowed or full screen.