| 2c10311a01a9414a8efcedb267a45289a1617888 |
|
15-May-2012 |
Martijn Coenen <maco@google.com> |
NFC API documentation.
Added docs for beam Uri push and added some sanity checks on params.
Change-Id: I7c43b71c8a9ca4f742933d2d5b9473e0e2451dd3
/frameworks/base/core/java/android/nfc/NfcActivityManager.java
|
| 20e8dd9f9e7cff63c83e36a1761538a04c224cc1 |
|
13-Apr-2012 |
Martijn Coenen <maco@google.com> |
Unhide new Beam push APIs.
Also added support for multiple Uris, removed mimeType argument.
Change-Id: Iad2c4d0e36a174080d7bc9c9c8ab893f90231d02
/frameworks/base/core/java/android/nfc/NfcActivityManager.java
|
| 20fe5378d73a1c01f8d5a6d3c53c2b4802a0a680 |
|
05-Apr-2012 |
Martijn Coenen <maco@google.com> |
Make sure initial activity state is correct.
Change-Id: Ic6199b42e59afa06a0f38f866e2924b84cd234b3
/frameworks/base/core/java/android/nfc/NfcActivityManager.java
|
| 1d7e9062330a5a02247752de32a68ecbeba82783 |
|
04-Apr-2012 |
Nick Pelly <npelly@google.com> |
First cut at Bluetooth Beam
Change-Id: I37e5759515ff8779095b6d8adf5ad9c456fa8529
/frameworks/base/core/java/android/nfc/NfcActivityManager.java
|
| 8ce7a27770735791b5c38e4128f4ab9cee86bc43 |
|
21-Mar-2012 |
Nick Pelly <npelly@google.com> |
Use Application#registerLifecycleEvents() instead of a Fragment for Beam.
Fragments don't work as desired if called after life-cycle events
such as onDestory() or onSaveInstanceState().
The new approach doesn't work after onDestroy() either, but we can more
easily detect this now. For pre-JB apps, we will log an error, and for
JB and onwards we will throw.
Update documentation to make these rules clear, and to encourage
the use of a single Activity per API call, and to make the call
in onCreate().
Bug: 5199662
Bug: 5994691
Bug: 6034901
Bug: 6125297
Change-Id: Ib0dde6abfa44cd56c7ddc13ba0ad0e83bbe30058
/frameworks/base/core/java/android/nfc/NfcActivityManager.java
|
| 2ec83936a1c05d3286cb5656566e905a50d871de |
|
14-Oct-2011 |
Martijn Coenen <maco@google.com> |
Remove NfcFragment from activity when no longer sharing.
This fixes scenarios where the same activity sets, unsets
and re-sets an NdefMessage and/or callback.
Bug: 5454848
Change-Id: I5ed98047b9cfe90d2f48656d978f2d08bb4bf0cc
/frameworks/base/core/java/android/nfc/NfcActivityManager.java
|
| 3433a8ae5abf7c518277e2e00c141e1dec83600c |
|
02-Sep-2011 |
Martijn Coenen <maco@google.com> |
Fix Activity ref-leak in NFC dispatch API.
Change-Id: I7b1ee6927747b12eb94cfd6ece40c2c73003f07f
/frameworks/base/core/java/android/nfc/NfcActivityManager.java
|
| c84c89a6cacaf16c1ba41f57cc1aecdb150e85f9 |
|
23-Aug-2011 |
Nick Pelly <npelly@google.com> |
Improve NDEF push API
Introduce
setNdefPushMessage()
setNdefPushMessageCallback()
setNdefPushCompleteCallback()
Deprecate public API
enableForegroundNdefPush()
disableForegroundNdefPush()
Hide & Deprecate staged (public but never released) API
enableForegroundNdefPushCallback()
The new API's do not require the application to explicitly call
enable()/disable() in onPause()/onResume(), we use a Fragment behind
the scenes to manager this automatically.
NDEF Push can be disabled by using a null parameter, so each
enable()/disable() pair is collapsed to a single set() call.
Application code should now look something like:
public void onCreate() {
NfcAdapter adapter = NfcAdapter.getDefaultAdapter(this);
if (adapter != null) { // check that NFC is available on this device
adapter.setNdefPushMessage(myNdefMessage, this);
}
}
And that's it - no need to explicitly hook into onPause() and onResume() events.
Also - introduce a generic NfcEvent class that is provided as a parameter on
all NFC callbacks. Right now it just provides the NfcAdapter, but using
the wrapper classes allows us to add more fields later without changing
the callback signature. (i'm thinking Bluetooth).
Change-Id: I371dcb026b535b8199225c1262eca64ce644458a
/frameworks/base/core/java/android/nfc/NfcActivityManager.java
|