summaryrefslogtreecommitdiffstats
path: root/jni/com_android_nfc_NativeNfcSecureElement.cpp
Commit message (Collapse)AuthorAgeFilesLines
* Fix to avoid a semaphore issue during the SE opendanieltomas2012-04-201-4/+25
| | | | | | | This fix is handling a new semaphore dedicated to the SE Notification to avoid the semaphore desynchronisation. Change-Id: I2e735247897a88eaddafcee0edbf3e5a89e18155
* Added shared prefs for SE wired modeSunil Jogi2012-04-201-2/+2
| | | | | | | | | When SE is in wired mode shared prefs sets the se_wired to true, when SE is no more in wired mode shared prefs sets se_wired to false. Default value for se_wired is false. se_wired shared pref is set during the NFC initialization. Change-Id: I9a3565c23035802895c8e99c671483c808312e0e
* Rename (IF_)LOGE(_IF) to (IF_)ALOGE(_IF) DO NOT MERGESteve Block2012-01-061-33/+33
| | | | | | | See https://android-git.corp.google.com/g/#/c/157220 Bug: 5449033 Change-Id: If3f714c482c26a9b90cae43dbab6e4ee7f46dcb9
* Rename (IF_)LOGD(_IF) to (IF_)ALOGD(_IF) DO NOT MERGESteve Block2012-01-031-2/+2
| | | | | | | See https://android-git.corp.google.com/g/156016 Bug: 5449033 Change-Id: Ie4ce01d556684684b2e3ccb5c2fd65307ec11960
* Fix NfcExecutionEnvironment.transceive() failures.Nick Pelly2011-08-091-2/+17
| | | | | | | | | | | | | | | | | An earlier change to add multiple protocol support for NfcA and IsoDep causes 3 technologies (NfcA, MifareClassic, IsoDep) to be enumerated on the Secure Element instead of 2 (MifareClassic, IsoDep). This caused a regression because com_android_nfc_jni_open_secure_element_notification_callback() always connected to the 2nd handle, without checking protocols. Fix is to walk the protocol list and look for IsoDep instead of hard-coding the index. For some reason IsoDep seems to be phNfc_eISO14443_A_PICC and not phNfc_eISO14443_4A_PICC in this code. Change-Id: If7471b494099a09cf6d0bf5e255da556f11570b1
* Merge 3d644e80Jean-Baptiste Queru2011-07-261-0/+9
|\ | | | | | | Change-Id: I8391bb474ecfe80ea9e7f13178fbaccf2cc576e8
| * Prevent SE from being opened while target is in field.Daniel Tomas2011-07-251-0/+9
| | | | | | | | | | | | | | | | | | This fixes an issue where an attempt to open the SE while the NFC Controller is in initiator (reader/writer or P2P Initiator) mode would cause a strange error response, and all further attempts to open the SE fail. Change-Id: I6401f644c73a993433cb73fee2eff8c11ededa1d
* | Fixes from code review.Jeff Hamilton2011-06-141-4/+2
| | | | | | | | Change-Id: I147cbf71b05e6d1868bcdcd5daa0bee7e6711267
* | Relocate the libnfc-nxp Java bridge sources.Jeff Hamilton2011-06-131-1/+1
|/ | | | Change-Id: I0b743245d60bf9c47ce84ec0ab7fd8c5b6202ec9
* Another attempt at fixing JNI local reference leaks.Jeff Hamilton2011-05-211-4/+5
| | | | | | | | | The thread making the call here may never make it into the virtual machine, so the local reference is explicitly deleted. Bug: 4383243 Change-Id: I44d546f7f71a4fb2631133d65573cee19d466fb6
* Merge "Better logging on SE open failure." into gingerbreadJeff Hamilton2011-04-281-1/+2
|\
| * Better logging on SE open failure.Jeff Hamilton2011-04-201-1/+2
| | | | | | | | | | | | | | | | | | If the secure element connection fails to open due to an external RF field being detected it's now logged to make debugging easier. Bug: 4304698 Change-Id: Iea6e23968ee18d4f99e7ecbbf1b60b7c1688f5b6
* | Avoid reference table overflows when dealing with secure elements.Jeff Hamilton2011-04-201-49/+27
|/ | | | | Bug: 4258601 Change-Id: Ib21892b6efa8e23ea86566ed6f88c2e9d284fa89
* Increase wired mode timeout to 10 seconds.Nick Pelly2011-03-301-8/+0
| | | | Change-Id: I496a74f2fbad55cb8f04a434a386d6d86e7d3636
* Don't re-use the same JNIEnv across threads.Nick Pelly2011-03-071-8/+8
| | | | | | | This caused SE access on eng builds to fail, and was pretty dangerous on other builds. Change-Id: Iea8f09559e8da61862cdb24ec0ea5ace91d5bbd1
* Patch to manage the transceive timeout in wired modedaniel_tomas2011-02-161-0/+8
| | | | Change-Id: Id825345c0c5cd131d25ff23184a57ee53f9fa9dd
* Patch for PN544 GPIO6 managementdaniel_tomas2011-02-161-67/+223
| | | | Change-Id: Ie9fc3f32cfdb043e67c774e3c222aa599f138932
* NfcSecureElement source code updated to use dynamic sempahoredaniel_tomas2011-01-071-52/+86
| | | | Change-Id: I63af03e79da263993db5a35df7602ae0b1c48c56
* Store the libnfc tag type inside the tag object.Martijn Coenen2010-12-151-2/+6
| | | | | | | | | | | Some functionality in libnfc is different for some technologies (e.g. reconnect(), transceive()). For these cases, we'll use the libnfc tag type to deal with them. We don't want to distinguish these cases based on the Java API technology types, since they may be changed and even mapped to different libnfc types. Ideally libnfc should abstract this away for us, but that is not the case now. Change-Id: I33ea04ca48d16ccf186e3f0882cafdd38a8adb34
* Initial work for supporting multi-protocol tags properly.Martijn Coenen2010-12-101-8/+11
| | | | | | | - Tech tree properly does multi-protocol - Implemented a handle list, where we can link each tech to a libnfc handle Change-Id: Id9522d505cb158f5163e866b686758c269390cde
* Initial support for technology tree based on libnfc return type.Martijn Coenen2010-11-251-12/+29
| | | | | | | Based on the tag return type from libnfc, we return a proper technology tree. Also fixed transceive to depend properly on the tech tree. Change-Id: I946577692c3a71602d88c2b6416c94154d2d434f
* Secure Element Access implementationDaniel Tomas2010-11-191-0/+533
Change-Id: Ia1c006c52aaf312408ef2fba96715b1b6c382ea9
generated by cgit v1.1 at 2025-01-08 18:03:01 +0000