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),...
android,android-intent,nfc,ndef,android-beam
The reason why you get an intent chooser is that multiple activities are registered for the data type text/plain. This is a rather common case and you should therefore avoid using such generic data types for the NDEF record that should launch your activity. You have two options to overcome...
android,nfc,android-4.4-kitkat,android-beam,hce
First of all (though this does not directly answer your question), the preferred way to transfer a URL between two Android NFC device is to use Android Beam (peer-to-peer mode). Android HCE (Host Card Emulation) is typically intended for emulation of contactless smartcard applications other than NFC tags. Do I...
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...
android,json,nfc,android-json,android-beam
Any ideas why? Android Beam uses the file extension of the first file in the Beam Uris array to look up a corresponding MIME type in an internal map, which is then sent with the Intent that initiates the file transfer via Bluetooth Object Push Profile (OPP). If the...
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)....