| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Change-Id: I86657f9c547840de33c35df4912b5f282d4fe459
|
|
|
|
| |
Change-Id: I1938f348704f6fabefa6600ecf32ff7d6204d021
|
|
|
|
| |
Change-Id: Ic6df1fc458cef2531119e5e5e2ef5f9a7b21a524
|
|
|
|
|
|
|
|
|
|
| |
Patch to add Secure Download Mechanism in the libnfc
This patch permit to support secure download update and
also to avoid locking states in case of download failures
Bug: 5331837
Change-Id: Ia5b6d9baf57231b0193bbbe85c88c7df557017c6
|
|
|
|
|
|
|
|
|
|
| |
o Fix most libnfc warnings, from 360 to 18
o Make DAL_DEBUG much less verbose and more useful
o Clean up Android.mk
Done with minimal textual diff to minimize merge conflicts.
Change-Id: I918645500723ff7bb092ad9959628fcabac45bec
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
P2P target 106 passive appears as an ISO 14443-3A target to reader/writers
in the field. This can confuse some terminals, especially when we also have
card emulation turned on, since it looks like we have two -3A targets in
the field.
P2P target 106 passive is just one of many P2P sub-modes. We do not know of any
P2P devices that only initiate using only 106 passive, so this should not
present inter-op issues.
Change-Id: I1cb84ed791a86a7f225a51806e99bab031dcb6ca
|
|
Source: Trusted_NFC_Device_Host_AA03.01e02_google.zip code drop (23-Sep-2010)
Change-Id: Ie47f18423f949a8d3e0815d13f55c814312add24
Signed-off-by: Nick Pelly <npelly@google.com>
|