What causes a Godot mobile game draining battery while idle?

On a static screen the game still renders and processes at full frame rate, keeping the SoC at high clocks and burning battery even though nothing is moving.

How do I catch this when it only happens for some players?

Capture it automatically from the player's device with the full stack trace, the device and OS, the build, and a breadcrumb trail of what they did. That turns a vague complaint into a specific, reproducible issue you can fix without owning the hardware it happens on.

How to Fix a Godot Mobile Game Draining Battery While Idle

Quick answer: Enable low-processor-usage mode or lower the render and physics frame rate on idle screens so the device can drop to a low-power state.

Players complain your Godot game eats battery even sitting on the title screen. The loop is rendering 60 identical frames a second for no reason. Throttling the frame rate on static screens lets the phone idle and cool down.

How to fix it

1. Lower the idle frame rate

On menus or paused screens, reduce Engine.max_fps or call OS.low_processor_usage_mode so the device is not pinned at full clocks rendering unchanging frames.

2. Pause unneeded systems

Stop particle systems, animations, and per-frame scripts that are not visible or relevant on idle screens so the CPU has real idle time.

3. Restore full rate on play

Bump the frame cap back up when gameplay starts so the throttling only affects truly static screens, not interactive play.

Catching the ones you can't reproduce

The hardest version of this to fix is the one you can't reproduce — it only happens on a player's hardware, OS, driver, or save state, under conditions that simply aren't present on your machine. A report that says “it crashed” or “it froze” gives you nothing to act on, so the bug survives release after release while quietly costing you players.

Automatic error capture closes that gap. Each failure arrives with its full stack trace, the device and OS, the build number, and a breadcrumb trail of what the player did right before it broke, so even a failure you have never seen becomes a specific, reproducible issue. Fold identical failures into one signature ranked by how many players each hits, and your worklist sorts itself worst-first instead of arriving as a stream of vague complaints.

This is where a tool like Bugnet earns its place. Its SDK captures every Godot error automatically with the full stack trace plus device, OS, memory, build, and game-state context, folds duplicates into one grouped issue with an occurrence count, and ties each to the build it first appeared on — so you fix the problem that hurts the most players first and confirm it is gone when its signature disappears from the next release.

A crash you can name from its stack trace is a crash you can usually fix in minutes.