Post

Replies

Boosts

Views

Activity

Reply to During the Wi-Fi Aware's pairing process, Apple is unable to recognize the follow-up PMF sent by Android.
Hi sengui, thanks for sharing these detailed Android/iOS Wi-Fi Aware interoperability results. I’m currently working on an Android/iOS Wi-Fi Aware interoperability PoC for a peer-to-peer app and am trying to identify a reproducible Android stack that supports NAN Pairing/PASN. I saw your explanation of the Android pairing flow already. Would you be able to share some details about the Android device you used? manufacturer and exact model/model number; Android version and build fingerprint; stock retail firmware or engineering/custom build; result of Characteristics.isAwarePairingSupported(); result of getSupportedPairingCipherSuites(); bootstrapping method and pairing cipher used; whether any vendor patches, privileged APIs, root access, or non-retail firmware were required. Also, did you later manage to progress from successful pairing verification to a usable NDP and actual TCP/UDP traffic? Even just the exact device/build and the two Android capability results would be extremely helpful. Thank you!
Aug ’26
Reply to Bug: Wi-Fi Aware (NAN) Subscriber Mode: nwPath.availableInterfaces Does Not Include nan0 Interface After Successful Peer Connection
Hi wu_aaron, thanks for sharing this result. A successful iOS ↔ non-iOS Wi-Fi Aware connection with actual TCP traffic is particularly useful to me. I’m working on an Android/iOS peer-to-peer app, and I’m currently trying to identify a reproducible non-iOS stack for a real app-to-app interoperability PoC. Would you be able to share some details about the non-iOS device you used? manufacturer and exact device/model number; Android version and build fingerprint, if applicable; stock retail firmware or engineering/custom build; result of Characteristics.isAwarePairingSupported(); result of getSupportedPairingCipherSuites(); bootstrapping method and pairing cipher used; publisher/subscriber roles and which side initiated pairing; whether any vendor patches, privileged APIs, root access, or non-retail firmware were required. If you reproduced the result on more than one device or firmware build, that would also be very useful to know. Even just the exact device/build and the two Android capability results would help me a lot. Thank you!
Aug ’26
Reply to During the Wi-Fi Aware's pairing process, Apple is unable to recognize the follow-up PMF sent by Android.
Hi sengui, thanks for sharing these detailed Android/iOS Wi-Fi Aware interoperability results. I’m currently working on an Android/iOS Wi-Fi Aware interoperability PoC for a peer-to-peer app and am trying to identify a reproducible Android stack that supports NAN Pairing/PASN. I saw your explanation of the Android pairing flow already. Would you be able to share some details about the Android device you used? manufacturer and exact model/model number; Android version and build fingerprint; stock retail firmware or engineering/custom build; result of Characteristics.isAwarePairingSupported(); result of getSupportedPairingCipherSuites(); bootstrapping method and pairing cipher used; whether any vendor patches, privileged APIs, root access, or non-retail firmware were required. Also, did you later manage to progress from successful pairing verification to a usable NDP and actual TCP/UDP traffic? Even just the exact device/build and the two Android capability results would be extremely helpful. Thank you!
Replies
Boosts
Views
Activity
Aug ’26
Reply to Bug: Wi-Fi Aware (NAN) Subscriber Mode: nwPath.availableInterfaces Does Not Include nan0 Interface After Successful Peer Connection
Hi wu_aaron, thanks for sharing this result. A successful iOS ↔ non-iOS Wi-Fi Aware connection with actual TCP traffic is particularly useful to me. I’m working on an Android/iOS peer-to-peer app, and I’m currently trying to identify a reproducible non-iOS stack for a real app-to-app interoperability PoC. Would you be able to share some details about the non-iOS device you used? manufacturer and exact device/model number; Android version and build fingerprint, if applicable; stock retail firmware or engineering/custom build; result of Characteristics.isAwarePairingSupported(); result of getSupportedPairingCipherSuites(); bootstrapping method and pairing cipher used; publisher/subscriber roles and which side initiated pairing; whether any vendor patches, privileged APIs, root access, or non-retail firmware were required. If you reproduced the result on more than one device or firmware build, that would also be very useful to know. Even just the exact device/build and the two Android capability results would help me a lot. Thank you!
Replies
Boosts
Views
Activity
Aug ’26