Thread: [Announce] advanced-systemui (ASUI)
View Single Post
auouymous is offline auouymous
2010-10-11 , 10:04
Posts: 875 | Thanked: 918 times | Joined on Sep 2010
#50
Behaviour only comes about only when my charger is plugged in and use the on screen locks.
Does it do the same thing when long pressing the lock button when not on the charger? Short pressing the lock button will blank the screen immediately unless its charging in which case short and long both lock it since the screen won't blank while charging.

Is there any way to add a take screenshot option?
Not yet, but it is planned.

btw; i have noticed that if i use the power button to bring the N800 out of idle, it takes a couple of seconds for the advsys ui to show up. Problem is that if a tap anywhere on the screen before that, it gets transferred to the advsys ui (resulting in "random" actions).
I think its a problem with maemo or the hardware. The device lacks realtime response times and can often take a second or two to wake the app so it can process the events. Problem is that you tap the screen or press button again thinking it didn't take and then the app is woken and all the events flood in. Happens in all the maemo apps I use, not sure if there is anything I can do about it, but it does happen less often when I'm not running in powersave mode all the time.

1. let the tablet idle long enough for the screen to go black as per the display settings in control panel
Do you have "lock screen and keys" unchecked in the control panel? I unchecked it and was able to reproduce the notification. Not sure why MCE is sending that signal but I'll look into it. Also found out that short press lock (and blank) doesn't lock the screen when that setting is unchecked, that will be fixed in next release.

expected result:
screen should turn back on.
I wouldn't expect screen taps to turn the device back on after pressing a button called "lock".

Hmm, not just screen sound. Key sound is also lost.
The power button automatically wakes the system when the default systemui isn't running, I didn't have to do anything to get that cool feature. MCE also doesn't send an unlock signal which is why asui doesn't display an unlock notification, yet.

So the system ends up in a kind of between state where parts think it is locked while others thing it is unlocked.
Can you get the device in this state and then run the follow command and tell me if it becomes normal again?

Code:
run-standalone.sh dbus-send --system --type=signal /com/nokia/mce/signal com.nokia.mce.signal.tklock_mode_ind string:unlocked