Windows Mobile 6.5 Wi-Fi and Cellular Switching

Windows Mobile 6.5 managed network traffic through a native subsystem known as the Connection Manager, which automatically arbitrated transitions between Wi-Fi and cellular data networks. Designed primarily to conserve bandwidth and reduce cellular carrier costs, the operating system used a strict priority hierarchy that favored Wi-Fi whenever an authenticated network was available, falling back to cellular packet data (such as GPRS, EDGE, or 3G) when the Wi-Fi signal was lost. While functional, this switching mechanism relied on distinct socket disconnections rather than the seamless handovers seen in modern mobile operating systems.

The Role of Connection Manager

The Windows Mobile Connection Manager (ConnMgr) served as the central broker for all network requests. Applications did not directly interface with network hardware; instead, they requested network access (such as Internet access or private corporate network access) from the Connection Manager.

The system maintained predefined priority tiers:

  1. Desktop Passthrough / Cradle: ActiveSync or Windows Mobile Device Center connections via USB.
  2. Wi-Fi (802.11): Wireless local area networks.
  3. Cellular Packet Data: GPRS, EDGE, UMTS, or HSDPA connections.

Transitioning from Cellular to Wi-Fi

When a device with an active cellular data session came within range of a known, configured Wi-Fi network:

  1. Association and DHCP: The Wi-Fi radio associated with the access point and acquired an IP address via DHCP.
  2. Routing Update: The Connection Manager detected that a higher-priority network adapter was available and updated the device's internal routing table.
  3. Traffic Migration: New outbound network requests were directed through the Wi-Fi adapter.
  4. Cellular Dormancy: The cellular data connection was either disconnected or placed in a dormant state after a configurable idle timeout (typically managed by registry keys such as IdleDisconnectTime) to preserve battery and avoid simultaneous data consumption.

Transitioning from Wi-Fi to Cellular

When moving out of Wi-Fi range or disabling the Wi-Fi radio:

  1. Signal Loss: The Wi-Fi adapter dropped the carrier signal, prompting the Network Driver Interface Specification (NDIS) layer to report the disconnection to the Connection Manager.
  2. Cellular Negotiation: If an application requested active data access, the Connection Manager initiated a cellular data session by signaling the Radio Interface Layer (RIL) to establish a packet data protocol (PDP) context with the mobile network.
  3. IP Reassignment: The carrier assigned a new cellular IP address to the mobile interface.

Technical Limitations and Handover Friction

The handover mechanism in Windows Mobile 6.5 was not hitless:

  • Broken Sockets: Switching between Wi-Fi and cellular changed the device's public and local IP addresses. Windows Mobile 6.5 did not feature native protocols like Multipath TCP (MPTCP) to persist established connections across adapters. Consequently, existing TCP connections (such as file downloads, streaming audio, or active Secure Shell sessions) were severed and required the application to initiate a reconnect.
  • Power Management Disconnects: To conserve battery life, the operating system's default power state policy often powered down the Wi-Fi radio when the device entered an unattended or suspended state (screen off). This routinely forced the device onto cellular data or disconnected background applications entirely unless OEM-specific registry tweaks or third-party utilities were used to keep the Wi-Fi adapter active during sleep.