Added audio_assets.xml resource listing the
audio asset files for each touch sound effect.
This resource can be overlayed to customize the
touch sounds for a given device.
Bug 8339000
Change-Id: I8c156f0ce7f8769a58d77442fbd9c46b57c202e9
* commit '6d9b3328a51ea7f139b525fcaaa3bf3cd5a54627':
Fix the media memeory stress test. The media memory stress test used the ps mediaserver to capture the memory usage of mediaserver. As the media.log is enabled recently, when runnign the ps mediaserver, it will show both entries. The fix is simply skip the first two lines and parse the laste output.
The media memory stress test used the ps mediaserver to
capture the memory usage of mediaserver. As the media.log
is enabled recently, when runnign the ps mediaserver, it will
show both entries. The fix is simply skip the first two lines
and parse the laste output.
Change-Id: Ib2a4ba7936505b4ea24463bf8a5af2c499b71138
* commit '4f394b006bf61163bcdafd2c4a6c58807c498793':
Media test clean up. Remove duplicated camera preview stress test. Remove duplicated recorder stress test. Remove camera recorder switching stress test. Reduced the total number of iterations for all the stress loop.
Remove duplicated camera preview stress test.
Remove duplicated recorder stress test.
Remove camera recorder switching stress test.
Reduced the total number of iterations for all the stress loop.
Change-Id: I447f8060fadd0599c160727fb7dda8a4cc384656
AudioManager.registerMediaButtonEventReceiver maps to
AudioService.registerMediaButtonIntent
AudioManager.registerRemoteControlClient maps to
AudioService.registerRemoteControlClient
To use RemoteControlClient, an application needs to have
first registered its button event receiver. Therefore
registerMediaButtonEventReceiver() needs to have
completed registration when returning, otherwise the
RemoteControlClient registration can sometimes fail due
to the lack of association between the button event
receiver and the RemoteControlClient.
Bug 8315459
Change-Id: I82c196c3f21a65e38bad275085ed4f9ec0ec60dd
Commit 2a57ca93 introduced a regression in startBluetoothSco()
where the calling pid was cleared before creating the entry for
the client app. The pid in the entry was always the system server pid
and the SCO client verification logic was broken preventing the activation
of the BT SCO connection.
Change-Id: I4e024b22fceb350f829ff0d8664703faeef7af48
Modify RemoteControlClient and AudioService to support multiple
simulataneous IRemoteControlDisplay interfaces active at the
same time.
Change-Id: I9f200a488afdd62a5e6957e64624d745e0f28149
Clear calling identity before calling BluetoothHeadset
methods from binder call.
Also send BT SCO audio state intents from the
message handler, not from binder calls.
Bug 8242429
Change-Id: I742ba8dc47a258dbee6fb9d57db302f2bffaafd7
Un-hide two new methods in MediaCodec, one new constant, and a new
EGL extension.
Bug 7991062
Bug 8191230
Change-Id: I028669132d9ffda1e4b34a561bab3997bbd7dae5
Added range checks for setPlaybackHeadPosition and setLoopPoints to
correspond to the new implementation. The checks are not expected to
cause any significant incompatibilities for real apps.
Change-Id: Ia52723419e7d0e2c561a0d1eeb8f36a5376c4e03
The support library MediaRouter implementation needs a couple
of extra generally useful APIs in the platform MediaRouter to ensure
that it can safely synchronize its state.
Change-Id: I72c5652e10f3b6de48800abfa922affbefbd250f
