<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html>
<html lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<!-- nfc-android.qdoc -->
<title>Qt NFC on Android | Qt NFC 5.12.6</title>
<link rel="stylesheet" type="text/css" href="style/offline-simple.css" />
<script type="text/javascript">
document.getElementsByTagName("link").item(0).setAttribute("href", "style/offline.css");
// loading style sheet breaks anchors that were jumped to before
// so force jumping to anchor again
setTimeout(function() {
var anchor = location.hash;
// need to jump to different anchor first (e.g. none)
location.hash = "#";
setTimeout(function() {
location.hash = anchor;
}, 0);
}, 0);
</script>
</head>
<body>
<div class="header" id="qtdocheader">
<div class="main">
<div class="main-rounded">
<div class="navigationbar">
<table><tr>
<td >Qt 5.12</td><td ><a href="qtnfc-index.html">Qt NFC</a></td><td >Qt NFC on Android</td></tr></table><table class="buildversion"><tr>
<td id="buildversion" width="100%" align="right"><a href="qtnfc-index.html">Qt 5.12.6 Reference Documentation</a></td>
</tr></table>
</div>
</div>
<div class="content">
<div class="line">
<div class="content mainContent">
<div class="sidebar">
<div class="toc">
<h3><a name="toc">Contents</a></h3>
<ul>
<li class="level1"><a href="#automatically-launching-ndef-message-handlers-on-android">Automatically launching NDEF message handlers on Android</a></li>
<li class="level2"><a href="#note">Note:</a></li>
</ul>
</div>
<div class="sidebar-content" id="sidebar-content"></div></div>
<h1 class="title">Qt NFC on Android</h1>
<span class="subtitle"></span>
<!-- $$$nfc-android.html-description -->
<div class="descr"> <a name="details"></a>
<a name="automatically-launching-ndef-message-handlers-on-android"></a>
<h2 id="automatically-launching-ndef-message-handlers-on-android">Automatically launching NDEF message handlers on Android</h2>
<p>Android, the registration of NDEF message handlers is done via the <a href="http://developer.android.com/guide/topics/manifest/manifest-intro.html">Android manifest file</a>. This means the application has to provide an AndroidManifest.xml file with proper <a href="http://developer.android.com/guide/topics/connectivity/nfc/nfc.html#manifest">NFC intent-filter.</a></p>
<pre class="cpp">
<span class="operator"><</span>intent<span class="operator">-</span>filter<span class="operator">></span>
<span class="operator"><</span>action android:name<span class="operator">=</span><span class="string">"android.nfc.action.NDEF_DISCOVERED"</span><span class="operator">/</span><span class="operator">></span>
<span class="operator"><</span>category android:name<span class="operator">=</span><span class="string">"android.intent.category.DEFAULT"</span><span class="operator">/</span><span class="operator">></span>
<span class="operator"><</span>data android:mimeType<span class="operator">=</span><span class="string">"text/plain"</span><span class="operator">/</span><span class="operator">></span>
<span class="operator"><</span><span class="operator">/</span>intent<span class="operator">-</span>filter<span class="operator">></span>
</pre>
<p>When the application is started it has to register an message handler with <a href="qnearfieldmanager.html#registerNdefMessageHandler">registerNdefMessageHandler()</a> The first NDEF message arriving in the handler is the message that started the application. See the <a href="qtnfc-corkboard-example.html">CorkBoard</a> application for an example.</p>
<a name="note"></a>
<h3 id="note">Note:</h3>
<p>Supported tag types in Android are <a href="http://developer.android.com/reference/android/nfc/NfcAdapter.html#ACTION_NDEF_DISCOVERED">NDEF_DISCOVERED</a> and <a href="http://developer.android.com/reference/android/nfc/NfcAdapter.html#ACTION_TECH_DISCOVERED">ACTION_TAG_DISCOVERED</a> with <a href="http://developer.android.com/reference/android/nfc/tech/TagTechnology.html">TagTechnology</a> NdefFormatable or Ndef. If the application register other types in the <a href="http://developer.android.com/guide/topics/manifest/manifest-intro.html">Android manifest file</a> the application will be started, but the tag will never get delivered to the handler. The handler should be registered as early as possible. If the application has not registered a handler, the application will be started every time a new tag is in range and the Android device end up running multiple instances of the application.</p>
</div>
<!-- @@@nfc-android.html -->
</div>
</div>
</div>
</div>
</div>
<div class="footer">
<p>
<acronym title="Copyright">©</acronym> 2019 The Qt Company Ltd.
Documentation contributions included herein are the copyrights of
their respective owners.<br/> The documentation provided herein is licensed under the terms of the <a href="http://www.gnu.org/licenses/fdl.html">GNU Free Documentation License version 1.3</a> as published by the Free Software Foundation.<br/> Qt and respective logos are trademarks of The Qt Company Ltd. in Finland and/or other countries worldwide. All other trademarks are property
of their respective owners. </p>
</div>
</body>
</html>
