Android boot from several methods, not to listen to receive_boot_completed processing methods

The first: monitoring receive_boot_completed, which is the boot event

The second type: Monitor SD card mount event boot always scan SD card? Monitoring SD Card event also has a similar boot effect, special app installed in the case of SD card some OS is not crawl receive_boot_completed

The Third Kind: android:installlocation= "internalonly", restrict the installation location of the app, so that it can crawl to receive_boot_completed

The fourth kind: listens to the telephone or the SMS event, the handset must call to send and receive the text message? In case it doesn't work, it is still possible to go back and beg for the second.

<uses-permission android:name= "Android.permission.RECEIVE_BOOT_COMPLETED"/>

        <receiver android:name= "Com.example.receiver.SystemEventReceiver"               android:permission= " Android.permission.RECEIVE_BOOT_COMPLETED ">            <intent-filter>                <action android:name=" Android.intent.action.BOOT_COMPLETED "/>             </intent-filter>           <intent-filter>                <action Android:name= "Restartserivcesforsystemeventreceiver"/>               </intent-filter>           <intent-filter>        <action android:name= "Android.intent.action.MEDIA_MOUNTED"/>        <action android:name= " Android.intent.action.MEDIA_UNMOUNTED "/>        <action android:name=" Android.intent.action.MEDIA_EJECT "/ >        <data android:scheme= "file" >        </data>              </intent-filter>        </receiver >

Android boot from several methods, not to listen to receive_boot_completed processing methods