The Decision Happening Thirty Times a Second

You're in a coffee shop, half-watching a video stutter on your phone. The café Wi-Fi password is saved. You've got decent 5G overhead and rock-solid LTE from your carrier. Three radios, one pipe, and somewhere inside your pocket a triage system is running constantly, silently, without once asking your opinion.

So how does it actually choose?

The short answer: a ranked preference system baked into both the operating system and the modem chip, weighted by signal quality, battery cost, and carrier instructions. The ranked list is just the starting point. The real behavior emerges from how those weights shift in real time.

The Pecking Order (And Why Wi-Fi Usually Wins)

Phones almost universally prefer Wi-Fi over cellular when a known network is in range. The reason isn't sentimental. Wi-Fi offloads traffic from your carrier's towers, which benefits the carrier, and it typically costs you less data, which benefits you. The incentive structure on both sides pushes Wi-Fi to the top.

Below Wi-Fi, the cellular stack has its own internal ranking. 5G sits above LTE, which sits above 3G, which sits above 2G. Most modern phones have already dropped 3G support, so in practice it's a 5G-versus-LTE contest. The phone registers on whichever generation the tower advertises, then watches signal metrics to decide whether to stay or step down.

Those metrics aren't just "bars." The modem watches Reference Signal Received Power (RSRP), measuring raw signal strength in decibels, and Reference Signal Received Quality (RSRQ), which captures how much interference is muddying the signal. A 5G connection with poor RSRQ can be slower and more power-hungry than a clean LTE connection a floor below. The brand name on the status bar is basically decorative at that point.

The Thresholds That Flip the Switch

Here's where it gets specific. Phones don't switch networks the instant a better option appears. They use hysteresis, a deliberate lag designed to stop the modem from ping-ponging between towers every few seconds.

Picture this: Priya is walking from her office lobby toward the elevator bank. Her phone has been on 5G Sub-6, the wide-coverage flavor rather than short-range mmWave, at a healthy signal. As she moves deeper into the building, RSRP drops below roughly -110 dBm, the threshold where most chipsets start evaluating a fallback. The phone doesn't switch immediately. It waits, typically one to three seconds of sustained poor readings, before committing to LTE. That pause is intentional. If Priya just walked past a structural column that briefly shadowed the signal, the phone would have switched unnecessarily and then switched back, burning battery both times.

The specific thresholds are set by a combination of the modem manufacturer (Qualcomm, MediaTek, Apple's own silicon), the OS radio layer, and carrier provisioning files pushed over-the-air. Which is why two people with the same phone model on different carriers can experience noticeably different handoff behavior.

The Wi-Fi Problem Nobody Talks About

Wi-Fi's position at the top of the hierarchy creates a failure mode that is quietly responsible for a lot of "why is my phone so slow" complaints. This is the part that genuinely frustrates me, because it's a design flaw dressed up as a feature.

A saved network with a weak signal still beats cellular in the default preference order on most Android and iOS builds. So if you walked through a hotel lobby three months ago and saved their Wi-Fi, and you're back in range of that same barely-there signal, your phone may latch onto it and deliver 2 Mbps when your LTE would give you 40. iOS and recent Android versions have added Wi-Fi Assist and Adaptive Connectivity features to detect this and switch to cellular automatically. Those features use their own quality thresholds, though, and they don't always trigger before you've already watched a video stutter for twenty seconds.

Take Marcus, who saved the Wi-Fi at his gym's front desk. The weights room is forty meters away, behind a concrete wall. His phone connects to that network every time he walks in, gets an RSSI of around -80 dBm (marginal, not catastrophic), and Wi-Fi Assist decides it's just barely good enough not to override. His Spotify buffers. His LTE, one meter away in his pocket, would be fine. The system worked exactly as designed and still produced a bad experience.

Found a saved network doing this to you? On iOS, forget it. On Android, you can usually set a per-network preference or let Adaptive Connectivity take over. Either way, you'll notice the difference immediately.

5G's Specific Complication

Fifth-generation networks introduced a wrinkle that older radio selection logic wasn't built for: there are effectively two different 5G technologies sharing a single brand name.

Sub-6 GHz 5G uses frequencies below 6 gigahertz, travels far, penetrates walls reasonably well, and offers speeds modestly better than LTE in most real conditions. mmWave 5G uses millimeter-wave frequencies (24 GHz and above), offers extraordinary peak speeds, and has a usable range measured in tens of meters with near-zero wall penetration. Think of it less like a network upgrade and more like a very fast spotlight that only works outdoors, in good weather, if you're standing close enough.

Phones with mmWave capability maintain a separate radio for it and treat it almost like a bonus layer on top of Sub-6. The modem rides Sub-6 or LTE as the baseline and only attempts mmWave when it detects a strong, close-range signal, typically in a stadium, a transit hub, or directly outside a carrier's small-cell installation. Step inside a building and the mmWave connection evaporates, the fallback happens in under a second, you never notice.

This is also why battery life on mmWave-capable phones can take a hit in dense urban environments. The radio is constantly probing for mmWave opportunities, deciding they're not good enough, and settling back to Sub-6. That probing isn't free.

What the Carrier Actually Controls

Your phone doesn't make these decisions alone. Carriers push configuration files, sometimes called carrier bundles or MCFG files, that adjust the thresholds and preferences described above. A carrier with strong 5G infrastructure might configure aggressive 5G camping behavior, keeping your phone on 5G even at marginal signal quality to improve their adoption metrics. A carrier with patchy coverage might configure earlier fallback to LTE to reduce call drops.

This is why unlocked phones sometimes behave differently than carrier-locked versions of the same model. The hardware is identical. The radio policy files are not.

Apple and Google publish some of this behavior in developer documentation, but the full carrier provisioning specs are treated as proprietary. You can't inspect them from a consumer interface. You can observe their effects: if your phone seems reluctant to grab 5G even when you're standing next to a tower, a carrier file is probably the reason. Worth knowing before you call support.

The Battery Cost You're Actually Paying

Every radio state transition costs power. Not catastrophic. Not nothing. The modem chip enters a high-power scanning state when it's evaluating a switch, then settles into a lower-power connected state once it's locked on. A phone that's constantly hovering at the edge of its Wi-Fi range, running those evaluations on repeat, will drain measurably faster than one with a clean, stable connection.

A two-year-old phone that starts the day at 100% and hits 20% by dinner is almost certainly not just suffering from battery degradation. If it spends those hours in a building with weak Wi-Fi and intermittent 5G, the modem is running hot all day. The battery takes the blame. The radio selection logic is the actual cause.

The practical fix is straightforward: strong, stable connections of any type beat weak connections of a nominally superior type. A solid LTE signal outperforms a struggling 5G one for both speed and endurance, and that's not a bug in the system.

Knowing the mechanism won't give you a control panel. But the gap between what the algorithm optimizes for and what you actually experience is where most of the frustration lives, and it's a lot easier to stop blaming the wrong thing once you can see the gap clearly.