To improve security, the reason why an overlay transaction failed is
hidden from the caller unless OverlayManagerService.DEBUG is set to
true.
Tweak the logic to not hide the reason on userdebug and eng builds: this
will make it easier to debug tests that fail in CI while keeping the
code secure on user builds.
Test: manual: make executeAllRequests throw, test via `adb shell cmd overlay enable`, check error message
Change-Id: I1c35b9b24a01ea30a50398df9f250ad4e43c0686
Merged-In: I1c35b9b24a01ea30a50398df9f250ad4e43c0686
* Previously, the height returned by Display#getSize was used to
determine visible objects. Based on the API level and the presence of
system decorations (e.g. notches), this can cause objects near the
bottom of the screen to be considered out of bounds (i.e. only objects
within y=0 and y=partial_height are considered even if the omitted
decorations are at the top of the screen).
Bug: 193270758
Bug: 188156320
Bug: 27537269
Test: manual
Change-Id: Iba21245c947cec0d0054f6d86e3585ba73233223
The fix is taken from AOSP patch aosp/2154236.
This will make sure the UI Automator always has the entire display to
interact with. Otherwise, in multi-windowing mode or on devices with
task bar, it will only be able to interact with the current focused
window, the default launch bounds, or the display excluding task bar,
depends on the actual scenario.
Test: PlatformSenarioTests
Bug: 238981445
Bug: 238985243
Bug: 238581838
Bug: 233945217
Change-Id: I9223ef5552ddb081e75de1242670862f2813e56d
(cherry picked from commit d1e350c7fc)
Merged-In: I9223ef5552ddb081e75de1242670862f2813e56d
This commit does:
- Skip the new retrying request when there is a pending retrying
task. Otherwise, the mRetryCount will be increased unexpectedly
before the current retrying task finishes its job.
- onChildOpened will call onSessionLost when MTU is invalid, and
onChildOpened will be called after onIkeOpened, so if
mRetryCount is reset in onIkeOpened, the mRetryCount will always
start from 0.
Bug: 256776571
Test: atest FrameworksNetTests:VpnTest
Manual test and check the log.
Change-Id: I396a3c279dc909f78c400cff1c31d77fe98cd7a6
This reverts commit ad0c6b5d8c.
Reason for revert: rolling forward the .so compression change. According to https://b.corp.google.com/issues/188859114#comment8, the underlying issue was fixed.
Bug: 254793035
Bug: 188859114
Fixes: 254793035
Fixes: 188859114
Change-Id: I4edc15d08527013206e3daf20c33ba29c87a01a2
Merged-In: I4edc15d08527013206e3daf20c33ba29c87a01a2
This CL contains two fixes:
- Make sure view is laid out before calling createBitmap.
- Organize some field declarations.
Bug: 246412041
Test: manual
Change-Id: Icd5637086b3935afe89743472e68bbd3a6102222
There is a race condition where loadPrivatePackagesInner() can run after
the volume has already been unmounted, and even reformatted as a public
volume. This race can be triggered by AdoptableHostTest in CTS.
Until the volume state change handling logic is fixed, it is necessary
to ignore the RuntimeException that sm.prepareUserStorage() can throw
after commit 9d2bb776ed (https://r.android.com/1959519).
Bug: 253711749
Bug: 253868095
Change-Id: I9985eb5e410a5a5ff41935c806370826c6e4117d
1. Non-conditional based evaluations will no longer trigger
setup data if the APN was marked as permanent failure earlier.
Only environmental changes can result in data setup.
2. Permanent failure can be only applied to the failed APN. When
this happens, frameworks retries the next non-permanent-failed
APN.
Fix: 254752857
Fix: 249908875
Test: Manual (verified on JP carrier) + atest FrameworksTelephonyTests
+ Basic testing.
Merged-In: Ic43100635907153bce9631473c56f1edef187fc4
Change-Id: Ic43100635907153bce9631473c56f1edef187fc4
On configuration changes such as screen orientation change,
activities are usually recreated to reload resources.
However, when DreamActivity is destroyed (also in the process
of activity recreation) the dream is dismissed.
To prevent this, DreamActivity was previously set to handle
orientation change without activity recreation, but orientation changes
often go along with screen size/layout changes, which still caused the
DreamActivity to be recreated.
This change lets DreamActivity handle all configuration changes without
recreation, similar to how Window-based dreams used to work.
Bug: 240892000
Merged-In: I345eb1d17ae88d893789dfcc160b4a9a664ba57f
Change-Id: I4fdf0fe5f0bcd28b9af5cbe55f20760a3719da9c
This change calculates the maximum possible MTU based on the underlying
network and proposed algorithms. If MTU drops below 1280, IPv6 is
disabled, per RFC2460.
In order to ensure that apps with UDP sockets on an IPv6 network are
reset when the IPv6 addresses/routes are removed, the network is
restarted (disconnected/reconnected) when the MTU first drops below
1280. If the VPN only supports IPv6, a VpnManager event is sent to the
provisioning app, and considered failed.
MTUs will only ever be lowered from the MTU provided by the provisioning
application, exclusively improving compatibility if the calculated MTU
is lower than the app-specified MTU. Similarly, MTUs of underlying
networks are gathered on a best-effort basis, using LinkProperties, or
actual Linux interface MTU if not populated in LinkProperties.
For stability & backwards compatibility, this change is ONLY applied for
IKEv2 VPNs.
Bug: 245612827
Test: atest FrameworksNetTests:VpnTest
Manual test:
- Test if IPv6 will be disabled when VPN's MTU is lower
than 1280
- Test if IPv6 only VPN will be restarted when its MTU
is lower than 1280
Change-Id: Ic97c16f12229c5377923b031497190082319d035
This reason is intended to be passed to TelephonyManager.setAllowedNetworkTypesForReason
when 2g is disabled by a user restriction.
Bug: 247522864
Test: Included in future commits
Change-Id: I617e629163cfb63235055a4e9a75b0c2d6629ad5
There is a mismatch between some of the UI components
in the AOSP apps, such as launcher3 (lpress shortcuts),
and some dialogs and such in SystemUI/Settings.
This corrects the mismatch.
Bug: 216182276
Test: See examples in bug
Change-Id: Ie3f6a74ef9d36d36d9ff6be956d37d030c64f12c
