diff options
| author | Sanket Agarwal <sanketa@google.com> | 2016-03-21 14:00:30 -0700 |
|---|---|---|
| committer | Sanket Agarwal <sanketa@google.com> | 2016-03-21 23:36:21 +0000 |
| commit | 26469ff3f9f4ab96ad288e0934220023a0c159f1 (patch) | |
| tree | 1b41cbdfcd7e03c697fbc48944c7c0ad26a1df26 /res | |
| parent | e94f8eb85b68b351319499337af937835730b508 (diff) | |
| download | android_packages_apps_Bluetooth-26469ff3f9f4ab96ad288e0934220023a0c159f1.tar.gz android_packages_apps_Bluetooth-26469ff3f9f4ab96ad288e0934220023a0c159f1.tar.bz2 android_packages_apps_Bluetooth-26469ff3f9f4ab96ad288e0934220023a0c159f1.zip | |
Forward in iPhone leads to play state being presisted as STOP.
When we press forward in iPhone (via AVRCP pass through or iPhone UI)
while connected over AVRCP we are resetting the state and expecting
AVRCP to give us a new play state when next song resumes. Turns out that
iPhone always keeps it state to be Playing.
The fix is to keep the mRemoteMediaPlayers a replica of what AVRCP says
so that when song resumes (from A2dpSinkService via startAvrcpUpdates)
we can restore the playing state.
Tested on iPhone and regression tested on Nexus 5X.
Bug: b/27768620
Change-Id: I8caf56072fa5743f28e1680860c161d3cd75b83c
Diffstat (limited to 'res')
0 files changed, 0 insertions, 0 deletions