nfc

Why doesn't Android HCE support Mifare Classic type?

无人久伴 提交于 2019-12-29 07:13:07
问题 Mifare Classic is the most used cards and I can't understand why HCE (Host-based Card Emulation) only supports ISO 14443-4, but not Mifare Classic type. Because NXP stops them from using their proprietary protocols and algorithms? Or because they didn’t implement Mifare Classic in Android OS level? Any comments will be very appreciated. 回答1: Short answer: Because Google decided to support only ISO/IEC 7816-4 over ISO-DEP (ISO/IEC 14443-4). Speculations on why they decided that way: First of

Why doesn't Android HCE support Mifare Classic type?

走远了吗. 提交于 2019-12-29 07:13:00
问题 Mifare Classic is the most used cards and I can't understand why HCE (Host-based Card Emulation) only supports ISO 14443-4, but not Mifare Classic type. Because NXP stops them from using their proprietary protocols and algorithms? Or because they didn’t implement Mifare Classic in Android OS level? Any comments will be very appreciated. 回答1: Short answer: Because Google decided to support only ISO/IEC 7816-4 over ISO-DEP (ISO/IEC 14443-4). Speculations on why they decided that way: First of

How to read detected NFC tag (NDEF content) details in android?

感情迁移 提交于 2019-12-29 06:29:50
问题 I want to read NDEF content contained within a detected NFC tag (i.e., Tag id, Tag Size, Tag Type, Is tag Writable, Target Type, and message types). 回答1: I assume that you are talking about tags with NDEF content? In that case, you can do: Tag myTag = (Tag) nfcintent.getParcelableExtra(NfcAdapter.EXTRA_TAG); // get NDEF tag details Ndef ndefTag = Ndef.get(myTag); int size = ndefTag.getMaxSize(); // tag size boolean writable = ndefTag.isWritable(); // is tag writable? String type = ndefTag

Android nfcA.connect(), nfcA.transceive(), nfcA.setTimeout() and nfcA.getMaxTransceiveLength()

人盡茶涼 提交于 2019-12-29 06:25:15
问题 I have a a number of newbie NfcA questions. There seems to be little guidance on this in the docs and elsewhere on the web, so I hope no-one minds me stringing a few basic questions together here... I am using nfcA.transceive() to write data to my NTAG213 tag like this: byte[] result = nfcA.transceive(new byte[] { (byte)0xA2, // WRITE (byte)(pageNum & 0x0ff), myData[0], myData[1], myData[2], myData[3] }); 1. The result array is a single byte of value 10. What does this mean and what other

List of OMAPI supported devices

流过昼夜 提交于 2019-12-29 05:35:07
问题 I'm developing with the Open Mobile API but so far haven't found a list of devices that support the API by default (by default being using the OEM ROM). I realise that since API level 21, Android telephony supports sending APDUs via basic and logical channels dirctly through the TelephonyManager. But I'd like to know about devices running pre-API level 21 too. So, has a list already been compiled of devices with built-in support or is there a way to find out for myself? 回答1: I'm not aware of

Can I prevent Host Card Emulation service from being triggered by select AID?

≡放荡痞女 提交于 2019-12-29 01:26:49
问题 I have an Android app with a service registered to Android beam and a service registered to host card emulation. I want to decide when to enable/disable the HCE service in the code. The HCE service in the manifest looks like this - <service android:name="com.bimo.verifonewallet.service.MyHostApduService" android:exported="true" android:permission="android.permission.BIND_NFC_SERVICE" > <intent-filter> <action android:name="android.nfc.cardemulation.action.HOST_APDU_SERVICE" /> </intent-filter

Can we transfer data between two iPhone devices using NFC in iOS? [closed]

孤街醉人 提交于 2019-12-25 20:02:03
问题 Closed . This question needs to be more focused. It is not currently accepting answers. Want to improve this question? Update the question so it focuses on one problem only by editing this post. Closed 5 months ago . With the release of iOS 13, iOS NFC core framework has added API's to write on NFC tags. But does this mean that now we can transfer data between two iPhone devices using NFC APIs. Writing and reading on NFC tags works fine. 回答1: Not directly between two phones. You can read from

NFC Tag Type 1 Protection

你。 提交于 2019-12-25 13:38:16
问题 I got a Type 1 NFC TAG from NXP semiconductor ... i tried many android applications to reset or format and never worked , it says Protected or Blocked . The question is , how can i crack the NFC Card protection. 回答1: Type1 NFC Tags have a simple but effective protection mechanism. There are one time programmable lock bits on the tag. Each of this lock bits makes 8 bytes of data on the tag read only (simplified view). Once these bits are set the memory is write protected for ever. Think of the

NFC Tag Type 1 Protection

戏子无情 提交于 2019-12-25 13:36:37
问题 I got a Type 1 NFC TAG from NXP semiconductor ... i tried many android applications to reset or format and never worked , it says Protected or Blocked . The question is , how can i crack the NFC Card protection. 回答1: Type1 NFC Tags have a simple but effective protection mechanism. There are one time programmable lock bits on the tag. Each of this lock bits makes 8 bytes of data on the tag read only (simplified view). Once these bits are set the memory is write protected for ever. Think of the

android nfc - mifare classic 1k Increment operation tranceive failed

£可爱£侵袭症+ 提交于 2019-12-25 11:54:29
问题 I want to store an integer value and increment or decrement it with API function. I have readed the card with an utility and this is the content of block 5: It seems that there is not any value block. This is my code: int sector = 5; this.mClassic.connect(); boolean success = this.mClassic.authenticateSectorWithKeyA(sector, MifareClassic.KEY_DEFAULT ); if(success){ int firstBlock = mClassic.sectorToBlock(sector); Log.i("MIFARE CLASSIC", "first block of the given sector:" + firstBlock); //set