Originally Posted by auouymous

New ASUI and settings test binaries.

• fix: cpu usage should no longer exceed 100% or go negative
• fix: turns off wifi and bluetooth before entering flight mode
• only start/stop ssh servers if their init.d files exist
• changed start/stop service buttons to toggle buttons to better highlight started services, at least if you use Diablo5 theme

I'm still testing it but the battery drain rate should work correctly now, even after a charge, and is documented on the widget page.

@ maacruz, does this fix your ICD problem?

Originally Posted by yukop4

installed asui and it worked well but when i reboot it show picture of pamela andersons boobs then it switch off

why it does this

Originally Posted by maacruz

No, ICD keeps scanning .

Originally Posted by auouymous

SystemUI magically enters flight mode, maybe via one of its powerkeymenu callback return values, and then MCE tells SystemUI to open a modechange dialog to get confirmation before it sends out the flight signal.

Code:

method call sender=:1.5 -> dest=com.nokia.system_ui serial=3277 path=/com/nokia/system_ui/request; interface=com.nokia.system_ui.request; member=modechange_open
   string "com.nokia.mce"
   string "/com/nokia/mce/request"
   string "com.nokia.mce.request"
   string "modechange_callback"
   uint32 0
method call sender=:1.1543 -> dest=com.nokia.mce serial=12 path=/com/nokia/mce/request; interface=com.nokia.mce.request; member=modechange_callback
   int32 1
signal sender=:1.5 -> dest=(null destination) serial=3279 path=/com/nokia/mce/signal; interface=com.nokia.mce.signal; member=sig_device_mode_ind
   string "flight"
method call sender=:1.1543 -> dest=com.nokia.mce serial=13 path=/com/nokia/mce/request; interface=com.nokia.mce.request; member=modechange_callback
   int32 2

ASUI calls req_device_mode_change and MCE sends out the signal confirming the change.

Code:

method call sender=:1.1572 -> dest=com.nokia.mce serial=23 path=/com/nokia/mce/request; interface=com.nokia.mce.request; member=req_device_mode_change
   string "flight"
signal sender=:1.5 -> dest=(null destination) serial=3299 path=/com/nokia/mce/signal; interface=com.nokia.mce.signal; member=sig_device_mode_ind
   string "flight"

All the wifi and bluetooth dbus activity after the flight signal is the same for SystemUI and ASUI. I don't see how the different MCE calling mechanisms would make any difference since the services all respond the same.

@ maacruz, could you try logging `dbus-monitor --system --profile` after entering flight mode with SystemUI and see if ICD still scans for networks?

Originally Posted by maacruz

Btw, your dbus-monitor logs lack return messages, you should install DT's dbus packages.

Originally Posted by auouymous

I have DT dbus packages and method_return is enabled.

Originally Posted by auouymous

Could you install the debug binary asui dd;asui id as root, reproduce the problem and then send me the log file in /root/asui-*? After you have reproduced the problem type asui r as root to restore the release binary.

And play around with the power button, different combos of short and long taps and something might eventually cause it to shutdown. Also try setting the secondary unlock key to 'none'. Something is different on your device and we just need to find out what that is.

Do you have ssh? It might be a good idea to install it on your device so you can reboot it via ssh while conducting these tests.