History log of /frameworks/base/media/java/android/media/midi/IMidiDeviceServer.aidl
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
80299748cc7ed5f59cb65122459b036b74150d4a 05-Apr-2016 Phil Burk <philburk@google.com> MidiDevice: fix connectPorts for same Process

If connectPorts() was called for a device in the same process then
the connection would die when the ParcelFileDescriptor was closed.

Bug: 26406775
Change-Id: Id0538452593b4761ac2a93d366ade76d2e35ce73
Signed-off-by: Phil Burk <philburk@google.com>
/frameworks/base/media/java/android/media/midi/IMidiDeviceServer.aidl
acd4321872387212bbd956e134faf22eee4bbadc 11-Jun-2015 Mike Lockwood <lockwood@google.com> MidiDeviceServer: Fix race condition in setting device server's mDeviceInfo

This made it unsafe to open ports on a device from the MidiManager onDeviceOpened callback

Bug: 21760692
Change-Id: I536acdf574a3ccecdb66a8fde87089538e8bb1ef
/frameworks/base/media/java/android/media/midi/IMidiDeviceServer.aidl
e0a6ca64fac5bd4f10139321604031816e90adb4 04-Jun-2015 Mike Lockwood <lockwood@google.com> MidiManager: proxy all requests to open devices through MidiService

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
/frameworks/base/media/java/android/media/midi/IMidiDeviceServer.aidl
f0a41d1c591193fbe02c9ddbaf24c79af4da9972 24-Mar-2015 Mike Lockwood <lockwood@google.com> Add support for Bluetooth MIDI devices

The Bluetooth MIDI devices are handled in the BluetoothMidiService APK.
Apps wishing to connect to Bluetooth MIDI devices call MidiManager.openBluetoothDevice()
which binds to BluetoothMidiService in a similar way as virtual devices are implemented.

Change-Id: Ie3fbca757928fd7873a009f9bf9e0ce0be487da6
/frameworks/base/media/java/android/media/midi/IMidiDeviceServer.aidl
46326e59a0a19367d4158c027d56d4b8440e8d3d 06-Mar-2015 Mike Lockwood <lockwood@google.com> MidiDevice: Add support for making direct connections between ports

The output port of one device can be connected to the input port of another
device using the new MidiDevice.connectPorts() method.
This allows an application to direct the output of one device directly
to the input port of another without having to copy data from one to another.

Change-Id: I4d361c4e0950b9b9516b0c2f0c158677b1aca208
/frameworks/base/media/java/android/media/midi/IMidiDeviceServer.aidl
4a3d7ed45d98ad2fe900221755845b87f26b554a 06-Mar-2015 Mike Lockwood <lockwood@google.com> MIDI Manager: Add explicit close mechanism for input and output ports

Relying on errors from closing the file descriptor is not reliable
and was resulting in file descriptor leaks in device servers.

Change-Id: Ib5cc22dba493eae6608a12cc6d4178d8390da77b
/frameworks/base/media/java/android/media/midi/IMidiDeviceServer.aidl
b673770f7172d4fca9bc05de1f36bc53e93eb247 20-Feb-2015 Mike Lockwood <lockwood@google.com> Add MIDI Manager API tweaks:

- Change the package name from android.midi to android.media.midi

- Add option for specifying a Handler for DeviceCallback notifications

Change-Id: Ia9e9817a651c06299f4e02ee1da3c9666ff64cb9
/frameworks/base/media/java/android/media/midi/IMidiDeviceServer.aidl