History log of /frameworks/base/core/java/android/nfc/NdefMessage.java
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
d3cb80d2af423eccdeef2697a1ca45eadb241988 27-Jan-2012 Nick Pelly <npelly@google.com> Fix doc bug.

Change-Id: Ib7361abb0461d4295e889c505dd45e3a40193451
/frameworks/base/core/java/android/nfc/NdefMessage.java
1f5badc1cb08f10ddf4b09aaaf34060a23999a51 24-Jan-2012 Nick Pelly <npelly@google.com> Add NdefMessage.getByteLength(), and more minor fixes:

Remove NdefMessage from dispatch(). It's already in the Tag.
/*package*/ cleanup
Fix sitemap after removal of NFCDemo

Change-Id: Ie1f6d9ea98144aa97f56bb709a33f5d0ef916e8b
/frameworks/base/core/java/android/nfc/NdefMessage.java
c97a552023c3c71079b39092e80c9b44f25a789b 05-Jan-2012 Nick Pelly <npelly@google.com> Improve NDEF API's

o Add NdefRecord.toMimeType()
Maps the record to a MIME type
o Add NdefRecord.toUri()
Maps the record to a URI
o Add hidden NfcAdapter.dispatch()
Helps test the dispatch path.
o Modify createMime(), createUri() and createExternal():
Do not try and strictly follow RFC requirements for URI or MIME content
types. This just leads to heartbreak - the RFC requirements are too strict.
For example RFC1341 forbids the use of '.' in a MIME type, however this is in
common use in types such as "application/vnd.companyname". I think the best
approach is to only remove 'obvious' whitespace issues, and to convert
uppercase to lowercase as per Android guidelines.

Change-Id: Id686f5f3b05b2dceafad48e1cfcbdb2b3890b854
/frameworks/base/core/java/android/nfc/NdefMessage.java
a356bf1cd81614a94ef6c720998792480ade4c84 14-Dec-2011 Nick Pelly <npelly@google.com> Rewrite NDEF parsing in Java, clean-up API.

o Lots of documentation fixes.
o Add NdefMessage(NdefRecord ... records) ctor
o Add NdefRecord.createMime()
o Add NdefRecord.createExternal()
o Add toString(), equals() and hashCode() implementations
o Deprecate NdefRecord(byte[]) and NdefRecord.toByteArray()
o Remove framework dependency on libnfc_ndef.so
o Remove NfcAdapter.getDefaultAdapter(), its been deprecated a while

next step:
o Attempt to move NdefMessage -> Intent conversion into NDEF, and
make it CTS tested. This will ensure consistent NDEF -> Intent
mapping across all Android devices.

Change-Id: Ifed4910caa9a1d6bad32dbf0a507ab22bca35e22
/frameworks/base/core/java/android/nfc/NdefMessage.java
3ebd59bb5dc9f421fd2b9b789ea824746d58fff7 03-Nov-2010 Jason parks <jparks@google.com> Return a zero length byte from toByteArray instead of null.

Change-Id: I67b388099c72a0d2ec6b429caea8f29bf8f7a75a
/frameworks/base/core/java/android/nfc/NdefMessage.java
11b075e218b9921a953eeebe73fcd1a8a81f764b 28-Oct-2010 Nick Pelly <npelly@google.com> Hide some NFC API's.

We are leaving enough API so that you can see when any Tag is discovered,
get its ID, and get its NDEF messages.

But for advanced use - creating tag connections and writing messages - we have
2 problems. Firstly a lot of the code is untested
(RawTagConnection.transceive()), or in some cases known not to work
(NdefTagConnection.write()). Secondly, there is still debate about how to
best expose information about Tags.

The set of data/methods exposed for a Tag changes completely depending on the
tag technology. There may be multiple sets of technology implemented in a
single tag. Tag A may have technology X and Y, Tag B may have technology Y
and Z. Furthermore, some NFC controllers will be not be able to use all
technologies, and so Android Device 1 may see technology X and Y on Tag A but
Android device 2 may only see technology X. So we have a pretty challenging
set of constraints to work under, and we are not convinced the current Tag and
NdefTag class is the best approach going forwards.

The Tag application should be able to remain unbundled, since it just needs to
get incoming NDEF Messages.

Change-Id: Ic09f094f33794e10f8d730fffe011c9a5957e0ac
Signed-off-by: Nick Pelly <npelly@google.com>
/frameworks/base/core/java/android/nfc/NdefMessage.java
da83f513ca661cd2bb1e6f1c8b64b716205bae48 22-Oct-2010 Jeff Hamilton <jham@android.com> Unhide some NFC APIs that are required for the Tag app.

Change-Id: Ic64e00476132dbf4644de5c465e06fe11a264508
/frameworks/base/core/java/android/nfc/NdefMessage.java
c9f7890a203a013646650a695157277df81b6a17 15-Oct-2010 Scott Main <smain@google.com> Revise some javadocs for NFC; add package description

Change-Id: I60223e2ad24af98b3b16a74960365185096ae614
/frameworks/base/core/java/android/nfc/NdefMessage.java
590b73bc5b8e5f7b59bff1d9264a52388a5162e6 12-Oct-2010 Nick Pelly <npelly@google.com> NFC API revision round 2.

- Add the second half of the new NFC API: NfcAdapter, Tag, NdefTag,
RawTagConnection, NdefTagConnection.
- Add implementations for all of the new NFC API.

Change-Id: I8da9fd1d2971ed2c8b76f2a93f207fa9e305b0f6
Signed-off-by: Nick Pelly <npelly@google.com>
/frameworks/base/core/java/android/nfc/NdefMessage.java
dc993791fc3cf7a270921f7419b0c6b875bbd92b 04-Oct-2010 Nick Pelly <npelly@google.com> New API stubs: NdefMessage and NdefRecord.

NDEF Messages and NDEF Record data classes.

Change-Id: I9b7114773281b0eb9680f595c95ac79943d2903b
Signed-off-by: Nick Pelly <npelly@google.com>
/frameworks/base/core/java/android/nfc/NdefMessage.java