Mobile connectivity faults, from the software side

Why this matters

Mobile connectivity faults are reported the same way every time — "the internet isn't working on my phone" — and behind that sentence are at least four completely different problems with four different owners: the radio, the network, the account, and the application.

The hardware exam in this certification covers the radios themselves. This one covers the settings and the services around them, and the examinable skill is separating the layers before changing anything. That matters more on a phone than on a laptop, because the destructive reset is two taps away and it costs the user things no scan will get back.

The lesson

Separating radio, network, account and application before touching settings

Four questions, asked in this order, and each one eliminates a layer.

1. Is the radio working at all? Does the phone see any wireless networks, or any cellular signal? If it sees nothing on either, the problem is the radio or its state — airplane mode, a software toggle, or hardware.
2. Is the network working for anything else? Does another device on the same network work? Does the phone work on a different network? Two tests, and between them they place the fault on the phone or on the network.
3. Is the account in order? A cellular plan with no data left, a suspended line, a wireless network whose password changed, a captive portal never accepted. These look exactly like technical faults and are not.
4. Is it one application or everything? If a browser reaches the internet and one application does not, the network is fine and the problem belongs to that application — its permissions, its account, or its own servers.

That fourth test is the fastest and most often skipped. Open a browser and load a page. If it loads, stop looking at the network.

Only after those four should any setting change. The most common support failure here is going straight to "reset network settings", which sometimes works, destroys every saved network and pairing, and teaches nothing about what was wrong.

Wi-Fi faults: saved profiles, captive portals, and the network that remembers wrongly

Wireless faults on a phone have a small set of causes and one that dominates.

The saved profile that remembers wrongly. A phone stores the network's name, its security type and its password. When the network changes — a new router, a new password, a security mode upgraded to WPA3 — the phone keeps trying the old details and reports a generic failure. The fix is forget the network and rejoin, and it is the first thing to try for a network that used to work and does not.

Captive portals — hotels, cafés, airports, guest networks. The phone joins the network and has no internet until a page is accepted. Symptoms: connected with a warning, applications failing while the browser eventually shows a login page. The portal often will not appear because the phone tried an encrypted address; opening a plain http:// address usually triggers it. Private or randomised addresses can also break portals that tie the session to the device.

Randomised hardware addresses. Phones now use a different address per network by default, and it changes on some operating system updates. On a network that filters by address, or one that ties a portal session to it, this produces a device that connected yesterday and cannot today. Turning randomisation off for that one network is the fix.

Band and standard mismatches — a network on a band the phone does not support, or set to WPA3-only when the phone is older. These fail at join time with no useful message.

Poor signal presenting as "connected but nothing works", which is the case where moving three metres is the whole diagnosis.

Cellular faults: data settings, APNs, roaming, and a plan that has run out

Cellular faults divide into settings, coverage and account, and the account half is the one technicians forget.

Settings worth checking, in order:

• Mobile data enabled, and enabled for that application — per-app data controls exist on both platforms and are a common cause of one application failing on cellular and working on wireless.
• Data roaming, when the user is abroad or near a border.
• Data saver / low data mode, which restricts background use and produces applications that update only when opened.
• The APN, which defines how the phone reaches the carrier's data network. Normally automatic; occasionally wrong after a carrier change, an imported handset, or a reset. Symptom: calls and texts work and data does not, which is a very distinctive signature.
• Preferred network type, where forcing an older generation can rescue a device in poor coverage and forcing a newer one can break it.

Account causes that look technical:

• The data allowance exhausted, which on many plans means throttling to unusable rather than a clear message.
• The line suspended for non-payment.
• Roaming not enabled on the account, which is separate from the phone's setting.
• An eSIM that did not transfer during a device change.

The test that separates them: does another device on the same account work, and does this device work with a different SIM? Between them those two answers place the fault on the phone, the SIM, or the account.

Bluetooth pairing failures, and removing a pairing properly before retrying

Bluetooth failures are almost all about state held on two devices that have gone out of step.

The mechanics: pairing stores a key on both devices. If either side loses or changes its half — a factory reset, a firmware update, pairing with a different phone — the stored pairing is stale. The symptoms are connecting and immediately dropping, appearing paired but not connecting, or not appearing in the list at all.

Removing a pairing properly means removing it on both sides. Forgetting the device on the phone while the accessory still holds the phone in its list produces a pairing that half exists, and re-pairing fails in confusing ways. Most accessories have a reset procedure in their manual — a button held for ten seconds — and it is the step everyone skips.

The order that works:

1. Forget the device on the phone.
2. Reset or clear pairings on the accessory.
3. Turn Bluetooth off and on, or restart the phone.
4. Put the accessory in pairing mode and re-pair.

Other causes worth knowing:

• The pairing limit. Many accessories hold a small number of pairings and silently overwrite the oldest, so a headset shared between three devices loses one.
• Already connected elsewhere. An accessory connected to a laptop will not appear available to the phone.
• Location permission, which some platforms require for Bluetooth scanning and whose absence produces a device that finds nothing.
• Interference and range, which is the hardware exam's half of this.

Resetting network settings, what it destroys, and what to note down first

"Reset network settings" is the tool people reach for first and should reach for last, because it works often enough to be tempting and it is destructive.

What it destroys:

• Every saved wireless network and its password.
• Every Bluetooth pairing.
• VPN configurations.
• Mobile data settings, including a manually set APN.
• Preferences such as which networks to auto-join.

What it keeps: applications, data, accounts, photos, messages. It is not a factory reset, and it is worth saying so clearly to a worried user.

What to note down first:

• The wireless networks the user actually needs, and where the passwords are — the home network's password is frequently unknown to the person holding the phone.
• Any manually configured APN, exactly as it is.
• VPN configuration details, particularly for a work VPN, which may need IT to reissue.
• Which accessories are paired, so they can be re-paired rather than rediscovered a week later when one does not work.

When it is the right answer: several unrelated connectivity symptoms at once, a fault that survives forgetting individual networks, or a phone whose settings have been changed by something and cannot be traced. When it is not: a single network failing, a single application failing, or anything you have not yet tested with the four questions at the start of this lesson.