| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Bug: 7276355
Change-Id: I65597f732c2ccb749f8fc5ef1793bacf5de8b592
|
|
|
|
|
|
|
|
|
|
|
|
| |
It was in com.android.nfc_extras, which caused it to get bundled with
com.android.nfc_extras.jar, which caused all kinds of confusion when
trying to push new versions of the test.
It should be in com.android.nfc_extras.tests
Also fix getContext() -> getTargetContext().
Change-Id: I1e3afa150809a3ed8c4f88531f039fe7797aca1d
|
|
|
|
|
|
|
| |
The new NFC Extras access control allows us to run these tests
without a vendor specific certificate.
Change-Id: I9425e08e557214cf6a74276622402c5682bbaef4
|
|
|
|
|
|
|
|
| |
This fixes a bug where NfcExecutionEnvironment.close() would NPE
if you called it on a different EE to the one you opened. We now
always return the same EE in the same contet.
Change-Id: I949998dc2ee738527ee281cae46ae50ea6950a2c
|
|
|
|
|
|
|
|
|
|
| |
The package name is now required when using the
NFC extras APIs so the context is stored away
and used to derive the package name to be sent
to the NfcService.
Bug: 4515759
Change-Id: I1a3aba3fc026e0090a914b0686fc4b8dec25b927
|
|
|
|
|
|
| |
return null)
Change-Id: I85fcbc5e79549835dac255ce614bd5d65d39fc25
|
|
|
|
| |
Change-Id: I8129b7812c0d551111f0c85eacc9535a441e5453
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Remove
o registerTearDownApdus()
o deregisterTearDownApdus()
They were already NO-OPS, and don't work in the general case.
Add
o authenticate(byte[] token)
This future proofs us for a more flexible access control scheme.
Change-Id: I4cb67ceeb63d61cbc333c9b244a96d8687402168
|
|
|
|
| |
Change-Id: I4f1d714c625470df4cda2c4c9aacb8d27bfabb10
|
|
|
| |
Change-Id: I1a3feda3b1007b08fcaa24c3f8dd21abf1efd885
|
|
|
|
| |
Change-Id: I9c319925008070cc5ea93d5dd3941c9396072a8c
|
|
|
|
|
|
| |
Instead of the final jar with classes.dex inside.
Change-Id: I2bc7eb6faedf328a93a6e2eacc4334d87761f597
|
|
|
|
| |
Change-Id: I409106d641a3a68ef1c6885b36d226411c8fe356
|
|
Change-Id: I45c4eaf59ec78167fc236fdd59676465a5e1bcb7
|