382cb48848cb3968d5a0088a825706d66cdfbd50 |
|
08-Jul-2016 |
Mikhail Naganov <mnaganov@google.com> |
Protect MIDI framework against client blocks in MidiReceiver.onSend Make the server-side socket non-blocking when creating MidiOutputPort for clients. Thus if a client ceases to read from its side of the socket pair, the server will just fail to write instead of blocking. One drawback is that the MidiOutputPort on the client can't indicate that it has become dysfunctional, but it's not possible without changing the API. Bug: 29413812 Change-Id: I9dfcbdd214a815cea8fd1365324fd78ca459268a
/frameworks/base/core/java/com/android/internal/midi/MidiDispatcher.java
|
7eb441cb4abcd3230a4d243469c5044f49e707c8 |
|
12-May-2015 |
Mike Lockwood <lockwood@google.com> |
MidiManager: Address API Council feedback: Rename MidiDeviceInfo.getPortList() to getPorts() Rename MidiManager.getDeviceList() to getDevices() Rename MidiReceiver.onReceive() to onSend() Replace MidiManager.DeviceOpenCallback and BluetoothOpenCallback with new interface MidiManager.OnDeviceOpenedListener Add MidiSender.onConnect() and onDisconnect() Add MidiReceiver.onFlush() Ensure that MidiReceiver max message size is immutable Bug: 21044677 Change-Id: I7711734a45e831e9744849a6f569e906feff9f80
/frameworks/base/core/java/com/android/internal/midi/MidiDispatcher.java
|
b6f50d357bd3d4d296be6bb047f5ce93a79cbca1 |
|
08-Apr-2015 |
Mike Lockwood <lockwood@google.com> |
Add support for flushing MIDI all scheduled MIDI events on a port Change-Id: I39d7862540d4d4b9e2df1265f9dd253541adb4c2
/frameworks/base/core/java/com/android/internal/midi/MidiDispatcher.java
|
d1b16fe2fb7527eee214898263ec4d6dabbfb0b4 |
|
30-Mar-2015 |
Mike Lockwood <lockwood@google.com> |
Move MIDI utilities for internal use to com.android.internal.midi package Change-Id: I7393ae1d4bca61667fb6ee809a7aa22c5c48de56
/frameworks/base/core/java/com/android/internal/midi/MidiDispatcher.java
|