Comment 57 for bug 1480877

So re-testing with krillin ( rc-proposed, #162 ).

Confirmed that using a patched version of dbus 1.8, the match rule limits aren't enforced, so each of the loc processes slowly grows its number of match rules till they cap out at 5000 each.

So, WiFi enabled & connected, with the HERE app running *or* the Nearby or Today scopes currently selected.

The scan interval of the phone is controlled by time in a particular state. If "disconnected", the scan interval starts low, and eventually tops out at ~60s. Likewise, if "connected" ( to an AP ), it'll top out at 2m.

What's odd, is how location-services seems to be influencing scanning. If I bring the HERE app, or the Today or Nearby scopes to the foreground, the phone starts to do WiFi scans every 15s. If I bring another app to the foreground, this behavior stops, most of the time. I've able to get the phone into a state where the interval stays at 15s, no matter what app/scope is visible. Perhaps the location-service is losing state? Confirming scan interval is a matter or running wpa_cli and watching the events output as scan occur.

Note, to mimic normal usage, I usually start fix or six apps ( camera, system settings, clock, term, messages, music ).
Also, my confirmation of whether or not the the bug is occurring is *not* based on top, it's based on observation of the UI.

I see UI freezes that occur in sync with WiFi scans, that can last anywhere from 1-6s when:

 - using the switcher, animation ( horizontal or vertical ) freezes
 - edges stop responding
 - app scrolling freezes

I also began to see the Shutdown menu displayed every so often when I let the screen go off, and then woke via the power button.

Freezes start at around 1s when the match rules for the loc services hits ~1000. As the match rules continue to increase, the lockups do seem to last a bit longer over time. When they've maxed out, the lockups might be as long as 3-5s.

When I disabled WiFi, the UI freezes disappeared. This also reset the counts... so I let the phone run overnight and the counts rose back up again, and the freezes returned. Note, overnight all of the running apps appear to have been killed.

Finally, I left WiFi on, but instead stopped the location services process per comment #56. At this point the freezes go away almost completely ( note by disabling location services, the scan interval goes back up to 60s ). I say *almost* go away as there's still the slightest tick whenever a scan occurs, but it's orders of magnitude smaller than when the rule counts have been max'd out.