Depending on what NFC devices you want to use in combination with the ACR122U NFC reader you multiple options: If you only need to exchange a single message (data packet) in a single direction, you could use peer-to-peer mode. However, the peer-to-peer protocol stack is relatively complex (in comparison to...
android,nfc,nfc-p2p,android-beam
If you do not set up Android Beam in your app, Android's default behavior upon beaming is to instruct the other device to either open that same app (first activity that filters for MAIN/LAUNCHER intents of an app with the same package name as the app on the source device),...
By default, an Android device will cyclically check if there is another peer-to-peer device, an NFC tag (or actually any contactless transponder with a supported protocol) or another ISO 14443 reader (this will typically only be available on some 4.4 devices and on devices with activated secure element) available. So,...
android,nfc,intentfilter,ndef,nfc-p2p
You are sending a MIME type record of type "application/com.devcompany.paymentvendor.fragments": NdefMessage message = new NdefMessage(new NdefRecord[] { NdefRecord.createMime("application/com.devcompany.paymentvendor.fragments", mToBeam.getBytes()) }); Consequently, you also need to instruct your receiving activity to actually receive that MIME type record. You can register your app to open (and receive) upon detection of that MIME...
android,nfc,ndef,nfc-p2p,android-applicationrecord
If you use an Android Application Record (AAR) and do not specify an NDEF_DISCOVERED intent filter in your app's manifest, Android won't know that you app can handle an NFC intent upon launching. Consequently, it will open the first activity from your manifest that declares a MAIN intent filter with...
android,nfc,android-5.0-lollipop,nfc-p2p,android-screen-pinning
I'm not sure if this actually answers your question, but I'd like to summarize my findings: When trying your example on Android 5.0.1 (LRX22C on Nexus 4), the receiving side automatically unpins the screen upon receiving the NDEF message and (re-)starts the activity. So it seems that the intent filter...
android,raspberry-pi,nfc,nfc-p2p
The peer-to-peer examples that you are using are transmitting data at the NFCIP-1 (NFC-DEP) layer. An Android device supports only exchange of NDEF messages through SNEP/NPP, so you would need to implement the missing layers between NFC-DEP and SNEP in order to get P2P communication with an Android device running....
What is the best way to pass a unique identifier from the NFC reader (ACR122U) to an Android device? That depends on what you want to achieve. Using the ACR122U in reader/writer mode will basically limit you to using Android 4.4 and later (as Android HCE -- for putting the...
It looks like you could just call setIntent() at the end of onNewIntent() with a new Intent that has an Action value that will not trigger further processing. Here is an example, where the new Intent for the Activity is set with an Action of "do_nothing": @Override protected void onNewIntent(Intent...
When you want to specifically use NFC peer-to-peer mode, then the same answers are valid today: Android only supports Android Beam for P2P communication. Hence, you can, in general, only transmit one message into one direction and you need to tap the Beam UI each time you want to send...
android,nfc,nfc-p2p,android-beam
If one of your device have Android KitKat (4.4), there's a new feature in this version: https://developer.android.com/guide/topics/connectivity/nfc/hce.html You could put one device in reader mode (default mode) and one device in card mode (card emulation)....
android,android-intent,nfc,nfc-p2p,android-beam
Android's MIME type matching for intent filters is case-sensitive (eventhough the MIME types themselves are not). Therefore, with Android (and also pretty much everywhere you use them) you should stick to the convention to use MIME types with lowercase letters only. Specifically with MIME type records received over NFC, Android...