MojoLauncherLag in Minecraft: Java Edition on a phone has five or six common causes, and most can be fixed in a few minutes if you work through them in the right order. This guide is for people who play with Mojo Launcher and see stuttering, low FPS, freezes or crashes. We will start with the quick wins and move to the deeper ones.
1. Update to the latest version first
Every release changes graphics drivers and compatibility. The newest stable build updated Mesa to 26.2, added Turnip support for more Adreno GPUs and improved support for devices with 16K memory pages. An older copy may simply not have the fix you need. Install the latest from the official Mojo Launcher page or Google Play, and see what changed in the changelog.
2. Choose the right renderer
The renderer translates the game's desktop graphics into something your phone GPU understands, and it has the largest effect on performance and glitches.
| Renderer | Good for | Notes |
|---|---|---|
| Holy GL4ES | Most vanilla and many modded versions | The safe default. Large texture atlases can look distorted in modpacks. |
| LTW | Shader-heavy mods | Iris fixed Angelica and Create: Aeronautics. |
| Freedreno | Adreno 5xx and newer | Desktop OpenGL through Mesa. Added in Iris. |
| Zink (legacy plugin) | Older Mali GPUs | Needs an optional plugin from the project. |
No benchmark can tell you which is fastest on your phone. Community reports conflict, with some devices doing better on Zink and others on GL4ES. Test two renderers in the same world at the same spot and compare the frame rate.
3. Set memory carefully
Allocating more RAM does not always help. Too little causes "out of memory" crashes and stuttering. Too much starves Android itself and the system kills the app. For vanilla, start around half of your device's RAM. Large modpacks need more, but leave room for the system. Raise the value gradually, and close other apps before playing. See the requirements for recommended RAM.
4. Lower the in-game load
- Render distance: 6 to 10 chunks is a good range for phones.
- Simulation distance: lower it; it affects CPU.
- Particles, entity distance and clouds: reduce them.
- Smooth lighting and fancy graphics: try off.
- Resolution scale: if the launcher offers it, reducing the render resolution is a powerful way to gain FPS on high-resolution screens.
5. Fight heat
Thermal throttling is the hidden cause of "good at first, bad later". Once the chip gets hot it slows itself down. Remove thick cases, avoid charging while playing, keep the phone out of the sun and take short breaks. If FPS falls after ten minutes but starts fine, heat is almost certainly the reason.
6. Use lighter mods
On weaker devices, Fabric with performance mods usually beats a heavy Forge pack. Add mods one at a time to find what hurts. Our mods guide covers loaders and modpacks. If your pack uses Angelica, note that a recent issue on the tracker reports that its built-in shaders can fail to compile on some setups, so check the Mojo Launcher GitHub tracker.
7. Check your input devices
A physical mouse that feels slow is a known issue and not an FPS problem. If your controls feel unresponsive, see Mojo Launcher controls.
Crashes on startup
- Switch renderer.
- Lower the allocated RAM.
- Try a different game version to see if it is version-specific.
- Remove recently added mods.
- Reinstall the latest launcher, keeping a backup of your worlds.
- If it persists, report it with your device model, GPU, launcher version and the log file on GitHub or Discord. Our contact page lists what to include.
Quick checklist
- Latest launcher installed
- Renderer tested against an alternative
- RAM around half of device memory
- Render distance at 6 to 10
- Device cool and unplugged
- Mods added gradually
For a complete starting configuration, see the best settings guide.