Timeline for Reading Mifare Classic chips with Samsung Galaxy S4?
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 22, 2017 at 7:26 | comment | added | Michael Roland | @JohnyTex Yubikey Neo uses standard ISO/IEC 14443-4 (i.e. ISO-DEP) so it will work just fine. There is no MIFARE Classic involved in typically Yubikey usecases. | |
| Feb 21, 2017 at 8:35 | comment | added | JohnyTex | Does this mean Yubikey Neo won't work with S4? | |
| Dec 29, 2015 at 11:03 | comment | added | Michael Roland | @GregWoods Right all (most?) Lumia devices contain NFC controller hardware from NXP. | |
| Dec 29, 2015 at 11:00 | comment | added | Greg Woods | Not sure about the licensing side, but my Windows Phone (Lumia 1020) can read and write MiFare Classic 1K cards... and Microsoft (and Nokia) were never ones to go out of their way to make something work. Most disappointed that my Galaxy S4 doesn't support these tags. Useful info on tag compatibility (non-technical) here andytags.com/nfc-tags-compatibility-issues.html#.VoJn_BWLRaQ | |
| Sep 10, 2014 at 10:20 | comment | added | Michael Roland | But this does not necessarily mean that the hardware itself is not capable of communicating with MIFARE Classic chips. While non-NXP chips won't have the MIFARE Classic reader-side directly in hardware/firmware, that capability could be implemented in software if (and only if) the chip provides adequate low-level interfaces that would permit this. | |
| Sep 10, 2014 at 10:20 | comment | added | Michael Roland |
Not necessarily. If a chip officially supports MIFARE Classic it will be likely that its software library also implements the MifareClassic tag technology. However, I doubt that this will happen for any non-NXP hardware due to legal reasons (as I wrote above, NXP does not currently license the reader-side to any other manufacturer).
|
|
| Sep 10, 2014 at 9:56 | comment | added | Malvineous | There is a MifareClassic API interface, so maybe the fact that that is not implemented for Broadcom chips means it is a hardware limitation then. | |
| Sep 10, 2014 at 5:03 | comment | added | Michael Roland |
Hard to tell without having access to the documentation of the NFC chip. It's at least an Android API limitation (NfcA will auto-append a CRC to each frame), but that limitation could just as well reach down to the NFC controller (if the NFC controller only implements the standards).
|
|
| Sep 10, 2014 at 0:13 | comment | added | Malvineous | So the non-standard frame format is at a lower level than you can access via the Broadcom NFC hardware inside one of these devices? Just wondering whether this is an API limitation or a hardware compatibility issue. I'd be surprised if Broadcom didn't include a small workaround for so many popular non-standard cards to make their controllers more versatile. | |
| Aug 10, 2014 at 9:07 | history | answered | Michael Roland | CC BY-SA 3.0 |