- Platform
- Android touch controls; game-side checks also apply on iPhone and iPad
- Scope
- Device settings and control names can differ
- Updated
- Last checked
First check whether the joystick releases
Open a safe practice area and hold one slow, continuous drag. Watch both the joystick graphic and the hero. A joystick that visibly returns to its centre while your finger is still down points toward touch registration or control handling. A joystick that stays held while the hero cannot move belongs in a different branch: crowd control, terrain, frame delay or connection delay.
Repeat the same movement without pressing another skill. If the problem appears only during two-finger input, note which second control is involved and whether the controls overlap at your screen size. That observation is more useful than calling every interruption lag.
| What you see | Test next |
|---|---|
| Joystick snaps back under a held finger | Screen area, protector and control layout |
| Joystick stays held but the hero stops | Crowd control, terrain or frame/connection delay |
| Release happens only with another button | Multi-touch position and overlapping controls |
| The same screen area releases outside MLBB | Device or screen support |
| Every control responds late | FPS and connection checks |
Test the same part of the screen outside MLBB
Clean and dry the screen and your hands. Check for cracks or damage, then repeat the test without a case or screen protector that obstructs the touch area. Android's official screen test uses one slow drag from a corner to the opposite corner; if the system panel releases repeatedly at the same place, note that location and contact the device manufacturer.
A successful drag outside MLBB does not prove the game is at fault, but it makes a dead screen region less likely. Do not jump to Android's factory-reset step for a game-only symptom: a reset removes apps and associated data and belongs at the end of device-level troubleshooting, after backup and manufacturer guidance.
Preserve the layout, then change one control at a time
Take a screenshot of the current controls before editing them. Move or resize only the joystick first, then repeat the same practice movement. If that changes the result, restore other controls gradually instead of importing a complete layout designed for another display size.
Also repeat the test with and without the second button that usually triggers the release. Record whether the joystick graphic releases, whether the hero is under a visible control effect, and whether the input works in a clear path. These details separate an input problem from an intended movement restriction.
Send a reproducible report if it continues
Keep the device model, operating-system version, MLBB version, control-layout screenshot and a short recording of the joystick graphic. State whether the same screen area releases outside the game and whether a second finger is involved. Do not include account credentials, recovery codes or private receipts.
Use device support when the same touch region fails in other apps. Use MLBB support when touch works elsewhere but the game reproduces the release after a restart and a controlled layout test.
Stopping point
Know when the fix is complete
Stop when you can reproduce the release in one defined place: outside MLBB, only in a particular control layout, or only under a visible in-game condition. Escalate that result to the matching device or game support route.
Sources
- Android Help: Fix a screen that isn't working right on Android
Screen checks, restart, affected-area drag test and advanced troubleshooting warning. Checked 2026-09-17.