| d4036b6b7f9609fe09efabdbfbb8c8f9428f76f7 |
|
28-Jul-2015 |
Andreas Gampe <agampe@google.com> |
SensorService: Fix some warnings
For build-system CFLAGS clean-up, remove unused variables.
Also fix some warnings related to format strings, and signed
comparisons.
Bug: 18632512
Change-Id: I5e48dce36678c12069c0e162b920870de81b89f2
/frameworks/native/services/sensorservice/BatteryService.cpp
|
| 63ff1c644f785c78adbf65b9abf6b998cee2c7a1 |
|
25-Sep-2013 |
Mike Lockwood <lockwood@google.com> |
Cleanup Binder interface between sensorservice and BatteryStats
Change-Id: Ia507160a2534059afe93849c8efc8407a046b50e
/frameworks/native/services/sensorservice/BatteryService.cpp
|
| ee83397bb07ef6807ca3f4d691da7d4fd7d632f0 |
|
16-Jul-2013 |
Dianne Hackborn <hackbod@google.com> |
Fix issue #9860494: Waiting for service batteryinfo...
I changed the name of the service, this needs to follow.
Change-Id: Id8e346cee9d75cfe142cd43f6aea43302878b6dc
/frameworks/native/services/sensorservice/BatteryService.cpp
|
| 787ac1b388f144f5e6dd38f8b807866a5256dafc |
|
19-Sep-2012 |
Mathias Agopian <mathias@google.com> |
improve sensor battery usage tracking
until now we were tracking when a sensors was
physically enabled or disabled and we were reporting
that to the BattaryService.
this wasn incorrect because we could have several different
apps enabling the same sensor, so the accounting by the
battery service would be incorrect in that case (depending
on the order in which these apps disabled said sensor).
BatteryService tracks sensors per uid, however SensorService
does this per binder connection, so we could have several
binder connections for the same uid, to solve this we keep
a list of sensor/uid -> count, which is the bulk of this
change.
Bug: 6661604
Change-Id: I561c198c42ba1736a8671bdacda4c76d72b9dd6f
/frameworks/native/services/sensorservice/BatteryService.cpp
|