256 Bytes / Block Size = 4 / Num Blocks = 64 (0-63) (0-0x3f)
Type: Tag-it HF-I Plus Chip (thats hf-i)
Manufacturer: Texas Instruments (France)
See datasheet attached at the end
This page was initially a copy from work done by Jesse Chen http://www.jessechen.net/blog/how-to-nfc-on-the-android-platform/
I will be updating it with my own experience as I build my own NFC based application
I am starting with the experiences detailed by Jesse.
More information on Android NFC can also be found here http://developer.android.com/guide/topics/connectivity/nfc/index.html
Someone else struggling with this
Starting with Android 2.3, the platform includes an NFC stack and framework API that allows you to read/write to NDEF (NFC Forum Data format) tags. For Android smartphones, that means the requirement is to be running at least Android 2.3 and have a NFC chip on the phone.
My application is targeted for Gingerbread so that it can be used with some of the cheaper Android devices out of China.
In the Android Manafest use the following to make an NFC application
To begin, both phones have to be running the same Activity in the foreground in order to work. Let’s call this Activity ‘NfcAddFriendsActivity’.
In NfcAddFriendsActivity’s onCreate method, we have the following code:
This sets up the different intents that are needed in order for p2p to work. mNfcPendingIntent is a generic PendingIntent that will be delivered to this activity, Android fills the intent later with the details from the discovered tag before sending it to this activity. The nDefDetected IntentFilter is set to filter for the intentNfcAdapter.ACTION_NDEF_DISCOVERED with the mime type “text/plain”. So there will be a dispatch to the foreground Activity when Android receives an intent matching the IntentFilter we just created.
The next step is to enable pushing NDEF messages and receiving NDEF messages. That means in our onResumemethod, we call enableNdefExchangeMode which looks like:
These method calls are what allows our device to initiate p2p communiation via NFC. NfcUtils.getUidAsNdef is the method that creates a NDEF message with mime type “text/plain” with the user’s UID as the payload. enableForegroundNdefPush will push this message to the other device. enableForegroundDispatch will set up the listener for the intent that we are filtering for such that when it detects an intent matching the intent filter, it calls our activity’s onNewIntent method:
Here, it parses the received NDEF message and gets the payload which should be the other user’s UID. Then I callfireFriendRequest which is a method that we can assume sends a friend request to the UID that was given.
NfcUtils.getNdefMessages is below, exactly the same as the Sticky Notes demo:
Let’s create a way for people to check in to places simply by tapping on a NFC tag. To start, we need to write some data onto a NFC tag, such that when the user taps on the tag, an Activity will launch based on the type of data stored on the tag. Well, each Facebook “Place” has an id associated with it, so lets write those ids onto NFC tags such that when a user taps on the tag, we can launch the correct Activity, passing the id as a parameter.
I hold the placeid in placeidToWrite, and call enableTagWriteMode. An alert dialog pops up prompting the user to tap the phone to the tag to write. enableTagWriteMode below:
I create a new IntentFilter for the intent NFCAdapter.ACTION_TAG_DISCOVERED, which is the intent to start an Activity when a NFC tag is discovered. Then, like in the adding friends example, enableForegroundDispatch is called to dispatch a discovered tag to the foreground activity. Once this is all set up, and the user taps the phone onto a tag, the ACTION_TAG_DISCOVERED intent is detected and onNewIntent is called:
NfcUtils.getPlaceidAsNdef takes the placeid and creates a NDEF message with mimetype “application/vnd.facebook.places”, which is a custom and vendor-specific mimetype that I made up to distinguish the different NFC tags (places, url, pages) for Facebook. That way, when the phone reads a NFC tag, it knows which Activity to launch (I detect mimetype “application/vnd.fb.places” – I should launch this specific Activity from Facebook).
Once you construct the NDEF message, you need to actually write it to the tag. NfcUtils.writeTag looks like:
And that’s how you write to a tag. Now, any person with an Android NFC-enabled phone with this build of Facebook for Android would just have to touch their phone onto the sticker (doesn’t need Facebook to be in the foreground), and wham, it takes you straight to the checkin activity with the place already set.
In the AndroidManifest, we need to write intent-filters that captures the different intents we created with our examples above. Such that when the Android phone receives the intent, it knows where to pass it along. For checking in, we have an Activity called, lets say, CheckInActivity. Within the activity, I am going to write an intent-filter that matches the exact intent I created in the NfcWriteCheckinActivity.
Notice the exact specification of the mimetype, which is the custom vendor mimetype that I created for checking in to places. That way, I can have one application, like Facebook, pass different intents to different Activities within Facebook.
Within CheckInActivity, it is fairly simple to extract the placeid and open the checkin activity. You do it in the onResumemethod of CheckInActivity:
Note: The user ID and the place ID are all written and transmitted in plaintext with no authentication or encryption. FWIW, that may or may not be acceptable for some apps. I haven’t looked into the security implications on NFC, but if you are passing confidential data, you will have to find a way to encrypt the data before writing, verifying the integrity of the data when receiving, and authenticating the entity that sent the data. Since this was a personal hackathon project, I did not implement any security features.