title: USB_DEVICE_ATTACHED only startsActivity of Galaxy S3 ICS
body: <p>Recently I've been trying to receive the intent android.hardware.usb.action.USB_DEVICE_ATTACHED using a broadcast receiver as per all the samples and examples that I've seen. </p>
  
  <p>I've declared a reciever in the manifest;</p>
  
  <pre><code>&lt;receiver android:name=".UsbDeviceReceiver"&gt;
          &lt;intent-filter&gt;
              &lt;action android:name="android.hardware.usb.action.USB_DEVICE_ATTACHED" /&gt;
              &lt;action android:name="android.hardware.usb.action.USB_DEVICE_DETACHED" /&gt;
              &lt;category android:name="android.intent.category.DEFAULT" /&gt;
          &lt;/intent-filter&gt;
      &lt;/receiver&gt;
      &lt;meta-data android:name="android.hardware.usb.action.USB_DEVICE_ATTACHED" 
                  android:resource="@xml/device_filter"/&gt;
  </code></pre>
  
  <p>I have also done similar in the activity code - onStart and OnStop register/unregister the receiver.</p>
  
  <pre><code>    IntentFilter filter = new IntentFilter();
      filter.addAction(UsbManager.ACTION_USB_DEVICE_ATTACHED);
  
      registerReceiver(mUsbReceiver, filter);
  </code></pre>
  
  <p>However, I am finding that the intent is just caught. Observing logcat I can see that attaching a usb device looks for activities to start, while detaching broadcasts the detatch intent. According to the aforementioned samples, this should not be the case.</p>
  
  <p>Am I missing something drastic concerning metadata? I have no problems at all with android.hardware.usb.action.USB_DEVICE_DETACHED. Perhaps this is a bug with the android version installed on the galaxy s3? Perhaps this is an ICS 'feature'.</p>
  
  <p>Any relavent information is welcome!</p>