Google is committed to advancing racial equity for Black communities. See how.

Wi-Fi Aware capabilities enable devices running Android 8.0 (API level 26) and higher to discover and connect directly to each other without any other type of connectivity between them. Wi-Fi Aware is also known as Neighbor Awareness Networking (NAN).

Wi-Fi Aware networking works by forming clusters with neighboring devices, or by creating a new cluster if the device is the first one in an area. This clustering behavior applies to the entire device and is managed by the Wi-Fi Aware system service; apps have no control over clustering behavior. Apps use the Wi-Fi Aware APIs to talk to the Wi-Fi Aware system service, which manages the Wi-Fi Aware hardware on the device.

The Wi-Fi Aware APIs let apps perform the following operations:

Discover other devices: The API has a mechanism for finding other nearby devices. The process starts when one device publishes one or more discoverable services. Then, when a device subscribes to one or more services and enters the publisher's Wi-Fi range, the subscriber receives a notification that a matching publisher has been discovered. After the subscriber discovers a publisher, the subscriber can either send a short message or establish a network connection with the discovered device. Devices can concurrently be both publishers and subscribers.

Create a network connection: After two devices have discovered each other they can create a bi-directional Wi-Fi Aware network connection without an access point.

Wi-Fi Aware network connections support higher throughput rates across longer distances than Bluetooth connections. These types of connections are useful for apps that share large amounts of data between users, such as photo-sharing apps.

Initial setup

To set up your app to use Wi-Fi Aware discovery and networking, perform the following steps:

Request the following permissions in your app's manifest: <uses-permission android:name="android.permission.ACCESS_WIFI_STATE" /> <uses-permission android:name="android.permission.CHANGE_WIFI_STATE" /> <uses-permission android:name="android.permission.ACCESS_FINE_LOCATION" /> Check whether the device supports Wi-Fi Aware with the PackageManager API, as shown below: Kotlin context.packageManager.hasSystemFeature(PackageManager.FEATURE_WIFI_AWARE) Java context.getPackageManager().hasSystemFeature(PackageManager.FEATURE_WIFI_AWARE); Check whether Wi-Fi Aware is currently available. Wi-Fi Aware may exist on the device, but may not be currently available because the user has disabled Wi-Fi or Location. Depending on their hardware and firmware capabilities, some devices may not support Wi-Fi Aware if Wi-Fi Direct, SoftAP, or tethering is in use. To check whether Wi-Fi Aware is currently available, call isAvailable() . The availability of Wi-Fi Aware can change at any time. Your app should register a BroadcastReceiver to receive ACTION_WIFI_AWARE_STATE_CHANGED , which is sent whenever availability changes. When your app receives the broadcast intent, it should discard all existing sessions (assume that Wi-Fi Aware service was disrupted), then check the current state of availability and adjust its behavior accordingly. For example: Kotlin val wifiAwareManager = context.getSystemService(Context.WIFI_AWARE_SERVICE) as WifiAwareManager? val filter = IntentFilter(WifiAwareManager.ACTION_WIFI_AWARE_STATE_CHANGED) val myReceiver = object : BroadcastReceiver() { override fun onReceive(context: Context, intent: Intent) { // discard current sessions if (wifiAwareManager?.isAvailable) { ... } else { ... } } } context.registerReceiver(myReceiver, filter) Java WifiAwareManager wifiAwareManager = (WifiAwareManager)context.getSystemService(Context.WIFI_AWARE_SERVICE) IntentFilter filter = new IntentFilter(WifiAwareManager.ACTION_WIFI_AWARE_STATE_CHANGED); BroadcastReceiver myReceiver = new BroadcastReceiver() { @Override public void onReceive(Context context, Intent intent) { // discard current sessions if (wifiAwareManager.isAvailable()) { ... } else { ... } } }; context.registerReceiver(myReceiver, filter);

For more information, see Broadcasts.

Note: Make sure that you register the broadcast receiver before checking availability. Otherwise, there could be a period of time when the app thinks that Wi-Fi Aware is available but isn't notified if availability changes.

Obtain a session

To start using Wi-Fi Aware, your app must obtain a WifiAwareSession by calling attach() . This method does the following:

Turns on the Wi-Fi Aware hardware.

Joins or forms a Wi-Fi Aware cluster.

Creates a Wi-Fi Aware session with a unique namespace that acts as a container for all discovery sessions created within it.

If the app attaches successfully, the system executes the onAttached() callback. This callback provides a WifiAwareSession object that your app should use for all further session operations. An app can use the session to publish a service or subscribe to a service.

Your app should call attach() only once. If your app calls attach() multiple times, the app receives a different session for each call, each with its own namespace. This could be useful in complex scenarios, but should generally be avoided.

Note: WifiAwareSession.close() when the session is no longer needed. As long as there are active sessions, the system maintains synchronization with a Wi-Fi Aware cluster. This clustering consumes resources and battery. To conserve resources, callwhen the session is no longer needed.

Publish a service

To make a service discoverable, call the publish() method, which takes the following parameters:

PublishConfig specifies the name of the service and other configuration properties, such as match filter.

specifies the name of the service and other configuration properties, such as match filter. DiscoverySessionCallback specifies the actions to execute when events occur, such as when the subscriber receives a message.

Here's an example:

Kotlin val config: PublishConfig = PublishConfig.Builder() .setServiceName(AWARE_FILE_SHARE_SERVICE_NAME) .build() awareSession.publish(config, object : DiscoverySessionCallback() { override fun onPublishStarted(session: PublishDiscoverySession) { ... } override fun onMessageReceived(peerHandle: PeerHandle, message: ByteArray) { ... } }) Java PublishConfig config = new PublishConfig.Builder() .setServiceName(“Aware_File_Share_Service_Name”) .build(); awareSession.publish(config, new DiscoverySessionCallback() { @Override public void onPublishStarted(PublishDiscoverySession session) { ... } @Override public void onMessageReceived(PeerHandle peerHandle, byte[] message) { ... } }, null);

If publication succeeds, then the onPublishStarted() callback method is called.

After publication, when devices running matching subscriber apps move into the Wi-Fi range of the publishing device, the subscribers discover the service. When a subscriber discovers a publisher, the publisher does not receive a notification; if the subscriber sends a message to the publisher, however, then the publisher receives a notification. When that happens, the onMessageReceived() callback method is called. You can use the PeerHandle argument from this method to send a message back to the subscriber or create a connection to it.

To stop publishing the service, call DiscoverySession.close() . Discovery sessions are associated with their parent WifiAwareSession . If the parent session is closed, its associated discovery sessions are also closed. While discarded objects are closed as well, the system doesn't guarantee when out-of-scope sessions are closed, so we recommend that you explicitly call the close() methods.

To subscribe to a service, call the subscribe() method, which takes the following parameters:

SubscribeConfig specifies the name of the service to subscribe to and other configuration properties, such as match filter.

specifies the name of the service to subscribe to and other configuration properties, such as match filter. DiscoverySessionCallback specifies the actions to execute when events occur, such as when a publisher is discovered.

Here's an example:

Kotlin val config: SubscribeConfig = SubscribeConfig.Builder() .setServiceName(AWARE_FILE_SHARE_SERVICE_NAME) .build() awareSession.subscribe(config, object : DiscoverySessionCallback() { override fun onSubscribeStarted(session: SubscribeDiscoverySession) { ... } override fun onServiceDiscovered( peerHandle: PeerHandle, serviceSpecificInfo: ByteArray, matchFilter: List<ByteArray> ) { ... } }, null) Java SubscribeConfig config = new SubscribeConfig.Builder() .setServiceName("Aware_File_Share_Service_Name") .build(); awareSession.subscribe(config, new DiscoverySessionCallback() { @Override public void onSubscribeStarted(SubscribeDiscoverySession session) { ... } @Override public void onServiceDiscovered(PeerHandle peerHandle, byte[] serviceSpecificInfo, List<byte[]> matchFilter) { ... } }, null);

If the subscribe operation succeeds, the system calls the onSubscribeStarted() callback in your app. Because you can use the SubscribeDiscoverySession argument in the callback to communicate with a publisher after your app has discovered one, you should save this reference. You can update the subscribe session at any time by calling updateSubscribe() on the discovery session.

At this point, your subscription waits for matching publishers to come into Wi-Fi range. When this happens, the system executes the onServiceDiscovered() callback method. You can use the PeerHandle argument from this callback to send a message or create a connection to that publisher.

To stop subscribing to a service, call DiscoverySession.close() . Discovery sessions are associated with their parent WifiAwareSession . If the parent session is closed, its associated discovery sessions are also closed. While discarded objects are closed as well, the system doesn't guarantee when out-of-scope sessions are closed, so we recommend that you explicitly call the close() methods.

Send a message

To send a message to another device, you need the following objects:

A DiscoverySession . This object allows you to call sendMessage() . Your app gets a DiscoverySession by either publishing a service or subscribing to a service.

The other device's PeerHandle , to route the message. Your app gets another device's PeerHandle in one of two ways: Your app publishes a service and receives a message from a subscriber. Your app gets the subscriber's PeerHandle from the onMessageReceived() callback. Your app subscribes to a service. Then, when it discovers a matching publisher, your app gets the publisher's PeerHandle from the onServiceDiscovered() callback.



To send a message, call sendMessage() . The following callbacks might then occur:

When the message is successfully received by the peer, the system calls the onMessageSendSucceeded() callback in the sending app.

callback in the sending app. When the peer receives a message, the system calls the onMessageReceived() callback in the receiving app.

Note: getMaxServiceSpecificInfoLength() . For high speed, bi-directional communication, your app should Messages are generally used for lightweight messaging, as they might not be delivered (or be delivered out-of-order or more than once) and are limited to about 255 bytes in length. To determine the exact length limit, call. For high speed, bi-directional communication, your app should create a connection instead.

Though the PeerHandle is required to communicate with peers, you should not rely on it as a permanent identifier of peers. Higher-level identifiers can be used by the application--embedded in the discovery service itself or in subsequent messages. You can embed an identifier in the discovery service with the setMatchFilter() or setServiceSpecificInfo() method of PublishConfig or SubscribeConfig . The setMatchFilter() method affects discovery, whereas the setServiceSpecificInfo() method does not affect discovery.

Embedding an identifier in a message implies modifying the message byte array to include an identifier (for example, as the first couple of bytes).

Create a connection

Wi-Fi Aware supports client-server networking between two Wi-Fi Aware devices.

To set up the client-server connection:

Use Wi-Fi Aware discovery to publish a service (on the server) and subscribe to a service (on the client). Once the subscriber discovers the publisher, send a message from the subscriber to the publisher. Start a ServerSocket on the publisher device and either set or obtain its port: Kotlin val ss = ServerSocket(0) val port = ss.localPort Java ServerSocket ss = new ServerSocket(0); int port = ss.getLocalPort(); Use the ConnectivityManager to request a Wi-Fi Aware network on the publisher using a WifiAwareNetworkSpecifier , specifying the discovery session and the PeerHandle of the subscriber, which you obtained from the message transmitted by the subscriber: Kotlin val networkSpecifier = WifiAwareNetworkSpecifier.Builder(discoverySession, peerHandle) .setPskPassphrase("somePassword") .setPort(port) .build() val myNetworkRequest = NetworkRequest.Builder() .addTransportType(NetworkCapabilities.TRANSPORT_WIFI_AWARE) .setNetworkSpecifier(networkSpecifier) .build() val callback = object : ConnectivityManager.NetworkCallback() { override fun onAvailable(network: Network) { ... } override fun onCapabilitiesChanged(network: Network, networkCapabilities: NetworkCapabilities) { ... } override fun onLost(network: Network) { ... } } connMgr.requestNetwork(networkRequest, callback); Java NetworkSpecifier networkSpecifier = new WifiAwareNetworkSpecifier.Builder(discoverySession, peerHandle) .setPskPassphrase("somePassword") .setPort(port) .build(); NetworkRequest myNetworkRequest = new NetworkRequest.Builder() .addTransportType(NetworkCapabilities.TRANSPORT_WIFI_AWARE) .setNetworkSpecifier(networkSpecifier) .build(); ConnectivityManager.NetworkCallback callback = new ConnectivityManager.NetworkCallback() { @Override public void onAvailable(Network network) { ... } @Override public void onCapabilitiesChanged(Network network, NetworkCapabilities networkCapabilities) { ... } @Override public void onLost(Network network) { ... } }; ConnectivityManager connMgr.requestNetwork(networkRequest, callback); Request a Wi-Fi Aware network on the subscriber using the same method as on the publisher. Do not specify a port when creating the NetworkSpecifier . The appropriate callback methods are called when the network connection is available, changed, or lost. Once the onAvailable() method is called on the subscriber, a Network object is available with which you can open a Socket to communicate with the ServerSocket on the publisher, but you need to know the ServerSocket ’s IPv6 address and port. You get these from the NetworkCapabilities object provided in the onCapabilitiesChanged() callback: Kotlin val peerAwareInfo = networkCapabilities.transportInfo as WifiAwareNetworkInfo val peerIpv6 = peerAwareInfo.peerIpv6Addr val peerPort = peerAwareInfo.port ... val socket = network.getSocketFactory().createSocket(peerIpv6, peerPort) Java WifiAwareNetworkInfo peerAwareInfo = (WifiAwareNetworkInfo) networkCapabilities.getTransportInfo(); Inet6Address peerIpv6 = peerAwareInfo.getPeerIpv6Addr(); int peerPort = peerAwareInfo.getPort(); ... Socket socket = network.getSocketFactory().createSocket(peerIpv6, peerPort); When you're finished with the network connection, call unregisterNetworkCallback() . Note: Building a network request and specifying the required network capabilities aren't specific to the Wi-Fi Aware API. For more information on working with network requests, see ConnectivityManager

Ranging peers and location-aware discovery

A device with Wi-Fi RTT location capabilities can directly measure distance to peers and use this information to constrain Wi-Fi Aware service discovery.

The Wi-Fi RTT API allows direct ranging to a Wi-Fi Aware peer using either its MAC address or its PeerHandle.

Wi-Fi Aware discovery can be constrained to only discover services within a particular geofence. For example, you can set up a geofence that allows discovery of a device publishing an "Aware_File_Share_Service_Name" service that is no closer than 3 meters (specified as 3,000 mm) and no further than 10 meters (specified as 10,000 mm).

To enable geofencing, the publisher and the subscriber both must take action:

The publisher must enable ranging on the published service using setRangingEnabled(true). If the publisher doesn’t enable ranging, then any geofence constraints specified by the subscriber are ignored and normal discovery is performed, ignoring distance.

The subscriber must specify a geofence using some combination of setMinDistanceMm and setMaxDistanceMm. For either value, an unspecified distance implies no limit. Only specifying the maximum distance implies a minimum distance of 0. Only specifying the minimum distance implies no maximum.

When a peer service is discovered within a geofence, the onServiceDiscoveredWithinRange callback is triggered, which provides the measured distance to the peer. The direct Wi-Fi RTT API can then be called as necessary to measure distance at later times.