View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0019759 | MMA | Playback | public | 2023-01-27 20:14 | 2023-02-05 01:57 |
Reporter | rusty | Assigned To | |||
Priority | immediate | Severity | major | Reproducibility | random |
Status | closed | Resolution | reopened | ||
Product Version | 2.0.0 | ||||
Target Version | 2.0.0 | Fixed in Version | 2.0.0 | ||
Summary | 0019759: Playback stops on NEXT | ||||
Description | With build 1065 on Android 9, pressing the 'Next' button after the device has gone to sleep causes playback to stop. 1 Run MM and press play in the miniplayer --> Playback starts as expected 2 Press NEXT --> Playback advances and continues playing as expected 3 Allow MM to continue playing for 10 minutes --> It keeps playing as expected even after the screen has turned off 4 Activate the screen and use the fingerprint to sign in --> MM displays as playback continues as expected 5 Click NEXT --> Playback stops! Debug log: Y1G6C71CPR Note: this is replicable on Android 9, but doesn't occur on Android 12/13. | ||||
Additional Information | User at ticket 5375 also experienced this issue with build 1063: Log ID FPJQUGM6D9 | ||||
Tags | No tags attached. | ||||
Fixed in build | 1066 | ||||
|
Note: I suspect that this issue is device-specific and/or performance-related since it seems to occur more frequently if I click NEXT immediately after unlocking the device (if I wait a few seconds after unlocking, then the issue doesn't occur). EDIT: It may not even be a regression and might just be coincidental that it occurred a few times after upgrading to 1065. I've tried replicating this a few more times, and it's no longer occurring. Hopefully the log has some useful information. |
|
Fixed in build 2.0.0.1066 |
|
The user at ticket 0005375 is still observing playback stopping on NEXT with his headphones: Log ID: JS9DWXEXRN Description: music stops on skipping track with pixel buds pro |
|
Log is from build 1065, the issue was fixed in build 1066. |
|
Appear fixed in 1066 User also confirmed and I can't replicate with 1066 on same script I used to simulate bug. |