diff options
| author | Bookatz <bookatz@google.com> | 2018-03-26 13:34:56 -0700 |
|---|---|---|
| committer | Bookatz <bookatz@google.com> | 2018-03-27 15:14:23 -0700 |
| commit | e5ec0b443346f9f019b2f6ef7afb4043364ebae7 (patch) | |
| tree | d46d5b003605cc45b7eeae872db6638e1bf1df27 /rs/java/android/renderscript/ProgramFragmentFixedFunction.java | |
| parent | dda147e179d5dc190191866221d74ae42675a263 (diff) | |
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
Diffstat (limited to 'rs/java/android/renderscript/ProgramFragmentFixedFunction.java')
0 files changed, 0 insertions, 0 deletions