| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
| |
Since all pullers now use StatsEvent instead of StatsLogEventWrapper,
this class can be deleted.
Test: m -j
Test: m -j statsd_test
Bug: 146578681
Change-Id: I63013768ee13af0235f8cd857ca3fc16d2fd877f
|
| |
|
|
|
|
|
|
|
|
| |
Users of these APIs are planning to move to apex.
Test: atest FrameworksCoreTests:android.os.WorkSourceTest
atest CtsOsTestCases:android.os.cts.WorkSourceTest
Bug: 143551137
Change-Id: I2e97a8b469254ea92e3ee21571ee8ae3cbb9abbe
|
| |
|
|
|
|
|
|
|
| |
If they were null, then the Parcelable would fail to work.
Bug: 126726802
Test: manual
Change-Id: I7929ffa2f20e5de1c8e68e8263cca99496e9d014
Exempt-From-Owner-Approval: Trivial API annotations
|
| |
|
|
|
|
|
|
|
| |
Creates a hidden api to register puller callbacks for vendor atoms.
Test: manual local test
Test: statsd unit tests
Bug: 119898637
Change-Id: Id28817b8fc718e128adc4e1c6b2e997db84517f9
|
| |
|
|
|
|
|
|
|
| |
This reverts commit 9c7b1319962673658ee28a7845fc0a7cf840c61e.
Reason for revert: Fixed build failures due to merge
Change-Id: I7d7bfed3a3234b966f3fe3fd6e0cbc63d2bedf83
Test: unit test
|
| |
|
|
|
|
|
|
| |
This reverts commit ce8e4dce609541f90c444f27250a6a341b3f1d23.
Reason for revert: breaking multiple targets in master
Change-Id: I3ee74b314e06cb2c4d3d6da82ca116a91aad67d4
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
+ also rewrite map and merge isolated uid to host uid.
output:
Pull from 10014: { 1541137009000000000 10430748770707
(10014)0x2010101->1[I] 0x2010182->lala1[S] 0x2010201->2[I]
0x2018282->lala2[S] 0x20000->10430750[L] }
Bug: 119043339
Bug: 117975376
Test: unit test
Change-Id: Ib6e3ea0f76594438ee1b3e12e965d85fefb405d7
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
BatteryStats calculates power usage of the device and various components
(such as apps). This information is used, e.g., in the battery panel of
Settings. We now log it to statsd. It can be used for validating how
good the information displayed in Settings is. In the long-term, it is
likely not ideal for off-device calculations, since that can be
hopefully estimated using statsd's raw data.
Three atoms: one for the total power use, one for the power use of each
uid, and one for each non-uid component. Since they will all likely be
pulled together, StatsCompanionService will provide stale data for
BatteryStats pulls called within a second of a previous BatteryStats
pull.
Also in this cl:
Remove StatsLogEventWrapper.writeDouble. Statsd doesn't support actually
writing doubles into its proto reports, so having this function is
misleading (the data will get to statsd and then be completely ignored).
It's less confusing if we don't pretend it does something.
Change-Id: If80bab8ea938afa4632535bb88ff59879fbe8099
Fixes: 119111972
Test: cts-tradefed run cts-dev -m CtsStatsdHostTestCases -t android.cts.statsd.atom.UidAtomTests#testDeviceCalculatedPowerUse
Test: cts-tradefed run cts-dev -m CtsStatsdHostTestCases -t android.cts.statsd.atom.UidAtomTests#testDeviceCalculatedPowerBlameUid
Test: BatteryStatsHelperTest#testDrainTypesSyncedWithProto
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
pull constants from PowerProfile into statsd for power model
calculations. The data is mostly from power_profile.xml
power_profile {
power_profile_proto {
cpu_suspend: 5.734
cpu_idle: 1.389
cpu_active: 18.76
wifi_controller_idle: 2.0
wifi_controller_rx: 107.0
wifi_controller_tx: 371.0
wifi_controller_operating_voltage: 3700.0
bluetooth_controller_idle: 0.01
bluetooth_controller_rx: 8.0
bluetooth_controller_tx: 7.0
bluetooth_controller_operating_voltage: 3300.0
modem_controller_idle: 105.0
modem_controller_rx: 175.0
modem_controller_tx: 176.0
modem_controller_tx: 216.0
modem_controller_tx: 300.0
modem_controller_tx: 427.0
modem_controller_tx: 604.0
modem_controller_operating_voltage: 3700.0
gps_signal_quality_based: 49.0
gps_signal_quality_based: 11.0
gps_operating_voltage: 3700.0
screen_on: 178.708
screen_full: 240.79
audio: 75.6
video: 50.93
flashlight: 298.498
camera: 1152.292
battery_capacity: 3450.0
cpu_cluster {
cores: 2
speed: 307200
speed: 384000
speed: 460800
speed: 537600
speed: 614400
speed: 691200
speed: 768000
speed: 844800
speed: 902600
speed: 979200
speed: 1056000
speed: 1132800
speed: 1209600
speed: 1286400
speed: 1363200
speed: 1440000
speed: 1516800
speed: 1593600
core_power: 11.272
core_power: 14.842
core_power: 18.497
core_power: 22.518
core_power: 25.967
core_power: 31.694
core_power: 37.673
core_power: 42.859
core_power: 46.872
core_power: 57.92
core_power: 67.561
core_power: 76.303
core_power: 87.613
core_power: 97.045
core_power: 109.544
core_power: 122.054
core_power: 136.345
core_power: 154.435
}
cpu_cluster {
id: 1
cores: 2
speed: 307200
speed: 384000
speed: 460800
speed: 537600
speed: 614400
speed: 691200
speed: 748800
speed: 825600
speed: 902400
speed: 979200
speed: 1056000
speed: 1132800
speed: 1209600
speed: 1286400
speed: 1363200
speed: 1440000
speed: 1516800
speed: 1593600
speed: 1670400
speed: 1747200
speed: 1824000
speed: 1900800
speed: 1977600
speed: 2054400
speed: 2150400
core_power: 7.055
core_power: 11.483
core_power: 14.979
core_power: 19.642
core_power: 23.167
core_power: 27.479
core_power: 31.632
core_power: 39.192
core_power: 47.817
core_power: 55.659
core_power: 64.908
core_power: 73.824
core_power: 85.299
core_power: 96.036
core_power: 109.233
core_power: 118.56
core_power: 132.959
core_power: 143.692
core_power: 161.378
core_power: 180.616
core_power: 193.897
core_power: 214.361
core_power: 238.338
core_power: 265.759
core_power: 297.918
}
}
}
Bug: 113353350
Test: manual test on statsd
Change-Id: I1edd4db255c0440ddbff1d40e1515caaccbc73f8
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When statsd pulls data from StatsCompanionService, the data is put into
log_msg format on java side and expanded into LogEvent on cpp side.
There is a lot of dependency on log_msg and liblog to add new types.
There is pending bug to rewrite thta part of the code in statsd to
completely rid the legacy of logd and liblog. But that may not happen
soon.
Now we can support new storage type.
Also no need to specify number of fields in StatsLogEventWrapper cstr,
which is a source of bug in P.
Bug: 115775035
Test: manual test and cts test
Change-Id: Id1f0b033885da6f3bcebe043968061821db48f35
|
| |
|
|
|
|
|
|
|
|
| |
This reverts commit 6188aa32946f6372f912ccc9281956ca38a8a264.
Reason for revert: ag/4819964 has now been submitted. undoing the roll back.
Test: revert
Test: manually verified output is the same as diskstats.
Change-Id: I9a3292f66e1e28661e1d29f3befd002073b681c1
|
| |
|
|
|
|
|
|
|
|
| |
Leaving a no-op CREATOR can lead to issues. We throw a run-time
exception to prevent anyone from using this. The StatsLogEventWrapper is
meant to be write-only since it's only used to send data to statsd.
Bug: 112550251
Test: Tested with provided POC app by external researcher.
Change-Id: I001d84e2a61a1cd8a4f59aa156ca52f73ad0f6e1
|
| |
|
|
|
| |
Test: statsd cts test
Change-Id: I2658dba747ff93a120c50b5294f696918588e9fe
|
| |
|
|
|
|
|
| |
lose data
Test: manual test
Change-Id: I7bf014e7e2007e0e065aa7ca99522d9effcf1a68
|
| |
|
|
|
|
|
| |
bug fix for ConfigManager fake config
Test: cts test
Change-Id: Ia07992dffb6520074c908151c96da1aa931f97f0
|
|
|
Previously, pulled data was returned as a string. We instead
return the data as an array of StatsLogEventWrapper, which encodes
using the binary-encoded format liblog uses. StatsD uses the same
parsing as for pushed events to convert these. This CL also fixes
the parsing of log_msg since the strings were previously emptied
before we had a chance to read the values.
Note that the cpp-aidl can't support List of Parcelable, so we
have to return the results as an array.
Test: Manual using the new command in StatsService to print results.
Also created a new unit-test by creating a dummy pull code of -1,
but this test is deleted since it required creating a fake output in
StatsCompanionService.
Change-Id: I1cfb9ea081a59292a60e934e8527adc40982ed80
|
