@Andrea

Thanks for the updates.

So our theory that this is related to a large number of APs  doesn't pan
out, as you're able to reproduce this at the office with only 25 access
points involved ( per the output of my script ).

Also, I'm pretty sure the problem is related to WiFi roaming.  It
appears when you first enable WiFi at Bluefin, goes away when WiFi is
disabled, and re-appears when WiFi is re-enabled while at Bluefin.

Looking at your syslog output, I see your phone associate with the
office network around 10:40:05, however I also see a suspicious message
right before the connection activation succeeds:

Aug 19 10:40:05 ubuntu-phablet NetworkManager[1417]: <info> (wlan0):
roamed from BSSID 18:33:9D:F8:AA:B0 (Canonical-2.4GHz-g) to (none)
((none))

This doesn't appear to affect your connection though, as there's no
subsequent disconnect, and I also see multiple DHCP renewals on wlan0 @
10:48, 10:56, 11:05, and 11:14.

As for dbus-monitor output, we're really more concerned with the traffic
on the session bus.   Can you please try disabling the upstart bridge as
mentioned in comment #14?

>  * This next step may break other things on your system, but it's worth a 
> try... If you can reliably reproduce the problem, 
> before entering the area with the excess of APs, please run the following 
> command as the phablet user on the phone:
> 
> % stop upstart-dbus-system-bridge
>
> * When you're done testing, please remember to start the bridge ( replace 
> "stop" with "start" ), or reboot the device.

Please note whether or not this makes the stuttering go away.

Can you also try disabling indicator-network ( as phablet, just run
'stop indicator-network ) and re-test too?

Finally, do you have another device ( ie. an arale or mako ) you could
compare results against?

I'm actually working on a related bug for BQ, and may have another test
package for you to try, but I'd like to see whether disabling the bridge
and/or indicator-network has any effect on the issue first.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1480877

Title:
  Access points' "PropertiesChanged" dbus signals freeze UI on mobile
  devices

Status in indicator-network package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  Krillin, rc-proposed, r83

  
  DESCRIPTION:
  I've been trying to track down the cause of the occasional UI freezes on my 
Krillin device, and I noticed that whenever the UI freezes for 2-4 seconds, I 
get a burst of "PropertiesChanged" signals in dbus-monitor

  Here's a log of what's shown in dbus-monitor:
  http://pastebin.ubuntu.com/11992322/

  I'd guess the problem is in the code that actually catches the signals
  and acts accordingly.

  HOW TO REPRODUCE: 
  1) Move to a place where many wifi hotspots are available
  2) Connect the device via USB and run "phablet-shell" and then "dbus-monitor"
  3) Use the device while keeping an eye on dbus-monitor output

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1480877/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to