GitLab

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

Change-Id: I83f79bc7a5f3227ef4a8222dc879beda53a8ab31

Change-Id: I0b709084992e8022deacd67e1b8c24f33e8d73fc

Use a cached value instead, which is based on the presence check that is running
anyway.

Change-Id: Ifa50ff38e884fa865bb7ba95dde45da39bebf7e8

Suppose you have a MifareClassic tag with NDEF; the following scenario failed
MifareClassic.connect()/close() -> Ndef.connect()/close() -> MifareClassic.connect() .

This last connect fails because the service refuses to connect any technology
on the same handle, except for NDEF. This check was too strict - it was only
intended to catch connecting to a NfcA technology on an IsoDep tag, as libNFC does not
support this. This change always allows connecting a tech on the same handle, except
when you want to connect a non-IsoDep technology on a tag that does have the IsoDep
technology on the same handle - in which case it refuses. This
matches exactly what libnfc supports.

Change-Id: I64d552b3cd51beb36712676492f36d182c605748

Bug: 3398076
Change-Id: Ib1a0ac03299f713b00bc93de2e8bb7a3b531711c

Change-Id: I0a62d1ee539aa6bf9147bed56055a460b9804aea

Change-Id: I0d8fce569f2e6431fe62a299278a0106c86cda9a

Some tags may be left in an inconsistent or "non-responding" state after we
do NdefFormatable checks. For example, tags that identify as DESfire
but don't support the getVersion() command. To make sure the stack can continue
to work with them, we reconnect().

Change-Id: I2890d3c70cc7cf7d15fb98090a031686d434168d

The pattern matching wasn't sufficient with the
move to identifying technologies with their class
names so now we use a custom dispatching mechanism.

Change-Id: I3e6379d454458bbb65730ade32cdaa1680c5e339

If the P2P target connect failed, the P2P target disconnect cannot be done.
However the polling loop must be restarted. This is already done in JNI layer
by the failing connect itself.

Change-Id: I1c3323e4c038c8133e7b6e16b3a238c050427cfc

This patch fixes the tag disconnect sequence in 2 cases:

1.
When the NFC service disconnects a tag because it is not needed anymore, the
disconnection should be effective immediately and not delayed until the tag is
removed from the field. The NFC service is responsible for discovering again
the same tag if the polling loop is restarted.
The looping "presence check" in native code is then removed.

2.
Before the screen is turned off, the polling loop configuration and - if any
tag is present - the tag disconnection must be done accordingly to the "normal"
tag management. In particular the watchdog must be stopped properly.

Change-Id: I58ee27cede110c419052b4eef07f1e4bd35ae208

libNFC doesn't support formatting tags that are already NDEF formatted. This
needs to be fixed in libNFC, but as a temporary work-around we will only
throw the NdefFormattable technology if no NDEF has been found on the tag.

Change-Id: I487b875de5fd66fdfec2d1b9c30fa886d8ca1477

There are lots of ways things could go
wrong when faced with invalid NDEF data
so just got for the catch-all and handle
it properly.

Change-Id: Ia762c8e337aef8fed867beab8159e6ed05bbacea

Foreground dispatch overrides now interpret
null for the filters as "catch all".

Foreground NDEF push disables standard dispatch
and only honors foreground dispatching so that
two NDEF push apps don't end up just swapping
between each other when the push happens.

Change-Id: Ic305d4a3a593fff732b8d88ae72e09b4a03d6286