e0a6ca64fa
Previously when a MidiManager client opened a virtual or Bluetooth device, the client bound directly to the virtual device's MidiDeviceService or BluetoothMidiDevice's IMidiDeviceServer for the given BluetoothDevice. Only USB devices were opened in MidiService. Now opening any type of MIDI device is done via IMidiManager.openDevice() or IMidiManager.openBluetoothDevice(). MidiService tracks all connnections between clients and devices. Services that implement virtual devices must now require android.permission.BIND_MIDI_DEVICE_SERVICE so only MidiService can bind to these services. Bug: 21044677 Change-Id: I7172f7b1e0cbfe4a2a87dff376c32dc9b41aa563
19 lines
748 B
XML
19 lines
748 B
XML
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
|
|
package="com.android.bluetoothmidiservice"
|
|
>
|
|
|
|
<uses-feature android:name="android.hardware.bluetooth_le" android:required="true"/>
|
|
<uses-feature android:name="android.software.midi" android:required="true"/>
|
|
<uses-permission android:name="android.permission.BLUETOOTH"/>
|
|
|
|
<application
|
|
android:label="@string/app_name">
|
|
<service android:name="BluetoothMidiService"
|
|
android:permission="android.permission.BIND_MIDI_DEVICE_SERVICE">
|
|
<intent-filter>
|
|
<action android:name="android.media.midi.BluetoothMidiService" />
|
|
</intent-filter>
|
|
</service>
|
|
</application>
|
|
</manifest>
|