| 8c447f37edc4510c35209882bd47879b5f5f5530 |
|
13-Apr-2018 |
Love Khanna <love.khanna@nxp.com> |
Set Felica Max Transceive payload length to 255 bytes
Bug: 76182441
Test: Perform 255 byte payload transceive with T3T Tag
Change-Id: I958fb22a4a9b2fedd6569e688affb00f457ab279
(cherry picked from commit ffb56073148b49a67606d83531785239a2ff1e4b)
/packages/apps/Nfc/nci/src/com/android/nfc/dhimpl/NativeNfcManager.java
|
| a109d87866a6be88d9123277397224720b26afe2 |
|
01-Feb-2018 |
Ruchi Kandoi <kandoiruchi@google.com> |
Add Transaction Event Notifications for NFCEE
Whenever an transaction is detected on any of the Secure Elements, an
event will be sent to the application which has the necessary
permission. Access control is checked by the Secure Element Service.
Bug: 72556384
Bug: 65127791
Test: Test App check for RF Events
Change-Id: I10cf119a1105c123b69f628f5420587bc84b1078
/packages/apps/Nfc/nci/src/com/android/nfc/dhimpl/NativeNfcManager.java
|
| 97e052f69713537204b454c8f60dd805f8fba5de |
|
07-Dec-2017 |
Ruchi Kandoi <kandoiruchi@google.com> |
Add power off use case (2/2)
Bug: 70294551
Test: manual
Change-Id: I79b0b3a94e30db86c26d73a360eccc04b3c05f5e
/packages/apps/Nfc/nci/src/com/android/nfc/dhimpl/NativeNfcManager.java
|
| 339f1a913abae2fbb558b4d747a1cc3c8be804d6 |
|
07-Dec-2017 |
Ruchi Kandoi <kandoiruchi@google.com> |
Add factory reset functionality (2/2)
Factory reset is needed to inform the underlying hardware to clear the
chip and full initialization will be needed during next init.
Test: manual
Bug: 70294869
Change-Id: I12a16a574772fba07f72398ce535debb3e2aa2f9
/packages/apps/Nfc/nci/src/com/android/nfc/dhimpl/NativeNfcManager.java
|
| 5d5dd8aceaac42d7814b0e69a01faab0187d1461 |
|
09-Nov-2017 |
Ruchi Kandoi <kandoiruchi@google.com> |
Make Transceive Length configurable for ISO DEP Technology
ISO_DEP_MAX_TRANSCEIVE has been added to indicate the maximum APDU
length that is supported by the underlying NFC chip. If the
configuration is not set, default maximum of 261 is set.
Check if device supports Extended APDUs, if yes, return true for
getExtendedLengthApdusSupported()
Test: Read IsoDep Tag and check the maxTransceive length.
Bug: 37005118
Change-Id: I198c06fdcbcd3b45932f544fa063e920f84f7968
/packages/apps/Nfc/nci/src/com/android/nfc/dhimpl/NativeNfcManager.java
|
| f939e8a61d3904ab30ec59e2762f5c543ebaa672 |
|
17-Jul-2017 |
Ruchi Kandoi <kandoiruchi@google.com> |
DTA support and extensions added.
Added SNEP server extension required by NFC Forum test cases.
Added support to configure the MW as per specifc configuration
required by NFC Forum test cases.
Bug: 63903843
Test: compiles.
Change-Id: I4df165b20388d87c25a07c8048eff7997fd21070
/packages/apps/Nfc/nci/src/com/android/nfc/dhimpl/NativeNfcManager.java
|
| fdcfcb0031a4fbf38dd828ac1b3ef8319342e2fa |
|
13-Apr-2017 |
Ruchi Kandoi <kandoiruchi@google.com> |
Add native logging for libnfc-nci
Bug: 63636926
Test: Verify logs in bugreport
Change-Id: I5f46582c75d05b8a88a9b7672e0005ff1f58f674
Signed-off-by: Ruchi Kandoi <kandoiruchi@google.com>
/packages/apps/Nfc/nci/src/com/android/nfc/dhimpl/NativeNfcManager.java
|
| 8ee2015a9c4639d465a390af93df3fdcd983cac8 |
|
12-May-2017 |
Love Khanna <love.khanna@nxp.com> |
NCI2.0 Support for AID suffix registration.
Test: compiles.
Change-Id: I11448f22dee90d9e93eb8705366c3e22967e521b
(cherry picked from commit 014170ea169484c0126b4a8ebc4ed4a0f6193af3)
/packages/apps/Nfc/nci/src/com/android/nfc/dhimpl/NativeNfcManager.java
|
| 3a894dda035a331860f0f23e93528527493a07a3 |
|
11-May-2017 |
Love Khanna <love.khanna@nxp.com> |
NCI2.0 Screen state and power sub state management.
As per NCI2.0 screen state transitions can be
handled without restarting the discovery loop
by using the con_discovery_param.
Also as part of screen trasition power sub state
info is updated to NFCC.
Test: compiles.
Change-Id: I28d7f58b299a8ae9acbe7aa643adfc0a16b787cc
(cherry picked from commit bd4c6c8c4a7553a77da8655c3d4d4816cb577185)
/packages/apps/Nfc/nci/src/com/android/nfc/dhimpl/NativeNfcManager.java
|
| 729dc345dae23c1990cf5377a3948584cff2171a |
|
24-Oct-2016 |
Andre Eisenbach <eisenbach@google.com> |
Log thread source for doAbort()
Test: manual
Bug: 29939338
Change-Id: Id0009c02a26cde4a12e6baceeab179a9ed1a7d37
/packages/apps/Nfc/nci/src/com/android/nfc/dhimpl/NativeNfcManager.java
|
| ecb8d7bbd1a44cd3edbcb6c5d903fc8d9a625d70 |
|
22-Jan-2016 |
Yoshinobu Ito <Yoshinobu.Ito@jp.sony.com> |
Implementation of HCE for NFC-F.
This impementation includes HCE(Host-based Card Emulation) for NFC-F
which emulates NFC Forum Type 3 Tag on a smartphone.
Signed-off-by: Daisuke Ito <DaisukeE.Ito@jp.sony.com>
Yoshinobu Ito <Yoshinobu.Ito@jp.sony.com>
Change-Id: I1618a7fba801e0705ff3cc078206a1446b3dd56d
/packages/apps/Nfc/nci/src/com/android/nfc/dhimpl/NativeNfcManager.java
|
| 31b0f4653686119d74876cae5d637c5baf52b935 |
|
12-Nov-2014 |
Andres Morales <anmorales@google.com> |
Prevent Beam at the lockscreen and during provisioning
Since we can poll at the lockscreen not for unlock
tags, need to explicitly disable Beam.
Also since we allow peripheral handover during provisioning,
we started allowing Beam as well. Blocking that.
Bug: 18349433
Change-Id: I987f43228d2c003c66201d2e91bd9bdfebd49d78
/packages/apps/Nfc/nci/src/com/android/nfc/dhimpl/NativeNfcManager.java
|
| c19c065b6d0e1a088780c4dca27a1404d5926765 |
|
09-Sep-2014 |
Martijn Coenen <maco@google.com> |
Reinstate RF field events.
These are generic enough to maintain in AOSP,
and can still be protected by nfcee_access.xml
like they used to be.
Bug: 16653617
Change-Id: Id604fcc45d4263b24fea2f16ca6a24e25f8580c3
/packages/apps/Nfc/nci/src/com/android/nfc/dhimpl/NativeNfcManager.java
|
| f5c979220fadb2c3ac0bca09e16d0d281ed20eb2 |
|
25-Jul-2014 |
Martijn Coenen <maco@google.com> |
Support for configuring SE listen technologies.
If the config file specified an SE to use, configure
its listen technologies correctly.
Also, fix commitRouting() to actually commit the
configuration.
Bug: 16517161
Change-Id: I1283fcb3f855c89a8b238be857bd56f06a14138f
/packages/apps/Nfc/nci/src/com/android/nfc/dhimpl/NativeNfcManager.java
|
| 304a6342ee7e5620d3b50d988755c035f1686dc2 |
|
28-Jun-2014 |
Martijn Coenen <maco@google.com> |
Don't conditionally enable snooze.
We keep our devices in snooze by default now.
Change-Id: Ia84635031d60221da054448b8c81c5c48f1f821d
/packages/apps/Nfc/nci/src/com/android/nfc/dhimpl/NativeNfcManager.java
|
| 0799bcbe2469aa6a88c6cbdf0cdee5b50e1994f0 |
|
18-Dec-2013 |
Andres Morales <anmorales@google.com> |
Refactoring NfcService routing logic.
Currently, routing logic contains a lot of nested conditionals
and causes unnecessary work to occur, particularly in enabling
reader mode. This CL moves this logic to a state object that contains
all necessary information to transfer from one routing state to another,
leading to fewer calls to the NFCC, eliminating duplicate work, and
making the code more readable.
Change-Id: I6a8758e61cc0cbb015d618575da35386eadf7d3a
/packages/apps/Nfc/nci/src/com/android/nfc/dhimpl/NativeNfcManager.java
|
| c8768e4b2ab114d227bd8af441d81525837f78cb |
|
25-Mar-2014 |
Martijn Coenen <maco@google.com> |
Goodbye secure element.
I really liked you,
but everybody else wanted you too.
Maybe some day you'll be back,
connected to the host CPU.
Change-Id: If78bce7c7178a77919b8b1b64334909f4ff7e037
/packages/apps/Nfc/nci/src/com/android/nfc/dhimpl/NativeNfcManager.java
|
| a1e95d30dbe8dad0a8bb333b4ca17c009fc34e2f |
|
04-Feb-2014 |
Andres Morales <anmorales@google.com> |
Revert "Refactoring NfcService routing logic."
This reverts commit 80e61a46c0541471ef01a9d3c91570139336bcff.
Change-Id: I0b4fc471a3dae22c4d732b1c002f51a412c2c121
/packages/apps/Nfc/nci/src/com/android/nfc/dhimpl/NativeNfcManager.java
|
| 80e61a46c0541471ef01a9d3c91570139336bcff |
|
18-Dec-2013 |
Andres Morales <anmorales@google.com> |
Refactoring NfcService routing logic.
Currently, routing logic contains a lot of nested conditionals
and causes unnecessary work to occur, particularly in enabling
reader mode. This CL moves this logic to a state object that contains
all necessary information to transfer from one routing state to another,
leading to fewer calls to the NFCC, eliminating duplicate work, and
making the code more readable.
Change-Id: I4c451cb96ed27954fe2e6e7e7704643f3f3456a6
/packages/apps/Nfc/nci/src/com/android/nfc/dhimpl/NativeNfcManager.java
|
| fb18ffb259fe8f40e81516842497735a7c0b6a8c |
|
18-Dec-2013 |
Andres Morales <anmorales@google.com> |
nfc-64 part 1: store native structure in a long rather than an int
Change-Id: I3ff21d3f1ad0f8e9e643c84fecd4c45a1b373133
/packages/apps/Nfc/nci/src/com/android/nfc/dhimpl/NativeNfcManager.java
|
| d2604c0544f7bc26e5b2407f0215cccfffedae2c |
|
11-Dec-2013 |
Andres Morales <anmorales@google.com> |
Expose snooze mode config and polling modes in java layer
Change-Id: I3a604fb4260a1e99e6aa40189e999996d5947ed4
/packages/apps/Nfc/nci/src/com/android/nfc/dhimpl/NativeNfcManager.java
|
| c4e4277a71c70e96198cb760676ad3b40f9e0e3d |
|
27-Aug-2013 |
Martijn Coenen <maco@google.com> |
Implement reader mode APIs.
Disable p2p/listen modes on request. Currently only
for NCI platforms, NXP will follow later.
Also, fixed some compiler warnings and a mem leak.
Bug: 10360259
Change-Id: Id13db24914adc43db62e055b66e0989e9cde2482
/packages/apps/Nfc/nci/src/com/android/nfc/dhimpl/NativeNfcManager.java
|
| a8aa07142ea0078d3ae4ae486e094e2f2f4ff732 |
|
27-Mar-2013 |
Evan Chu <evanchu@broadcom.com> |
Sync up with Broadcom JNI changes.
Patches contributed by Evan Chu<evanchu@broadcom.com>
and Paul Chaisson<pchaisson@broadcom.com>.
Bug: 10360038
Change-Id: I1402191406b08e097680f8c7f587f393f749184e
/packages/apps/Nfc/nci/src/com/android/nfc/dhimpl/NativeNfcManager.java
|
| 9f8f6cf9c58405ecafe2d425801e6c14088db8c7 |
|
30-Apr-2013 |
Martijn Coenen <maco@google.com> |
Host-based card emulation.
Initial check-in that allows to build basic HCE apps:
- Introduced new RoutingManager, taking care of programming
the routing table to the NFCC.
- Added DeviceHost interfaces for adding/removing aids to
the routing table, and sending raw frames.
- On devices that have an eSE, the eSE is the default route.
- Removed routing code from SecureElement class.
- HostEmulationManager resolves and dispatches AIDs
routed to the host to an application service.
- Simple Messenger service interface for exchanging APDUs.
- RegisteredAidCache keeps a cache of AIDs that are registered
by Android applications, as well as their route.
TODO:
- Dynamic registration of AIDs.
- Dynamic updates of the routing table.
- AID conflict resolution.
- Allow apps to indicate AIDs present "off-host".
- Implement base-class HCE service in framework.
- Switch default route to host.
Change-Id: I7d7643770fcc848699810ec5443d0d9b81d85669
/packages/apps/Nfc/nci/src/com/android/nfc/dhimpl/NativeNfcManager.java
|
| 57a44d07a3de327e8cdbbcd622118aa517313dbe |
|
28-Mar-2013 |
Martijn Coenen <maco@google.com> |
Deal with pre-MR2 PN544 NXP stack LLCP bugs.
In MR2 we started connecting LLCP on link
activation instead of when the send was confirmed. Pre-MR2
NXP-stack devices have a bug that causes them to only
send the first SYMM after 750 ms (in case they are the
initiator). There is another bug that causes that same stack
to crash if two threads try to send a packet at the same
time.
Unfortunately, this combination of factors creates the
following race:
1) pre-MR2 PN544-initiator initiates p2p link with MR2 device
2) pre-MR2 PN544-initiator starts Touch to Beam animation
3) pre-MR2 PN544 doesn't have data to send, but delays SYMM for 750ms
4) MR2 device finally gets SYMM after 750ms, and sends CONNECT PDU
5) pre-MR2 PN544-initiator device responds to CONNECT PDU with CC on Thread 1
6) Within a ~50 ms window, the user on the pre-MR2 PN544-initiator touches
the screen to confirm the send. This causes Thread 2 to try to send
something, which fails.
As a result, the Beam transaction fails. Unfortunately
this is quite easy to reproduce, since the Beam animation takes
about 750ms, just the same amount of time it takes for the SYMM
to get sent.
To prevent such a race condition, we should make sure that we do
not create multi-threaded access on the remote device. The best way
to do that is to not connect the LLCP services automatically when
talking to a pre-MR2 PN544-initiator.
Long story short, when we don't receive a first packet of data
after 200 ms, we consider the remote device to be a buggy
implementation, and delay the connect until the time the user
decides to send something (in which case it's fine - it's unlikely
the user at the other side tries to send something at exactly the
same time).
Also fixed RF field notifications to be more robust; whenever
p2p is activated, we disable field events, and always treat the
field as being on.
Bug: 8508568
Change-Id: I41b427afb24c7f8d228adc91d258cca553539588
/packages/apps/Nfc/nci/src/com/android/nfc/dhimpl/NativeNfcManager.java
|
| 525c260303268a83da4c3413b953d13c9084e834 |
|
14-Dec-2012 |
The Android Open Source Project <initial-contribution@android.com> |
Snapshot 1a6bcf3cca90fedfbad33c1cdd6d05af5774fc01
Change-Id: I3ccb25bf7cde2c22f52260cae0e9957517e6bb5f
/packages/apps/Nfc/nci/src/com/android/nfc/dhimpl/NativeNfcManager.java
|