View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0011410 | MMA | General | public | 2013-10-23 18:15 | 2013-10-30 20:10 |
| Reporter | rusty | Assigned To | |||
| Priority | urgent | Severity | major | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 1.0.4 | ||||
| Target Version | 1.0.4 | Fixed in Version | 1.0.4 | ||
| Summary | 0011410: When paused MMA causes screen to flash / behave strangely | ||||
| Description | Normally, when the user receives a phone call, the standard screen settings apply (e.g. if the screen is set to blank out after 30 seconds, it does so). However, when MMA is playing a track while a phone call is received, the screen flashes continuously, turns off when the screen timeout occurs, but then turns back on by itself, and flashes further. Tested with Lock screen player disabled, and 'Show in notifications bar' set to 30 seconds. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
|
|
Could you please specify the conditions: a) The screen flashes during the phonecall or after phone call? b) Does turn on after some event ? Fixed time interval, next song ? c) What API you use? d) Generally could you please describe the exact steps? I am not able to reproduce it. I tried the following: 1. Start MMA 2. Play track 3. Call from another device (MMA is still active) 4. Answer the call 5. Wait till screen turns off 6. Screen is turned off and remains black (no flashing) 7. Wake up the phone by power button after 2 minutes 8. End call 9. Default lock screen without player is displayed. 10. It turns off after screen interval and remains black (no flashing) 11. Wake by power button 12. Unlock lock screen to go to MMA 13. It turns off after screen interval and remains black again (no flashing) Could you please try to create log. I don't think that it will be useful but something can be visible. It would be great to know when exactly it occurs to match it with log information. |
|
|
These issues no longer occur following the changes made re. 0011402 / 0011342. Resolving. |
