maemo.org Bugzilla – Full Text Bug Listing
|Summary:||Volume buttons do not work as expected when answering a call while in landscape mode|
|Product:||[Maemo Official Applications] Chat & Call & SMS||Reporter:||Markus <markuspublic>|
|Component:||Call Application UI||Assignee:||rtcomm <rtcomm>|
|Status:||RESOLVED WONTFIX||QA Contact:||call-ui-bugs|
SOFTWARE VERSION: 2.2009.51-1 EXACT STEPS LEADING TO PROBLEM: (Explain in detail what you do (e.g. tap on OK) and what you see (e.g. message Connection Failed appears)) 1. Hold the N900 in landscape mode, showing the desktop. 2. Call the N900 from another telephone. The Phone application is automatically started (in landscape mode). 3. Tap "Answer" 4. Bring the N900 up to the ear (quickly). The display turns off. 5. Turn the volume up by pressing the upper side of the physical volume button that is behind the front "Nokia" label. EXPECTED OUTCOME: Volume is turned up ACTUAL OUTCOME: Volume is turned down REPRODUCIBILITY: Always if the phone is not brought up to the ear too slowly. The problem can also be reproduced by bringing the N900 to landscape mode while in a conversation (for example to check the calendar) and the quickly bring it up to the ear to continue the conversation. EXTRA SOFTWARE INSTALLED: N/A OTHER COMMENTS: I believe that problem occurs because the Phone application is not rotated when the screen is turned off by the proximity detector. Removing the phone from the ear will re-activate the screen and you can then see that the Phone application is rotated to portrait mode: The volume keys will now work as expected. ("Display orientation" must be set to "Automatic" in the Phone application.)
Thanks for reporting this. For the story before see bug 6384.
The problem presented here is that the screen does not seem to rotate to portrait mode if the proximity sensor is active, i.e. when holding the phone to the ear after receiving a call in landscape mode. The volume buttons are not swapped as expected for portrait mode. Bug 6384 was fixed in release 2.2009.51-1, which is the software version where current bug now exists. It (if verified by others as well) should therefore be registered somewhere; Either as a failed fix of bug 6384 (i.e. reopen that bug) or as a new bug here. (Or a somewhat strange WONTFIX)
I reopen this bug as I consider it different from bug 6384. Bug 6384 was fixed in release 2.2009.51-1. This issue is present is release 2.2009.51-1. See also comment #3.