Skip to content

GitLab

Switch branch/tag
  1. 25 May, 2011 3 commits
  3. 24 May, 2011 3 commits
  5. 21 May, 2011 1 commit
  7. 12 May, 2011 1 commit
    • mike wakerly's avatar
      Add Rev · 6344b654
      mike wakerly authored 
      Change-Id: Ide8d8dfe75eebb93420bc7a95130b0f6a72756b6
      6344b654
  9. 28 Apr, 2011 1 commit
  11. 20 Apr, 2011 3 commits
  13. 04 Apr, 2011 2 commits
  15. 01 Apr, 2011 3 commits
  17. 30 Mar, 2011 3 commits
  19. 26 Mar, 2011 1 commit
    • Jeff Hamilton's avatar
      Add com.android.nfc.permission.NFCEE_ADMIN. · 93d8a69c
      Jeff Hamilton authored 
      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
      93d8a69c
  21. 25 Mar, 2011 1 commit
  23. 11 Mar, 2011 1 commit
  25. 10 Mar, 2011 1 commit
  27. 08 Mar, 2011 1 commit
  29. 24 Feb, 2011 2 commits
  31. 18 Feb, 2011 2 commits
    • Martijn Coenen's avatar
      Fix isConnected() implementation. · 6a7ba70e
      Martijn Coenen authored 
      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
      6a7ba70e
    • Martijn Coenen's avatar
      Fix race in NFC tag registry/dispatch. · 10389c11
      Martijn Coenen authored 
      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
      10389c11
  33. 16 Feb, 2011 4 commits
  35. 09 Feb, 2011 1 commit
  37. 01 Feb, 2011 1 commit
  39. 28 Jan, 2011 2 commits
    • Martijn Coenen's avatar
      INfcTag isPresent() should not block and not cause RF activity. · ab2b44b9
      Martijn Coenen authored 
      Use a cached value instead, which is based on the presence check that is running
anyway.

Change-Id: Ifa50ff38e884fa865bb7ba95dde45da39bebf7e8
      ab2b44b9
    • Martijn Coenen's avatar
      Fixed connect() failure from technology->ndef->technology. · 6b3ccb6e
      Martijn Coenen authored 
      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
      6b3ccb6e
  41. 27 Jan, 2011 1 commit
  43. 26 Jan, 2011 2 commits