That command gave the "touch screen and keys active" message, but the actual status seems to not have changed. That is, still no screen or key press sounds. And the screen is still considered locked when it idles.

And i honestly keep forgetting that the advsysui lock button have a long press option...

The next release will send an unlock request when unlocking screen with the power button and the "screen active" notification will appear. That notification will no longer appear when screen turns back on and wasn't locked. I'm also trying to send a lock request along with the display off request to fix the problem with lock&blank but its producing strange behavior.

There is a new test binary up at http://qzx.com/asui/?p0=download if you wanna try it.

the test version seems to behave as it should.

advanced-systemui (0.2.2)

• removed all polling for wifi and bluetooth
• display access point name and connection status in wifi widget, improved warm/cold start sequence
• display device name and connection status in bluetooth widget, improved warm/cold start sequence
• display volume output: speakers, headphones or bluetooth headset
• power button now leaves asui in the same state (visible or hidden) it was in before device blanked or locked
• power button sends an unlock request when it is used to unlock the screen (displays "active" notification)
• "active" notification no longer displayed when screen is unblanked and wasn't locked
• lock&blank becomes a lock when the display setting to auto-lock is unchecked

It doesn't query the initial headset status so it'll be out of sync if a headset is connected when asui is started or restarted with the escape button. I released now to get the power button and lock fixes out.

Let me know if there are any more issues with locking/unlocking, unblanking or the power button.

So far it appears to behave correctly. Nice work

Agree with the sentiment above. So far so good.

Thank youuuuu>!

discovered a small issue with the process list.

each time a process is selected, its number stacks on top of the old on the kill process button.

Heh, good thing you didn't find the much larger problem causing that "small issue". Try rotating the screen while in the process viewer.

just opening closing then opening the keyboard again wakes the screen up... you shouldn't have to take the battery out. This is annoying though

advanced-systemui (0.2.3)

• converted bme and governor to libdbus
• increased memory query speed
• query cpu frequency first so its not always at 400mhz for ondemand
• wifi and bluetooth will abort cold start if services fail to start
• process viewer can now kill processes, including self
• escape button now hides window instead of restarting
• fixed problem that made it hard to select some processes
• fixed multiple drawing issues with the process viewer
• fixed problem where message could be sent to signal bus before dbus thread had created it
• fixed problem where X wouldn't update window contents for long periods of time