Low cost investment for tools, increasing ROI and speeding up market trials.Broad product portfolio providing an optimized price performance ratio.Easy-to-use and proven toolkits for fast project executionįeatures / benefits for card and reader makers.Card and reader compatibility across all generations leads to reduced infrastructure costs.Based on the international standard ISO/IEC 14443 A, ensuring a broad marketplace of solution developers and providers.

Many companies with commercial products, enabling a broad and competitive supply chain.Read range up to 10 cm increasing the convenience of touch-and-go experience.Multiple suppliers in the value chain reducing risk withinįeatures / benefits for solution developers.

Low cost investment for tools, increasing ROI and speeding.

Broad product portfolio providing an optimized price performance ratio.

NXP originality signature to prove MIFARE Classic genuinenessįeatures / benefi ts for card and reader makers.

2 x 48 bit keys per sector for key hierarchy.

Memory access conditions freely programmable.

Available with ISO/IEC 14443-3 7-byte unique identifier.

Fully ISO/IEC 14443 Type A 1-3 compliant.

Power LogOn® Enterprise Identity Management Software.

eHealthONE™ Patient EHR Management Software.

BIOSID™ Pro Tablet Biometric Mobile Identity.BIOSID™ Tablet Biometric Mobile Identity.IDBX™ Instant Biometric Smart Card Issuance.CEE™ Instant Smart Card Personalization.I will add that to the MFC support check algorithm. Where did you get that information? I tried google but found nothing.īut I've found simple way to check which controller is used by phone - just run command Unfortunately this LG uses Broadcomm chip too, so just add it to incompatible list. It should recognize the ATQA+SAK(+ATS) and show an error message saying 'You device does not support Mifare Classic' So the real problem why Mifare Classic is not working on your device is the missing MifareClassic class (due to the Broadcom chip). MCT then tries to to find out whether it is the tag or phone by checking ATQA+SAK(+ATS). If MifareClassic is not in that list it is usually due to the fact that either the tag does not support MFC or the phone does not support it. MCT checks the list of supported technologies using getTechList(). The problem is the missing MifareClassic class. Oh now I see too: you are very well familiar with Android and NFC! :)

Nxp mifare classic 1k