That's very wrong. Happened to you running ASUI or just SystemUI?
By the way, I've found that running mce with --verbose 5 times will very much increase the syslog/terminal output of mce. May be that helps you to find why.

Both.

--

New test binary up. You will need to enable the new secure_button setting and then restart ASUI, only reason to install this test. The secure button can only be long pressed and will lock the device with your code (make sure you know it). Power button will lock&blank the screen. Long press on power button will shutdown the device, but its a little tricky to do because the screen wakes up or locks and aborts the long press (but this could also be a security feature to keep people from turning it off ). All other keys are disabled when the keypad is visible, n810 keyboard will be supported later on.

The devlock_callback(3) MCE method call doesn't store internally in MCE unless systemui is running or is started later on at which time MCE finally registers the call and sends out the locked signal. This means that if ASUI is restarted while the keypad is showing then MCE will report the device as unlocked and ASUI won't redisplay the keypad.

If the device is shutdown while locked, osso-systemui-early (make sure you haven't disabled that service) will prompt for the code when rebooted. There is currently no way to use ASUI's keypad since MCE would report it as unlocked until systemui-early starts and somehow causes MCE to update.

If the device is attached to the charger then osso-systemui-early, which I assume displays the brief charging screen, will not update MCE and doesn't prompt for code. ASUI will then show its charging screen and the device can be fully booted without needing a code.

So the only two ways to bypass the code is to boot on charger or make ASUI restart itself with a crash.

EDIT: disable ASUI in the charging runlevel and systemui-early will prompt for the code, leaving only a crash to bypass the code.

And yet another test binary.

The clock on the devicelock keypad window will open the fullscreen clock and returns to the keypad when swiped. The fullscreen hardware button activates the flashlight when the devicelock keypad is visible and returns to the keypad when flashlight is turned off.

If device autolock is enabled in the control panel and the screen is off for the autolock timeout duration then the device will lock when turned back on. This will happen even if secure_button is not enabled.

Decided to code some more before sleeping, so there's now another test binary.

The ALS fix from an earlier test binary was slightly broken but not anymore.

Escape button can be used to close the fullscreen clock or flashlight when the device is locked. Battery and temperature values above device lock keypad are now updated immediately. Secure button locks or locks&blanks the screen, depending on autolock value. Pressing the power button while device is locked now locks or locks&blanks the screen, depending on autolock value.

New n800_lock_mode setting is enabled by default on n800 but not n810 and causes the power button to always open ASUI and never close it. Disable it if you want to use the power button to close ASUI.

The dpad center button now does whatever the onscreen lock button does, and it supports long or short presses. When combined with the n800_lock_mode you can always use power+dpad to lock the device.

not working here.

Which part doesn't work, the power button or the dpad center? If dpad center, can you do `asui rt`, press dpad center and tell me if it outputs a keycode message?

key release (36).

Ah, i think i may know the problem. dpad center can also be set to bring up the full screen on screen keyboard...

or maybe not, same issue even tho i disabled that osk feature.

It is emulating the ENTER key on your device, it sends a 104 on mine. I will support both in the next release.

ah yes, forgot about that. was a problem in the past on other projects as well.

New test binary up.

This should fix the dpad center button locking on n800.

The device lock keypad will disable itself for 30 seconds after three failed attempts.

Each dialog has received its own key handler allowing them to make better use of hardware keys. The device lock keypad can now be used with the n810 keyboard. All keys used through out ASUI have been documented on the new keys page. Let me know if anything is broken from this.

EDIT: rotation buttons can now be long pressed to invert the rotate-and-close setting.