Active Topics

 


Reply
Thread Tools
Posts: 1,101 | Thanked: 1,184 times | Joined on Aug 2008 @ Spain
#321
Originally Posted by auouymous View Post
I don't normally run ASUI and systemui together, only for testing purposes but I'll test it out soon. (that is the bug you are refering to right?)
My bug happened with just systemui (I'm not running ASUI at the moment), but it can be the same bug.

Not sure if I missed it but did you test the sequence between systemui and mce when locking the device?
No, just the startup and powermenu sequences. If ASUI is going to replace systemui it will have to mimic systemui behaviour wrt mce and friends.
Sequence locking/unlocking attached here, will comment tomorrow, today is too late.
Attached Files
File Type: gz logs.tar.gz (2.0 KB, 91 views)
 
Posts: 875 | Thanked: 918 times | Joined on Sep 2010
#322
advanced-systemui (0.4.7)
  • fix: wifi widget now turns on the hardware light for PPP connections and can disconnect them
  • fix: cpu frequency is polled before services so value isn't always 400mhz
  • fix: cpu freqency is polled every 10 seconds instead of every 30 like the governor
  • fix: ALS is no longer polled while screen is off
  • fix: tap throttling wasn't using the correct throttle period
  • fix: added a 60 second limit for tap throttling to prevent unresponsive buttons
  • fix: flashlight used a black background when white theme was active
  • fix: "rotating..." screen was black text on black background when white theme was active
  • moved brightness dsme code to dsme.c, brightness no longer has to create dsme socket for each change
  • green box around "Charged" label in battery widget
  • flashlight and clock now use dsme to permanently disable blanking and enable it when they are closed
  • lock&blank will always blank even after a blanking pause was used, no more timer on the lock button
  • console errors will only be displayed for test and debug releases
  • secure_button setting displays secure button to manually lock device with a code
  • keypad is displayed to unlock device when locked
  • keypad is disabled for 30 seconds after three failed attempts
  • keypad code is cleared if not unlocked within 60 seconds
  • fullscreen clock and flashlight can be used while device is secure locked
  • device is secure autolocked after idle timeout when screen is off
  • ASUI will hide after unlocked if it was hidden when secure autolocked
  • ASUI will hide after unlocked if manually secured and lock-and-close is enabled
  • dpad center button now does whatever the onscreen lock button does, short or long press
  • n800_lock_mode setting is enabled by default on n800 and causes power button to always open ASUI and never close it
  • refactored key handler for main screen and all dialogs
  • escape key now exits widget edit mode, flashlight and fullscreen clock instead of hiding ASUI
  • brightness and volume can't be changed with hardware keys in widget edit mode
  • long press for onscreen rotation buttons inverts the lock-and-close action
  • added GTK settings test support to the asui convenience script
  • added 'config' button on secondary widget page to launch GTK settings app

I can't believe no one spotted the flashlight and rotating screen bugs that have been around since 0.2.6
 

The Following 2 Users Say Thank You to auouymous For This Useful Post:
tso's Avatar
Posts: 4,783 | Thanked: 1,253 times | Joined on Aug 2007 @ norway
#323
can not speak for anyone else, but i do not use rotate or flashlight much.
 
Posts: 637 | Thanked: 445 times | Joined on Dec 2009 @ Kaliningrad, Russia
#324
Hey there! I installed a last release and it looks very nice.
A few questions:
Why somebody would need to disable a Desktop?
What does the button Audio? I disabled it and tablet still plays any sounds I want.
What is charging runlevel button on the second screen (if I press Home button in ASUI)?

It will be a really nice feauture to show Clock screen if press a Power button while device is locked. And use Esc button to go back from clockscreen to ASUI in other cases.
 
tso's Avatar
Posts: 4,783 | Thanked: 1,253 times | Joined on Aug 2007 @ norway
#325
I think all of those are documented on the page linked to in the first post.
__________________
Be warned, posts are often line of thoughts at highway speeds...
 

The Following User Says Thank You to tso For This Useful Post:
Posts: 637 | Thanked: 445 times | Joined on Dec 2009 @ Kaliningrad, Russia
#326
Yeah, thanks.
 
Posts: 875 | Thanked: 918 times | Joined on Sep 2010
#327
What does the button Audio? I disabled it and tablet still plays any sounds I want.
It just stops all of the audio services but some programs like mplayer use direct access and will work without all the Maemo bloat.

The other questions are all answered on the website. And now the audio question is also answered there.

It will be a really nice feauture to show Clock screen if press a Power button while device is locked. And use Esc button to go back from clockscreen to ASUI in other cases.
Power button just unlocks and puts device back in the state it was in before it was locked.
  • If the device is locked with a code you can tap the clock (or press home button) to go fullscreen and it will remain in the clock until you manually exit it. Power button will lock or unlock the screen and fullscreen clock will still be active.
  • If you enable n800_lock_mode then power button will always open ASUI and you can tap the clock to go fullscreen. Dpad center button will lock the screen and power button will unlock it, and fullscreen clock will still be active.
  • Without n800_lock_mode you will have to press the power button once or twice depending on ASUI's state, tap the clock and then dpad center works the same as n800_lock_mode, except that pressing the power while unlocked will cause ASUI and the fullscreen clock to hide.
The escape button always exits fullscreen clock.
 

The Following User Says Thank You to auouymous For This Useful Post:
Posts: 637 | Thanked: 445 times | Joined on Dec 2009 @ Kaliningrad, Russia
#328
The escape button always exits fullscreen clock.
Yeah. but it exits ASUI completely.
Power button just unlocks and puts device back in the state it was in before it was locked.
Ok, what I want to say it is that very often I just need to check the time and to do it I need to drag the unlock button or press the power button, check it and lock the device again. But it takes some time to lock it again so I thought it would be a nice feature to be able check the time just using one button...

And thanks, it became a really cool application.
 
Posts: 637 | Thanked: 445 times | Joined on Dec 2009 @ Kaliningrad, Russia
#329
I suspect this app in changing size of fonts (for example in wifi connection dialog).
 
Posts: 1,101 | Thanked: 1,184 times | Joined on Aug 2008 @ Spain
#330
Sequence locking/unlocking:
In the logs, dbus name :1.7 is mce (com.nokia.mce), :1.8 is the gconf part of mce, :1.46 is systemui (com.nokia.system_ui), 1.45 is the gconf part of systemui, 1.470 is the device lock keypad plugin of systemui
For the complete mce/systemui method calls look at the logs.
  • same first 3 steps of pressing powerkey interaction
  • selecting lock in the menu, systemui calls com.nokia.mce.request.powerkey_callback with value uint32=4 (I guess this is the menu value for locking)
  • mce calls com.nokia.system_ui.request.powerkeymenu_close to close the menu, systemui will ack later with reply value uint32=0
  • mce calls com.nokia.system_ui.request.devlock_open (uint32=3) to open the keypad, systemui will ack later with reply value uint32=1
  • systemui calls com.nokia.mce.request.powerkey_callback with value uint32=-4
  • mce calls com.nokia.system_ui.request.powerkeymenu_close again, systemui will ack later with reply value uint32=0
  • systemui sends ack replies mentioned before, and updates gconf value /system/systemui/devlock/devicelock_autolock_enabled
  • mce sends signal com.nokia.mce.signal.devicelock_mode_ind with value
    string "locked"
  • mce updates gconf values /system/osso/dsm/locks/devicelock_failed and devicelock_total_failed
  • after entering a code, systemui's device lock plugin will adquire a dbus name to send messages to mce
  • now comes the interesting part, device lock plugins calls com.nokia.mce.request.validate_devicelock_code with two string values. The second one is a crypt seed for md5 (see man 3 crypt), the first one is the result of calling crypt with the typed code and the seed.
  • mce receives the seed, so it can use it to call crypt with the unlock code stored in the device and check the result against the crypted typed code. If it is correct, mce will reply string "true", if it is incorrect, it will reply "false" to the previous call.
  • systemui calls com.nokia.mce.request.devlock_callback with value uint32=3 if the typed code was wrong, and uint32=2 if it was correct
    If the typed code was wrong
  • systemui calls com.nokia.mce.request.devlock_callback with value uint32=3
  • mce calls com.nokia.system_ui.request.devlock_open (uint32=2)
  • mce updates gconf values devicelock_failed, devicelock_autolock_enabled, devicelock_total_failed
  • mce sends the locked signal again
  • mce calls com.nokia.system_ui.request.devlock_open (uint32=3) again
    If the typed code was correct
  • systemui calls com.nokia.mce.request.devlock_callback with value uint32=2
  • mce calls com.nokia.system_ui.request.devlock_close
  • mce sends signal com.nokia.mce.signal.devicelock_mode_ind with value
    string "unlocked"
  • mce updates gconf values devicelock_failed, devicelock_autolock_enabled, devicelock_total_failed

Last edited by maacruz; 2011-02-09 at 23:12.
 

The Following User Says Thank You to maacruz For This Useful Post:
Reply

Tags
bada blows, bada rox


 
Forum Jump


All times are GMT. The time now is 00:29.