Android.Nfc.Tech.ITagTechnology is an interface to a technology in a Android.Nfc.Tag.

Obtain a Android.Nfc.Tech.ITagTechnology implementation by calling the static method get() on the implementation class.

NFC tags are based on a number of independently developed technologies and offer a wide range of capabilities. The Android.Nfc.Tech.ITagTechnology implementations provide access to these different technologies and capabilities. Some sub-classes map to technology specification (for example Android.Nfc.Tech.NfcA, Android.Nfc.Tech.IsoDep, others map to pseudo-technologies or capabilities (for example Android.Nfc.Tech.Ndef, Android.Nfc.Tech.NdefFormatable).

It is mandatory for all Android NFC devices to provide the following Android.Nfc.Tech.ITagTechnology implementations.

• Android.Nfc.Tech.NfcA (also known as ISO 14443-3A)
• Android.Nfc.Tech.NfcB (also known as ISO 14443-3B)
• Android.Nfc.Tech.NfcF (also known as JIS 6319-4)
• Android.Nfc.Tech.NfcV (also known as ISO 15693)
• Android.Nfc.Tech.IsoDep
• Android.Nfc.Tech.Ndef on NFC Forum Type 1, Type 2, Type 3 or Type 4 compliant tags

It is optional for Android NFC devices to provide the following Android.Nfc.Tech.ITagTechnology implementations. If it is not provided, the Android device will never enumerate that class via Android.Nfc.Tag.GetTechList.

• Android.Nfc.Tech.MifareClassic
• Android.Nfc.Tech.MifareUltralight
• Android.Nfc.Tech.NfcBarcode
• Android.Nfc.Tech.NdefFormatable must only be enumerated on tags for which this Android device is capable of formatting. Proprietary knowledge is often required to format a tag to make it NDEF compatible.

Android.Nfc.Tech.ITagTechnology implementations provide methods that fall into two classes: cached getters and I/O operations.

Cached getters

These methods (usually prefixed by get or is) return properties of the tag, as determined at discovery time. These methods will never block or cause RF activity, and do not require ITagTechnology.Connect to have been called. They also never update, for example if a property is changed by an I/O operation with a tag then the cached getter will still return the result from tag discovery time.

I/O operations

I/O operations may require RF activity, and may block. They have the following semantics.

• ITagTechnology.Connect must be called before using any other I/O operation.
• ITagTechnology.Close must be called after completing I/O operations with a Android.Nfc.Tech.ITagTechnology, and it will cancel all other blocked I/O operations on other threads (including ITagTechnology.Connect with Java.IO.IOException.
• Only one Android.Nfc.Tech.ITagTechnology can be connected at a time. Other calls to ITagTechnology.Connect will return Java.IO.IOException.
• I/O operations may block, and should never be called on the main application thread.

Note: Methods that perform I/O operations require the NoType:android/Manifest$permission;Href=../../../../reference/android/Manifest.permission.html#NFC permission.

[Android Documentation]

Namespace: Android.Nfc.Tech
Assembly: Mono.Android (in Mono.Android.dll)
Assembly Versions: 0.0.0.0
Since: Added in API level 10