How to Fix Sticky WiFi Clients: Tuning Roaming Aggressiveness on Windows, Android, and Mac for Multi-AP Homes

You move from your home office to the kitchen, and your laptop’s WiFi speed tanks. The signal bar in the corner still shows three or four bars — so what’s wrong? Most likely, your device is a sticky client: it’s still holding onto the access point in your office, even though the kitchen mesh node is ten feet away. The result is slower speeds, higher latency, and sometimes outright dropped connections.

This is one of the most common complaints in multi-AP homes — mesh systems, separate access points, or any setup with more than one wireless node. The fix usually lives on both sides of the connection: the device and the infrastructure. Here’s how to address both.

Why Devices Become Sticky

Every WiFi client — your phone, laptop, tablet — decides on its own when to roam. The access point cannot force a device to disconnect and reconnect to a different node (with the exception of 802.11v BSS Transition Management, covered below). The client measures signal strength from its current AP and only triggers a roam when that signal falls below an internal threshold.

The problem: most operating systems set that threshold conservatively. A Mac, for example, won’t roam until the current AP’s RSSI drops below −75 dBm and the candidate AP is at least 10–12 dBm stronger. Windows defaults to “Medium” aggressiveness, which means it keeps scanning but may still hold a −70 dBm connection even when a −50 dBm node is nearby. Android behavior varies by manufacturer and driver, with some Pixel models notorious for clinging to the originally connected AP across the whole house.

Fixing Sticky Clients on Windows

Windows exposes roaming aggressiveness as a per-adapter setting in Device Manager. Intel adapters call it Roaming Aggressiveness; Ralink and Qualcomm adapters may label it Roaming Sensitivity. The steps are the same either way:

1. Press Win + X and open Device Manager.
2. Expand Network adapters, then double-click your wireless adapter (e.g., “Intel Wi-Fi 6E AX211”).
3. Click the Advanced tab.
4. In the Property list, select Roaming Aggressiveness (or Roaming Sensitivity).
5. Change the Value from 3-Medium to 5-Highest.
6. Click OK and allow the adapter to reconnect.

With “Highest” set, the adapter scans for candidate APs more frequently and will roam to a stronger node even when the current connection is still acceptable. The trade-off is a slight increase in background scanning overhead, but on any modern Intel or Qualcomm adapter this is negligible.

Windows Power Plan Interaction

Even with aggressiveness set to Highest, a laptop running on a battery-saver power plan can suppress roaming scans to conserve power. In Device Manager’s Advanced tab, also check Power Management (or Wireless Mode) and ensure it is not set to “Maximum Power Saving.” Set it to Maximum Performance when you need reliable multi-AP roaming. For a deeper look at how power plans affect WiFi speed, see our guide on fixing WiFi slowdowns when plugged in.

Fixing Sticky Clients on Android

Android does not expose a user-facing roaming aggressiveness slider the way Windows does. The underlying WiFi chip driver controls roaming thresholds, and these vary by device manufacturer and firmware version.

Google Pixel: Disable Adaptive Connectivity

On Pixel 4a and newer, a feature called Adaptive Connectivity adjusts WiFi and mobile data behavior to conserve battery — which can inadvertently suppress roaming scans. To disable it:

1. Open Settings → Network & Internet → Adaptive Connectivity.
2. Toggle Adaptive Connectivity off.

After disabling this, most Pixel owners report noticeably faster handoffs between mesh nodes.

Samsung Galaxy: Use 5 GHz or Wi-Fi 6 Bands

Samsung’s WiFi stack tends to be more aggressive about roaming than stock Android when the 5 GHz or 6 GHz bands are in use. If your Galaxy phone is sticky, check that band steering on your router is enabled so it is not stuck on 2.4 GHz, which has wider range and thus a lower incentive to roam. See our guide on WiFi band steering for how to configure this.

General Android Fix: Forget and Reconnect Near the Target Node

Android remembers which AP (BSSID) it first associated with for a given SSID. If a device originally connected to a far node, it may prefer that BSSID indefinitely. Forgetting the network and reconnecting while physically near the node you want as the “home base” can reset this preference.

Fixing Sticky Clients on Mac

macOS is the most conservative of the three when it comes to roaming. Apple Silicon Macs support 802.11k (neighbor reports) and 802.11v (BSS transition management), but Intel-based Macs do not support 802.11r fast roaming. Even on supported hardware, macOS applies strict hysteresis: the current AP’s RSSI must fall below −75 dBm before the device considers roaming, and the candidate must be at least 10–12 dBm better.

Using the Wireless Diagnostics Network Preferences

macOS does not expose a roaming aggressiveness slider in System Settings. However, you can influence roaming behavior through the hidden JoinMode setting using the networksetup command-line tool:

sudo networksetup -setairportnetworkpreferences Wi-Fi JoinMode:Strongest

Setting JoinMode to Strongest instructs the WiFi driver to evaluate candidate APs and connect to the one with the best signal, rather than holding the current connection until it degrades. This is the single most effective client-side fix for sticky Mac behavior on mesh networks.

To revert to default behavior:

sudo networksetup -setairportnetworkpreferences Wi-Fi JoinMode:Automatic

Router-Side Fixes: The Other Half of the Problem

Client-side settings help, but infrastructure configuration is often more impactful — especially for Android and Mac devices that offer limited client-side control.

Enable 802.11r, 802.11k, and 802.11v

These three amendments work together to enable fast, assisted roaming. Most WiFi 6 and WiFi 7 mesh systems enable them by default, but on standalone access points you may need to activate them manually. For a full breakdown of how each protocol works, see our guide on WiFi roaming protocols 802.11r, 802.11k, and 802.11v.

• 802.11k — Provides the client a list of neighboring APs and their signal levels, so it can make informed roaming decisions without scanning every channel from scratch.
• 802.11v BSS Transition Management — Allows the AP to suggest (not force) that a client roam to a better node. The client still decides, but a BSS transition request is a strong nudge, and most modern devices honor it.
• 802.11r Fast BSS Transition — Reduces the re-authentication time during a roam from hundreds of milliseconds to under 50ms, eliminating the brief connectivity gap that causes VoIP calls or gaming sessions to hiccup during handoffs.

Set a Minimum RSSI Threshold

Many enterprise-grade and prosumer access points (UniFi, ASUS AiMesh, Netgear Orbi, OpenWRT) let you configure a minimum RSSI threshold (also called BSS Min Rate or kick threshold). When a client’s signal drops below this value — typically −70 to −75 dBm — the AP disassociates the client, forcing it to reconnect to the strongest available node. This is the most reliable way to fix persistent sticky clients on devices that ignore BSS transition requests.

Reduce Transmit Power

Counterintuitively, lowering your access point’s transmit power can reduce sticky client behavior. When every node blasts at maximum power, clients can maintain a technically “acceptable” (but degraded) signal from a far node for much longer than they should. Reducing transmit power shrinks each node’s effective range, which forces the client’s signal to drop faster as it moves away — triggering a roam sooner. For mesh systems covering 2,000–3,000 sq ft, 50–75% transmit power on the 5 GHz radio often produces better roaming than 100%. See our WiFi transmit power guide for how to tune this on common routers.

Quick Checklist

• Windows: Device Manager → Advanced tab → Roaming Aggressiveness = Highest
• Pixel Android: Settings → Adaptive Connectivity → Off
• Mac: sudo networksetup -setairportnetworkpreferences Wi-Fi JoinMode:Strongest
• Router: Enable 802.11k, 802.11v, and 802.11r on all APs
• Router: Set minimum RSSI kick threshold to −70 to −75 dBm
• Router: Reduce AP transmit power to 50–75% on 5 GHz if nodes are close together

Apply the client-side fix for your OS, enable the roaming protocols on your mesh system, and run a speed test from different rooms to verify that handoffs are happening correctly. In most homes, this combination eliminates sticky client behavior entirely.