在機器開機過程中，可以抓取到以下的正常logcat資訊：

//setp1
I/NfcService( 3809): Starting NFC service
D/NFCJNI  ( 3809): NFC Service : loading JNI
I/RegisteredComponentCache( 3809): ComponentInfo: ResolveInfo{41344108 
com.android.apps.tag.TagViewer p=0 o=0 m=0x108000}, techs: android.nfc.tech.Ndef, 
W/NfceeAccess( 3809): could not find /etc/nfcee_access.xml, no NFCEE access allowed
I/NfceeAccess( 3809): read 0 signature(s) for NFCEE access
D/NfcService( 3809): checking on firmware download
 

下面是硬體不支援NFC的異常logcat資訊：

I/NfcService( 3485): Starting NFC service
D/NFCJNI  ( 3485): NFC Service : loading JNI
W/NfceeAccess( 3485): could not find /etc/nfcee_access.xml, no NFCEE access allowed
I/NfceeAccess( 3485): read 0 signature(s) for NFCEE access
D/NfcService( 3485): checking on firmware download
D/NfcService( 3485): NFC is on. Doing normal stuff
I/NfcService( 3485): Enabling NFC
D/NFCJNI  ( 3485): Start Initialization
E/NFCJNI  ( 3485): hw_get_module() failed.
D/NFCJNI  ( 3485): Terminating client thread...
W/NfcService( 3485): Error enabling NFC
 

來看正常logcat資訊setp1,NfcService 是application，它的onCreate()方法：

@Override
    public void onCreate() {
        super.onCreate();

        mNfcTagService = new TagService();
        mNfcAdapter = new NfcAdapterService();
        mExtrasService = new NfcAdapterExtrasService();

        Log.i(TAG, "Starting NFC service");
        
        //setp2：NFC Service : loading JNI
        mDeviceHost = new NativeNfcManager(this, this);

        HandoverManager handoverManager = new HandoverManager(mContext);
 		
 	//NfcDispatcher主要負責tag訊息處理，並派發Intent訊息，啟動Activity。
 	mNfcDispatcher = new NfcDispatcher(this, handoverManager); 
 	    
 	mP2pLinkManager = new P2pLinkManager(mContext, handoverManager); 
 	mSecureElement = new NativeNfcSecureElement(mContext);                 
 	    
        //setp3:could not find /etc/nfcee_access.xml, no NFCEE access allowed 
        mNfceeAccessControl = new NfceeAccessControl(this); 
        
   //把mNfcAdapter 作為Service 新增到系統服務中，ServiceManager.getService("nfc")可以獲取到binder                      
        ServiceManager.addService(SERVICE_NAME, mNfcAdapter);
 	    
 	updatePackageCache();         
 	    
 	//setp4：checking on firmware download        
 	new EnableDisableTask().execute(TASK_BOOT); // do blocking boot tasks 
    }
 

Setp2：NFC Service loading JNI，這一部分是在NativeNfcManager.java中處理的  

//載入jni編譯生成的nfc_jni.so.通過NativeNfcManager呼叫jni部分
static {
        System.loadLibrary("nfc_jni");
    }

//NativeNfcManager 構造方法
public NativeNfcManager(Context context, DeviceHostListener listener) {
        mListener = listener;

        //setp2-1:com_android_nfc_NativeNfcManager.cpp的native方法
        //com_android_nfc_NfcManager_init_native_struc(JNIEnv *e, jobject o)
        initializeNativeStructure();
        mContext = context;
    }

Setp2-1:com_android_nfc_NfcManager_init_native_struc(),初始化nfc_jni_native_data結構體

static jboolean com_android_nfc_NfcManager_init_native_struc(JNIEnv *e, jobject o)
{ 
  /* Initialize native structure */   
  // 涉及到nfc_jni_native_date結構體的定義在com_android_nfc.h
   nat = (nfc_jni_native_data*)malloc(sizeof(struct nfc_jni_native_data));
   if(nat == NULL)
   {
      ALOGD("malloc of nfc_jni_native_data failed");
      return FALSE;   
   }
   memset(nat, 0, sizeof(*nat));

   /* Initialize native cached references */ 
   //通過jni 呼叫java 層的方法
   cached_NfcManager_notifyNdefMessageListeners = e->GetMethodID(cls,
      "notifyNdefMessageListeners","(Lcom/android/nfc/nxp/NativeNfcTag;)V");

   cached_NfcManager_notifyTransactionListeners = e->GetMethodID(cls,
      "notifyTransactionListeners", "([B)V");
         
   cached_NfcManager_notifyLlcpLinkActivation = e->GetMethodID(cls,
      "notifyLlcpLinkActivation","(Lcom/android/nfc/nxp/NativeP2pDevice;)V");
         
   cached_NfcManager_notifyLlcpLinkDeactivated = e->GetMethodID(cls,
      "notifyLlcpLinkDeactivated","(Lcom/android/nfc/nxp/NativeP2pDevice;)V"); 
      
   cached_NfcManager_notifyTargetDeselected = e->GetMethodID(cls,
      "notifyTargetDeselected","()V");   
   
   //nfc_jni_cache_object 原型在com_android_nfc.cpp中，有什麼作用，做什麼動作暫時沒有搞清楚？
   if(nfc_jni_cache_object(e,"com/android/nfc/nxp/NativeNfcTag",&(nat->cached_NfcTag)) == -1)
   {
      ALOGD("Native Structure initialization failed");
      return FALSE;
   }
         
   if(nfc_jni_cache_object(e,"com/android/nfc/nxp/NativeP2pDevice",&(nat->cached_P2pDevice)) == -1)
   {
      ALOGD("Native Structure initialization failed");
      return FALSE;   
   }
   TRACE("****** Init Native Structure OK ******");
   return TRUE;
}

Setp3：解析/etc/nfcee_access.xml,NfceeAccessControl.java主要用來解析nfcee_access,xml並做一些證書和安全方面的check。nfcee_access.xml的檔案內容：

<?xml version="1.0" encoding="utf-8"?>
<resources xmlns:xliff="urn:oasis:names:tc:xliff:document:1.2">
    <!-- The built in list of signatures and package names that are allowed
    access to the NFCEE (Secure Element).

    Format:
    <signer android:signature="SIGNATURE">
        <package android:name="PACKAGE_NAME" />
        ...
    </signer>       
     Example：
    <signer android:signature="308201c53082012ea00302010202044ebb27cc300d06092a864886f70d01010505003026310f300d060355040a1306476f6f676c65311330110603550403130a4e69636b2050656c6c793020170d3131313131303031323432385a180f32313131313031373031323432385a3026310f300d060355040a1306476f6f676c65311330110603550403130a4e69636b2050656c6c7930819f300d06092a864886f70d010101050003818d00308189028181008d43e546b3f5572707a095ced120d8f06781fa162bcf0ffa0ed0ecb48eb90ed009f65a5a1afd69fb4d38cf24e931b69b061741b8c7ca9f785ba59509e883f5a308f5e2da3c496bb362a2229da8f95f08a92f7f94c829c56e78a34e5147d138d0be0671cb5b7caceaffae6199ba544496a7645e7df3c9f02c5ac156eb0501584f0203010001300d06092a864886f70d0101050500038181003511bcb73651a7927db71ad76e4f6dc5ba121c941ae0fd4dfe519aae8775520b204a5e3cdad2c61ad41aff2c510dbe3376a7578d8aba00f35633e1ae72c91ec83d80eac6f5f081fb8361c6c30c47b0a17932d859d7e991e02cba410a82b35234b2b1bc859e50fe308bf9b64b71a8046777300c07ead159287c187b8865e23f23" />
    <signer android:signature="3082044c30820334a003020102020900de7695041d7650c0300d06092a864886f70d01010505003077310b3009060355040613025553311330110603550408130a43616c69666f726e6961311630140603550407130d4d6f756e7461696e205669657731143012060355040a130b476f6f676c6520496e632e3110300e060355040b1307416e64726f6964311330110603550403130a476f6f676c65204e4643301e170d3131303332343031303332345a170d3338303830393031303332345a3077310b3009060355040613025553311330110603550408130a43616c69666f726e6961311630140603550407130d4d6f756e7461696e205669657731143012060355040a130b476f6f676c6520496e632e3110300e060355040b1307416e64726f6964311330110603550403130a476f6f676c65204e464330820120300d06092a864886f70d01010105000382010d00308201080282010100e6ff3defe92aa10d71eb0fa6408bc036b7e243eeed68a6a4763dc7a52a31757cdac61fe510bb73c716e4000104265b347fcecef4c42bf1e1379dd0a876f028227fbbc1f9bdd5d713b2f6a935a379d2cba9c96f92d2d0787c11f1eb19548008a6a072b34b91836cfa0ae1276780e9007530166986a11c9cef46cef7c704806dde9431fb60284d120ab0e7de1d633f07687d468c51139afffdc6bc9a207ca904b8be1da0aa7b4e97756f43606488be5cae3c68e8bb7942cdf51607c930a2fcda655b75d0759cba89ad06e739bd0ba29b1f404296c2c0a85a847f5ab0d067c6c3ec9c49212042ac63a7e53b546c65b46080b4e3e680e23e1f77cfe7f6de744b1a65020103a381dc3081d9301d0603551d0e04160414a2e89064b05d08865c34db930a9d840050117aec3081a90603551d230481a130819e8014a2e89064b05d08865c34db930a9d840050117aeca17ba4793077310b3009060355040613025553311330110603550408130a43616c69666f726e6961311630140603550407130d4d6f756e7461696e205669657731143012060355040a130b476f6f676c6520496e632e3110300e060355040b1307416e64726f6964311330110603550403130a476f6f676c65204e4643820900de7695041d7650c0300c0603551d13040530030101ff300d06092a864886f70d010105050003820101003771870ce87c3c52ea84899230c6e962d94b4d5f1293c25d88261541fd90b5555d1285cef3b8312c3f5df691a8aae04cb981b305e427fd1d2d9e1987e1d29078f13c8452990f1821980263d8d4bd36519348d8d8ba26d8b99fbf09f5fd3ebb0ea3c2f0c9376f1e1fca76f3a6a405429d081b752a7a90b756e9ab44da41abc8e1e8f88ac2758da743fb73e650719a57840ccb6b7add21b99fc681e456e1872c223d5c074adf55f6abda268c2d8b64ea0a8845eecd968f92b493127e75c753c3ff30cbc678b51c9f52961472f17da20a0dc6274aa2463434c1a9b614df697d8ff5ca8101e7a25c7db3fb055d65569c04b01d389cabba57b3a1703ec2e74a88d334">
        <package android:name="com.foo.my.awesome.wallet" />
        <package android:name="com.foo.my.awesome.wallet.tests" />
    </signer>      -->
</resources>

 我的理解nfcee_access.xml是用來控制一些Apps對NFC的訪問的，可能用於手機錢包，手機支付等安全性要求高的應用中。不知道對不對,歡迎探討。

             Setp4:用以個AsyncTask來後臺處理，檢測NFC 是否開啟，NFC是否具備開啟的環境等問題。如果沒有開啟，呼叫Jni初始化NFC。
             以上是根據logcat資訊來一步一步分析的。還有背後沒有發現的資訊，NfcAdapter的初始化.NfcService 作為一個application啟動時，會建立一個ContextIml的物件。在               ContextIml中有如下code：

tatic{

registerService(NFC_SERVICE, new ServiceFetcher() {

                public Object createService(ContextImpl ctx) {

                    return new NfcManager(ctx);

                }});

}

在NfcManager的建構函式中，呼叫了NfcAdapter.getNfcAdapter(context)，建立NFC Adapter。

public static synchronized NfcAdapter getNfcAdapter(Context context) {
……

            sService = getServiceInterface();//獲取NFC服務介面

        ……

            try {

                sTagService = sService.getNfcTagInterface();//獲取NFC tag服務介面

            } catch (RemoteException e) {

            }

        ……

        NfcAdapter adapter = sNfcAdapters.get(context);

        if (adapter == null) {

            adapter = new NfcAdapter(context);

            sNfcAdapters.put(context, adapter);

        }
       return adapter;

}

private static INfcAdapter getServiceInterface() {//獲取NFC服務介面

        IBinder b = ServiceManager.getService("nfc");

        if (b == null) {
           return null;

        }

        return INfcAdapter.Stub.asInterface(b);

}

我們看看getServiceInterface()方法，呼叫ServiceManager.addService()將NfcAdapterService的例項新增到系統的服務列表中，這裡我們呼叫ServiceManager.getService(“nfc”)獲取到了服務端的NfcAdapterService物件的例項。
在NfcAdapterService類中提供了getNfcTagInterface介面，用於獲取遠端服務端的TagService物件的例項。
如果一切正常，那麼將建立NfcAdapter的例項，在其建構函式中，建立了NfcActivityManager的例項。
有張圖可以更說明問題，且很清晰：