Android nfcA.connect(), nfcA.transceive(), nfcA.setTimeout() and nfcA.getMaxTransceiveLength()
<p>I have a a number of newbie NfcA questions. There seems to be little guidance on this in the <a href="https://developer.android.com/reference/android/nfc/tech/NfcA.html" rel="noreferrer">docs</a> and elsewhere on the web, so I hope no-one minds me stringing a few basic questions together here...</p>

<p>I am using nfcA.transceive() to <em>write</em> data to my NTAG213 tag like this:</p>

<pre><code>    byte[] result = nfcA.transceive(new byte[] {
            (byte)0xA2,  // WRITE
            (byte)(pageNum &amp; 0x0ff),
            myData[0], myData[1], myData[2], myData[3]
    });
</code></pre>

<p><strong>1.</strong> The <code>result</code> array is a single byte of value 10. What does this mean and what other values should I look out for?</p>

<p>I am also using the same method to <em>read</em> data from my NTAG213 tags:</p>

<pre><code>    byte[] result = nfcA.transceive(new byte[] {
            (byte)0x30,  // READ
            (byte)(pageNum &amp; 0x0ff)
    });
</code></pre>

<p><strong>2.</strong> I expected this to return 4 bytes of user data (i.e., the 4 bytes that correspond to my pageNum), but it returned 16 bytes. Why is that the case?</p>

<p><strong>3.</strong> Is it good practise to check <code>nfcA.isConnected()</code> before calling <code>nfcA.connect()</code> and, if so, is there likely to be any sigificant performance penalty in doing so? (I ask as I have seen code examples from reputable sources of both.)</p>

<p><strong>4.</strong> Is it better to call <code>nfcA.setTimeout()</code> before or after <code>nfcA.connect()</code>?</p>

<p><strong>5.</strong> For my NTAG213 tags <code>nfcA.getMaxTransceiveLength()</code> returns 253. Does that really mean I can write up to 251 bytes of user data (plus the 2 other bytes) in one go and, if so, is that advisable or is it better to write each page (4 bytes) with separate <code>nfcA.transceive()</code> calls?</p>