View Single Post
Posts: 875 | Thanked: 918 times | Joined on Sep 2010
#535
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?