wifi-direct

Wifi P2P service discovery is not behaving as expected. I am seeing intermittent issues where the DNSSD listeners are not called always and hence I have no clue of nearby devices running the same app. I am using the following two APIs - one to register a service to be discovered by other devices and the other to discover the nearby services running on other devices. Any idea if I am doing anything wrong here or is there some specific sequence of other android API calls that need to be made before I call these APIs to ensure that the listeners are always called whenever there is a new service

I have 2 Android devices using WiFi Direct. On one device I can get information about the other device using the WifiP2pManager class, and request a connection to the other device. However when I request a connection, the other device pops up a little window and asks the user if they want to accept the connection request. Is it possible to auto-accept these connection requests? I.E to be able to connect to the other device without user confirmation? Based on the comments, do you really need to connect to the devices if you just want to track and log the vehicles around you ? I don't know the

I've been looking at iOS 7's new P2P networking framework, MultipeerConnectivity , and from the description, it seems to me that it uses a combination of some kind of Wi-Fi Direct technology and Bluetooth PANs. Is the Wi-Fi Direct technology in this framework compatible with Android's Wi-Fi Direct? Can this framework actually be used for cross-platform P2P networking? The device is not found by either when advertising or browsing with MultipeerConnectivity. Tried on Galaxy Tab 2: barbazoo This is what we know: There's no BTLE/Bluetooth 4.0 advertisement visible on my Texas Instruments

I am developing an Android application based on the use of Wifi Direct API. I have registered in my Activity a BroadcastReceiver in order to be notified about the following Wifi Direct events: WifiP2pManager.WIFI_P2P_STATE_CHANGED_ACTION WifiP2pManager.WIFI_P2P_PEERS_CHANGED_ACTION WifiP2pManager.WIFI_P2P_CONNECTION_CHANGED_ACTION WifiP2pManager.WIFI_P2P_THIS_DEVICE_CHANGED_ACTION I believed that any change in the list of peers (the inclusion or exclusion of a peer in the Wifi Direct range) could trigger the BroadcastReceiver . In my app, when a new peer is found, its name is correctly

Like here: Automatic authentication for Android WiFi Direct I want to create a mobile ad-hoc Wifi network with Android devices. But unlike the linked question above I want to use the official Android WiFi Direct API which is availabe since Android 4.0. So is there a way to not only connect 2 devices via WiFi Direct but also three or more? So messages could be passed from one device to another using several other devices in between (therefore spanning a larger distance between the sender and receiver)? The Wifi Direct demo only works for pairing two devices and I could not find a way to do

When creating a group via Wi-Fi Direct, I know that I can make a persistent group. My question is: can I create a persistent group, but each time change the group owner (i.e; each turn the group owner will be one of the devices in the group). Also, when creating a persistent group, it is required to accept the connection only the first time, right? Bill G You can now create a new persistent group via WifiP2pManager.createGroup(..) . It will create a new group and make the calling device (A) group owner and can do what you described. The only problem is once you create a group and connect to

Starting from ICS, Wi-Fi Direct is introduced. Normally, we use the WifiP2pManager class to operate on Wi-Fi Direct, but it seems that it can only retrieve the GroupOwner IP address after connected. But, actually, any device all came negotiate to become the GroupOwner. In Upper Application, we need to get the peer's IP address, or each peer's IP address in a group so that we can send/communicate with them. How to get each IP address in Wi-Fi Direct? Include own IP address and each peer in the group? I encountered the same problem. Since both devices know the group owner's ip, it is already