[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["缺少我需要的資訊","missingTheInformationINeed","thumb-down"],["過於複雜/步驟過多","tooComplicatedTooManySteps","thumb-down"],["過時","outOfDate","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["示例/程式碼問題","samplesCodeIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間:2025-07-27 (世界標準時間)。"],[],[],null,["# Wi-Fi AP/AP concurrency\n\nAndroid 12 introduces Wi-Fi AP/AP concurrency, which\nlets devices create two access point (AP) interfaces. This feature lets\ndevices support tethering through a dual band simultaneous (DBS) Wi-Fi\nhotspot (soft AP). For details on supporting tethering through a single Wi-Fi\nhotspot, see\n[Wi-Fi Hotspot (Soft AP) Support](/docs/core/connect/wifi-softap).\n\nThis page describes the device behavior when this feature is enabled and\nimplementation details for device manufacturers and vendors.\n\nHow it works\n------------\n\n| **Note:** Android 12 supports the 2.4 GHz and 5 GHz bands for Wi-Fi AP/AP concurrency. Android 13 adds support for the 6 GHz band.\n\nWhen Wi-Fi AP/AP concurrency is supported, the device can create two AP\ninterfaces, for example, one interface working on the 2.4 GHz band and one\non the 5 GHz band. Clients can then connect to each of the AP interfaces.\n\nThe Wi-Fi HAL generates a single bridged interface with the two AP\ninterfaces and exposes it to the Wi-Fi and connectivity stack when the stack\nenables a soft AP. After the soft AP is enabled, the Wi-Fi HAL indicates that\ntwo interfaces are available and updates the information\n(such as operation channel, bandwidth, and BSSID) for each AP.\n\nTo save power, the framework disables an unused AP (2.4 GHz, 5 GHz, or\n6 GHz) after a period of inactivity. The framework considers an AP to be\ninactive when no client is connected. Device manufacturers can customize the\nlength of this inactive period. For more information, see\n[Customize the inactivity period](#customize).\n\nDevices support Wi-Fi AP/AP concurrency by using one of the following\nbridged soft AP configurations:\n\n- Configuring two bands (the channel is automatically selected by the framework or the driver)\n- Configuring two channels on a dual-band AP\n\nRequirements\n------------\n\nTo implement Wi-Fi AP/AP concurrency, devices must meet the following\nrequirements:\n\n- The Wi-Fi chip or firmware must support two concurrent AP\n connections. The firmware must support all channel and band combinations\n for both connections. To avoid performance issues, we recommend using\n a 2x2+2x2 DBS capable Wi-Fi chip.\n\n- The device must support the following methods in the Wi-Fi Vendor HAL:\n\n - `IWifiChip.createBridgedApIface()`\n - `IWifiChip.removeIfaceInstanceFromBridgedApIface()`\n - `IWifiApIface.resetToFactoryMacAddress()`\n - `IWifiApIface.getBridgedInstances()`\n\nImplementation\n--------------\n\nTo implement Wi-Fi AP/AP concurrency, do the following:\n\n1. Enable at least one of the following functions (disabled by default) using\n [runtime resource overlays](/docs/core/architecture/rros):\n\n - `config_wifiBridgedSoftApSupported`: Supports multiple APs that are bridged together.\n - `config_wifiStaWithBridgedSoftApConcurrencySupported`: Supports concurrency of a station (STA) and multiple bridged APs.\n2. For devices using the AIDL Wi-Fi HAL or HIDL Wi-Fi HAL 1.6,\n define `AP_BRIDGED` in the Wi-Fi HAL interface combination. For more\n details, see\n [Wi-Fi multi-interface concurrency](/docs/core/connect/wifi-hal#wi-fi_multi-interface_concurrency).\n\n3. Configure the bridged soft AP configuration by calling one of the following\n methods:\n\n - [`SoftApConfiguration.Builder#setBands`](https://cs.android.com/android/platform/superproject/+/android-latest-release:packages/modules/Wifi/framework/java/android/net/wifi/SoftApConfiguration.java?q=%22Builder%20setBands%22)\n - [`SoftApConfiguration.Builder#setChannels`](https://cs.android.com/android/platform/superproject/+/android-latest-release:packages/modules/Wifi/framework/java/android/net/wifi/SoftApConfiguration.java?q=%22Builder%20setChannels%22)\n4. Register a callback to obtain the device capabilities using\n `WifiManager#registerSoftApCallback`. The `SoftApCallback` callback\n provides the following methods for a bridged soft AP configuration:\n\n - [`SoftApCallback#onInfoChanged`](https://cs.android.com/android/platform/superproject/+/android-latest-release:packages/modules/Wifi/framework/java/android/net/wifi/WifiManager.java?q=%22void%20onInfoChanged%28@NonNull%20List%22): Provides information about the running soft AP instances.\n - [`SoftApCallback#onConnectedClientsChanged`](https://cs.android.com/android/platform/superproject/+/android-latest-release:packages/modules/Wifi/framework/java/android/net/wifi/WifiManager.java?q=%22onConnectedClientsChanged%28@NonNull%20SoftApInfo%22): Provides a list of connected clients for a soft AP instance.\n\nCustomize the inactivity period\n-------------------------------\n\nTo customize the length of the inactivity period, configure the following\noverlay, which is found\nin [`packages/modules/Wifi/service/ServiceWifiResources/res/values/config.xml`](https://cs.android.com/android/platform/superproject/+/android-latest-release:packages/modules/Wifi/service/ServiceWifiResources/res/values/config.xml):\n\n- `config_wifiFrameworkSoftApShutDownIdleInstanceInBridgedModeTimeoutMillisecond`:\n The default shutdown timeout interval. Only valid if\n `SoftApConfiguration#setBridgedModeOpportunisticShutdownEnabled` is enabled.\n\n- (Available from 13)\n `config_wifiFrameworkSoftApDisableBridgedModeShutdownIdleInstanceWhenCharging`:\n Indicates whether to disable the inactivity shutdown timer when charging."]]