<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Hide NTAG216 information in NFC</title>
    <link>https://community.nxp.com/t5/NFC/Hide-NTAG216-information/m-p/621209#M1126</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Jimmy,&lt;/P&gt;&lt;P&gt;I'm not getting access to NXP docstore. Can I use your contact name on NXP registration form?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 17 Oct 2016 12:57:02 GMT</pubDate>
    <dc:creator>lucasmoretto</dc:creator>
    <dc:date>2016-10-17T12:57:02Z</dc:date>
    <item>
      <title>Hide NTAG216 information</title>
      <link>https://community.nxp.com/t5/NFC/Hide-NTAG216-information/m-p/621207#M1124</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have recently seen many NFC tags that are not detected in smartphones by applications such as TagInfo, NfcTools, etc. Generally, the tags are Mifare Classic type, where I imagine that some sectors have been modified or some password.&lt;/P&gt;&lt;P&gt;Thus, the tag means undetectable for smartphones.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have two questions about this practice:&lt;/P&gt;&lt;P&gt;1) In the case of these modified tags, to use them in android, is there any way to get an "intent" within the application? I mean take advantage of the resources offered by SDK android.&lt;/P&gt;&lt;P&gt;2) Is there any way to do this with tags type NTAG216?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm studing NTAG216 data sheet wanting to find a way of read/write lock.&lt;BR /&gt;I like to try the lock using a password (but i think that information of tag will be available for reading from another software).&lt;BR /&gt;I'm not sure about the differences betwen static and dynamic lock bytes too. Maybe, one of them is what i need.&lt;/P&gt;&lt;P&gt;In NTAG216 data sheet, section 8.5.3, it's quoted another document: "Ref. 9 “AN11456 NTAG215/216(F)/NTAG I2C Using the dynamic lock bits to lock the tag”. I couldn't find this document on web. &lt;BR /&gt;Someone has this document? I don't know if I can find this on NXP docstore (waiting for registration approval)&lt;/P&gt;&lt;P&gt;Thanks for attention&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 10 Oct 2016 12:24:48 GMT</pubDate>
      <guid>https://community.nxp.com/t5/NFC/Hide-NTAG216-information/m-p/621207#M1124</guid>
      <dc:creator>lucasmoretto</dc:creator>
      <dc:date>2016-10-10T12:24:48Z</dc:date>
    </item>
    <item>
      <title>Re: Hide NTAG216 information</title>
      <link>https://community.nxp.com/t5/NFC/Hide-NTAG216-information/m-p/621208#M1125</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;yes, this AN11456 is in the NXP docstore. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 14 Oct 2016 08:58:07 GMT</pubDate>
      <guid>https://community.nxp.com/t5/NFC/Hide-NTAG216-information/m-p/621208#M1125</guid>
      <dc:creator>jimmychan</dc:creator>
      <dc:date>2016-10-14T08:58:07Z</dc:date>
    </item>
    <item>
      <title>Re: Hide NTAG216 information</title>
      <link>https://community.nxp.com/t5/NFC/Hide-NTAG216-information/m-p/621209#M1126</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Jimmy,&lt;/P&gt;&lt;P&gt;I'm not getting access to NXP docstore. Can I use your contact name on NXP registration form?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 17 Oct 2016 12:57:02 GMT</pubDate>
      <guid>https://community.nxp.com/t5/NFC/Hide-NTAG216-information/m-p/621209#M1126</guid>
      <dc:creator>lucasmoretto</dc:creator>
      <dc:date>2016-10-17T12:57:02Z</dc:date>
    </item>
  </channel>
</rss>

