This API allows app to construct custom metrics based on labels
chosen by the app developers. Also added some buttons to manually
test this functionality in the dogfood app.

Test: Verified that Android can be built and tested with custom app.
Bug: 69522276
Change-Id: Ifb7abea4c1d62fb435a9cb6f32df12bc2234d82f

Merge "Merge "Use consistent naming for allocating SPI." am: bf48afea am: 4753ed4b am: f71c95df"

am: f71c95df

Change-Id: Ib6845ab0d7f385fbd1d59c0179771542e12c8be0

am: 4753ed4b

Change-Id: Ib5d89044313341790b1ee9271642072ddce181af

am: bf48afea

Change-Id: I9adb5c14e91b33f09707c85c865cf2fc454f80ba

* changes:
  BatteryService: don't set battery low or critical states if no battery
  BatteryStats: Don't collect battery stats if no battery

am: 8e509222  -s ours

Change-Id: I2dd835282a9de847cd3e5fd0e5a0e54bff2538af

am: 3a3fc7a4

Change-Id: Ia40246372d156d308c4e3930c3789dfe0a1010f8

am: 3adfec2d

Change-Id: I98d29b9f3aeeaf78ba93b631b0746cc37ac9e7e5

am: 059f59cc  -s ours

Change-Id: I01e484836f1ac335414acba266b0abb6e191bedc

If device has no battery then never set states "battery low" or
"battery critical".

Bug: 34507420
Test: manual: inspection (with hack to disappear the battery device)
Change-Id: I1eee79032507121de2fa7bf29d1359a29f21d3d0

If the device has no battery, or has a removeable battery that is
currently removed, do not collect battery statistics.

Bug: 34507420
Test: manual: dumpsys batterystats
Change-Id: Id8edb494f353a40c648f798690f611f89f464d34

am: 67c9a436

Change-Id: If333cd7cee4785779cdd4acc8421059c4a947dd2

am: 6e41b2c5

Change-Id: I9fd9ab01b770fc8a1c5998d3a4c3e824123e2076

If the KeyGenParameterSpec passed into
DevicePolicyManager.generateKeyPair contains an attestation challenge,
request an attestation record for the newly-generated key with the
challenge provided.

This particular implementation was chosen, rather than letting the
attestation record be generated at the same time as key generation, to
avoid having the attestation chain stored in Keystore and associated
with the generated alias.

The rationale is that this is a key that is potentially accessible by
multiple applications and the attestation chain may end up being sent
as a TLS client certificate chain, for example.

As the attestation challenge should be unique per device, to avoid
the potential of sending / sharing unique device information, by
explicitly requesting an attestation record after key generation, the
attestation record is only returned to the generateKeyPair client and
not persistend in Keystore.

Bug: 63388672
Test: New CTS test to be run with: 'cts-tradefed run commandAndExit cts-dev -a armeabi-v7a -m CtsDevicePolicyManagerTestCases -t com.android.cts.devicepolicy.DeviceOwnerTest#testKeyManagement -l DEBUG'
Change-Id: I95a9aef179173b571b533301ac438c675e8fe702

No longer used.

(cherry-picked from commit c87f8124)

Bug: 37966211
Test: make
Merged-In: I5a1ef82ed6d8cf771513b86960c3d1d8cf7418f9
Change-Id: I5a1ef82ed6d8cf771513b86960c3d1d8cf7418f9

+ Remove the protobuf *Metric object from MetricProducers
   -- This saves ~150 bytes per metric.
+ Remove the StatsdConfig from ConfigManager
   -- This saves us xKB per config.
+ Also remove alerts from fake config to avoid crash (Bug: 70627390)
+ Other misc fixes too.

Test: statsd_test & manual
Change-Id: Ied4eb3fa31c50599817b3a5e1caf5077c487fad2

Merge "use running sum for ValueMetricProducer bucket simplify ValueMetricProducer logic for pulled data"

am: b5a913cc

Change-Id: Idcaa642e763284dfde7b52f2f87e28796675b127

am: 4f697fe5

Change-Id: Ice43c79858930ccc48b9470152e0af2d99e966ae

While the doc suggested that the phone number was "incoming" (e.g.
only populated for incoming calls), it should also be populated for
outgoing calls.

Bug: 67748129
Test: Verified expected behavior on Taimen running OC-MR1, added CTS
test (see other CL in this topic)
Change-Id: I1ddd9c042f287953358a794b91b2af5ed6f5b597
Merged-In: I1ddd9c042f287953358a794b91b2af5ed6f5b597

am: 11ec2eb1

Change-Id: I7e527a58332a4453fe104538e55a60a444602159