frameworks_base.git - frameworks/base

	Commit message (Collapse)	Author	Age	Files	Lines
*	BLE-MIDI: change binding for BluetoothMidiService	Phil Burk	2015-11-10	1	-2/+15
\| \| \| \| \| \| \| \| \| \| \|	Add a remote call addBluetoothDevice() using AIDL. This was needed because onBind() is only called once. Bug: 23219556 Bug: 23760886 Change-Id: Id7554ca55d596352d11dbd6ae3e403138a29c864 Signed-off-by: Phil Burk <philburk@google.com> (cherry picked from commit 7cd06c0b9e087a555d2c5dd4cab5b7eac8497526)
*	MidiService: update listener with current status when registered	Phil Burk	2015-11-10	1	-0/+21
\| \| \| \| \| \| \| \| \| \|	This will give an app an opportunity to learn whether an input port is busy before the user tries to connect and then fails. Bug: 22825043 Change-Id: Ifede60f166dfe66ea15453044fce06f4a8452b18 Signed-off-by: Phil Burk <philburk@google.com> (cherry picked from commit b2355940e3e697deeecd1b6511cd5094f9dc553a)
*	MidiDeviceServer: Fix race condition in setting device server's mDeviceInfo	Mike Lockwood	2015-06-11	1	-0/+9
\| \| \| \| \| \| \|	This made it unsafe to open ports on a device from the MidiManager onDeviceOpened callback Bug: 21760692 Change-Id: I536acdf574a3ccecdb66a8fde87089538e8bb1ef
*	MidiManager: proxy all requests to open devices through MidiService	Mike Lockwood	2015-06-04	1	-65/+369
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	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
*	MidiManager: Address API Council feedback:	Mike Lockwood	2015-05-12	1	-1/+1
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	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
*	MidiManager: Improve output of "dumpsys midi"	Mike Lockwood	2015-05-07	1	-1/+3
\| \| \| \| \| \| \|	- Include each device's port status from MidiDeviceStatus - MidiDeviceInfo.toString() now outputs all the names and values in the properties Bundle Change-Id: Ic9329153e4ae4d5619e274d27a420943473377e5
*	Add support for Bluetooth MIDI devices	Mike Lockwood	2015-04-09	1	-2/+2
\| \| \| \| \| \| \| \|	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
*	Make the MIDI Manager optional, enabled by "android.software.midi" feature	Mike Lockwood	2015-03-27	2	-0/+686
	Change-Id: I76d442ea28beea4b9e2876bfef501d8f61403702