[Bug 1205] New: Qwerty keyboard covers button when screen in locked mode

bugzilla-daemon at bugzilla.openmoko.org bugzilla-daemon at bugzilla.openmoko.org
Tue Jan 29 23:51:37 CET 2008


           Summary: Qwerty keyboard covers button when screen in locked mode
           Product: OpenMoko
           Version: current svn head
          Platform: Neo1973
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: openmoko-keyboard
        AssignedTo: mickey at vanille-media.de
        ReportedBy: plr at udgaard.com
                CC: buglog at lists.openmoko.org

Since the appearance of the mobile keypad the qwerty keyboard can be misplaced
when in use:

1.Select power savings mode to "Dim only, don't lock"
2.Go into Message screen and select to have the qwerty keyboard appear.
3.Now both keypad and keyboard are present on the screen.
4.Wait for the screen to lock (and the selection was "don't lock" in #1 above :-)
5.Tap on the screen to have the light come on
6.Notice that the OpenMoko icon that should be dragged from the bottom to the
top lock, to unlock the screen, is now covered with the qwerty keyboard
7.It is not possible to drag the keyboard away or in some other neat way get to
the OpenMoko icon, so it seems like a dead-lock only fixable by reboot.
8.Not good

However, there is a funny work-around to rebooting:

1.Activate the AUX menu by pressing and holding the AUX button for a few seconds
2.Select screenshot
3.Select Browse
4.Notice the "X Save File" bar at the top.
5.Drag that bar downwards and the qwerty keyboard icon will appear at the top.
6.Push the qwerty keyboard icon in order to disable that selection
7.The keypad appears instead of the qwerty keyboard
8.Select Cancel and Cancel and the locked screen re-appears
9.Now you may drag the OpenMoko icon to the top, to unlock the screen

This was found on the latest build:


------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

More information about the buglog mailing list