hce

问题 Mifare Classic is the most used cards and I can't understand why HCE (Host-based Card Emulation) only supports ISO 14443-4, but not Mifare Classic type. Because NXP stops them from using their proprietary protocols and algorithms? Or because they didn’t implement Mifare Classic in Android OS level? Any comments will be very appreciated. 回答1: Short answer: Because Google decided to support only ISO/IEC 7816-4 over ISO-DEP (ISO/IEC 14443-4). Speculations on why they decided that way: First of

问题 I have an Android app with a service registered to Android beam and a service registered to host card emulation. I want to decide when to enable/disable the HCE service in the code. The HCE service in the manifest looks like this - <service android:name="com.bimo.verifonewallet.service.MyHostApduService" android:exported="true" android:permission="android.permission.BIND_NFC_SERVICE" > <intent-filter> <action android:name="android.nfc.cardemulation.action.HOST_APDU_SERVICE" /> </intent-filter

问题 In order to help debug a HCE app I would like to make an Android phone act as a contactless terminal. Is this possible without rooting the phone and using NFCProxy? (http://sourceforge.net/projects/nfcproxy/) i.e. I have two phones and want to run my app on one while making the other act as a reader. 回答1: This is only possible if your reader Android device (the one that acts as contactless terminal) has Android 4.4 or later. The problem is that Android's HCE capabilities run in parallel with

问题 I want my android device to act as NFC tag. Is it possible to use NFC device as NFC tag? How can I achieve that? I have done read/write tag, beam data between devices. 回答1: Depending on your NFC device, this may be possible. However, I do not agree with kamituel that this is being done by multiple applications through Android Beam. Android Beam uses NFC's peer-to-peer mode which (while it may have a similar effect) is not the same as using one device as a reader ( reader/writer mode ) and one

问题 See NFC reader "SELECT (by AID)" APDU is not routed to Android device on debugging and eventual results. TL;DR the reader might simply be defunct. I have ACR122U nfc reader. I try to run this example http://www.nfc-tools.org/index.php?title=Libnfc:APDU_example#apdu_example.c on my Ubuntu machine. This is the log output I get when I tap my Android device (should be in HCE mode) to the reader: ./apdu_example debug libnfc.general log_level is set to 3 debug libnfc.general allow_autoscan is set

问题 I found two approaches to let an Android app detect and process NFC tags: NfcAdapter.enableReaderMode(activity, callback, flags, extras) and then receive the tag info in the callback. NfcAdapter.enableForegroundDispatch(activity, intent, filters, techLists) and then receive the tag info in the onNewIntent(intent) activity method. I currently use the second approach, however, I recently discovered the enableReaderMode approach and wonder if it's better to use that to process NFC tags. So what

问题 How can I get the NFC contactless reader ACR122U to behave as a tag (card emulation mode)? The prospectus claims that the device can do card emulation, but the SDK does not seem to provide an example or documentation for this feature. Does anybody know how to do this? Is there additional software required? Please note that my target platform is MS Windows. Thanks in advance 回答1: For "Card Emulation" or in other words, "Configure as target and wait for initiators", please refer to here: http:/

问题 How can I get the NFC contactless reader ACR122U to behave as a tag (card emulation mode)? The prospectus claims that the device can do card emulation, but the SDK does not seem to provide an example or documentation for this feature. Does anybody know how to do this? Is there additional software required? Please note that my target platform is MS Windows. Thanks in advance 回答1: For "Card Emulation" or in other words, "Configure as target and wait for initiators", please refer to here: http:/

问题 I wanna emulate a host card with the HCE feature from Android. For that I extend the service class HostApduService and overwrite following method: public byte[] processCommandApdu(byte[] commandApdu, Bundle extras) { if (Arrays.equals(SELECT_APDU, commandApdu)) { NdefMessage message = new NdefMessage(new NdefRecord [] {NdefRecord.createTextRecord("en", "test"}); return message.toByteArray(); } else { return UNKNOWN_CMD_SW; } } With a second device its possible to receive data from the HCE

问题 It is possible to know others NFC TAG ID when we used to the APK & TAG each phones. For example, Phone A and B try to tag. Then Phone A can know Phone B's NFC TAG ID (4 Bytes - HEX). But I wanna know how to know my NFC TAG ID on my phone. Not used other phones. If you know any other information, please give me your advice on that. 回答1: A phone does not necessarily have a fixed anti-collision identifier ("NFC Tag ID", as you call it). For instance, it could have an anti-collision identifier,