Fix Sticky WiFi Roaming: Help Phones Move Between Access Points

A video call is clear at the desk, freezes in the corridor and recovers only after WiFi is toggled off and on. Another access point is visible nearby, so the original AP looks guilty. However, proximity alone does not prove the phone can join the second AP with the same working network and security.

Begin with a repeatable route and one affected device. A brief internet slowdown, a poor uplink and a failed roaming transition can feel similar during a call, but they require different fixes.

Prove That the Failure Follows a Handover

Test the phone while stationary beside each AP. If it performs poorly without moving, investigate coverage, interference, the wired path and service quality first. Roaming settings will not repair a broken AP uplink.

Then walk the same route at a normal pace while monitoring the connected AP or BSSID through the supported tools. Record where the phone changes AP, whether the call pauses and whether the device retains the expected address and access.

Repeat in both directions. One transition can behave differently from the return journey because the starting association, signal environment and client decisions have changed. The meeting-room WiFi guide is useful if calls fail mainly when the room fills rather than when someone moves.

Create Usable Overlap, Not Just Visible Names

The next AP must provide a usable connection in the handover area. Seeing its network name is not enough. Check the client’s return signal, interference and the capacity of each cell, as well as the AP’s transmit setting.

Do not automatically turn every AP to maximum power. A high-power AP may remain audible across the building while the phone’s lower-power transmission struggles to return. Deliberate placement and power planning can produce more useful cells than simply making every signal larger.

Keep the network name, security policy and intended client-network design consistent where seamless movement is required. A matching SSID on two unrelated routers does not make their addressing and session paths the same. Establish which device routes and assigns addresses before tuning radio features.

Know What Roaming Assistance Actually Adds

The client makes its roaming decisions. The access infrastructure can provide information and assistance, but it cannot guarantee that every phone reacts identically.

UniFi and Omada expose their own controls, with support depending on the AP, controller, security mode and client. A label such as Fast Roaming should not be assumed to enable identical features on every platform. Check the installed versions and test the affected phone.

Use Forced Disconnection Carefully

Minimum RSSI is measured from the AP’s perspective. When a policy disconnects a weak client, that client still needs to discover and join another suitable AP. If none is available, it may reconnect to the original AP and be removed again.

There is no universal threshold that fixes every building. Measure the transition areas and tune per deployment. A value copied from another office can turn a marginal but functioning connection into a repeated outage.

Preserve a working baseline and change one control at a time. Avoid simultaneously altering power, channel width, security, roaming settings and minimum signal. Test the supported client mix, including older devices and equipment that does not move.

Test the Devices and Applications People Actually Use

A current phone, an older laptop and a handheld work device can make different decisions on the same route. Include the devices that caused the complaint rather than using one new test phone as proof for everyone.

Check a live call, an ordinary file or web task and any application that is sensitive to interruptions. A large download can recover invisibly while a conversation loses several words. Record the symptom that matters to the user, not only the peak speed after the transition.

Where necessary, test compatibility with advanced roaming features enabled and disabled in a controlled profile. Retain suitable security. A feature that benefits compatible mobile clients does not justify weakening authentication or applying an untested configuration to every network.

Choose APs for a Managed Deployment

The Ubiquiti U7-Pro and TP-Link EAP772 are current catalogue examples from two managed ecosystems. Their WiFi generation and Ethernet uplink do not, by themselves, solve a sticky-client problem.

Compare management, placement, compatible features and the supporting wired network as a system. The mesh and access-point guide explains why backhaul design matters before adding more nodes.

Call the fix complete when the real walking route works repeatedly. Test both directions, record the chosen settings and confirm that stationary clients remain stable. Buying a faster AP is appropriate when the deployment needs its capacity or features, but it is not a substitute for correcting the handover design.

Frequently Asked Questions