I am trying to implement an Android-Beam-like behavior between an Android smartphone and a Linux host. The Android smartphone (Galaxy Note 3, Android 4.4.2) deals with the NFC Dongle connected to the Linux host and the data exchange with the Bluetooth carrier via NFC, so it can connect to the Bluetooth Dongle also connected to the Linux host.
Now the problem is that the Android smartphone always asks the user (me) if I really want to connect to the Bluetooth Dongle. In Android Beam, between the two Android mobile phones this confirmation of the user is not displayed, the user only needs to click on the content (for example, the image) to send it (and this is the behavior I'm trying to get to). I use “nfctool” to sniff the incoming “Confirmation Request” message with my Android mobile phone (see http://pastebin.com/Dr0D0nqn ). According to the "Bluetooth Secure Simple Pairing Using NFC" document from the NFC Forum (see http://members.nfc-forum.org/resources/AppDocs/NFCForum_AD_BTSSP_1_0.pdf, p. 19), this handshake request should contain a Simple Pairing Hash and a simple pairing randomizer, both of which are missing from the Android Handshake request.
So my questions are:
- First of all, is it Android Beam using Secure Simple Pairing with OOB in general or some other mechanism? Why does Android Beam work between two Android devices without pairing confirmation?
- If SSP is used, why are SSP Hash and Randomizer missing from the HR message? Could this be the reason why my connection requires user confirmation?
- If Android uses a different mechanism, what do HR messages look like? Do they use a special type name (other than the /vnd.bluetooth.ep.oob application) or anything else in their Confirmation Statement that bypasses the BT user connection confirmation?
- - ( ) Android Beam? NFC Android (http://developer.android.com/guide/topics/connectivity/nfc/nfc.html) Android Beam.
:)