View Issue Details

IDProjectCategoryView StatusLast Update
0018253MediaMonkey for AndroidGeneralpublic2021-09-20 14:34
Reporterrusty Assigned To 
PriorityimmediateSeverityblockReproducibilitysometimes
Status newResolutionopen 
Product Version2.0.0 
Target Version2.0.0 
Summary0018253: Initiating playback sometimes triggers endless flashing of the lock screen + device reboot (regression)
DescriptionThis is an extremely severe issue that often occurs with MMA 2.0.0.1009 / Android 11 when used with bluetooth devices or when casting. I've never been able to figure out an exact sequence, but it often occurs after MM has been connected and played to a bluetooth device, or connected and played to a Google Cast device. (on some occasions it occurred as soon as playback was initiated, on others after the connection was terminated and then reconnected).

What then happens is that the lock screen appears, and then flashes repeatedly. Any attempt to unlock the device fails because the lock screen keeps flashing.

If the user presses the Power button then the screen turns off, but as soon as the power button is pressed again, the lock screen continues to flash. This goes on until either:
a) the device turns off
b) the user press-holds the Power button until a white dialog appears offering to Power off, Lock, or ???.

When the device is then rebooted, it often reboots into the OEM factory reset screen!

I realize that the bug is kind of vague, but I've seen this occur about 10 times, but there's no way to generate logs of the issue.

09/19: edited for clarity and to indicate that it also occurs when casting (not just bluetooth).
TagsNo tags attached.
Fixed in build

Activities

rusty

2021-09-20 03:32

administrator   ~0064756

This bug occurred earlier tonight. When I rebooted the device, a crashlog was sent at 11:30pm EST that may shed light on this issue.

rusty

2021-09-20 14:33

administrator   ~0064764

This bug occurred for me again today, without streaming--i.e. playback was to the speaker. I still can't figure out the cause, but I guess it's somehow related to the miniplayer on the lock screen.