Did a bit of research...
Here's what's expected:
https://code.google.com/p/media-button- ... tail?id=16Looking at the DSub source, and comparing it with some old Subsonic source (
https://github.com/haxzamatic/Subsonic- ... nifest.xml), and other nearby entries, it looks like the action below should be enclosed in intent-filter tags... (BluetoothIntentReceiver included for comparison):
- Code: Select all
<receiver android:name="github.daneren2005.dsub.receiver.MediaButtonIntentReceiver">
<action android:name="android.intent.action.MEDIA_BUTTON" />
</receiver>
<receiver android:name="github.daneren2005.dsub.receiver.BluetoothIntentReceiver">
<intent-filter>
<action android:name="android.bluetooth.a2dp.action.SINK_STATE_CHANGED"/>
<action android:name="android.bluetooth.headset.profile.action.CONNECTION_STATE_CHANGED"/> <!-- API Level 11 -->
<action android:name="android.bluetooth.device.action.ACL_CONNECTED"/>
<action android:name="android.bluetooth.device.action.ACL_DISCONNECTED"/>
</intent-filter>
</receiver>
But, I'm a tyro, I could be wrong. But I think that's it, according to
http://developer.android.com/guide/topi ... ement.html , a receiver can contain an event-filter or meta-data and the intent-filter must contain the actions.