maemo.org Bugzilla – Bug 9270
Device unlockable if it get locked when being in portrait mode
Last modified: 2010-05-28 21:32:30 UTC
You need to
before you can comment on or make changes to this bug.
SOFTWARE VERSION: Maemo5 3.2010.02-8
EXACT STEPS LEADING TO PROBLEM:
Had a phone call, the phone app was in portrait mode when the N900 was "put
aside" on the desk. After 1 hour, the automatic device lock kicked in. When
trying to unlock device it was impossible, because a disabled "Done" button was
covering the "9" digit on the keypad which I needed for my unlock code.
1. Set the automatic device lock to 5 minutes
2. Start the phone app and do a phone call.
3. Hang up and lay the phone down without flipping back to landscape mode.
4. Wait for at least 5 minutes
5. Access the phone again and (hopefully) it "forgot" to switch to landscape
All keypad digits should be available by always switching to landscape mode
Device unlock happens in portrait mode and a few keypad digits are covered and
unavailable by the "Done" button
Hi David, thanks for reporting this!
Hopefully the device won't get stuck in portrait mode at the end of a call
anymore, re-testing once PR1.2 has been released welcome.
Not sure if it's an unrelated bug or if it relates to this and maybe a mix with
#8910, but ...
It seems that having the device in the browser in full screen and letting the
device time out itself into the secure locks mode results some times (always?
Not sure!) in the keypad not being visible at all except for the title... no
numbers, no "Done" button, nothing!
But you can still try to guess where the buttons are and get a success /
failure at entering your code.
According to internal testing and comments this seems to be FIXED in later
(Note to myself: Tested on 2010.16-8)
It's a bit unclear, but this should most probably be FIXED in PR1.2 (the next
Retesting once it is available for public highly welcome.
This week Nokia released the Maemo5 update version 10.2010.19-1 for public
(also called "PR1.2").
If you have some time we kindly ask you to test again if the problem reported
here still happens in this new version - just leave a comment (and feel free to
update the "Version" field to the new version if it's still a problem).