hce

问题 I have a HCE service which sends data to and from a NFC reader but I was wondering if I can specify the launch settings of my service. I want to specify that my service can only be called if the app is running. If the app is closed the service shouldn't be called. Is this possible or was it intended that the service can always be called? 回答1: Currently you can only specify if the HCE service should be considered for card emulation from the lock-screen or only if the user passed the lock

问题 The Android's developer guide states that "Support for Nfc-B is optional". I cannot find any more information about Type B HCE. So is it possible to enable Type B support on Android devices? 回答1: From an app developer perspective you should(*) not really care which underlying protocol is used. The application layer protocol (ISO/IEC 7816-4) is the same for ISO/IEC 14443 Type A and Type B. Looking at devices in the field, some devices use Type A for HCE and some seem to use Type B. So it's

问题 I want to exchange (or only read) the NFC tag ID from one Android device to another but I don't know if I should use peer-to-peer mode or emulate an NFC tag with HCE. If I use HCE, is the emulated tag ID unique? What is the better option or is there a simpler one? 回答1: Neither P2P nor HCE will provide you a unique ID, least not on any phone I'm aware of. With P2P it's required that the ID exchanged in ATR is random. With HCE the emulated tag ID is usually set to 08h plus a random number.

问题 I understand from the official android web site https://developer.android.com/about/versions/kitkat.html which says that " Android 4.4 introduces new platform support for secure NFC-based transactions through Host Card Emulation (HCE), for payments,... " that we can not use HCE in the devices lower than Android Kit-Kat 4.4.x. But I want to ask if we can download an Android application which uses/contains HCE and its related classes on the device which has a version that lower than Android Kit

问题 I have my own Android app (App A) which reads and writes NFC tags and ISO-14443 Type A tags. It works well on many Android devices. I want to give the role of ISO-14443 tag to my Nexus5, so I implemented my own HCE (Host Card Emulation) application (App B) on my Nexus5. When I touch the Nexus5 on an external NFC reader (which uses ISO 14443), it works perfectly. However, when I touch the Nexus5 (App B) on a Nexus7 (running App A), p2p (Android beam) data exchanging sequences start. Even after

问题 I am currently attempting to connect between an Arduino UNO with NFC Shield to my Nexus 4 running Android 4.4. I have the service setup, it's simply logging at the moment. Problem is, the NFC intent doesn't get bound to my app. The debugger reports the following error: 11-24 02:45:46.139 4006-4027/? E/BrcmNfcNfa﹕ UICC[0x0] is not activated So here's my 2 questions: On the Arduino side of things, what kind of 'message' does the NFC shield needs to send to my phone for my phone to understand

问题 I am gonna write a Payment Application based on Host-Based Card Emulation(HCE) of Android 4.4 (Kitkat) but I don't understand a process between AID (Application ID) and HCE service of Android 4.4 after I read this article Host-based Card Emulation. After we register an Application ID of both "Payment" and "Other" Category in the manifest file, Where else is the AID used? or It is used for Our written HCE service to recognize and then do whatever that define in our written HCE Service? 回答1: or

问题 The AID of my app is F239856324897348 and I have constructed a SelectAID APDU for it. Now how do I actually send it to the receiving Android device which is using host card emulation. I have a created my HCE service to respond with a response APDU as in this thread: How to define an APDU for STORE DATA for Host Card Emulation? public static byte[] SelectAID = new byte[]{ (byte) 0xF2, (byte) 0x39, (byte) 0x85, (byte) 0x63, (byte) 0x24, (byte) 0x89, (byte) 0x73, (byte) 0x48}; private void

问题 I have an Android tablet with Android 4.2. This tablet does not have NFC hardware. However I have an external USB reader: ACR 1252U, that came with an Android library. I have asked some general questions of my setup here. Now that it gets more specific, I need to ask another one. In this previous question I found out, that I can use the ACS Android library to access the readers card emulation capabilities. My first goal is to make that reader emulate an NFC tag, that contains a URL. Any NFC

问题 I'm busy with an app to emulate normal APDU communication on a Nexus 7 with CM10.1 to an ACR122U102 reader/writer. I found this blog about software card emulation and wrote an app to make my device (the nexus) appear as a card. Now I'm trying to send messages back and forth between this device and the ACR122u. So far, I've only managed to communicate with the nexus 7 by sending D4 40 01 (InDataExchange page 127) APDU's. For the application I'm writing, this should be sufficient. The problem