View Issue Details

IDProjectCategoryView StatusLast Update
0019973MMAPlaybackpublic2023-05-08 11:56
Reporterrusty Assigned To 
PriorityimmediateSeverityblockReproducibilityalways
Status closedResolutionfixed 
Product Version2.0.0 
Target Version2.0.0Fixed in Version2.0.0 
Summary0019973: Playback starts by itself / Audio blips
DescriptionThere's a regression in 1078 in which there are audio glitches when clicking/launching MMA after a bluetooth connection has been terminated.

1) Playback starts by itself
1 Launch MM and leave it open
2 Connect headset and initiate playback via headset
3 Disconnect BT without pausing playback
--> Audio stops as expected
4 Unlock the screen so that MMA displays
--> Playback starts by itself!

Debug log: 1KQ916SL7S

2) Audio blip on launching MM
1 Connect headset and initiate playback via headset (without launching the MMA UI)
2 Disconnect BT without pausing playback
--> Audio stops as expected
4 Launch MMA
--> A 1s audio blip of the last played track briefly plays!
5U5IIUYQ44
TagsNo tags attached.
Fixed in build1079

Relationships

related to 0019792 closedmartin Playback sometimes starts by itself 
related to 0019968 closedmartin Bluetooth Playback issues (regression 1076) 
related to 0020014 feedbackrusty Playback starts by itself 

Activities

rusty

2023-04-28 15:47

administrator   ~0071656

Last edited: 2023-04-28 15:50

3) Endless hourglass on launching MM in Playing view
1 Connect headset and initiate playback via headset (without launching the MMA UI)
2 Disconnect BT without pausing playback
--> Audio stops as expected
4 Launch MMA in Playing view
--> No audio glitch, but the Playing > Art view shows an endless hourglass!
Debug log: 2UMJMYAAR3
Note that the endless hourglass in the Now Playing > Art view doesn't go away even after playing other tracks / switching views etc. BUT upon closing MMA and restarting it
--> Audio glitch occurs, and the hourglass disappears!

martin

2023-04-28 18:16

developer   ~0071668

Last edited: 2023-05-02 01:31

Unable to replicate it on my devices.
Anyway I have improved the workaround related to ~71284

Fixed in build 2.0.0.1079

rusty

2023-04-28 19:36

administrator   ~0071669

Note: on further testing, I was able to replicate the issue with build 1076, so it's not a regression.

rusty

2023-04-28 23:45

administrator   ~0071676

Verified 1079.