This CL logically reverts recent CLs [1][2][3][4][5][6][7][8][9] to
switch back to the previous sync IPC approach in IInputMethodManager
except for the following two IPCs.
* reportPerceptibleAsync
* removeImeSurfaceFromWindowAsync
Reason for revert:
We need more time to understand its performance implications.
[1]: If4b40244a2e0e3b11c38c1da9340ba8e5166ad64
b9590fa1e1
[2]: If79e063641a01b325c63eb9f871f5b992d7c0b72
5a5648dcb5
[3]: I1547b98b2aacf764e33aadc9ab784f2013f58f2f
d833f0dab4
[4]: I646ef4ae0570aae1812ea267f309441fdec6938d
38fd020616
[5]: Iaa63e01453da4ff0e3f446eac036b3be3180cb73
4a820ccc41
[6]: Id516fd1c961f43ac3e139c88d7ed004c188d458b
0a32fd21ef
[7]: Icb396ae5d74060af69c4ecb16723b2e37b9f2067
c4663ba6a9
[8]: I3eafbc28ed3acf3ba859885bf201cb06b3149b94
f226a79fee
[9]: Ic584203c1221fbae17f5e2d8f09e3992df061646
5e2d9f271d
Bug: 163453493
Bug: 174892351
Fix: 190486491
Test: atest CtsInputMethodTestCases
Change-Id: If16ac0de536d9089eb04f6e07b1ee47378124658
Merged-In: If16ac0de536d9089eb04f6e07b1ee47378124658
Libcore class StringPool has single usage outside libcore, in framework.
As a part of api cleanup in libcore StringPool is removed from
SystemApi, thus, it is copied to com.android.internal.util package.
Bug: 154796679
Test: m droid
Test: atest FrameworksUtilTests
Change-Id: Iaa332eb8ade68f3451639bdce62d5cfea30c2f97
For easy copy-paste if someone is configuring their server to host an
assetlinks.json.
Bug: 184954099
Test: manual, pm get-app-links on device
Merged-In: I5ed3505d72b5522202743a49559fbf1230b5767e
Change-Id: I5ed3505d72b5522202743a49559fbf1230b5767e
Slog is a core class provided by frameworks.jar, and these new methods
were causing performance regressions, so they were moved to a
system_server only class (com.android.server.utils.Slogf).
Test: m
Fixes: 183523451
Bug: 182476140
Change-Id: I511dd57faee194b58cf77c0c39c92dd0e876566e
Slog is a core class provided by frameworks.jar, and these new methods
were causing performance regressions, so they were moved to a
system_server only class.
Bug: 182476140
Bug: 183523451
Test: atest --rebuild-module-info FrameworksMockingServicesTests:SLogfTest
Change-Id: I98cbb122d5410b61812edc85162aa6b10b995fdc
The latter is being removed.
The date(1 Jan 2019 00:00) was a cut-off date used in
SettingsUI. This change moves it to reuse that date without
duplication.
Affected method is used in setup wizard to answer "What time zone
IDs should we show for a country?". The question is vague, but
the change keeps user experience consistent across device w/o
breaking method contract.
Bug: 155738410
Test: presubmit
Change-Id: Ib139b316e5909cab18d015b7c163bb9c79bcef5b
This CL reworks our previous CL [1], which enabled "adb bugreport" to
include ime-tracing files into bugreport with some unpleasant
side-effect described in Bug 177462676.
Basically what this CL aims to do is to mirror my CL [2] for
InputMethodManagerService. Instead of relying on heuristics, this CL
introduces a clear and dedicated command
adb shell cmd input_method tracing save-for-bugreport
so that "adb bugreport" can explicitly tell IMMS to dump the tracing
files.
See the corresponding CL for frameworks/native [3] about how it's
triggered from "adb bugreport".
[1]: Ie87eb8423e2bb70f28c330983d45b95e2e07062d
ac24994aaa
[2]: I887ae6941b4844a606675b447f67ecee88d7f192
96a51f9971
[3]: I62105334e4efbb4514390ffa8be5416482ca3b29
02b1d2c70b2f4703a9dd51ba69d78604d66916e1
Bug: 177462676
Test: Manually done as follows.
1. adb shell cmd input_method tracing start
2. adb logcat -d -s imeTracing:*
Make sure ime tracing is running
3. adb shell dumpsys input_method \
--dump-priority CRITICAL --proto > /dev/null
4. adb logcat -d -s imeTracing:*
Make sure ime tracing has not been stopped.
5. adb shell cmd input_method tracing save-for-bugreport
6. adb logcat -d -s imeTracing:*
Make sure ime-tracing was dumped and is still running.
7. adb root && adb shell ls /data/misc/wmtrace/ -al
Make sure ime tracing files are saved.
Test: Manually done as follows.
1. adb shell cmd input_method tracing start
2. adb logcat -d -s imeTracing:*
Make sure ime tracing is running
3. adb bugreport bugreport.zip
4. adb logcat -d -s imeTracing:*
Make sure ime-tracing was dumped and is still running.
5. unzip -v bugreport.zip | grep ime_trace_
Make sure ime_trace_{clients,service,managerservice}.pb are
included.
Change-Id: Ib106e077a10eb6a4f37b38aa9172e7c99a81f898
Docs will be super useful, especially to new developers.
I see several docs and questions inside/outside google asking
what is it and when to use it.
Bug: 182476140
Test: m -j
Change-Id: Ibb41ab0b6fd808f2a1e5475103860fc415a502d6
Introduces a SparseDoubleArray class.
It is based on a SparseLongArray, storing the double values
in the bits of the long in the SparseLongArray.
This is a hidden class.
Not all long-term desired features of SparseDoubleArray
have necessarily been implemented here; only the ones needed
right now have been written.
Bug: 182845832
Test: atest BatteryStatsTests
Test: atest FrameworksCoreTests:android.util.SparseDoubleArrayTest
Change-Id: Id68b22328f2660839e2005990766d99140b00c16
This is a preparation to add new command:
adb shell cmd ime tracing save-for-bugreport
which is to be an important piece of functionality to get rid of an
unintentional behavior change (Bug 177462676).
Anyway this CL itself is still a mechanical refactoring hence there
should be no observable behavior change.
Bug: 177462676
Test: "adb shell cmd input_method tracing start" works.
Test: "adb shell cmd input_method tracing stop" works.
Test: "adb shell ime tracing start" still works.
Test: "adb shell ime tracing stop" still works.
Test: "adb shell ime list" still works.
Change-Id: I972f287bddda962dd42d4dd5226cb8b42e759121
Adds a feature flag to enable the security hub functionality in
settings.
Bug: 181764276
Test: tested manually by checking the flag in developer options
Change-Id: I1a8c70b7f1037f8fdab95206c2a719e43d9254f4
Digest calculation is currently optimized for perfromance, and
it uses fine-tuned mmap() to access the APK. As IncFS-based APKs
aren't supposed to be fully digested, this code will probably
never run for those. But just in case, it's better to switch
over to a slightly slower read()-based implementation that
doesn't have any chance of crashing the whole process via a
SIGBUS signal
Bug: 175632872
Test: atest framework/base/core
Change-Id: Id3dc4cd5090679120d95da40c0dfdde0d72b6bb0
This follow recommendations from the API council review.
Based on those recommendations: I updated the API and updated the
comments to make the function behavior clearer.
Bug: 181611658
Test: atest android.widget.cts.RemoteViewsSizeMapTest
Test: Local widget to check rendering
Change-Id: Ie9fcedbc7b18b83f6d1220f99240f264e53e3649
The flag was added before screen record was a full feature and is no
longer necessary to maintain
Fixes: 118826991
Test: atest com.android.systemui.globalactions
Change-Id: I728a2d8c7c8527d8a6a61c1bc9feb833724afeb8
Revert submission 13519571-revert-13479025-multiuser_test-BVTHGRYHSS
Reason for revert: b/179457252 has been fixed.
Reverted Changes:
I35e436e99:Revert "Fix the broken test"
I4f77afda4:Revert "Revert "Revert "Turn on the feature flag f...
Change-Id: I92f7ce09a4e4a7ccf302dd67e13bf97e7ecb47e8
Introduce a lever we can use to enable / disable all new backup
eligibility behaviours from one place.
Bug: 174216309
Test: m -j
Change-Id: I17618a72c04f138204c5c0ca2c23330044c169e7
The Parcel read/write speed of MergedConfiguration/InsetsSource
becomes 4x+ faster.
Because writeParcelable sends additional type info which is
unnecessary if the type is known on the reading side, replace
the usages to writeTypedObject and well-written readFromParcel.
That saves the time of class lookup and object creation.
Bug: 181025587
Test: vogar --mode app_process --benchmark \
frameworks/base/core/tests/benchmarks/src/android/os/ParcelableBenchmark.java
Change-Id: I29548ce6c2e5886f0e90a5dc70d8e9ecc0fb25a8
Rotation_90 + rotation_90 is different from the result of rotation_180
with the current implementation. Should also take care of rotation_180.
Fix: 180751251
Bug: 173124775
Test: atest WmTests:DisplayContentTests
Test: atest WMShellUnitTests:DisplayLayoutTest
Test: atest FrameworksCoreTests:RotationUtilsTest
Change-Id: Ia1c87409b4c4cc412c3fd89e58d08b6ae2069fd0