Hello, I am analyzing the Power Save algorithm used on a pair of Nexus 5 devices. The devices use the bcmdhd Broadcom driver and are Wi-Fi Direct connected. My test is very simple: I send ping packets from the P2P client towards the P2P GO. Before sending a ping packet the P2P client enters PS mode (it sends a Null frame with the PWR MGT bit set). A few miliseconds later, the P2P client sends the ping request message. Once the ping request is ACKed the P2P client exits the PS mode (it sends a Null frame with the PWR MGT bit unset) and the P2P GO decides to send him the ping reply. What is the decision triggering the exit from the PS mode immediately after the ping request? I am asking this because 802.11 PS legacy specifies that the client should wait for a beacon with TIM set in order to wake up: in my case, there is no beacon between the ping request message and the Null frame that announces the exit from the PS mode. For reference, the Wireshark trace can be found at [1]. SSID: DIRECT-35-Android_Intel WPA pass: JYdrhZp3 [1] https://drive.google.com/file/d/0B5SBH08PU_ChQk95LWpzekh3VU0/view?usp=sharing Thank you, Doru
