hce

I'm trying to put my PN532 in card-emulation mode. When i send the TgGetData command the error i get an error back from the reader. 1 . Read register {(byte)0xFF,0x00,0x00,0x00,0x08, (byte)0xD4, 0x06, 0x63, 0x05, 0x63, 0x0D, 0x63, 0x38 } RESPONSE :: D507 07 07 15 9000 2 . Update registers byte xx = (byte) 07; byte yy = (byte) 07; byte zz = (byte) 15; xx = (byte) (xx | 0x004); yy = (byte) (yy & 0x0EF); zz = (byte) (zz & 0x0F7); 3 . Write register {(byte)0xFF,0x00,0x00,0x00,0x11, (byte) 0xD4, 0x08, 0x63, 0x02, (byte) 0x80, 0x63, 0x03, (byte) 0x80, (byte) 0x63, (byte) 0x05, xx, 0x63, 0x0D,yy,

Apple just announced new NFC Core API to public. Here is what they said. Core NFC With Core NFC framework, your apps can now support tag writing, including writing to NDEF formatted tags. The framework also provides supports for reading and writing tags using native protocols such as ISO 7816, MIFARE, ISO 15693, and FeliCa. For more information, see the Core NFC framework documentation. https://developer.apple.com/ios/whats-new/ So, now we have write and read API, and I read all documentation about Core NFC, but I couldn't find about card emulation. Does this mean we can emulate the card like

I've tested my Android Java application with Nexus 4, Nexus 5 and Samsung Galaxy S4 phones. In the test, the reader sends APDUs changing in length up to 252 bytes. Nexus phones receive APDUs successfully. On the other hand the Galaxy S4 phone can't receive APDUs which contain more than 128 bytes. It receives only the first 128 bytes of the sender's 252 bytes. How can I determine a device's maximum receivable APDU size? Currently there is no method to find the maximum receivable APDU length (except for trial and error). Regarding maximum receivable APDU length there is an open AOSP bug report (

I'm trying to do Host card emulation on an Android device using this example using ACR1281U NFC tag reader. This is the kind of application I want to make. As per the Android documentation and the example, it is required to register an AID in the Android project: <host-apdu-service xmlns:android="http://schemas.android.com/apk/res/android" android:description="@string/servicedesc" android:requireDeviceUnlock="false"> <aid-group android:description="@string/aiddescription" android:category="other"> <aid-filter android:name="F0010203040506"/> <aid-filter android:name="F0394148148100"/> </aid

I just read this answer about how to put my ACR122U in card-emulation mode. I do understand the purpose but how do you need to send the commands to the ACR122u. As far as I know FF000000 means: FF [Class] 00 [INS] 00 [P1] 00 [P2] I just can't figure out how I can send the actual PN532 command for example: FF000000 08 D406 6305 630D 6338 FF000000 11 D408 6302 80 6303 80 6305 xx 630D yy 6338 zz I have come this far: TerminalFactory factory = TerminalFactory.getDefault(); List<CardTerminal> terminals; try { terminals = factory.terminals().list(); CardTerminal terminal = terminals.get(0); Card

I would like to create NFC Payment Application based on Android Kitkat 4.4 which now support the NFC Card Emulation Mode for both not involving secure element and involving secure element. I would like to let My Application involve a secure element. So, I have a question. The Android KitKat can let my application access to the java card applet which is installed into a secure element? No, while the Android HCE documentation lists the possibility to use secure element-based card emulation, there are several problems hindering the use of a secure element in current devices: Nexus devices have a