Bug 9977 – Hardware T&K lock switch must be used twice to unlock device when keyboard open

Bug 9977 - (int-164904) Hardware T&K lock switch must be used twice to unlock device when keyboard open

(int-164904)
Summary:	Hardware T&K lock switch must be used twice to unlock device when keyboard open

Status:	RESOLVED FIXED

Product:	System software
Component:	Device lock
Version:	5.0:(10.2010.19-1)
Platform:	N900 Maemo

Importance:	Unspecified normal (vote)
Target Milestone:	5.0/(20.2010.36-2)
Assigned To:	unassigned
QA Contact:	device-lock-bugs

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree

Reported:	2010-04-20 13:22 UTC by Benedict Meier
Modified:	2010-10-25 17:11 UTC (History)
CC List:	2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note

You need to log in before you can comment on or make changes to this bug.

Description Benedict Meier (reporter) 2010-04-20 13:22:31 UTC

SOFTWARE VERSION:
03.2010.02-8

EXACT STEPS LEADING TO PROBLEM: 

1. open keyboard for screen to unlock
2. wait until screen locks by itself (default setting: 30 sek.)
3. press lock switch on right side of device

EXPECTED OUTCOME:
screen should unlock

ACTUAL OUTCOME:
screen does not unlock

REPRODUCIBILITY:
always

EXTRA SOFTWARE INSTALLED:

OTHER COMMENTS:
if lock switch is pressed twice, screen unlocks. When keyboard is closed the
problem does not occur.


User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US)
AppleWebKit/532.5 (KHTML, like Gecko) Chrome/4.1.249.1045 Safari/532.5

Comment 1 Andre Klapper maemo.org

2010-04-20 14:22:51 UTC

Hi Benedict, thanks for reporting this!

I can confirm this.

Comment 2 Mohammad Abu-Garbeyyeh 2010-04-28 22:14:46 UTC

I think this is normal behavior, the touchscreen doesn't get locked at all when
the keyboard is open. When you slide the switch once it gets locked, and again,
it gets unlocked.

Repeat steps 1 and 2 but touch the screen instead of using the switch.

Comment 3 Andre Klapper maemo.org

2010-06-08 17:44:45 UTC

This has been fixed in package
mce 1.8.121+0m5
which is part of the internal build version
2010.22-3
(Note: 2010 is the year, and the number after is the week.)

A future public update released with the year/week later than this internal
build version will include the fix. (This is not always already the next public
update.)
Please verify that this new version fixes the bug by marking this bug report as
VERIFIED after the public update has been released and if you have some time.


To answer popular followup questions:
 * Nokia does not announce release dates of public updates in advance.
 * There is currently no access to these internal, non-public build versions.
   A Brainstorm proposal to change this exists at
http://maemo.org/community/brainstorm/view/undelayed_bugfix_releases_for_nokia_open_source_packages-002/

Comment 4 Andre Klapper maemo.org

2010-10-25 17:11:35 UTC

The problem reported here should be fixed in the update that was released today
for public: The Maemo5 update version 20.2010.36-2 (also called "PR1.3"
sometimes). Please leave a comment if the problem is not fixed for you in this
update version.