Android 15 defaults games to 60Hz to save battery and heat

Android 15 defaults games to 60Hz to save battery and heat, and any game that wants 120 FPS has to ask for it explicitly. That is why a flagship phone can still feel choppy when refresh-rate policy, frame pacing, throttling, or thermal limits get in the way.

Why a powerful phone can still feel choppy

Raw silicon alone does not decide smoothness in mobile gaming. Mobile games run on battery-powered devices, so the real target is sustainable performance, not just peak bursts that look great in a benchmark. A game can look impressive on paper and still feel off in your hand if the display policy and the game loop are not aligned.

On a phone with a 120Hz panel, a title that stays pinned to 60Hz can feel less responsive than the hardware suggests. The panel spec matters, but platform policy and app-level requests decide what you actually see.

That is why a game can feel different from one device to another, or even from one mode to another on the same phone. A title that opts into high refresh on one handset may behave very differently on another if the device is willing to sustain the rate under heat or battery pressure.

How to tell whether the problem is refresh, pacing, or throttling

Not every stutter has the same cause, and the symptoms usually give it away. If a game feels locked even though your screen supports a higher refresh rate, the first suspect is refresh-rate policy. If motion feels uneven rather than simply slower, frame pacing is often the real issue.

Android’s Slow Sessions metric gives a useful benchmark here. A slow session is one where more than 25% of frames are slow, and a frame counts as slow if it is presented 50ms or more after the previous frame, which is effectively a 20 FPS threshold. That explains why a game can feel fine in a short burst and then turn choppy during long sessions, raids, or high-action multiplayer matches.

A few common symptoms line up with specific bottlenecks:

• Smooth menus, but choppy combat: the game may not be maintaining steady pacing once the action ramps up.
• Great performance at the start, worse later in the session: heat and battery pressure are likely forcing throttling.
• A 120Hz display that still seems capped: the game may not have opted into higher refresh behavior.
• Jittery motion even when the frame rate seems acceptable: pacing is probably uneven.

Why frame pacing matters more than most players think

Android’s Frame Pacing library, also known as Swappy, is built into the Android Game Development Kit. It helps OpenGL and Vulkan games present frames smoothly and in the correct rhythm, which is exactly what players notice when a game stops feeling sticky or uneven. When frame pacing is right, a game can feel cleaner even if the raw frame rate is not the highest possible number on the screen.

A real example is Mir 2, which improved rendering performance by using the Frame Pacing library. The fix is not always a more powerful phone or a more aggressive overclocked profile. Sometimes the difference is simply whether the game is feeding the display in a way the panel can use cleanly.

For engine developers, this is where Unity’s adaptive performance tools come in. Unity’s Android provider can expose thermal and performance-mode data through IThermalStatus, IPerformanceModeStatus, Android.GameMode, and related Game Mode APIs. In practice, that gives a game a way to react to heat and performance changes instead of blindly pushing the device until the frame delivery starts to wobble.

Battery, thermals, and Game Mode are part of the performance story

Game performance on Android is a balancing act. The platform’s Game Mode API and Game Mode interventions balance performance and battery life, and FPS throttling is one of those interventions. It is designed to help games run at a more stable frame rate while reducing battery consumption, which is exactly the kind of tradeoff mobile players feel when a session goes from fluid to hot and uneven.

Game Mode interventions are game-specific optimizations set by OEMs for games that are no longer being actively used by the player. That means the device maker can nudge a game toward stability and efficiency, but the result depends on the phone, the title, and the mode the device chooses. The player-facing effect is simple: performance settings are not cosmetic labels, they are active policies that can reshape how the game behaves.

The labels in the settings menu matter because they point to real tradeoffs. Performance, battery saver, and high frame rate are not just marketing words. They decide whether the phone is prioritizing fluidity, heat, runtime, or some mix of all three.

Why forcing native refresh is not a universal fix

Android 15 brought another wrinkle into the picture with frame-rate override behavior. As of March 28, 2024, the feature would let users force some games to run at native refresh rate, but not all games. Games that set their own maximum frame rate can override the system behavior, which means a system-level toggle is useful in some titles and irrelevant in others.

So the practical rule is straightforward: a 120Hz phone does not guarantee 120 FPS, and a frame-rate override does not guarantee the game will obey.