Where this applies

General connection diagnostics, without packet capture or an India server-status test. No ping target or server location is asserted.

What to do

  1. Describe the symptom and stage: lobby, matchmaking, match or login. Record time zone, network type and whether it affects other applications.

  2. Compare camera motion with interaction timing in one similar scene. Smooth motion with late actions is a network lead; uneven motion everywhere is a performance lead.

  3. Where permitted, compare a known stable connection with the usual one while avoiding large downloads. Keep device settings similar.

  4. If the same error persists across both connections, preserve both results and use official support rather than repeatedly changing account or region settings.

Choose the branch that matches your symptom

  1. The store download never completesCan't find or install it? Follow the message
  2. The app opens, but sign-in failsSecure your account and prepare a support ticket
  3. The picture is smooth, actions arrive lateNetwork delay or frame stutter? A diagnostic path
  4. Camera movement stutters before a matchLow-end phone: separate lag, heat and network

Worked checks & examples

Branch A: image catches or freezes

If turning the camera is visibly uneven even before an online match, begin with the device-performance guide. Repeat a quiet scene after one safe graphics change and note the result. Do not buy a network service just because the experience was described as lag. Conversely, one smooth menu does not prove every match is free of rendering problems; note where the symptom first appears. The goal is to select the next test, not to diagnose hardware or a server from one impression.

Branch B: motion is smooth, actions arrive late

Check whether the delay coincides with a network change, weak coverage or another large transfer on your connection. Pause your own nonessential downloads and compare again without altering graphics at the same time. On a shared network, ask permission before changing equipment or interrupting anyone else's use. If a different authorized connection improves the same action, record the lead. Avoid declaring a specific server defective or promising a fix to other players from this single comparison.

Branch C: a login or matchmaking message

Write the full message before trying again. 'Cannot log in', a queue and a completed login followed by a match error are different stages. Check the official notice relevant to the India app and your date; this guide is not a live outage monitor. Confirm that the intended login provider is selected without sharing its secrets. If a message explicitly mentions account eligibility or verification, do not treat it as a Wi-Fi fault or attempt to evade it by changing region. Use the official support route.

A comparison record that makes the result useful

Record connection A and B using ordinary labels such as home Wi-Fi and mobile data; do not publish network passwords or precise location. For each, note time, game stage, visible message, whether camera motion stayed smooth and whether the same action was delayed. State 'A delayed, B improved' rather than inventing an unmeasured millisecond value. If both fail, include that too. End the test if it consumes unwanted mobile data or a device warning appears. Support can then separate your observation from your interpretation.

Choose your next step

Only one connection affected: continue with that network's ordinary support. Both connections affected only in the game: send a game-specific report. A login message needs its own exact-error branch.

What this does not confirm

A local comparison does not prove a server outage. No VPN, region spoofing, port-opening recipe or promised latency reduction is recommended.

Sources & evidence