Make sure it starts up to everything showing and that the StatusBar
calculates the bar mades after it is attached.
There is still a bug where the behind scrim is showing during SUW,
but this fixes many of the issues besides that case.
Test: visual
Change-Id: I93314c607e374c97d5c06f936ef8b7e07e057648
Bug: 36407135
On second thought, let's set accept_ra_rt_info_m**_plen in
Netd (InterfaceController::initializeAll())
This reverts commit 25870a2c9effd7a7d31c0678c34a6e952b2d56a1.
Change-Id: I22b000623bb852e375385d4aae789d007e84ba3d
Allows for selecting a single accessibility service or feature
to be triggered by the accessibility button in the navigation bar
Bug: 34720082
Test: Manual
Change-Id: I320febede0398b1eff38a87d4db31fd7dfc53062
Uses ImageReader as a do-nothing Surface to ensure the Virtual Display
gets passed through to SurfaceFlinger.
Without a Surface, the Virtual Display never makes it through the
android system to SurfaceFlinger. This change is needed to get the
Virtual Display recognized in the Flinger layers.
Test: 'setprop vr_virtualdisplay true' to enable virtual displays.
'setprop vr_debug_vd_receiver true' and shell restart for the test app.
Bug: 36491910
Change-Id: I2bf2cb4035dcf04484b7fb0bec61671864069335
For adding CTS tests for packages having key-value backup agents, we add
support for key-value backups to the adb backup/restore command.
Previously, packages not supporting fullbackup would just be skipped on
this command. Now, by adding the -keyvalue flag to the adb backup command,
packages supporting key-value will also be added to the resulting
tarball. Similarly, if the tarball being supplied to adb restore
contains data from key-value packages, it will be restored.
This will later be utilized for writing CTS tests for such packages.
Test: adb backup -includekeyvalue -all && adb restore backup.ab
Change-Id: I7b4ccfb7072d01d29a888952145d7cce90a4f59e
Now the autofill UI tracks the movement of the anchor view,
both real and virtual and while still preventing the filled
app from accessing the chooser UI. This was achieved by using
a popup window in the app process to determine the window
location and adding a window presenter interface to popup
window that controls the actual window addition, removal, and
update which is implemented by the system server.
Test: all autofill CTS tests pass
bug: 36392498
bug: 35708258
bug: 34943932
fixes: 36039182
fixes: 36493078
Change-Id: I0321913b2e2e759f4b17003bf85cb873e63a467c
- Allows an app to specify the maximum aspect ratio it supports.
- Support for overriding configuration and bounds at the activity
record and app window token level.
Test: cts/.../run-test CtsAppTestCases android.app.cts.AspectRatioTests
Test: bit FrameworksServicesTests:com.android.server.wm.WindowContainerTests
Test: bit FrameworksServicesTests:com.android.server.wm.WindowFrameTests
Bug: 36505427
Bug: 33205955
Bug: 35810513
Change-Id: Ib2d46ed0c546dd903d09d6bb7162a98bd390ba81
Previously we were only using the component name, which is not always
enough.
Now the resolved ActivityInfo is used and only 'flags'/'exported' and
'enabled' attributes are modified.
Test: Manual
Bug: 34751853
Change-Id: I32a2a2bd98cc5d73ab02ccfc100868b826bb8105
There was a typo causing the feature to be falsely detected as not present.
Test: Ensure feature presence is now detected correctly
Bug: 30932767
Change-Id: I44d137e89546596058b272e8eeaccc0a1db21aef
