Home / User guide
User guide

From connection check to clear next steps.

Use the guided Check for a complete diagnosis and reports. Use Live Monitoring when the issue is intermittent and you want to watch the current connection.

1. Before a check

Go to the place where the problem normally happens and keep the intended Wi-Fi or mobile connection active. A full Check is intended to describe one active connection during one measured window, so avoid deliberately switching links while it runs.

  1. Use the same place and connection where the problem occurs.
  2. Start the check and let the measurement window finish.
  3. Avoid changing several settings during the run.
  4. When the app suggests an action, change one thing and retest.

2. Optional problem description during a check

The start dialog has two optional tick boxes: Include a speed test (about 25 seconds more) and Explain my result with AI (see section 4). While diagnosis runs, you can optionally say what made you check, such as buffering, call breakup, games lagging or general slowness. Your choice shapes the advice, not the measurements. You can skip it.

Optional symptom contextChoose what you noticed while the test runs, or skip this step.

3. Simple and Detailed views

The Simple/Detailed switch stays in the header. Simple shows the main finding and next step. Detailed offers more measurement evidence, without changing the test result.

Path and actionSee what was measured and what to try first.
Detailed resultsSee the measured evidence and what contributed to the score.

4. Full Check

A full Check is the finite diagnostic workflow. It can examine Wi-Fi/mobile radio, Phone → Router where measurable, end-to-end and decomposed Internet paths, configured DNS, regional references, common service setup, readiness estimates and security/integrity indicators.

Score is not the diagnosis by itself. Read the primary finding and component evidence. A historical Watch does not, by itself, hard-cap the current Connection Health result.
  1. Start from Check.
  2. Optionally choose what you noticed when prompted during the check.
  3. Let the test finish without changing the intended connection.
  4. Read the conclusion, score and first recommended action.
  5. Retest after one change and compare the relevant component.

AI Diagnosis

Tick Explain my result with AI in the start dialog, or tap the AI button under a finished result. The answer has a one-line verdict, What we found (two or three short points), Do this first, Also try and the most useful next test. It follows the levels shown in your report and never changes the score; when nothing is wrong it says so. You can leave the app while it works. There are 2 free explanations a day, shown in the start dialog; one that fails is not counted. Share result makes an image of the answer, and the same explanation goes into your PDF reports.

5. Live Monitoring

Live Monitoring is a separate user-started session for intermittent problems. It can run for up to 90 minutes and keeps current quality separate from longer session evidence.

  • Current delay, jitter and packet-loss cards focus on the recent monitoring window.
  • The session graph and counters build over time so outages and changing conditions are easier to see.
  • Wi-Fi and mobile network changes are recorded as separate connection sessions instead of being blended into one network.
  • If you minimise the app or lock the screen, an ongoing Android notification keeps the user-started monitoring session visible and provides a way back to the app or to stop it.
  • When you stop, Diagnostix360 can create a compact Live Monitoring result summarising the session.
Live MonitoringApp UI preview with identifying network details removed.

6. Local history and comparisons

History compares completed full Checks. When comparable runs exist, it can show score trends and repeated observations for a matching network context. Historical information is context: a repeated Watch is not treated as a confirmed current fault unless the current evidence supports that conclusion.

7. Customer, Technical and Monitoring reports

The Reports area offers two audiences from a completed full Check.

Customer report

A concise one-page result intended to omit sensitive technical identifiers. It shows the health score and plain-language connection-path status.

Technical report

The detailed evidence package for an ISP, IT team or advanced troubleshooting. Depending on the report privacy settings, it can contain active network name, IP/ISP/ASN information, DNS/resolver addresses, approximate area, nearby Wi-Fi information, traceroute details, mobile operator/cell information and exact timestamps.

  1. Choose the completed run.
  2. Select Customer or Technical report.
  3. Preview the report.
  4. For a sensitive Technical report, accept the in-app acknowledgement only when the recipient is trusted.
  5. Share only the minimum detail required.

8. Privacy and analytics

There are two separate optional controls:

  • Diagnostic Data Sharing can upload an allow-listed measurement summary plus a random app-installation UUID used for distinct-installation statistics, deduplication and abuse protection. It excludes raw IP addresses, location fields, Wi-Fi names, BSSID/MAC, cell identity, nearby-network identities and the full per-second timeline.
  • Usage Analytics can enable Google Analytics for Firebase for broad product events. Diagnostix360 does not add raw diagnostic measurements, score values, ISP/ASN, report IDs, Wi-Fi/cell identifiers, GPS coordinates or its diagnostic installation UUID to Firebase event parameters. Firebase uses its own app-instance identifier and standard service data when Analytics is enabled.

Both choices can be changed independently in Settings. If a diagnostic Privacy ID already exists, turning Diagnostic Data Sharing off stops future uploads but keeps the ID locally so you can use it for a later access/deletion request. Core diagnostic lookups such as public-IP/profile, DNS and test-target requests can still occur when sharing is off because they are part of the diagnosis you start. See the Privacy Policy.

9. What the results do — and do not — mean

  • A result describes a measured window, not every moment before or after it.
  • A healthy result does not guarantee that an intermittent problem will not occur later.
  • A weak radio reading is context, not proof that radio conditions caused the observed symptom.
  • A failed or delayed ICMP probe does not, by itself, prove packet loss or which organization is responsible.
  • Readiness scores estimate path suitability; they do not run a real game, call or video session.
  • Diagnostix360 is not a certified test instrument, security audit or SLA recorder.

10. Speed Test and its limits

Use the Speed tab for a standalone throughput test or choose the optional speed step during a full diagnosis. It measures download and upload throughput, idle ping, jitter and responsiveness under load, and saves recent results on the device. The network name appears where Android grants access. Quick tests generally take about 12 seconds; Full tests around 25 seconds. On mobile data the app budgets up to 55 MiB (Quick) or 170 MiB (Full) for measurement payloads. Actual data billed by the carrier can be higher because of protocol overhead.

Comparison is most precise when Android exposes the Wi-Fi name; when hidden, the app may use the network type as a fallback. The connection-health score measures a different thing: a reliable path can still have limited bandwidth. Speed Test transfers real data, so check the data-use notice when using cellular service.

11. Sharing safely

Customer reports are usually the safer choice for ordinary support. Technical reports can include local and public IPs, DNS settings, Wi-Fi network names, approximate region and routing information. Always review the contents before sharing. Public report samples on this website are fictitious and contain no real network details.