Hi, Am facing the exact same issue, and the logcat shows that the native function seems to be losing the connection to the card on the transcieve(). I increased the timeout and that didn't solve the issue either.
Please let me know if you find a solution :-) Thanks, Priti On May 3, 11:50 pm, Wilson Chew <[email protected]> wrote: > Hi All, > > I noticed that the connection created (using IsoDep) is not stable. > For example, when I perform a signing(digital signature) and > verification of signature via APDU, the NFC service will die or > connection totagwill belosteven if I set the timeout to 20sec. It > happen quite often. > > Is it a known issue or I have missed out something in my code? > > Thanks. > > Regards, > Wilson > > On Apr 26, 5:09 pm, perumal316 <[email protected]> wrote: > > > > > For IsoDep using setTimeOut function to set a time resolves the issue. > > > On Apr 26, 12:13 pm, perumal316 <[email protected]> wrote: > > > > Hi Michael, > > > > I changed MiFareClassic object to IsoDep. But I am getting the > > > following error: > > > > "android.nfc.TagLostException:Tagwaslost" > > > > Must I add in additional code to sustain the connection? (Am I > > > correct?) > > > > Thanks In Advance, > > > Perumal > > > > On Apr 25, 5:00 pm, Michael Roland <[email protected]> wrote: > > > > > Hallo Wilson, > > > > > > I am facing an issue with a Mifare Classic card (this is a dual > > > > > interface smart card; contact and contactless). > > > > > Alright, then it is most likely not a MIFARE Classic card but a > > > > contactless (dual interface) smart card (with ISO 14443-4 interface) > > > > that additionally provides a MIFARE Classic emulation. > > > > > > When I use transceive() to send apdu corresponding to "select AID", > > > > > it always > > > > > return null. > > > > > Right, as you write here:> 2) Create MifareClassic object using > > > > > you create a MifareClassic but what you really want to do is open an > > > > APDU connection to the card. If your card is a real dual-interface > > > > smart card(*) it should also expose an IsoDep interface (ISO 14443-4 / > > > > ISO 7816-4). This is the interface you would want to use for APDU > > > > communication. > > > > > br, > > > > Michael > > > > > (*) There could also exist some hybrid cards that have a MIFARE > > > > Classic _contactless_ card and an APDU-based _contact_ smart card > > > > joined into the same plastic card. In that case the contact and > > > > contactless parts would be independent chips and no communication > > > > between them would be possible.- Hide quoted text - > > > > - Show quoted text -- Hide quoted text - > > > - Show quoted text -- Hide quoted text - > > - Show quoted text - -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
