This should be the highest scoring one, not the first one.
Test: cts-tradefed run cts-dev -m CtsViewTestCases -t
android.view.textclassifier.cts.TextClassificationManagerTest
Change-Id: Ib790d8aa4aeccdd7a7972eaa6c04ed4fc69ad00e
This CL contains following clean up:
- Hide unnecessary constructors.
- Change List<XX> to XX[] since actually all fields are immutable.
- Change font's variant type from String to int.
- Decouple resource related members to FontResourcesParser.
- Add NonNull/Nullable to all fields.
Test: ran android.content.res.FontResourcesParserTest
Change-Id: If456266ffff86d41342572a19662cc8f3cd13181
Also fix a bug that doesn't trigger directory specific update for
removal.
Test: Manual tests.
Bug: 31001477
Change-Id: Ibae8a7aa5c72c82dc5e3cb4951fbc91ea6456964
(cherry picked from commit c574ec40640d83dfbbb0f022103c6dfa774bca40)
- When calling adjustFocusedActivityStackLocked(), prevent the home stack
from being brought forward if the task is not over the home stack. This
was causing issues with the docked stack triggering minimized mode when
a task was removed in the assistant stack.
- When checking the visibility of the docked stack, only base it on the
visibility of the assistant stack when it is above the docked stack.
This was causing issues with the docked stack reporting as visible even
when behind the assistant stack due to the subsequent code being run.
Bug: 35363819
Test: android.server.cts.ActivityManagerAssistantStackTests
Change-Id: I48cc901cb6b6166697a4130cc4639ee8f9581f02
- The orientation needs to be calculated from the screen width/height,
which are set below the current calculation of the orientation (whoops).
This bug was introduced in ag/1905010 and causes extra configuration
changes due to the configuration orientation being set correctly before
it is corrected on the next change (at the end of the transition).
Bug: 36099204
Test: android.server.cts.ActivityManagerPinnedStackTests
Change-Id: Ieca1f73fe61fc1dcea106535c019b52d126b8743
Save the state when the fragment is getting re-created so we come
back up in the same state we left in.
Fixes: 36082443
Test: Change density using "adb shell wm density"
Change-Id: I531de728b1f4bf59d4def7ebc5562b3a1ee6694b
Ostensibly for instant apps, we allow play to mark an app as having
an update available. This will trigger instant app resolution even
if the instant app is already installed on device.
Bug: 35143464
Test: Manual; launch URI of installed instant app, see it runs w/o resolution. set bit. launch URI of installed instant app, see it runs resolution
Change-Id: I511df2b2a3eab39377167c770255ccbe02d5dad2
This washes out the network logging icon in the network monitoring
dialog, making it look strange compared to the dark VPN key.
Fix: 35620542
Test: inspection of dialog
Change-Id: I72bc6337b88b16235dab7b48d11efee4410ede5e
Now that we have CTS tests to verify the cache clearing v2 logic,
we're ready to enable it!
Switch storage APIs over to "usable space" to match implementation
down in installd. Add a missing clearCallingIdentity(), and offer
better logging for missing appop permission.
Load quotas from disk right away at device boot instead of waiting.
Bug: 35685848, 35684969
Test: cts-tradefed run commandAndExit cts-dev -m CtsAppSecurityHostTestCases -t android.appsecurity.cts.StorageHostTest
Change-Id: I8167e0322b4662ca6c975da5c50715e2d71332a7
This patch adds a few missing counters to APF events:
- an actual lifetime duration to ApfProgramEvent.
- counters for total number of updates to ApfStatistics.
ApfProgramEvents are now recorded at program removal in order to
populate the actual lifetime of the program. ApfProgramEvents whose
actual lifetime was less than 1 second are filtered out.
Finally, instance fields of ApfProgramEvent and ApfStats classes are
made mutable to allow for simple record-like creation. This was not
possible when these classes were tagged @SystemApi.
Test: - manually verified output of $ dumpsys connmetrics list
- unit tests updated.
Bug: 34901696
Change-Id: I02694ebb9421ce1c2aa757fa6aa209d19a654dcd
