am skip reason: Change-Id I2510de0ab1ce40c8d191a17dbae7f4c33418006c with SHA-1 75e6aa2764 is in history
Change-Id: Ib4c8895efc2411d7f744d24ae2ec46667cf85eea
am skip reason: Change-Id I43c7e088e46e40f38d8114548e0fc4e39d7f91cb with SHA-1 77a7ea65fd is in history
Change-Id: Ia8b26d50299dfb07178d0adef52cc422317070e9
am skip reason: Change-Id I0fb0e7e466a0188f04db595b8e417870666005ba with SHA-1 7125d3ba10 is in history
Change-Id: If5b0208edcfb7b1a764758282080c1aa5da064d4
am skip reason: Change-Id Iffd9351d2170a496639eced2c4618819f522494c with SHA-1 ac37b6344d is in history
Change-Id: I9f23eb07c789feab8674cea9246e76ea8653be73
Offset the view instead of using setForwardedInsets which doesn't
work anymore with the new insets system. That should resolve
itself automatically once we migrate Bubbles off VD.
Also, make sure we don't consider a window to be animating when
being insets controlled since it breaks syncInputWindows, for
example.
Bug: 111084606
Test: Open Bubbles test app, open IME.
Change-Id: Idb4d32a77e96924e106688c4e11c63e8cff3ae1f
am skip reason: Change-Id Ia938502d2443f5a6de6a3cabdb7ce1d41d3ff6d1 with SHA-1 0a8a1e9d40 is in history
Change-Id: I495ade5c369293aab036ef8f4c3697e5c9bfc6f0
So that mReadOnlyNotifList always tracks mNotifList, even after
switching mNotifList and mNewNotifList
This CL also updates ShadeListBuilderTest to catch bugs like this.
Mockito keeps shallow references when verifying mocks, so we can't rely
on verifying the passed list after the test is run (since the list is
recycled within ShadeListBuilder). Instead, make a deep copy of the list
we receive in the listener and verify this list for equality.
Test: atest ShadeListBuilderTest
Fixes: 148421960
Change-Id: I85eb439f77686c67b365f04585da8fc54cb854ec
am skip reason: Change-Id Ia938502d2443f5a6de6a3cabdb7ce1d41d3ff6d1 with SHA-1 0a8a1e9d40 is in history
Change-Id: I74fef17a0cd95ffab64f8e18ef5970d1389bba82
Otherwise it fails permission check since it would use the caller's uid.
Bug: 148521528
Test: Post a background custom toast and observe it either posts the
toast or shows a textual warning toast (before this change,
neither would happen and we'd see a SE in logcat).
Change-Id: I338846bda08b8a002440dd3b1a43393f2ff25011
am skip reason: Change-Id Ia938502d2443f5a6de6a3cabdb7ce1d41d3ff6d1 with SHA-1 0a8a1e9d40 is in history
Change-Id: Ie771ffdfc4cfc2d58d0b74ea29f56655462924ca
Motivation: if the Content Capture service want's to end the session, it
can close the read-fd, while not have finished reading, and that would
result in an exception in the system server, that can later be
propagated to the caller as an error.
Similarly, timeout of the sharing session can be reflected as an error
with a specific error code.
Test: built Android locally and perfomed a manual test.
Bug: 145203958
Change-Id: Iaeb45e0ab68da9fe30dce1ae4eab2354ef56d827
am skip reason: Change-Id Ia938502d2443f5a6de6a3cabdb7ce1d41d3ff6d1 with SHA-1 0a8a1e9d40 is in history
Change-Id: I8fd65309a87e6f428dd9f7ae8112861b5cc856b6
In an effort to keep CL that enables app enumeration as simple as
possible, this change collapses several inline booleans to a single
constant boolean.
Test: atest AppEnumerationTests
Bug: 136675067
Change-Id: Iac4b2fceb61d5680baf6fac76d58ee4525c615bd
The usage was removed from opt/net/wifi earlier.
Also, cleaned up a bunch of other settings in SettingsProvider
that were previously removed in ag/10080845.
Bug: 141623345
Test: Compiles
Change-Id: I18690ee12d6b701b6f487285e36ca0143244bcfd
Change mtu->mtuV4 and add mtuV6 for DataProfile and DataCallResult
Add mtu to RouteInfo and update test
Test: atest FrameworksTelephonyTests
Bug: 146668814
Change-Id: I43c7e088e46e40f38d8114548e0fc4e39d7f91cb
Merged-In: I43c7e088e46e40f38d8114548e0fc4e39d7f91cb
The rescue level returned from onBootLoop must be incremented, since
otherwise USER_IMPACT_NONE would be returned to Package Watchdog if
the initial rescue level was 0, and no mitigation would take place.
Add a test to verify this.
Test: atest RescuePartyTest
Bug: 136135457
Change-Id: I27c56d17a6177abdeb3707fda70ca38d4fd4ef2c
This adds tests in StagedRollbackTest for apex data directory rollback.
The test performs the following steps:
- Push files into the apex data directory
- Update the APEX with rollback enabled
- Remove files from data directory
- Add new files to data directory
- Roll back the update
- Verify old files are restored
Bug: 141148175
Test: atest StagedRollbackTest#testRollbackApexDataDirectories_DeSys
Test: atest StagedRollbackTest#testRollbackApexDataDirectories_Ce
Change-Id: Ie1e7ed626c0b654c19b23bfcb008ac4d717aafe2
am skip reason: Change-Id I70c72d7d74c72a78d919ae34906b6f7b96466ad1 with SHA-1 e12de0beb4 is in history
Change-Id: Ieaefce68c10856e68d970a834ce7abee05c33fee
This change extends the existing mechanisms for snapshotting and
restoring CE data for APKs to also support CE apex data.
StagingManager now calls through to RollbackManager to perform the
snapshot/restore (at the same time as it does for APK-in-APEX,
added recently).
For APEXes, the actual snapshot or restore is performed by apexd instead
of installd. Tracking of pending backups and restores is performed by
RollbackManager in the same way as for APKs.
Bug: 141148175
Test: Manual install/rollback of an APEX with dummy files in CE data directory.
Check that snapshot and restore occur as expected.
Test: atest CtsStagedInstallHostTestCases
Change-Id: I82e1818f927881ea774148d97ca1981a447b598d
