Where this applies

General device troubleshooting; no benchmark or guaranteed frame rate for India.

What to do

  1. Compare the lobby, a quiet practice scene and a match. If turning the camera stutters everywhere, inspect graphics and device load; if movement is smooth but actions arrive late, inspect the connection.

  2. Lower one graphics option offered by your build, close unnecessary background work and test the same scene again. Keep a note of the original setting.

  3. If performance declines as the phone warms, pause and let it cool naturally. Avoid heat-trapping covers during testing; never use unsafe cooling or disable device protections.

  4. For connection issues, compare a stable Wi-Fi connection with your normal mobile connection where permitted. Note time, network type and whether other apps are also affected.

Worked checks & examples

Start with a symptom log, not a booster

Describe what you can observe: camera motion is uneven, button response arrives late, the app closes, or performance declines after the device warms. Record whether the symptom occurs before a match and whether it affects other apps. A displayed network indicator can help if your build provides one, but do not infer a precise diagnosis from a single number. General checks below do not establish India-specific hardware requirements or certify that the game is at fault.

Use a short, controlled comparison

Save the starting graphics settings. Compare the same quiet scene with one lower option, keeping brightness, connection and other activity similar. If the phone is already hot, let it rest before comparing; otherwise the later test has a different starting condition. Prefer consistent motion over chasing a maximum setting. If the app closes rather than stutters, record the crash stage and available storage, then switch to the installation/support path instead of repeatedly lowering unrelated visual options.

Example: smooth camera, delayed interaction

If looking around stays smooth while actions arrive late or players seem to jump position, check whether the connection changes at the same time. Where permitted, compare your usual network with a known stable one and note the result. Do not run large downloads during the comparison. A better result on another network suggests a connection-related lead; it does not prove a specific server problem. If both networks fail similarly, retain both observations for support rather than installing a packet tool or exposing credentials.

Heat and stopping conditions

If performance starts well and deteriorates as the phone warms, pause and let it cool naturally before repeating. Stop immediately for a device temperature warning, swelling, unusual smell or other hardware concern and follow the device maker's support instructions. Do not bypass thermal protection, place the phone in a freezer or install root-based performance tools. For a persistent game-only problem, submit model, OS, app version, scene, settings changed and the before/after result. Avoid claiming an exact FPS unless you actually measured it.

Choose your next step

Send support a reproducible example with app version, model, OS and error details. A repeatable pattern is more useful than 'laggy'.

What this does not confirm

Do not use unofficial boosters, root tools or config files promising unlocked FPS. No claim that one setting fixes all phones.

Sources & evidence