Description: The user is able to reach a state where the UI may display with the Software Home Button (the "bottom of the phone") being drawn about halfway up the screen. The entire screen is framed around this, and the former "top of the screen" rolls up from the bottom. This has been reproduced 3 times, all involving opening the camera and utilizing volume control (directly outside adjusting dialer volume, and directly inside as a camera shutter button). Location behavior of all buttons are where they are expected to be, not where they are drawn (for example: software home button displays in center of screen, but is acted on by tapping at the bottom where it is normally drawn). Repro Steps: 1) Update a Aries to 20150619021036 2) Tap the Volume down button. 3) Open the Camera app. 4) Tap the volume up button. 5) Close the Camera app. 6) Repeat 3-5 until UI breaks. Actual: Bottom of the UI is drawn starting in the middle of the screen; Top of the UI that rolls off the screen is drawn from the bottom Expected: Bottom of the UI is drawn starting at the bottom Notes: - Issue may resolve itself on resetting display (tap power button to lock and tap again to unlock) - After "soft" display reset, issue seemed easy to trigger again - Camera Hardware Button has been observed to trigger the issue as well, may be related to using multiple manners of accessing camera/shutter buttons Environmental Variables: Device: Aries 3.0 Build ID: 20150619021036 Gaia: 4eb81c190cbddf0860877bf36bea096d9d051a38 Gecko: 8a8307ba002f07c6a36668c65f6f39083bd30703 Gonk: 2916e2368074b5383c80bf5a0fba3fc83ba310bd Version: 41.0a1 (3.0) Firmware Version: D5803_23.1.A.1.28_NCB.ftf User Agent: Mozilla/5.0 (Mobile; rv:41.0) Gecko/41.0 Firefox/41.0 Repro frequency: 10/20 Link to failed test case: See attached: video- https://www.youtube.com/watch?v=jyCZdEL1mqM&edit=vd logcat
QA Whiteboard: [QAnalyst-Triage?]
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 1176301
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
You need to log in before you can comment on or make changes to this bug.