Game profiles (mobile games)

The Game profiles page turns the generic emulator recommendations into per-game tuning. For 41 popular mobile titles, BRUTAL shows the emulator settings and in-game graphics options that suit your hardware — and with one click raises your emulator's priority, prioritises the game's network traffic where its server ports are known, and writes the frame-rate setting into your emulator's config where the profile carries one.

The 41 built-in profiles

Open Game mode and click Choose a profile. The Profiles list on the Game profiles page has an entry for each of the 41 supported games, Call of Duty: Mobile and Free Fire MAX among them.

Each entry shows the resolution and FPS target for your hardware tier. Select one to see its settings.

What's in a profile

The detail panel shows three things, all tuned to your hardware tier (LOW / MID / HIGH / ULTRA) and GPU vendor:

• Emulator settings — editable dropdowns for resolution, CPU cores, RAM, DPI, target FPS and renderer. The renderer recommendation is vendor-aware: NVIDIA gets OpenGL+/DirectX+, AMD gets Vulkan, Intel gets OpenGL+.
• In-game settings — the graphics options to pick inside the game (such as graphics quality, frame-rate mode, shadows and effects) for your tier.
• Network ports — the TCP/UDP ports the game's servers use, where they are published; the profile prioritises them on your network. A profile without published ports shows None declared.

Customising a profile

Change any dropdown (resolution, FPS, RAM, etc.) and BRUTAL saves it as a Custom override for that game — the profile gets a Custom tag and your values persist between sessions. To go back to the tier defaults, click Reset to recommended.

Applying a profile

Click Apply profile. BRUTAL then:

• Sets IFEO priority (High CPU and I/O) for the real emulator host executables — GameLoop, BlueStacks, LDPlayer, Nox, MEmu and MuMu — so the emulator gets scheduler priority on its next launch.
• Where the game's server ports are known, creates QoS policies (DSCP 46, Expedited Forwarding) scoped to them, so game traffic is prioritised over background traffic.
• Where the profile carries an emulator setting, raises the target FPS (never lowering a frame-rate cap you set) in the config of each detected GameLoop, BlueStacks or LDPlayer install, and the renderer on GameLoop — only into the real config files those emulators actually read. BlueStacks is written only while it is closed, because an open BlueStacks saves its own config file.

The live log shows each step. The applied profile is remembered across restarts and shows as Applied. To undo, open the active profile and click Remove — the IFEO entries and QoS policies BRUTAL created are cleaned up.

Best practice

• Apply the profile, then open your emulator and confirm the resolution/RAM/cores match the panel — the config writer covers the frame rate (and the renderer on GameLoop); you set resolution, CPU cores and RAM in the emulator's own settings.
• Inside the game, copy the in-game settings list exactly. They're chosen for clarity and frame stability on your tier, not just maximum eye-candy.
• Use the FPS warning as a guide — if it flags your choice, the recommended value is usually the better experience.

Common issues / troubleshooting

• "Applying a game profile is part of Pro." Apply requires Pro. Activate your license, then apply.
• Log says config wasn't written. That's expected if the emulator isn't installed, or (for GameLoop) if its real config file isn't in the user-data location yet — launch the emulator once so it creates its config, then re-apply. BRUTAL deliberately won't write an orphan file the emulator would ignore. If BlueStacks is open, close it and apply again.
• A profile is marked Retired. BRUTAL no longer offers that profile, because the game's terms of service don't allow emulators. It stays in the list while it is applied on your PC, so you can click Remove and clear the priority and network entries it added.
• FPS warning won't go away. That's by design — it's telling you your target exceeds your monitor or hardware. Pick the recommended FPS to clear it.

For PC (non-emulator) titles, see PC games: scanning and per-game settings. To push an emulator to its FPS ceiling, see Getting 90–120 FPS in Android emulators.