If every time you enter your favorite Android game the FPS drops, the screen freezes, or everything is choppyIt's normal to get frustrated. The good news is that, unless your phone is really old, there are tons of tweaks and tricks you can use to drastically improve your experience without having to spend a fortune on a new smartphone.
The key is to understand that There is no magic app that fixes everythingbut rather a set of small optimizations: adjustments to the game itself, system settingWe'll cover using developer options, tools like GFX Tool or Game Booster, and finally, all the new features of Android 13 regarding FPS limits and Game Mode. Let's look at it step by step, in detail, and without beating around the bush.
Why are your FPS games running slow on Android?
When a game starts to stutter, it's usually because one or more components are at their limit: CPU, GPU, RAM, storage, or poorly chosen graphics settingsIt's not just that "the phone is bad," sometimes the settings are simply poorly adapted to your device.
The processor and GPU define the raw power available to run graphics, physics, and effectsIf the game is set to too high a visual quality or FPS for your chip, the result will be constant performance drops and excessive heating.
RAM is also critical: when you have With many apps open in the background, the system starts closing processes and moving data. from one place to another. This results in pauses, endless texture loading times, and, in the worst cases, sudden game crashes.
Almost full storage is another classic. A phone at 90-95% capacity. It reads and writes much slower, fragments data, and makes the whole system sluggish.Loading times are longer and the smoothness suffers during gameplay.
And, of course, we have the software part: Internal game graphics settings, Android version, background apps, wireless connections, and location servicesEverything adds up... or subtracts, depending on how you have it configured.
Android 13, Game Mode and Smart FPS Limiting
With Android 13, Google has introduced a rather interesting system: the FPS limitation as a Game Mode interventionIt is designed to ensure that games maintain a stable frame rate, consume less battery power, and avoid the typical "roller coaster" effect of FPS.
Today, many Android phones come with screens of 90 Hz or 120 Hz, and games try to keep up with that pace by maximizing the FPS. The problem is that almost none of them take into account whether the user prioritizes battery life or stability, and that's when the stuttering occurs: the game tries to run at full speed, but the CPU/GPU can't keep up.
The idea behind this Game Mode intervention is simple: It cannot increase the game's original FPS rate, only limit it.In other words, if the game is designed to run at 60 FPS, it won't magically jump to 120, but it can lock it to values like 40 or 30 FPS to make the frame rate more stable and reduce resource consumption.
Google's tests have shown that limiting the frames per second can Reduce GPU power consumption by up to 50% and overall system power consumption by around 20%.In practice, this means less overheating of the phone, fewer performance drops due to temperature, and a battery that lasts longer within the same gaming session.
Something very important is that this intervention It is designed specifically for "non-rhythmic" gamesThat is, titles that reach very high FPS but with huge variations from one moment to the next. Even if the average FPS seems decent, these variations are precisely what the player perceives as lag or instability.
How the FPS limit works depending on your mobile screen
The FPS limit isn't applied just any way. Ideally, the The chosen frame rate must be an exact divisor of the maximum refresh rate of the screen, so that everything is in sync and the panel is used more efficiently.
In practice, depending on the type of screen, you have these recommended FPS combinations:
- 60Hz displays60 FPS and 30 FPS.
- 90Hz displays: 90 FPS, 45 FPS and 30 FPS.
- 120Hz displays: 120 FPS, 60 FPS, 40 FPS and 30 FPS.
Notice that no “unusual” values appear For example, 50 FPS or 70 FPS. If you force figures that don't match the panel's refresh rate, you may end up with more stuttering than benefits, because the system has to constantly adjust the timings.
The FPS limiting intervention It is combined with the frame rate applied by the game itself.As a general rule, in this "battle" of limits, the lower value always wins: if the game wants to run at 60 and the platform limits it to 40, you will be stuck at a stable 40 FPS.
There is one curious exception: if the app uses a very aggressive pacing technique and explicitly suspends the rendering thread to set the paceThe system can no longer reduce the FPS limit. In that case, the Game Mode FPS limit ceases to apply, and only the game's FPS limit matters.
Also, do not forget that Results may vary greatly depending on the device, ambient temperature, and battery status. and other factors. The same game with the same FPS limit can run better on one phone than another, even using the same version of Android.
Configure FPS limiting with ADB and Game Mode
If you're one of those people who isn't afraid to connect your mobile phone to your PC and tinker with ADB, Android allows you to Configure FPS intervention at the packet level (app) using the tool device_configThis is intended more for developers, but it's a very useful reference.
First of all, there is an important warning: the game You must not declare compatibility with the Game Mode APIIf the developer has integrated that API, their own performance tweaks can override the platform's FPS limiting intervention.
To activate Game Mode interventions in a specific app, a command like this is used:
adb shell device_config put game_overlay <PACKAGE_NAME> <CONFIG>
Within that configuration, you can specify the game mode and target FPS rateFor example, a typical command would be:
adb shell device_config put game_overlay <PACKAGE_NAME> mode=2,fps=90:mode=3,fps=30
In this case, mode=2 is usually associated with performance mode and mode=3 with battery mode, while the parameter fps It accepts values such as 0, 30, 40, 45, 60, 90, and 120, depending on what the device's screen supports. 0 acts as the default value, without imposing any additional limit.
Keep in mind that these ADB commands are advanced and that Any changes you make are at your own risk.If something goes wrong, you can always revert to the default value or remove the overlay configuration for that package.
How to check FPS and measure results
Once you've adjusted the FPS limit—whether from the game settings, Game Mode, or with more technical interventions—the ideal thing to do is check the FPS and really see what's happening on screen and how your game behaves.
On many Android phones with a game panel or Game Dashboard you can activate an overlaid FPS counterIt usually works like this:
- Open the game and slide the notification bar down.
- Tap on the Game Dashboard icon.
- Enable the FPS counter option by tapping the corresponding button.
- Close the panel with the close button (X) and slide to the side to view the counter while you play.
This way you can check, for example, if your title remains stable at 120 FPS on a 120Hz screen or if it gets stuck at 40 FPS when you activate a battery saving mode or a forced limit.
If you want to go a step further, Android offers plotting tools like PerfettoThese are very useful if you're a developer or like to work with data. Capturing performance data from the source is helpful. android.game_interventionsYou will be able to see detailed records of when the FPS limit is applied and with what values.
In the trace reader, under Information and Statistics, you will see a list of game modes and active interventionsThose related to FPS appear in the format fps=Xwhere X is the rate applied for that specific mode. When 0 appears, it means that no specific limit has been set.
Although this sounds very technical, the key takeaway is that You have fairly accurate ways of knowing if your changes are working and whether FPS stability actually improves or not.
Optimizing a mobile game: Project settings, RAM, CPU, and GPU
Beyond what Android offers at the system level, many performance issues stem from the game itself. A real-world example: a developer managed to reduce the memory usage of their title... 2,5 GB of RAM at approximately 250 MBand went from crashing instantly to running at over 60 stable FPS on a Galaxy S8 simply by adjusting a few parameters.
In terms of graphics, settings such as sampling quality or GPU preference usually make small differences, but options such as scaling quality or maximum sprite sheet size They can be decisive, especially in mobile phones with little RAM.
Downscaling, in particular, can be a powerful weapon: turning it down makes it Do not generate mipmaps (smaller versions of textures)This saves memory because fewer image variations are stored, which makes a difference in games with very large textures.
The maximum size of the sprite sheet is also key. Decreasing it from 4096 to 2048, for example, It greatly reduces RAM consumption at the cost of a slight increase in CPU workload.On mobile phones, it usually pays off: you'd rather the processor work a little harder than overload the memory.
Regarding full-screen quality, many engines allow render at a lower resolution and then scale it up to adjust it to the panel's resolution. Setting it to low might make the game look a tad more pixelated (it's barely noticeable on a 1440p mobile screen), but the performance increase is huge in some cases.
Antialiasing, on the other hand, is usually a luxury: It consumes resources for each edge it smooths.In mobile games, if the visual style doesn't critically require it, disabling or lowering it to the minimum can squeeze out several extra FPS.
Controlling RAM usage: sprite sizes and resources
In terms of memory, one of the most common mistakes is overusing giant sprites. For example, an image of 4000 x 4000 pixels. It doesn't take up twice as much space as a 2000 x 2000 one, but four times morebecause memory depends on the total number of pixels.
In practice, you can usually reduce most graphics (buttons, backgrounds, interface elements) to much more reasonable sizes without any visible loss of quality. A 250 x 250 button, for example, It is usually more than enough for most screensand any size reduction translates into less RAM used.
It's also helpful to understand how sprite sheets package your assets. A 400 x 400 image is typically... reserve a space of 512 x 512 on the sheet, and a 600 x 600 one can occupy 1024 x 1024. If you reduce a sprite from 258 x 258 to 256 x 256, you still see it the same, but you fit it better on the grid and don't waste space.
Another point that confuses many people: Compressing images only reduces the size of the APK or installation filenot the RAM they use when running. As soon as the game loads them, they are decompressed into a format suitable for the GPU, and that's where the actual pixel size matters.
If you use static graphics (icons, logos, interfaces), vector formats like SVG can be a good option. However, It is not recommended to overuse SVG in sprites that move or are animated a lot.because then the CPU is forced to recalculate the geometry in each frame and performance plummets.
In engines with debugging tools you can see which layers or scenes use the most memoryUse these dashboards to quickly locate disproportionate resources and start cutting them, instead of going in blind.
Reduce CPU usage: events, text, and game logic
Where many games suffer is in CPU usage. There are projects full of running events. “every tick” or “every frame” without actually needing to. This forces the processor to evaluate conditions thousands of times per second, and ultimately, the bottleneck appears logically, not due to graphics.
A basic but effective trick is to replace many "each tick" with more specific conditions (for example, checking a variable only when it changes state)If you only need an action to run once when something happens, activate functions like "trigger once" or "activate only when condition changes".
Constantly updating text is another CPU drain. Modifying text on screen each frame or too many times per second This involves recalculating sizes, positions, and, in some cases, reassembling the text texture. For elements that change frequently (counters, markers), sprite fonts may be a better option.
It is also very useful disable event groups or entire sections of code when they are not needed. For example, the code that controls a store is only needed when the store is open; the rest of the time it can be disabled to save CPU.
And a note for the more technically inclined: in some engines, migrate certain parts of the logic to JavaScript or other more direct languages You can achieve additional improvements. Even so, good use of visual event systems is usually enough to have a smooth mobile game.
Optimizing GPU performance: effects, particles, and layers
On the purely graphical side, anything involving advanced effects, post-processing, or complex shaders This translates to more load on the GPU.A simple water effect applied to a huge sprite can drop the FPS on a mid-range device.
Particles are another important factor. They look spectacular, but they need to be controlled. It's recommended. destroy or recycle particles that are no longer visible on screen, instead of leaving them alive outside the play area, because they continue to consume CPU (for logic) and GPU (for rendering).
Some engines offer the option of “rendering cells” in static layersEnabling it on backgrounds that don't change improves performance because the engine can reuse those cells instead of redrawing everything from scratch each frame. However, don't enable it on layers full of particles or moving objects, because the cost of constantly recalculating cells completely changes the equation.
It is important to remember that An object with 0% opacity is still drawn in many situationsIf a sprite is no longer needed, it's better to destroy it or make it truly invisible (depending on the engine) than simply make it transparent.
Finally, adding layers itself doesn't usually penalize much; what matters are the objects and effects you put on those layers. Controlling visual complexity and Avoid heavy filters across the entire screen It's a direct way to recover FPS.
Developer options: animations, forced GPU, and Force 4x MSAA
Android itself has a menu that many users don't touch, but it can make a difference: the Developer OptionsTo activate them, simply go to Settings > About phone (or similar) and tap several times on “Build number” until the message appears that you are now a developer.
Within that menu, you have some very useful tools to improve the perceived speed and, in some cases, actual performance. One of the most effective is reduce or disable system animations: animation scale of window, transition and duration of the animator.
If you set them to 0.5xo directly in “Animation disabled”, The transitions between screens are almost instantaneous. And the phone feels much more responsive. It doesn't increase the hardware's power, but it does free up a little GPU that's no longer being used for visual embellishments.
Another interesting option is “Force GPU rendering” (or similar depending on the manufacturer's skin). Enabling it, Part of the 2D rendering of the interface is offloaded to the GPU instead of leaving everything to the CPU. This usually results in smoother navigation, with softer animations.
The price to pay is that, in many devices, the GPU consumes more power than the CPU for these tasks, so you may notice a battery reduction of between 5 and 15% If you keep it always active. It can be especially useful on phones with weak CPUs, while on current high-end phones it's not usually as necessary.
You'll also see settings like "Force MSAA 4x" or "Force 4x MSAA," which enable strong antialiasing in games that support OpenGL ES 2.0. This It improves graphics quality but increases GPU and battery consumption.If your phone is struggling to perform, it's best to disable it to avoid FPS drops.
Limit background processes and close apps before playing
Developer options also allow limit the number of processes that can run in the backgroundIn this way, Android prioritizes the foreground app (the game) and more aggressively closes what you're not using.
You have to be careful not to set the limit too low, because you could cause things to go wrong. Messaging apps or important services close and stop receiving notificationsIdeally, try it at a moderate level and see if you notice an improvement in the games without losing functionality.
Apart from that, it's still a good idea to do what we've always done: Manually close resource-intensive apps running in the background (social networks, browsers loaded with tabs, etc.) before opening your favorite game, so that the RAM is as free as possible.
If you want to go a little further, you can use apps like Advanced Task Killer or other process-closing utilities, always downloaded from official sources and in moderation, because Constantly killing processes can also generate extra consumption. when the system has to relaunch them.
Brightness, dark mode, connections and notifications: small adjustments that add up
It might sound like a minor trick, but playing with the brightness at maximum is a perfect way to overheat the mobile phoneWhen the temperature rises, both the CPU and GPU tend to reduce their frequency to protect themselves, and that's when the FPS drops occur.
Ideally, the brightness should be adjusted to the value lower than you feel comfortable with And, whenever the game and system allow it, activate dark mode. This helps the screen and processor work more efficiently, especially during long sessions at night.
It also doesn't make much sense to have all the connections enabled if you don't need them. Deactivate Bluetooth, NFC, location services, and even mobile data (If you play over WiFi) it allows the system to focus more on the game and less on scanning networks or updating background services.
Notifications are another source of interruptions and minor lag spikes. Activate a Do Not Disturb mode or the built-in system. The manufacturer's integrated game mode, which usually silences alerts and calls. during gameplay. Not only will you gain smoothness, but you'll also avoid a notification covering half your screen at the worst possible moment.
Finally, avoid playing games with your phone plugged into the charger whenever possible. It greatly increases the temperature and accelerates battery aging.In addition to forcing the system to reduce performance to avoid overheating, it's best to charge before or after a gaming session.
Game Booster, GFX Tool, and other apps to boost FPS
Almost all brands already include a Game mode or Game Booster It comes standard. It usually comes in the form of a pre-installed app called “Games”, “Game Space”, “Game Launcher” or similar, and its mission is simple: to automatically optimize the mobile when it detects that you are playing.
These utilities can block notifications, adjust brightness, prioritize CPU and RAM usage for the game, improve touch response and even optimize the internet connection for reduce latency in online games.
Many Game Boosters also allow record the screen or take screenshots on the flyas well as creating custom profiles per game, where you choose whether you want to prioritize raw performance or graphical quality.
If your phone doesn't have a built-in game mode or you want something more advanced, there are specific tools like GFX Tool – Game BoosterThese are designed for specific titles. With them, you can unlock resolutions and FPS rates that the game doesn't offer by default, adjust the level of detail, and enable or disable specific effects.
GFX Tool, for example, allows Increase resolution, enable HDR graphics on low-end devices, unlock extreme FPS and change the visual style. They also often include "Game Turbo" features to close background apps and free up resources before launching the game.
However, it's important to use these apps responsibly: incorrect configuration can cause problems. unexpected shutdowns, excessive battery drain, or overheatingAlways stick to reasonable options for the hardware you have and don't push it too hard.
Update Android and the games themselves
Something that is constantly forgotten is that System and game updates bring performance improvements and bug fixesA bug in memory management, an FPS synchronization failure, or a graphical problem may already be fixed in a more recent version.
From your mobile settings, check if there is pending system updates Apply these updates when you have sufficient battery and are connected to Wi-Fi. On Google Play, check if your favorite games have new versions available and install them.
Developers usually include in each update Optimizations for new devices, adjustments to graphics profiles, and stability improvementsIf you fall behind in versions, you may be dealing with problems that no longer exist.
In addition, many manufacturers adjust their own Game Booster, GPU drivers, and power management over time, so Keeping up to date is almost mandatory if you're concerned about performance in FPS games..
With all these tips—FPS limits in Android 13, good graphics settings, RAM, CPU and GPU management, smart use of Developer Options and tools like Game Booster or GFX Tool—you have plenty of room to make your Android FPS games go from choppy to much more stable and enjoyable, taking full advantage of the hardware you already have without needing to change your phone at the first opportunity.
