text: Android/NFC: read ATR from Smartcard (EMV) - Stack Overflow
  I got an EMV Smartcard wich I want to communicate with with my Mobile phone.
  The communication itself works without problems via IsoDep, but I can't figure out how I can get the ATR.
  As far as I know the intent should contain the ATR, can someone please tell me the code I need therefore?
  Or if this is not possible maybe someone knows how to warm reset the card with a command like SELECT where the answer is the ATR.
  android nfc emv share|improve this question asked Jul 25 '12 at 19:21
  share|improve this answer answered Jul 27 '12 at 11:18
  What is the purpose of the ATR? How does it relate to the hilayer response? Would it allow me to access more data from the card?
  Oct 6 '13 at 11:10
  Contactless card do return ATR. However, you can't get ATR from current android NFC API. Android NFC API only returns historical bytes from ATR. The reason that contactless card do return ATR:
  Please note that ATR is 7816 Answer to reset. The reader (nfc phone in this case) talks to smart cards using ISO 7816 (T=CL) APDU exchange, which is transported via contactless interface ISO 14443-4. Since there is ISO 7816 in this case, you will get ATR.
  Contactless cards do NOT provide a real ATR (answer-to-reset) as they do not undergo the ISO 7816-3 reset procedure. (Though cards may contain a EF.ATR file containing the data normally contained in an ATR.) T=CL (which is basically the transport protocol defined in ISO 14443-4) has an ATS (answer-to-select) for type A (which comes close to an ATR as in that it also contains historical bytes) and an answer-to-ATTRIB for type B (that's where the data for getHiLayerResponse() comes from).
  I can get ATR from contactless card using SCM reader from both A & B card. It may not be 'real' in traditional sense as you pointed out. However, it does return ATR.
  Well, the card does not return that ATR. Instead what you see is a pseudo-ATR generated by the PC/SC driver that connect your smartcard reader to applications. The pseudo-ATR (not generated or "returned" by the card) is used to pass (otherwise inaccesible) information about the contactless protocol to the application layer. As Android does not use PC/SC for access to smartcards through NFC there is also no ATR involved here.
  Not the answer you're looking for?	Browse other questions tagged android nfc emv or ask your own question.	asked