2026-11-17 · 2 min read
On Android the games were closing by themselves
On Android some games closed by themselves: the phone started in Vulkan, not in the web's Compatibility renderer. On 24 October one line moved five games onto the right path.
On the phone some games closed by themselves. The app started, stayed open for a moment, then vanished. No message, no error screen, nothing to read. In the browser the same games worked. On the computer they worked. Only on Android they didn't, and only some of them.
Two ways of drawing
Godot can draw the screen in more than one way, and it is no small detail: it is the engine that pushes every frame. On the web our games have always used the Compatibility renderer. On Android, instead, the app started in Vulkan — another path, chosen automatically, without us deciding it.
The problem did not hit everyone the same way. The ones that suffered were the games that draw a lot in code: rectangles, circles and polygons traced line by line instead of ready-made images. On Vulkan, on the phone, that load was enough to make them close by themselves.
It is a fault you notice late. In the places we looked at every day — the browser, the computer — it wasn't there. It lived only on the stretch of road we tested the least.
One line
The fix was one line. On 24 October we set rendering_method.mobile to Compatibility: the same renderer the web was already using. Nothing to invent, just moving the phone onto the path that worked.
The line went into five games. As of 24 October:
- Merge Demon: Cyber Idle was at version 91
- QUOTA — Geometric Slot at 25
- Maze Lume at 68
- Last Lantern at 18
- ONE — The Chain at 35
Rebuilding the packages
Changing the line is not enough: the Android packages have to be rebuilt, otherwise the phone still installs the old copy.
On 24 October we rebuilt the APK and AAB of Last Lantern (v18), Maze Lume (v68), QUOTA — Geometric Slot (v25) and Merge Demon: Cyber Idle (v91).
On 26 October it was ONE — The Chain's turn: APK and AAB for Android, and on the same day the packages for Windows, Linux and macOS too, all at version 35.
The browser and the computer did not change: there the renderer was already the right one. The only thing that changed was the phone, which now draws like everyone else. What Godot does and what the layer that publishes the games does we tell on the engine page.
What we take away
- A fault that lives on a single platform is invisible from the places you look at every day. The phone was exactly the one we tested the least.
- When a path already works — the Compatibility renderer on the web — moving the rest onto it costs one line and zero new ideas.
- A changed line only counts after the packages are rebuilt: while the APK is the old one, on the phone nothing has happened.