Comment 2 for bug 1496875

Ok so I can reproduce this issue flawlessly by connecting to a subscription hotspot nearby and refreshing any remote scope (In fact there seems to generally be high CPU usage spikes coming from the smartscopesproxy process even on a working wifi spot). This is on the mako with:

build: 113
channel: ubuntu-touch/rc-proposed/bq-aquaris.en

I then upgraded to:

build: 115
channel: ubuntu-touch/rc-proposed/bq-aquaris.en

and didn't see the issue anymore. The smartscopesproxy process seemed to work fine with no excessive CPU usage. However, I did see a completely new issue: https://bugs.launchpad.net/ubuntu/+source/android/+bug/1497167. Perhaps this masked smartscopesproxy's usage? Not sure.

Then I flashed my BQ with the latest image from ubuntu-touch/rc-proposed/bq-aquaris.en:

current build number: 127
device name: krillin
channel: ubuntu-touch/rc-proposed/bq-aquaris.en
last update: 2015-09-18 04:54:49
version version: 127
version ubuntu: 20150918
version device: 20150821-736d127
version custom: 20150821-887-33-32-vivid

I tried the same test and did not experience any excessive CPU usage from smartscopesproxy. I checked the version of libunity-scopes3 on both the mako 113 and krillin 127, and both are at 0.6.19+15.04.20150724.3-0ubuntu1.

So to me this looks to be a mako specific problem. The same version of smartscopesproxy is on both devices, yet on the mako it seems to eat the CPU like crazy.