My game runs smoothly for a while, then slows down as the phone gets hot

Short tests on a cool phone never show what a twenty-minute session does to it. This entry shows how to find the minute from which the game really slows, how to ignore one-off hitches like a loading screen and what a long test session has to look like.

Why this works

A hot phone protects itself by slowing down, and that builds up over minutes. A lasting rise over several minutes in a row is heat, while a single spike is a loading screen or an ad, so only a long test on a real phone can show it.

When not to use it

Skip it for games people play in short sessions of a few minutes, where the phone never gets hot. Do not test it on a desk with a fan, which hides the problem. When a slowdown is found, lower the load first.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 3 common mistakes and the fix
• 35 lines of example code with 4 checks that pass
• How your AI shows you that it works

Say this to your AI

Use the Spielerando entry "My game runs smoothly for a while, then slows down as the phone gets hot" (read_entry game-slows-down-as-the-phone-heats-up) in my game. Build it step by step, and show me how you checked that it works.

Or skip this and connect the MCP: your AI then finds all of this by itself.Connect the MCP