View Issue Details

IDProjectCategoryView StatusLast Update
0011402MMAGeneralpublic2013-10-30 05:20
Reporterrusty Assigned To 
PriorityimmediateSeverityblockReproducibilityalways
Status closedResolutionfixed 
Product Version1.0.4 
Target Version1.0.4Fixed in Version1.0.4 
Summary0011402: Back button causes MMA to become 'inaccessible' (regression)
DescriptionIn build 173, the following series of steps causes MMA to be inaccessible from the UI, so that it is impossible to stop playback / close the app / etc...

0 enable the lock screen player via the options menu
1 initiate playback
2 press 'back' to exit the app
3 press 'power' to trigger the lock screen player (or wait for the lock screen timeout)
4 press 'power' again to turn on the screen
--> Lock screen player fails to activate and MediaMonkey isn't on the home screen notifications bar (even though it's playing)!!
5 Try to click the MediaMonkey icon in order to access the MMA UI
--> The screen briefly flashes but MMA UI won't appear

The only way to access the UI is to force MMA closed, and then rerun the app--though on occasion, even that fails and then MMA must be ininstalled.

Note: if step 0 or 2 is skipped the bug won't occur
Additional InformationTested on GS3 running Android 4.1.1.
'Show MediaMonkey when screen is locked' enabled
'Hide the default Android lock screen player' disabled
'Show in notifications bar' is set to 3 minutes
TagsNo tags attached.
Fixed in build178

Relationships

related to 0011342 closedmartin Lock screen player fails to activate if MMA isn't in focus 
related to 0011410 closedrusty When paused MMA causes screen to flash / behave strangely 

Activities

rusty

2013-10-22 17:29

administrator   ~0037988

Last edited: 2013-10-22 21:22

Further testing reveals that the bug only occurs after the user has activated the lock screen player once. i.e.

-5 enable the lock screen player via the options menu
-4 initiate playback
-3 press 'power' to trigger the lock screen player (or wait for the lock screen timeout)
-2 press 'power' again to turn on the screen
--> Lock screen player appears
-1 press home to get to the lock screen and then re-open to MMA

Then proceed with the originally described steps:
1 initiate playback
2 press 'back' to exit the app
--> MM continues playing but the MM icon fails to display in the notifications bar
3 press 'power' to trigger the lock screen player (or wait for the lock screen timeout)
4 press 'power' again to turn on the screen
--> Lock screen player fails to activate and MediaMonkey isn't on the home screen notifications bar (even though it's playing)!!
5 Try to click the MediaMonkey icon in order to access the MMA UI
--> The screen briefly flashes but MMA UI won't appear

rusty

2013-10-22 21:23

administrator   ~0037994

Last edited: 2013-10-22 22:11

Note also, that at step 2, MM usually fails to display an icon in the notifications bar. This behavior isn't consistent.

rusty

2013-10-22 22:09

administrator   ~0037996

Further testing reveals an even simpler set of repro steps--steps 3/4 can be skipped:

Further testing reveals that the bug only occurs after the user has activated the lock screen player once. i.e.

-5 enable the lock screen player via the options menu
-4 initiate playback
-3 press 'power' to trigger the lock screen player (or wait for the lock screen timeout)
-2 press 'power' again to turn on the screen
--> Lock screen player appears
-1 press home to get to the lock screen and then re-open to MMA

Then proceed with the originally described steps:
1 initiate playback
2 press 'back' to exit the app
--> MM continues playing but the MM icon fails to display in the notifications bar
5 Try to click the MediaMonkey icon in order to access the MMA UI
--> The screen briefly flashes but MMA UI won't appear

martin

2013-10-22 23:06

developer   ~0038004

Fixed in build 175.

rusty

2013-10-23 07:30

administrator   ~0038013

Verified 175, though I noticed occasional strange behavior in which:
- clicking back failed to exit the home screen, and clicking it again worked
- clicking the MMA icon caused MMA to flash and not open, but clicking it again worked

rusty

2013-10-23 18:25

administrator   ~0038021

Re-opening as a lower-priority issue since the problem still occurs occasionally:
- Sometimes, backing out of the application while playback is in progress doesn't trigger the MMA notification to appear
- Sometimes, clicking the MMA icon fails to launch the UI, though the issue usually resolves itself after a few clicks
- One a couple of occasions, clicking 'back' failed to exit the home screen, and clicking it again worked

I can't figure out the specific trigger, but these issues do occur consistently when going through the series of steps outlined earlier in this bug, or variations thereof.

martin

2013-10-25 18:39

developer   ~0038057

I changed detection of MMA visibility so issues about MMA notification should be fixed. About other issues described above I have not reproduced but behaviour around Lockscreen player was changed so maybe it could help.
Fixed in build 177.

rusty

2013-10-27 03:07

administrator   ~0038066

Tested build 177, and the bug consistently occurs as originally described:

0 In Android, enable lock screen on pressing 'power button'. In MMA, enable the lock screen player via the options menu
1 Run MMA and initiate playback
2 press 'back' to exit the app
3 press 'power' to trigger the lock screen player
4 press 'power' again to turn on the screen
--> Lock screen player activates as expected
5 press 'home' button to hide the lock screen player and cause the Android Lock Screen to appear
6 get past the lock screen (e.g. password / swipe)
-->Android home screen appears
7 Click the MediaMonkey icon in order to access the MMA UI
--> The screen briefly flashes but MMA UI won't appear!
--> The only way to access MMA UI at this stage is via the notifications bar

The really interesting thing is that if at step 5, I press the 'back' button instead of the 'home' button in order to hide the lock screen player, then the bug does _not_ occur at step 7

Also, I tested this on two different devices this time, and it occurs in the exact same manner. Tested on:
GS3 / Android 4.1.1
Experia Pro / Android 4.0.3

Setting to Immediate, and the bug occurs 100% of the time.

martin

2013-10-29 16:27

developer   ~0038097

Fixed in build 178.

rusty

2013-10-30 05:20

administrator   ~0038107

Verified 178.