Android 8（Oreo）IoT应用配网阶段Wi-Fi连接异常问题咨询

Hey there, let's break down this issue you're facing with your IoT app's onboarding flow on Android 8 devices. Your hunch about the Seamless Connectivity feature is totally right—here's exactly why it's causing problems and how to fix it:

Why Seamless Connectivity is the Culprit #

Android 8.0 (API level 26) rolled out Seamless Connectivity, a feature that automatically switches your device to what it considers a "better" Wi-Fi network—almost always one that has internet access. Since your IoT device's hotspot doesn't have internet, the system sees any previously saved, internet-enabled network as a better option and jumps to it mid-onboarding, which breaks your setup flow.

Fix 1: Use a Wi-Fi Lock to Hold the Hotspot Connection #

This is the simplest and most reliable fix. A Wi-Fi Lock tells the system your app needs to stay connected to the current Wi-Fi network, overriding automatic switching.

First, add the required permissions to your AndroidManifest.xml:

<uses-permission android:name="android.permission.ACCESS_WIFI_STATE" />
<uses-permission android:name="android.permission.CHANGE_WIFI_STATE" />

Then, in the component handling your onboarding flow (activity or service), acquire the lock when connecting to the IoT hotspot:

// Get the Wi-Fi manager instance
val wifiManager = getSystemService(Context.WIFI_SERVICE) as WifiManager
// Create a high-performance Wi-Fi lock (adjust mode if needed)
val wifiLock = wifiManager.createWifiLock(WifiManager.WIFI_MODE_FULL_HIGH_PERF, "IoTOnboardingLock")
// Acquire the lock
wifiLock.acquire()

Don't forget to release the lock once configuration is done and the user is ready to switch to home Wi-Fi:

if (wifiLock.isHeld) {
    wifiLock.release()
}

Fix 2: Temporarily Disable Auto-Connect for Saved Networks #

If the Wi-Fi Lock alone isn't enough, you can temporarily turn off auto-connect for all other saved networks while onboarding. Note this requires the WRITE_SETTINGS permission, which users have to grant manually.

First, request the permission:

if (!Settings.System.canWrite(this)) {
    val intent = Intent(Settings.ACTION_MANAGE_WRITE_SETTINGS)
    intent.data = Uri.parse("package:$packageName")
    startActivity(intent)
}

Then, disable auto-connect for all networks except your IoT hotspot:

val configs = wifiManager.configuredNetworks
configs?.forEach { config ->
    // Replace with your IoT hotspot's SSID (wrap in quotes as stored by the system)
    if (config.SSID != "\"MyIoTDeviceHotspot\"") {
        config.autoConnect = false
        wifiManager.updateNetwork(config)
    }
}
// Save the changes
wifiManager.saveConfiguration()

Make sure to re-enable auto-connect for these networks once onboarding finishes!

Fix 3: Use NetworkRequest to Prioritize the IoT Hotspot #

You can use Android's NetworkRequest API to explicitly tell the system your app needs the IoT hotspot connection, binding your app's network traffic to it.

Here's how to set it up:

val connectivityManager = getSystemService(Context.CONNECTIVITY_SERVICE) as ConnectivityManager
// Build a network request targeting your IoT hotspot
val networkRequest = NetworkRequest.Builder()
    .addTransportType(NetworkCapabilities.TRANSPORT_WIFI)
    .addCapability(NetworkCapabilities.NET_CAPABILITY_NOT_METERED) // IoT hotspots are typically unmetered
    .setNetworkSpecifier("MyIoTDeviceHotspot") // Your IoT hotspot SSID
    .build()

// Create a callback to bind to the network when available
val networkCallback = object : ConnectivityManager.NetworkCallback() {
    override fun onAvailable(network: Network) {
        // Bind your app's process to this network
        connectivityManager.bindProcessToNetwork(network)
    }
}

// Request the network
connectivityManager.requestNetwork(networkRequest, networkCallback)

When you're done with the hotspot, clean up:

connectivityManager.unregisterNetworkCallback(networkCallback)
connectivityManager.bindProcessToNetwork(null)

Final Notes #

Start with Fix 1—it's the least intrusive and works for most cases. If you still see issues, combine it with Fix 3 to enforce network priority. Avoid Fix 2 unless absolutely necessary, since modifying user network settings can be disruptive.

内容的提问来源于stack exchange，提问作者Digital Da