As part of preparing to enable the new binary XML wire format across
the device, we ran a large suite of unit tests which uncovered a
handful of bugs where client code was assuming that the serializer
would create TEXT tokens for newlines between tags.
Also relaxes all binary XML classes to accept either "UTF-8" or
"utf-8" as the encoding name. Slight bug fixes to clear names, text,
and attributes for each event to match XmlPullParser documentation.
Fixes for existing unit tests that were assuming human-readable XML,
or assuming that the serialization would perform UTF-8 validation.
Bug: 171832118
Test: atest FrameworksServicesTests
Change-Id: I841fe41e4967b36ab17551294ae0f42fb87a8e71
Switching the share action to a Supplier interface allows us to
maintain the current code style, while ensuring that the
APIs required to start the transition are called when the
share chip is pressed.
Bug: 174811491
Test: manual
Change-Id: I201b82eaea650fcef23909212385fd6d56831429
Modeled power components are computed without regard
for power measured with ODPM/rails.
The purpose of this is mostly to support testing
of power models themselves.
Bug: 175644968
Test: mp :BatteryStatsViewer && adb shell am start -n com.android.frameworks.core.batterystatsviewer/.BatteryStatsViewerActivity
Change-Id: Icca6fe6954776baed48b593017abd8c9bab4dfb7
Adds support for blaming measured energy (rail) data on individual uids
starting with display.
1. Display measured energy data is apportioned to apps.
This is based on their relative foreground activity time and PROCESS_STATE_TOP
time, in accordance with the current BatteryStatsHelper smearing algorithm.
2. Infrastructure is in place for additional energy rails
to do likewise.
3. Fixes a bug in Bluetooth activity data not being reset properly
4. Fixes a bug in that resets didn't handle external data properly
Test: atest FrameworksServicesTests:com.android.server.am.MeasuredEnergySnapshotTest \
FrameworksCoreTests:com.android.internal.power.MeasuredEnergyStatsTest \
FrameworksCoreTests:com.android.internal.os.BatteryStatsNoteTest#testUpdateDisplayEnergyLocked
Bug: 174818228
Bug: 174818483
Bug: 174818545
Bug: 173652857
Change-Id: Ibade3689ad7c3c22e181c8086df25c203fe0ad6b
After the pipeline changes to Pointer Capture, this CL cleans up the
following:
- The old way of notifying windows of Pointer Capture
(IWindow::dispatchPointerCaptureChanged) is removed.
- Tracking Pointer Capture in WindowManagerService is removed.
Bug: 141749603
Test: manual, flash crosshatch, pointer capture works.
Change-Id: I5bbcef42fe8d0d93a64a4a411b1d493fcb800f92
IME can use this method to redo spell checking after it has learned a
new user dictionary word.
Bug: 166304720
Test: atest CtsInputMethodTestCases:SpellCheckerTest
Change-Id: I956cd46f25bb77b7e1a6a3e1478c0d7efa1a056a
We're not tinting, we're actually drawing an alpha blended color on top
Test: Manual
Bug: 159712515
Change-Id: I12788b19ecf0d4a8e65056914bc0dafd16f417c9
For now the field is always set to 0 since we do not
get this data from sf yet
Test: UTs for affected classes
Bug: 171049584
Change-Id: I128afe514393e78636c01469075d415068326ef8
We trade off increased cost of (rare) mutations of the set of "bad" apps
in order to make the core lookup "is this specific app bad?" lock-free.
Locking discipline turned out to be a dominant cost in a very hot code
path within the running system, even uncontended.
Bug: 175339368
Test: tbd
Change-Id: I8803a177d46b01b86897f1e8d0966eb2452849fd
