Re: [Announce] advanced-systemui
 

Just run `asui uu; asui dit`.


"I miss" makes it sound like another package provides that functionality?

I was going to add a button to disable device locking but decided against it because ASUI would need to prompt for code. I think that was before ASUI supported devlock so I've added this back on the todo page since I can reuse the keypad code. It will also allow the timeout to be changed. I'll try to get it done soon, but need to finish some other things first.

I've also added a blanking pause button to the todo list. It'll require a double tap to begin the pause to prevent accidental taps.

Re: [Announce] advanced-systemui
 

Sorry, I mean that I am looking for this functionality. The car navigation system navit does not disable device locking and dimming. Further more, I sometimes just do not want to bother with unlocking when taking more time than the lock timeout for the next keypress.

Powerlaunch is the only package I know with this function. It comes with the command line tool, powerline. You can run:

$ while powerline DisplayOn; do sleep 30 ; done

for delayed tk-locking and dimming. Powerlaunch is buggy on my device and inhibits auto device locking. So I do not know wheather 'powerline displayon' delays device locking.

Perhaps I am a little bit pedantic, but I prefere to change the system settings myself and not to give passwords to user space software. This way I'd also prefere asui using the system interface for unlocking the device not asui reading the unlock code itself.

I expect the OS to provide a technique to the user for interruption of devlocking and dimming. Blanking pause sound good to me.

Re: [Announce] advanced-systemui
 

ASUI already has code to pause blanking, turn on its flashlight or long press the fullscreen clock. You can also send the blanking pause message to MCE every 60 seconds and don't any apps to do it.


Sadly, any app you install can read your plain text lock code from DSME. The lock code keypad is drawn by SystemUI and ASUI is a replacement, so it has to replace it. And I didn't use a lock code until ASUI supported it because SystemUI's keypad was hard to use with fingers and doesn't support the n810's keyboard.

Re: [Announce] advanced-systemui
 

Thus the technique is known. I just cannot put the clock into the background to serve as screen blocker.

You are completely right, my mistake. Asui runs with root privileges and thus the code can be drawn anyhow. And, asui's big keypad is realy an advantage. Entering the lock code with systemui's keypad is always a pain while driving.

Thank you very much for asui!

Re: [Announce] advanced-systemui
 

New ASUI test binary.

• fix: vertical swipe on secure keypad must be the height of the bar and cross the line
• fix: a second long press on fullscreen clock will now turn screen blanking back on
• battery widget now has a simple charging animation

Re: [Announce] advanced-systemui
 

New ASUI test binary.

• fix: window now slides smoothly when dragging to unmap

Re: [Announce] advanced-systemui
 

Hmm, i keep wondering if the MCE issue has something to do with the interaction between alarmd, ASUI and MCE when using the pre-boot charging screen. This because once the issue manifests itself it seems to stick around until the device is fully shut down rather then rebooted. Hell, it could be in how the screen and such is turned on from the insertion of the charger rather then the power button. And that could mean that is the power management code that is at fault in some way.

Edit: bah, just when i think about testing the theory it flies in my face. A shut down with alarmd disengaged cause the same "no blanking on lock" symptom as simply rebooting.

edit2: The more i poke at it, the more it appears that MCE is no longer starting correctly. Even if i turn of ASUI and start the N800 with systemui enabled, nothing responds correctly until i restart MCE.

edit3: funny. With systemui enabled there is difference between reboots and shutdowns. From a shutdown state, MCE do not work correctly. But once it has been restarted and is behaving correctly, a reboot from the systemui menu seems to work as it should.

edit4: or i am looking at the weirdest inconsistent behavior ever. One reboot systemui reacts, the next is does not, and i can find no pattern as to why.

edit5: well color me confused. /etc/init.d/mce restart as user do not work (no response from power button or similar), but as root it does. Is there some kind of context issue during the boot going on perhaps?

edit6: going back to ASUI after all this muching about with MCE and systemui and the problem is just gone. Even when shutting down and plugging in the charger i can not get MCE to misbehave.

Re: [Announce] advanced-systemui
 

i found myself wondering if it was possible to have a memory display mode that showed both memory and swap left free (numbers or percentage, with the latter perhaps also having a version showing percentage used), rather then having to long-press to move between them. Or maybe it could be automatic if one set both to either percentage free or percentage used as there seems to be room for that in those modes.

Re: [Announce] advanced-systemui
 

Yes, is that weird. I myself did 10's hours of testing trying to find a way to fix this reliably before giving up.

Re: [Announce] advanced-systemui
 

If you feel adventurous, could you install powerlaunch, stop the powerlaunch service, make sure powered service is running and let me know if it is fully functional and bug free? If so, I could fork the MCE component into its own package.


Added to the todo list.