GitLab

Bug: 4487211
Change-Id: Iad5c641926eb0e121d630d16f8ce02b8b9713cd3

1) Put a watchdog on the NFC Service disable path.
All the bug-reports show we were stuck in _disable(), watch-dog
this path (10 seconds).

2) Only attempt a SE reset once, even if it fails the first time.
All the bugs reports should the _disable() was due to SE reset
on first boot.

3) Grab the NFC service lock before the wake-lock.
So even if someone has NFC service lock, at least we don't
hold a wake-lock waiting for it.

Bug: 4581084
Change-Id: Ic9829dddde8d0c67cf0e8e4912357fa2902faa11

The regression occured when we switched to certificate based checking
for NFC-EE access control (this switch was only fully completed a few days
ago).

Change-Id: I43d7adfad020446af8e863e876c59caf3b852920

Change-Id: Id5e1443fefa3a79d6a9da1ff79d1ddde6dada5f2

This fixes a regression at about GRJ46 where phones that had NFC
turned off would fail to perform SE reset on first boot of GRJ46
and later. This would prevent NFC from being turned on, and caused
NFC service to eat battery.

Change-Id: I4714f06e8a3c92a5974851dd1be90b797e3058ac
Bug: 4504474

Change-Id: Ic9dc3f981e6abe52d7732eab35d6cc2c535a2dad

Remove per-package support for tear-down. It just complicates things.

Change-Id: I9ab413df339b2d5407084b2b83c0c2a8feabc0e4

The URN is converted to a URL in the form:

vnd.android.nfc://ext/<domain_name>:<service_name>

so that it can be processed by IntentFilter. For example to
catch all TNF_EXTERNAL entries for example.com you would use
the following in your manifest:

<intent-filter>
    <action android:name="android.nfc.action.NDEF_DISCOVERED" />
    <category android:name="android.intent.category.DEFAULT"/>
    <data android:scheme="vnd.android.nfc"
          android:host="ext"
          android:pathPrefix="/example.com:" />
</intent-filter>

Change-Id: I5f5b121aa217364611923113985261a5c9a2171e

This patch permit to avoid a collision between NFC-WI and P2P NFC Target 106 passive mode
in front of a payment reader.

Change-Id: Ie044cf519c7cf56f70277a2bc4cb661cf43529db

Also add debug hooks to manually set P2P modes.

Change-Id: I4abd8d5ac35c3ef6c6ffee475760b917a8bcebf1

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

Change-Id: Ide8d8dfe75eebb93420bc7a95130b0f6a72756b6

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

Bug: 4258601
Change-Id: Ib21892b6efa8e23ea86566ed6f88c2e9d284fa89

Bug: 4316508
Change-Id: I498eb09cfb48b3b14268c649936186000f360c16

Bug: 4205311
Change-Id: I116e7c2e12c7e160d81154d22589b1bdefe93e44

Change-Id: Ie6d491b4bf1a735d4119f78f252aa14a95536149

Change-Id: Idebe263500839a0238fd5b0cf732e5ecc477698e

Change-Id: I496a74f2fbad55cb8f04a434a386d6d86e7d3636

Change-Id: If8de4243ae945dd4203ac37e77d52521dfa31044

It controls permissions for NFCEE administration
and is checked based on the signature of Nfc.apk
and the caller.

The NFCEE admin permission checking is currently
set to check the stock NFC permission.

Change-Id: I164511d8f6850034ca0fc1f6f7f75c5ef212fbc2

Change-Id: I89243027b25a3904df0e50414b64387d172c181b

The deadlocked thread will hang with

"emergency_recovery: NFC stack dead-locked, please show to npelly"

so we have a chance to attach gdb and figure out what happened.

Change-Id: I8d2f06eddf79441b246381c1c671b2b7b8bb16f1

Change-Id: Id16b91a9cde25a4f4a746492921250c0834199f1

This caused SE access on eng builds to fail, and
was pretty dangerous on other builds.

Change-Id: Iea8f09559e8da61862cdb24ec0ea5ace91d5bbd1

Throw NdefFormatable only when ICODE tag.

Change-Id: I6cc54f5f076cfd1a223d0daaac0951d5d56007a3

Added type for NDEF on ICODE, changed type for MIFARE_CLASSIC as discussed.

Change-Id: I29f38c4e963f2f2211ca22f4fde244c29d5a590e

The NFC API's isConnected() is mapped to isPresent on a NativeNfcTag
object, which in turn uses a cached value. This value was however not
updated properly when the internal presence check loop detected the
tag to be gone. The cases where isConnected() does work properly
are screen off and explicit disconnect.

Change-Id: Ieac76ceb1f161ead772ce9fd2acf273b23caca37

The tag handle was only registered after the dispatch; with the "normal"
dispatch the activity would take a while to start and this problem would not be
seen. With foreground dispatch however, if you'd immediately try to connect to a tag,
sometimes the tag handle is not registered yet, causing the connect() to fail.

Change-Id: I92b5e36a5d8f08e410a656d364e88bce2d25c854

Change-Id: I019ad3fc62f49280031320c2c32532e64097d3f9

Change-Id: Id825345c0c5cd131d25ff23184a57ee53f9fa9dd

Change-Id: Ic7046ea686b1cf3eb232f6125122dea5d919ac2d

Change-Id: Ie9fc3f32cfdb043e67c774e3c222aa599f138932