<p>After reading the message from the remote device, check its number of records using the <span style="font-family: Courier New,Courier,monospace;">nfc_ndef_message_get_record_count()</span> function and get more detailed info about the message by calling the <span style="font-family: Courier New,Courier,monospace;">nfc_ndef_message_read_cb()</span> function described earlier.</p>
-<p>While having some other device connected through NFC, hand over the connection to some alternative carrier (AC), such as Bluetooth, Wi-Fi, or Wi-Fi Direct™.</p>
-
-<p>Firstly, call the <span style="font-family: Courier New,Courier,monospace;">nfc_p2p_is_supported_ac_type()</span> function to find out which alternative carriers are supported by the device.</p>
-<pre class="prettyprint">nfc_ac_type_e ac = NFC_AC_TYPE_BT;
-
-while(NFC_AC_TYPE_UNKNOWN != ac)
-{
- if (nfc_p2p_is_supported_ac_type(ac)) break;
- ac++;
-}</pre>
-
-<p>Iterate through the known AC types and break the iteration after finding the first one that is supported. The supported AC type is stored in the <span style="font-family: Courier New,Courier,monospace;">ac</span> variable.</p>
-<p>Now, make the connection handover by calling the <span style="font-family: Courier New,Courier,monospace;">nfc_p2p_connection_handover()</span> function.</p>
-<pre class="prettyprint">if (NFC_AC_TYPE_UNKNOWN != ac)
- nfc_p2p_connection_handover(target, ac, on_nfc_p2p_connection_handover_completed, NULL);</pre>
-<p>The parameters are:</p>
-<ul><li>Handle to the remote device</li>
-<li>Preferred alternative carrier</li>
-<li>Callback function to invoke after this function has completed
-<p>It can be null if notification is not required.</p></li>
-<li>User data to be passed to the callback function</li></ul>
-
-<p>The <span style="font-family: Courier New,Courier,monospace;">on_nfc_p2p_connection_handover_completed()</span> callback in this tutorial only prints the alternative carrier data if no error occurs during the handover.</p>
-<pre class="prettyprint">static void on_nfc_p2p_connection_handover_completed(int error_code, nfc_ac_type_e carrier, void * ac_data, int ac_data_size, void *user_data)
-{
- if (!found_error(NFC_ERROR_NONE, "on_nfc_p2p_connection_handover_completed", error_code))
- {
- char *_data = (char *) malloc(sizeof(char) * (ac_data_size + 1));
- strncpy(_data, (char *)ac_data, ac_data_size);
- _data[ac_data_size] = '\0';
- dlog_print(DLOG_INFO, LOG_TAG, "AC: %s", _data);
- free(_data);
- }
-}</pre>
-
<h4>Working with NFC Secure Element</h4>
<p>The secure element event notification is received through the <span style="font-family: Courier New,Courier,monospace;">on_nfc_se_event()</span> function. The first parameter defines the event type. The second one is user data - in this case it is not used. Depending on the event type, you can take some additional actions.</p>
</li>
<li>Send a message to another device.
-<p>When another P2P device is attached, send the prepared message to it. You can use the <span style="font-family: Courier New,Courier,monospace">nfc_p2p_send()</span> or <span style="font-family: Courier New,Courier,monospace">nfc_p2p_send_no_permission()</span> function if you do not want to check permissions. Provide a target handle and a sent message handle. You can also set a callback called when the sending is completed.</p>
+<p>When another P2P device is attached, send the prepared message to it. You can use the <span style="font-family: Courier New,Courier,monospace">nfc_p2p_send()</span> function if you do not want to check permissions. Provide a target handle and a sent message handle. You can also set a callback called when the sending is completed.</p>
<pre class="prettyprint">nfc_p2p_send(target, ndef_message, NULL, NULL);</pre></li>
<li id="receive" name="receive">Receive a message from another device.
</script>
</body>
-</html>
\ No newline at end of file
+</html>