GitLab

This patch permit, when NFC is off, to perform a download if the PN544
is not up to date

Change-Id: I497d9e9123dfb2b9781a7ff1ba5fc927dab4d05b

Plumb status codes up through the stack.

Change-Id: Id30e69fff3bb56082ab29d42f166cb12c3061857

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

This patch permit to enable Card Emulation detection mechanism, via an EEPROM setting,
to avoid any card emulation notification when two Nexus S are in front of each other.

Change-Id: I200a2a1b3ce31863a1684cd0968cd0eec008885a

Merge "- Properly initialize NfcService.mEeRoutingState to ROUTE_OFF . This allows   NfcAdapterExtras.getCardEmulationRoute() to properly return ROUTE_OFF when   the service restarts." into gingerbread

  NfcAdapterExtras.getCardEmulationRoute() to properly return ROUTE_OFF when
  the service restarts.

Change-Id: I833bb2afae06778a0e4bdd5f5d25374636885f42

The card emulation duration is kept in EEPROM, and does not need to
be re-configured. Just turning the polling loop off is enough.

Change-Id: I25ee443d04635b3434dabf675ad5a32c4f0f468c

Bug: 4967769
Change-Id: I7a72cbe831d4b3f44bed7feeea8abaf468cdc19b
Signed-off-by: Nick Pelly <npelly@google.com>

Bug: 4967769
Change-Id: I7a72cbe831d4b3f44bed7feeea8abaf468cdc19b
Signed-off-by: Nick Pelly <npelly@google.com>

Change-Id: I4fe95c6cff9c50eef64bd99de415e66e7174b46a

Change-Id: Id89207194a87e918aee2493c8c0fa93a97a1ff4a

(removing registerTearDownApdus(), adding authenticate())

Change-Id: Ie1b0f7f088317ff3e52721158b0e588dfda14ce4

Change-Id: Id89207194a87e918aee2493c8c0fa93a97a1ff4a

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