View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0014440 | MMA | Playback | public | 2017-10-04 21:04 | 2017-11-10 01:24 |
| Reporter | rusty | Assigned To | |||
| Priority | urgent | Severity | major | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 1.3.1 | ||||
| Target Version | 1.3.2 | Fixed in Version | 1.3.1 | ||
| Summary | 0014440: Bluetooth playback: playback status and metadata display incorrectly on Oreo devices / crashes on some others | ||||
| Description | If the user plays via Bluetooth on a device running Android 8, playback status displays incorrectly and metadata usually doesn't display at all. 1) Incorrect status: If MediaMonkey is paused, and the user initiates playback via Bluetooth --> MediaMonkey plays the correct track over bluetooth but the head unit shows 'stopped'. Log ID: AHYV8EEB2D 2) Incorrect metadata: If MediaMonkey is Stopped, and the user initiates playback via Bluetooth --> MediaMonkey plays the correct track over bluetooth, but the head unit displays no metadata and time 0:00 Log ID: HH92ZAD7SY Note: Google Music and other players running on the same Android 8 device display the correct time and player status. None of them display track metadata--probably because it's not supported on the Subaru head unit (I don't remember whether it displayed previously or not). Regardless, at least 3 users have reported that metadata is not displaying for devices running Oreo. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 734 | ||||
|
|
3) In testing this further, I've also found that Bluetooth player control buttons sometimes stop working when playing over bluetooth. 4) Users have reported that "whenever I switch Bluetooth on, Mediamonkey crashes. The same happens if I pause or resume the app using Bluetooth. My device is a Samsung Galaxy Tab A with S Pen (SM-P550). Android version: Marshmallow." note: I'm unable to replicate this on an S5 Mini running Marshmallow. |
|
|
5) When MMA 1.3.1.732 is running on an S5-mini (Marshmallow), it shows the correct time on the same Subaru. However, upon moving the Seek bar (e.g. from 1:00 to 1:30, the timer on the headunit fails to adjust--instead of displaying 1:30, it shows 1:00. In contrast, this works correctly with Google Music and the Samsung Player. I'm not sure whether this is a regression in 1.3.1.732 or if this behavior is longstanding. |
|
|
re 5) fixed |
|
|
4)Weird, no crash from device SM-P550 on HockeyApp - working on my devices |
|
|
Tested build 733. 1)/2) still exist on Orea. I noticed a bit more interesting behavior though: 1 Turn on car --> MMA launches in background and turns off after about a minute (notification timer is set to 1m)--even if the head unit is set to play FM radio (MMA shouldn't run in the notifications drawer until bluetooth playback has been initiated)!! Log ID: PRZFYJA9WJ (occurs on Oreo) 2 Switch to BT Audio and press NEXT --> MediaMonkey plays the correct track over bluetooth, but the head unit displays no metadata and time 0:00 Log ID: 3V4EYZWBBY Description: bug 14440. Bluetooth playback fails to initiate on activation (user must press Next BT button). Bluetooth playback always shows 0:00. Issue 5) Verified. Seek status displays correctly (for pre-Oreo devices). |
|
|
Tested with Nexus 5X Oreo and KMM BT car radio and SBH 52 - no issue |
|
|
1) A) Re: MMA PlaybackNotification when head unit is set to play FM radio - fixed B) Bluetooth playback fails to initiate on activation - improved (related to A)), but It can fail if A2DP is not connected(I have replicated that A2DP device is connected delayed or upon "play" action -it is some system bug on Oreo), usually it works. Partly fixed in build 1.3.1.734. Metadata and playback status shows correctly on my BT devices. MMA setups it correctly in your logs. Maybe for some BT devices, new support library is needed. So I will create new Build from 1.3.2 branch where the library is already updated. This build is not stable and will be for testing only. Let me known whether playback status is displayed correctly with this build. |
|
|
I tested build 733 after updating to the Android security patch level of Oct. 5, 2017, and the problems specific to Oreo (1/2/3) seem to be resolved! This is probably as a result of: https://support.google.com/pixelphone/forum/AAAAb4-OgUsiJeDphsoOJ4 Leaving this assigned to Martin to decide how to proceed (i.e. whether to revert changes or not). |
|
|
Closing based on earlier verification and changes in latest versions of Oreo. |
