The screen-on popup clock would also have battery status but would only black out the middle of the screen instead of being fullscreen like the minimal UI. This popup would cover ASUI and other apps so it would always be there after screen turns on. I could also have it popup briefly over the top of ASUI each time it is mapped.

The clock popup could also be removed with a tap so you could use a long timeout and manually close it. And mapping or unmapping ASUI would close the popup if it was open.

Another setting could make the popup always be fullscreen. So three settings: popup_duration (after screen on), popup_on_map (when ASUI appears with power button) and popup_fullscreen.

You like that?

Hello again,

I've been using ASUI for a while now, and I quite like it. The bug (not sleeping) and request (lock with old sequence) that I posted many pages back both seem to be fixed, and I like the new layout. However, I think my "alarms not going off" problem is related to ASUI.

I can set an alarm, but when the time comes around, nothing happens. I ran "tail -f /var/log/syslog" and saw this come up at the alarm time (date and system identifier not included, since I'm typing this by hand):

alarmd[1402]: GLIB WARNING ** default - DBUS error: Name "com.nokia.system_ui" does not exist
DSME: Accepted new client connection
DSME: Closed a client connection
DSME: Accepted new client connection
DSME: Closed a client connection

this looks like it might be related to ASUI. I'm wondering whether anyone else has experienced this behavior?

Thanks again.

Indeed. You need SystemUI running for alarms to function. In short, SystemUI comes with a plugin that provides the alarm UI you see with snooze etc. on it. It provides a D-Bus service that is invoked by alarmd to show the alarm dialog etc. If SystemUI is not running then it cannot handle the event. The alternative would be to get ASUI to handle it, I presume, but I imagine the lack of information doesn't help

Ah. So, I assume that by installing ASUI, SystemUI is stopped, or interrupted somehow? I guess the alarm behavior is related to [url=http://maemo.org/packages/view/osso-systemui-alarm/ oss-systemui-alarm], correct?

Looking at Control Panel->Services, I see a check box next to both "System UI (oss-systemui)" and "System UI (oss-systemui-early)", however the "Running" box is not blue, like the other running services. I tried restarting it by unchecking, then rechecking the checkbox, but that doesn't seem to have accomplished anything.

What am I missing?

You can edit /etc/asui-svc to keep ASUI from stopping systemui but it will probably cause duplicate notifications to appear. The power button will also open ASUI and the systemui menu but I think you can keep systemui from opening its menu by changing PowerKeyShortAction from menu to disabled in /etc/mce/mce.ini and then restarting MCE.

Tell me how to create alarms and I'll add support for them as soon as possible.

I am also having the alarm problem. Do you want to know how to set the alarm?

Generally, that seems to behave properly.

I ran into something else weird while testing. I had Canola2 running, playing music, when I plugged in the charger. It remained lit as expected. Just to check the manual blank, I opened ASUI and pressed blank—but it didn't blank.

I don't remember exactly the next sequence of presses, but I twice got into the state where I pressed Blank, ASUI closed, but the screen did not blank—and, I could not bring up ASUI again (using the power button) until some amount of time (maybe a minute) had passed. Canola2 was running in the foreground this entire time.

Then I closed Canola2, let it sit for a while (still on the charger) and it auto-blanked. I was able to open ASUI at this time and checked the setting: it had been changed to "Never". I toggled it and then ran several tests, changing the setting in ASUI each time, and it behaved properly from that point on, including manually blanking when I pressed the Blank button.

I restarted Canola2 and was able to immediately reproduce the Blank failure. Then I quickly minimized Canola and opened ASUI from the status bar, which worked. But, a long-press on the Blank button was not recognized, nor was a drag across the screen to close ASUI. After a short wait, everything became active again.

just tested something. I fired up a video using mplayer, let it run for a couple of seconds, quit it and then tried to lock the screen using asui. End result was that while it said "dimmed" under the backlight slider, the screen stayed lit. Before i played the video the screen dimmed as it should.

Did the screen lock? Was the charger attached?

If ASUI said dimmed then MCE sent out a dimmed signal and MCE should have dimmed the screen. Mplayer probably paused blanking and ASUI's lock function would restore blanking if the charger isn't connected or the stays lit is set to never. MCE is stupid and sends out the dim signal even if blanking is paused.

There is a second stayslit setting that I wasn't changing but the next release will handle it and it could be causing the stayslit toggle to not work properly. This is assuming you were connected to the charger.

nope, not connected to charger.