This fixes some failing cts tests running on user builds.
Test: atest android.devicepolicy.cts.DevicePolicyManagerTest
Fixes: 181567444
Change-Id: I07c3a98fcbe79d41fb224967569b877eefbc593c
Also made sure to invoke the callback on the main
handler thread, like all other callbacks.
Fixes: 182164620
Test: atest PackageManagerTests
Change-Id: Ic2abe0877a716e83a10965bf348888a53ae95db8
Currently the diff only counts public fields. If only the rotation
of the window configuration is changed, the activity still receives
onConfigurationChanged which is unexpected.
Bug: 165794724
Test: AppConfigurationTests
Change-Id: Ice2db32b700493bcd47a38468ae66e91504895a6
This is only necessary when a notification is posted without a title.
Fixes: 177976174
Test: Manual inspection of various staes.
Change-Id: I15fdc31e1557b7e5d6fb99e410f4bf37d6734ac4
Bug: 175207142
Test: Post a notification with a customContentView, but not a bigCustomContentView; note that it is no longer expandable.
Change-Id: I9bf41f3313e68ddbb43485cee37911bc8cfeb012
This change returns the behavior of initializeJavaContextClassLoader in
LoadedApk to throw an IllegalStateException calling out the package it
attempted to fetch. This was removed when client-side caching was added
resulting in a different stack trace without this critical piece of
information that could help make sense of why this is happening.
Bug: 180418767
Bug: 140788621
Test: N/A; builds
Change-Id: Ia1ceff922f693093012eb6e3e0f6e1d90222cde7
The documentation for EXTRA_PROVISIONING_PERMISSION_GRANT_OPT_OUT says
it should be used ACTION_PROVISION_MANAGED_DEVICE. However, that is
deprecated since it's no longer needed (and there's another way to
provision a fully-managed device).
Remove reference to the deprecated constant and simply mention device
owner provisioning.
Bug: 182180699
Test: That it compiles.
Change-Id: I8681c09fb9fa008f0e2ccf62c5dad8d37cd1b843
Since this parameters object is likely going to grow over time, we
should offer a way for callers to easily "inherit" all sub-parameters
by default, instead of making them copy the values manually.
This also gives a path for legacy apps to automatically preserve any
new sub-parameters that have been added in more modern API levels.
This change also relaxes the nullability annotations to match the
existing createAttributionContext() behavior, while also supporting
clearing of specific inherited values.
Bug: 181812281
Test: atest CtsContentTestCases:android.content.cts.ContextTest
Change-Id: Ic797e1aef578926b04ea0000ca3a1bf8684183b9
* changes:
SysUI changes for setSuppressBubble
Track locusId visibility in ShellTaskOrganizer
Add locus id to ActivityRecord / TaskInfo
Bubble API: suppress bubble
After a ton of regression testing on Forrest and checking dashboards,
turns out the boot time regression due to new color code only happens
on Wembley in CI.
Wembley in CI has 1 GB of RAM, or at least, it returns true for
`ActivityManager.isLowRamDevice`
To fix the regression, when we're performing clustering
on a low RAM device, we'll use the prior clustering strategy (Kmeans,
5 colors). Net impact is speed improvement + there will be less options
for colors. Kmeans erases less common colors first, and those colors
tend to be good candidates for highly chromatic colors.
Fixes: 181348302
Fixes: 181194430
Test: Did about 50 runs on Forrest, isolated issue. Final Forrest
run showing that startservices_avg decreases to previous levels on
Wembley with this CL is here:
https://android-build.googleplex.com/builds/forrest/run/L87800000829799585
To see the improvement back to baseline (~1350 ms), open that link,
at the table of the bottom of the page, click "asit/perf/boottime_test",
then click Artifacts, then click
test_results15031410639465275315_8163110686177237845.txt, and search
for SystemUIBootTiming_startservices_avg.
Alternatively, here is a direct link to the test results text file:
https://android-build.googleplex.com/builds/I89400007809099518/git_master/P20404532/successiveboottest/inv_17043739560101466259/test_results15031410639465275315_8163110686177237845.txt
Change-Id: I53ee5b5f95e6fd54f1327005e391d428f650dbfa
* changes:
Show text and progress bar for CallStyle
The title of a notification can take 2 lines when expanded.
Remove the line1 container for the title
Move text to new line in big base style
Fix dark mode progress bar background color
Different logical components within an app may have no intention of
interacting with data or services that are protected by specific
permissions.
The new overload added in this change provides the initial mechanism
for a logical component to indicate a set of permissions that should
be treated as "renounced". Interactions performed through the
returned Context will ideally be treated as if the renounced
permissions have not actually been granted to the application,
regardless of their actual grant status.
This is a low-risk change from a security standpoint, since it can
only reduce the set of permissions that might have been granted to
an app; it can never be used to expand the set of permissions.
Note that this change only provides an initial implementation which
only applies to local permission checks within the app; future
changes will begin wiring this up across process boundaries.
Bug: 181812281
Test: atest CtsContentTestCases:android.content.cts.ContextTest
Change-Id: I96439e5344c85300fb6a0f03e572746c3c96ee95
This was only used when progress was shown, did not exist for headerless, and was then hidden for all styles; this just left the big base template, where it needed more room. Now we just only set the text with progress when using that template.
Note: The line1 container is used for margin adjustments, so removing it is non-trivial; I'll do that in a followup CL.
Bug: 181048615
Test: visual inspection
Change-Id: I465f7be95249b90ae8906b2bc951c9ff6066550a
- Bubbles needs to know if a task has a LocusId for the
Suppress Bubble API
- Apps can already set a locusId on the activity, this
occurs after the activity has been created.
- This CL adds the locusId to the ActivityRecord and
triggers a task info change
- TaskInfo uses the top activity in the stack to populate
the locusId
Bug: 170267239
Test: atest NotificationManagerTest (in CTS CL)
Change-Id: I33cf784e3f3f89835d91e31961b3abe7a7b68c8d
* changes:
Rename to DomainVerificationUserState
Rename to DomainVerificationInternalUserState
Expose getDomainVerificationUserSelection as public API
Fix setDomainVerificationLinkHandlingAllowed docs
Rename get -> queryValidVerificationPackageNames
Make DomainVerificationManager a final class
