Bug: 171015766
Test: Manual - adb shell dumpsys meminfo com.android.systemui,
verify the correctness of the RSS total
Change-Id: I21c7198cdad773adfced4b66257b9e01f1cffad2
Those annotations could be inferred by some tools (like Kotlin), but the
https://checkerframework.org/ doesn't check inherited annotations
complaining about all equals() invocations that get nullable argument.
The change was generated by running
find . -name \*.java | xargs sed -i 's/public boolean equals(Object /public boolean equals(@Nullable Object /'
in the frameworks/base directory and by automatically adding and
formatting required imports if needed. No manual edits.
Bug: 170883422
Test: Annotation change only. Should have not impact.
Exempt-From-Owner-Approval: Mechanical change not specific to any component.
Change-Id: I5eedb571c9d78862115dfdc5dae1cf2a35343580
These are essentially false positives that are just taking the flags in
as an argument and passing that over to PendingIntent methods. This
change should clear up the noise.
Bug: 160794467
Test: Errorprone builds should no longer show these as violations
Exempt-From-Owner-Approval: Trivial warning suppression
Change-Id: I8ae309fd53140718d41f4d3b94f92e111cdd8955
- Existing tasks for supported windowing modes are returned when
registering the organizer and the organizer will not receive
onTaskAppeared() for these tasks. For now, the shell task
organizer will keep these tasks for reporting task appeared when
individual components add listeners for their windowing modes.
- Fixed some tests now that we organize fullscreen tasks
Bug: 162028888
Test: atest WindowOrganizerTests
Test: atest ShellTaskOrganizerTests
Change-Id: Iedc5f58fbfa819e753a5dcea7a8eb9dee8b6843b
This code was added for an earlier implementation of the PIP animation.
In this earlier implementation PIP was animated by directly scaling the
WSA level surface. This means that if we were in SCALING_MODE_FREEZE the
requested v active geometry logic in SF could freeze our
matrix/position/crop updates. Now that we manipulate the PIP surface
via higher levels of the hierarchy this wont be a problem and we don't
need to change the scaling mode.
Bug: 161937501
Test: Existing tests pass
Change-Id: Iaf10ee4fae9a56a79c1432d9ffd4c8227b832b01
Rename HomeVisibilityObserver to HomeVisibilityListener and expose it as
module-only API. This listener is used by the SIM toolkit to detect when
the home screen is visible.
Also fix some bugs in the original implementation that were uncovered
during CTS writing.
Fixes: 170226810
Test: atest ActivityManagerTest#testHomeVisibilityListener
Exempt-From-Owner-Approval: Previously approved in ag/12775889
Change-Id: Ia44462e55ad71119cf356485c60c121d331c50d4
Revert "Add CTS for HomeVisibilityListener"
Revert submission 12775890-home-vis-listener
Reason for revert: broke build, b/170776449
Reverted Changes:
I8e6de3267:Add CTS for HomeVisibilityListener
I33d943603:Follow rename of HomeVisibilityObserver
I5d99f2bad:Expose the HomeVisibilityListener API
Change-Id: I9483fac8cf40ecfa6f80f6f66068978ebe493258
We need to grant/revoke notification listener privileges from
PermissionController maniline module.
This exposes a @SystemApi API to do so
Bug: 165951651
Test: atest NotificationManagerTest
Change-Id: I81502756e9c7f11ce0347f5f3c006a1539f91b37
Not all devices have the ETHERNET_SERVICE service, which is expected,
so do not send WTF even when it's not available.
Fix: 169024836
Test: Build
Change-Id: Ia1fa2d1753aa40e1d09996be11082d65afc5458f
Bug: 170472470
Do not disable the permission caches inside the system server. This
is beneficial because permission checks require many binder calls, and
the cache, even though it is in-process, eliminates those calls.
1. Make the PermissionManager cache more effective by increasing the
maximum size to 2048. Experiments show that the high-water mark is
about 600.
2. Suppress cache content in the 'dumpsys cacheinfo' output. dumpsys
fails if the output is too large in a single process, and the new
caches push the system server cacheinfo over the limit. The
content can be added to the output by setting the new DETAILED
boolean in PropertyInvalidatedCache to true, but this flag should
never be committed with a value of true.
Test: two atest runs
* atest FrameworksServicesTests:com.android.server.devicepolicy.DevicePolicyManagerTest#testGetPermissionGrantState
* atest FrameworksServicesTests:NetworkPolicyManagerServiceTest
Change-Id: I7d3c1f34b44216bb510319ca5b6aced1cc53e05d
After [1], display context had not been regarded as an UI context
even if it is derived from an UI context. Thus, we need to migrate
Presentation to use WindowContext to obtain UI components accesses
and also receive configuration changes from the server side.
Also remove isConfigurationStillValid() related logic since now
the configuration gets updated if the property of the display changes.
[1]: 3c0078e80f
Test: atest PresentationTest VirtualDisplayTest KeyguardPresentationTest
Bug: 167462327
Change-Id: Ib5c4a33eeba0e0a6213960300dd4c0a18047686b
.. to match behavior post I1f9662c2bd14b34e00fbc8ebb926538f0329c37a
Bug: 167593637
Test: Javadoc change only.
Change-Id: I4cb9fe4a5ae74b1474f9da39b6aeb3a374f8cf12
