commit 509f07a7e565da54efd1c397f026727cd41e9345
author Bookatz <bookatz@google.com> Mon Mar 26 13:34:56 2018 -0700
committer Bookatz <bookatz@google.com> Tue Mar 27 15:14:23 2018 -0700
tree a8bdc965e7d5d70d8b16b7d91d333fc4723ec8c7
parent 2f3c07447e22463c1b5e55f2113464a22f743d48

Fix statsd ble scan logging

Ble scan logging in statsd has a few problems:

1. We want finer-grained detailed than just 'unoptimized'. What defines
unoptimized should be done at the config level, not be hard-coded.

2. The current mechanism is actually incorrect. When reset is called,
each ble scan is only told *once* that it stopped, but if the nesting
level is higher than that, statsd will think it is still nonetheless
running.

Test: cts-tradefed run cts-dev -m CtsStatsdHostTestCases -t android.cts.statsd.atom.UidAtomTests#testBleUnoptimizedScan
Test: cts-tradefed run cts-dev -m CtsStatsdHostTestCases -t android.cts.statsd.atom.UidAtomTests#testBleScan
Fixes: 71607284
Fixes: 69478888

Change-Id: Ied44f79aa569daab2acc85e90627a9736d0689a3