Cross Reference: /frameworks/base/core/java/android/nfc/NfcAdapter.java

Lines Matching refs:Ndef
33 import android.nfc.tech.Ndef;
57      * Intent to start an activity when a tag with NDEF payload is discovered.
67      * <p>If the tag has an NDEF payload this intent is started before
106      * {@link MifareClassic}, and {@link Ndef}:
117      *     &lt;!-- capture all MIFARE Classics with NDEF payloads --&gt;
121      *         &lt;tech&gt;android.nfc.tech.Ndef&lt;/tech&gt;
161      * {@link NdefMessage} element. Most NDEF tags have only one NDEF message,
255          * Called on successful NDEF push.
266      * A callback to be invoked when another NFC device capable of NDEF push (Android Beam)
283          * that might support NDEF push. It allows the application to
284          * create the NDEF message only when it is required.
286          * <p>NDEF push cannot occur until this method returns, so do not
291          * input from the user to complete the callback, or provide custom NDEF
295          * @return NDEF message to push, or null to not provide a message
728      * but the NDEF message is only made available for NDEF push when the
735      * <p>Only one NDEF message can be pushed by the currently resumed activity.
742      * the Android OS may choose to send a default NDEF message on your behalf,
745      * <p>If {@link #setNdefPushMessage} is called with a null NDEF message,
747      * then NDEF push will be completely disabled for the specified activity(s).
748      * This also disables any default NDEF message the Android OS would have
751      * <p>If you want to prevent the Android OS from sending default NDEF
772      * OS will automatically release its references to the NDEF message and the
775      * <p>If your Activity wants to dynamically generate an NDEF message,
789      * @param message NDEF message to push over NFC, or null to disable
790      * @param activity activity for which the NDEF message will be pushed
832      * Set a callback that dynamically generates NDEF messages to send using Android Beam (TM).
835      * but the NDEF message callback can only occur when the
842      * <p>Only one NDEF message can be pushed by the currently resumed activity.
849      * the Android OS may choose to send a default NDEF message on your behalf,
852      * <p>If {@link #setNdefPushMessage} is called with a null NDEF message,
854      * then NDEF push will be completely disabled for the specified activity(s).
855      * This also disables any default NDEF message the Android OS would have
858      * <p>If you want to prevent the Android OS from sending default NDEF
891      * @param activity activity for which the NDEF message will be pushed
965      * @param activity activity for which the NDEF message will be pushed
1091      * Enable NDEF message push over NFC while this Activity is in the foreground.
1101      * <p>For NDEF push to function properly the other NFC device must
1102      * support either NFC Forum's SNEP (Simple Ndef Exchange Protocol), or
1103      * Android's "com.android.npp" (Ndef Push Protocol). This was optional
1112      * @param message a NDEF Message to push over NFC
1126      * Disable NDEF message push over P2P.
1156      * Enable NDEF Push feature.
1170      * Disable NDEF Push feature.
1184      * Return true if the NDEF Push (Android Beam) feature is enabled.
1186      * NDEF Push feature is enabled.
1187      * <p>Note that if NFC is enabled but NDEF Push is disabled then this
1188      * device can still <i>receive</i> NDEF messages, it just cannot send them.
1189      * <p>Applications cannot directly toggle the NDEF Push feature, but they
1190      * can request Settings UI allowing the user to toggle NDEF Push using
1192      * <p>Example usage in an Activity that requires NDEF Push:
1204      * @return true if NDEF Push feature is enabled
OpenGrok
