| 430fc48865e5a371b08f180390946b96d73848fe |
|
13-Jun-2014 |
RoboErik <epastern@google.com> |
Work on removing non-session media routing code
Change-Id: I73e7d22f2f8772c7b07ccf32d962161d79d5db74
/frameworks/base/media/java/android/media/PlayerRecord.java
|
| 1990fe4e965f6cb5a65bf58f4764489cdc10acde |
|
15-Apr-2014 |
Jean-Michel Trivi <jmtrivi@google.com> |
PlayerRecord: remove obsolete accessors
Change-Id: I0a7789e28c1427b6e9f770368f9bab9c097b3594
/frameworks/base/media/java/android/media/PlayerRecord.java
|
| 8be88d114432c102264c0a73536efc537c6770ac |
|
11-Apr-2014 |
Jean-Michel Trivi <jmtrivi@google.com> |
MediaFocusControl: priority to playing players for media button
When registering a media button event receiver (through
AudioManager.registerMediaButtonEventReceiver()), do not
always push the receiver to the top of the stack of event
receivers:
- only push to the top if the associated RemoteControlClient
is in a playing state
- otherwise push it below the entries at the top of the stack
that are in a playing state
When changing the playstate of a RemoteControlClient:
- push to the top of the stack the corresponding PlayerRecord
is the state is a playing state
- otherwise push it below the entries at the top of the stack
that are in a playing state
When AudioService starts (e.g. after boot) and the last media
button receiver is restored, it goes in the stack.
After this CL, this entry is not "orphaned" anymore after the
same application registers itself to receive media buttons:
the entry from the restoration is now properly associated with
the registration from the application.
Bug 10749554
Change-Id: I985f9cc17b64a60ed4f2f2f6d03e117fb4e27570
/frameworks/base/media/java/android/media/PlayerRecord.java
|
| dda1c4040c034af14f21e54b1271e20b35620475 |
|
26-Mar-2014 |
Jean-Michel Trivi <jmtrivi@google.com> |
Continue refactoring MediaFocusControl
Rename MediaController to PlayerRecord.
Change-Id: Icf474b4107649f501341309bf7ec520aa1e71586
/frameworks/base/media/java/android/media/PlayerRecord.java
|