Android Network Connection Detection and Broadcast Receiver Optimization

Analysis of Broadcast Receiver Multiple Invocation Issue

In Android application development, real-time monitoring of network connection status is a common requirement. Developers typically use BroadcastReceiver to listen for network state changes, but often encounter the issue of the receiver being invoked multiple times. According to user feedback, when device network status changes, the broadcast receiver is triggered twice, which clearly does not meet the business requirement of "notify only when network is available".

Root Cause: Multiple Intent Filters

Analyzing the original code's AndroidManifest.xml configuration reveals that the core issue lies in the intent filter setup:

<intent-filter>
    <action android:name="android.net.conn.CONNECTIVITY_CHANGE" />
    <action android:name="android.net.wifi.WIFI_STATE_CHANGED" />
</intent-filter>

This configuration causes the receiver to simultaneously listen for two different network state change events. When network connection status changes, the system sends both CONNECTIVITY_CHANGE and WIFI_STATE_CHANGED broadcasts, triggering the receiver to execute twice.

Solution: Single Intent Filter

The simplest and most effective solution to the duplicate invocation problem is to use a single intent filter. According to Android official documentation and best practices, the CONNECTIVITY_CHANGE action already covers all network connection state changes, including Wi-Fi and mobile data connections and disconnections.

<intent-filter>
    <action android:name="android.net.conn.CONNECTIVITY_CHANGE" />
</intent-filter>

With this configuration, the broadcast receiver is only called when the overall network connection status changes, avoiding duplicate notification issues.

Network Connection State Detection Optimization

The network detection logic in the original code has room for improvement. While using wifi.isAvailable() || mobile.isAvailable() can determine if network interfaces are available, this method cannot accurately reflect the actual network connection status. According to Android official guidelines, the isConnected() method should be used to verify if the network is truly available.

Improved Network Detection Method

Here is the optimized network connection detection method:

public boolean isOnline(Context context) {
    ConnectivityManager cm = (ConnectivityManager) context.getSystemService(Context.CONNECTIVITY_SERVICE);
    NetworkInfo netInfo = cm.getActiveNetworkInfo();
    return (netInfo != null && netInfo.isConnected());
}

This method offers the following advantages:

• Uses getActiveNetworkInfo() to obtain current active network connection information
• Accurately determines if the network is truly available through isConnected()
• Handles null pointer exceptions in special cases like airplane mode
• Provides more concise and reliable code

Complete Broadcast Receiver Implementation

Combining the above optimizations, the complete network change broadcast receiver implementation is as follows:

public class NetworkChangeReceiver extends BroadcastReceiver {
    @Override
    public void onReceive(final Context context, final Intent intent) {
        if (isOnline(context)) {
            // Logic to handle when network is available
            Log.d("Network", "Network connection established");
            // Perform network-related operations
        }
    }
    
    private boolean isOnline(Context context) {
        ConnectivityManager cm = (ConnectivityManager) context.getSystemService(Context.CONNECTIVITY_SERVICE);
        NetworkInfo netInfo = cm.getActiveNetworkInfo();
        return (netInfo != null && netInfo.isConnected());
    }
}

Permission Configuration Requirements

To implement network state detection functionality, necessary permissions must be declared in AndroidManifest.xml:

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

This permission allows the application to access network state information and is fundamental to network detection functionality. If the application also needs to perform actual network communication, the INTERNET permission should be added.

Broadcast Receiver Registration Methods

In addition to statically registering broadcast receivers in AndroidManifest.xml, they can also be registered dynamically in code. Dynamic registration offers the advantage of better control over the receiver's lifecycle, avoiding unnecessary system resource consumption.

// Dynamic registration in Activity
private NetworkChangeReceiver networkReceiver;

@Override
protected void onResume() {
    super.onResume();
    IntentFilter filter = new IntentFilter(ConnectivityManager.CONNECTIVITY_ACTION);
    networkReceiver = new NetworkChangeReceiver();
    registerReceiver(networkReceiver, filter);
}

@Override
protected void onPause() {
    super.onPause();
    if (networkReceiver != null) {
        unregisterReceiver(networkReceiver);
    }
}

Network Type Differentiation

In certain scenarios, applications may need to distinguish between Wi-Fi and mobile data networks to provide differentiated functionality. For example, performing large data transfers only in Wi-Fi environments:

public NetworkType getCurrentNetworkType(Context context) {
    ConnectivityManager cm = (ConnectivityManager) context.getSystemService(Context.CONNECTIVITY_SERVICE);
    NetworkInfo activeNetwork = cm.getActiveNetworkInfo();
    
    if (activeNetwork != null && activeNetwork.isConnected()) {
        switch (activeNetwork.getType()) {
            case ConnectivityManager.TYPE_WIFI:
                return NetworkType.WIFI;
            case ConnectivityManager.TYPE_MOBILE:
                return NetworkType.MOBILE;
            default:
                return NetworkType.OTHER;
        }
    }
    return NetworkType.NONE;
}

Performance Optimization Considerations

Frequent network state detection may impact application performance. In actual development, you should:

• Avoid performing time-consuming operations in broadcast receivers
• Use appropriate thread management to handle network operations
• Consider using network state caching to reduce repeated detection
• Register and unregister broadcast receivers at appropriate times

Compatibility Considerations

As Android versions update, network state detection APIs have also evolved:

• In Android 7.0 and above, CONNECTIVITY_ACTION broadcast is restricted
• It's recommended to use NetworkCallback for more granular network state monitoring
• For applications needing to support older versions, fallback solutions should be provided

Practical Application Scenarios

Network state detection has wide application scenarios in mobile applications:

• Network condition judgment for automatic data synchronization
• Video quality adaptation in video playback applications
• Automatic switching between offline and online modes
• Retry mechanisms after network request failures

Testing and Debugging Recommendations

To ensure the reliability of network state detection functionality, it is recommended to:

• Conduct thorough testing in different network environments
• Simulate various scenarios of network connection and disconnection
• Use Android Studio's network analysis tools to monitor network state changes
• Record detailed network state information in logs

Using the methods introduced in this article, developers can build stable and reliable network state detection functionality, avoid broadcast receiver duplicate invocation issues, and provide better user experience and higher code quality.