| 15c4e31b0f7226987267656926c98d2c5d53585a |
|
03-May-2016 |
Badhri Jagan Sridharan <Badhri@google.com> |
Change low power stats format to make it easier for parsing
New format: PlatformIdleStat state_1 name=XO_shutdown time=0 count=0
voter_1 name=APSS time=48264099 count=484 voter_2 name=MPSS
time=48573849 count=39857 voter_3 name=LPASS time=49584723 count=2082
state_2 name=VMIN time=47171000 count=38222
Old format: PlatformIdleStat XO_shutdown_time=0 XO_shutdown_count=0
APSS_time=9467486 APSS_count=583 MPSS_time=10835070 MPSS_count=9131
LPASS_time=10624719 LPASS_count=595 VMIN_time=9231000 VMIN_count=7878
In the old format it was hard to differentiate between the various
low power states and the voters for each state.
Bug:26564574
Change-Id: I3930aaf1c8c6e17066ef043552096ba61373f9f4
/frameworks/base/services/core/jni/com_android_server_am_BatteryStatsService.cpp
|
| 68cdf1997f7b007e4c81089bc402a0356292f4c2 |
|
04-Apr-2016 |
Badhri Jagan Sridharan <Badhri@google.com> |
Add low power stats to batteryhistory
Exports SOC specific low power state info to batterystats service.
BatteryStats service queries the powerHAL module whenever and
updates the HistoryStepDetails whenever setBatteryState is called by the
BatteryService. The stats get appended to the battery history whenever
there is a change in the battery level.
Bug: 26564574
Change-Id: I02b4db00aec0c69d1558492224f3a4dc1c386fa6
/frameworks/base/services/core/jni/com_android_server_am_BatteryStatsService.cpp
|
| b57dd722f1dc0663417da37d3a82f8283ad3c982 |
|
24-Sep-2015 |
Elliott Hughes <enh@google.com> |
resolved conflicts for a884d81e to stage-aosp-master
Change-Id: Ice485967fa96f13786024b6939b826638e906ff0
|
| 76f6a86de25e1bf74717e047e55fd44b089673f3 |
|
19-Sep-2015 |
Daniel Micay <danielmicay@gmail.com> |
constify JNINativeMethod function pointer tables
Change-Id: I4036c924958221cbc644724f8eb01c5de3cd7954
/frameworks/base/services/core/jni/com_android_server_am_BatteryStatsService.cpp
|
| 515702c29e5eae0e3f02b5d65ed86218813e8945 |
|
24-Jul-2015 |
Adam Lesinski <adamlesinski@google.com> |
BatteryStats: Decode wakeup reasons in Java
Wakeup reasons come from drivers and sometimes are malformed UTF-8.
Decode them in Java so we can easily replace malformed characters
and still have user visible strings.
Bug:22368519
Change-Id: Ifade1a7fcdf6545e7e344d74390200c329430e14
/frameworks/base/services/core/jni/com_android_server_am_BatteryStatsService.cpp
|
| 87fd322ecb5cd7582f449e5b4721a1e4dea062e6 |
|
25-Jun-2015 |
Adam Lesinski <adamlesinski@google.com> |
BatteryStats: Record suspend abort reasons
Bug:18179405
Change-Id: I28c77f035400c32375dbe6d3c7057c0a2c093e8f
/frameworks/base/services/core/jni/com_android_server_am_BatteryStatsService.cpp
|
| 6b0331a03025f2ea8c966bf9406dd5788ffa176e |
|
06-Jun-2015 |
Adam Lesinski <adamlesinski@google.com> |
Wait for wakeup_reasons on first init
Previously if we were initializing the wakeup callback for the first time,
we would read the wakeup_reason file and ignore the contents, sending a
wakeup_reason of "unknown" up to BatteryStats.
Now we initialize the callback and wait on it immediately. Wakeup reasons are reset
when we go into sleep, so when we wakeup, we will always have fresh wakeup reasons.
Bug:21665793
Change-Id: I20832d8a143fc2715915fcecf4bb71980f279440
/frameworks/base/services/core/jni/com_android_server_am_BatteryStatsService.cpp
|
| a1bd79268be693f04f4adee90673d6ed400cc9fd |
|
21-Mar-2014 |
Dianne Hackborn <hackbod@google.com> |
Battery stats: track actually running time
Use the uptime while creating the battery stats history to
generate a new event indicating when the CPU is actually running.
We can do this in combination with the new event reporting when
the CPU comes awake, looking at the difference between the
uptime and elapsed time at that point to determine when it last
when to sleep.
Also use this information to generate a new set of aggregated
states, the uptime caused by each wake reason.
Finally use new radio down timestamp to adjust the times we
compute for radio use. Note that this information is not (yet)
being used to adjust how these are recorded in the history.
Change-Id: I723b3b526c8e7d64de0cac9d1193e04132d5a3e4
/frameworks/base/services/core/jni/com_android_server_am_BatteryStatsService.cpp
|
| c51cf03cf2458c8c137f60c7379f2cccf681d16f |
|
03-Mar-2014 |
Dianne Hackborn <hackbod@google.com> |
Start recording wakeup reasons in battery history.
Depends on a modification to libsuspend so that we can get
a callback each time the device wakes up, to read the current
wakeup reasons from the kernel. These are then stuffed in
to a new field in the battery history.
Also add new dump options --history-start and --charged
to better control what is dumped.
Finally the alarm manager uses a "*walarm*" tag for history
item wake locks that are coming from a wakeup alarm.
Change-Id: I457571973d5b2b5fdc4e4b63ab16275db20d7edd
/frameworks/base/services/core/jni/com_android_server_am_BatteryStatsService.cpp
|