This switch suppresses output of compile SDK-related attributes
in AndroidManifest.xml, including android:compileSdkVersion and
platformBuildVersion.
Fixes: 278115511
Test: ManifestFixer_test
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:2ada8ffbe1a62f50fe5e966e8e9ec1f417cea179)
Merged-In: I552e50802a328c2318c9f261e30beadcbca5fd29
Change-Id: I552e50802a328c2318c9f261e30beadcbca5fd29
The math for `vibrationDelayMs` was slightly off due to order of operations.
Bug: b/280825875
Test: manual - tap (not long-press) a lockscreen shortcut, and feel that the vibration starts and ends at the same time as the shake animation.
Change-Id: I616e99c484b4509d2a526ab5cd6a2612c93d52a2
Set the background of the resize veil to light or dark based on whether
dark theme is applied.
Video: http://recall/-/hJNEr4C0IUowK3TyPPf4wT/diSieIqfY6tdF5rsoOT0PH
Bug: 274773589
Test: Manual; resize apps with different caption colors.
Change-Id: Id94d81ae01ad0e9edeaed51591f539d4fe5eb913
This is not directly related to b/225902574 but I noticed it while
looking at that issue.
In the case where carrier merged comes through a WIFI connection, it
would never show the ! because mobileIsDefault=false. However, the
carrier merged connection could be non-validated, in which case we
*should* show the ! (but wouldn't right now).
This CL updates the `isDefaultConnectionFailed` calculation to also
show the ! if carrier merged is default and not validated. It does this
by using the interactor's interally calculated `mobileIsDefault` flow,
which includes carrier merged (as opposed to the repo's
`mobileIsDefault` flow, which does not include carrier merged).
Bug: 225902574
Test: atest MobileIconsInteractorTest
Change-Id: Ic79cc1755a67400de067a51abcf654b1294b7fe1
Add a metric to track the maximum number of jobs that are scheduled at a
time, in 30 minute increments.
Bug: 138239687
Bug: 279935506
Test: atest CtsJobSchedulerTestCases:ConnectivityConstraintTest
Test: atest CtsJobSchedulerTestCases:JobSchedulingTest
Test: atest CtsJobSchedulerTestCases:NotificationTest
Change-Id: If0c190bf8ebcca55ef1907020b37a0e1c72181ae
- Because a mutable pending intent is returned, we actually do need to
enforce that SysUI is the only caller of this method
Bug: 278881947
Bug: 253216640
Bug: 256590334
Test: atest LauncherAppTests
Change-Id: I89dd6891a826f934a247881c6dd9ec5cacf2d082
When launching an EDIT action from the long screenshot activity,
only send a shared element transition when the target is specified.
The shared element transtion ActivityOptions cause a crash when
sent through ResolverActivity.
Bug: 277206284
Test: manual; modified build to suppress editor component name
Change-Id: I57262c622c1d5c2ab4930f3c1bb3512d4dd37ea3
LatencyTrackerTest exposed a race condition leading to deadlock in
FakeLatencyTracker.
This also fixes users of FakeLatencyTracker like
SoundTriggerMiddlewareLoggingTest
Bug: 275113847
Test: atest LatencyTrackerTest --iterations 20
Test: atest FakeLatencyTrackerTest --iterations 20
Test: atest SoundTriggerMiddlewareLoggingTest --iterations 20
Change-Id: I5e4a4e489711fff05c2fceffbe76c258a54cd49f
The current method immediately sends a change event to the listener,
which causes the AuthDialogPanelInteractionDetector dialog to
immediately cancel itself upon adding the listener. Adding a new
method that doesn't fire the event and calling that instead fixes
the problem.
Test: manually verified
Test: atest SystemUITests SystemUIGoogleTests
Fixes: 278455611
Change-Id: Id94bba0ab10890fd3c380d69cf6409c614c7e84c
split was changed to preserve splits in "background", so it
needs to be detected via isSplitActive instead of isSplitVisible
so that it can update properly when a PiP transition comes in.
Bug: 280253323
Test: wait for b/280523948, then open split with an auto-pip
and then swipe-to-home. Try this with both single and
multi-activity pip and dump window containers to verify
correct hierarchy.
Change-Id: Id3f28cad593a799933ddc24a570b7a91e22bd275
The following APIs now enforce limits and throw IllegalArgumentException
when limits are violated:
* DPM.setTrustAgentConfiguration() limits agent packgage name,
component name, and strings within configuration bundle.
* DPM.setPermittedAccessibilityServices() limits package names.
* DPM.setPermittedInputMethods() limits package names.
* DPM.setAccountManagementDisabled() limits account name.
* DPM.setLockTaskPackages() limits package names.
* DPM.setAffiliationIds() limits id.
* DPM.transferOwnership() limits strings inside the bundle.
Package names are limited at 223, because they become directory names
and it is a filesystem restriction, see FrameworkParsingPackageUtils.
All other strings are limited at 65535, because longer ones break binary
XML serializer.
The following APIs silently truncate strings that are long beyond reason:
* DPM.setShortSupportMessage() truncates message at 200.
* DPM.setLongSupportMessage() truncates message at 20000.
* DPM.setOrganizationName() truncates org name at 200.
Bug: 260729089
Test: atest com.android.server.devicepolicy
Merged-In: Idcf54e408722f164d16bf2f24a00cd1f5b626d23
Change-Id: Idcf54e408722f164d16bf2f24a00cd1f5b626d23
