This patch fixes an initialization order bug in the USAP pool policy
management code. Previously, bad values were used when initializing the
USAP pool when it was enabled on device boot. This patch ensures that
the policy system properties have been checked before the pool is
initialized.
Test: Boot with USAP pool enabled
Change-Id: I29d91abd511bc35c7a70a3a56668c7ee2290864b
Previously, the agent will have to query the TrustManager to see if a
recently added escrow token has been activated. If the agent asked too
soon about the token state, then the result could be inactive. That
will be hard to distinguish from when the token is actually inactive
because activation failed.
This change pipes the call from LockSettings to the TrustAgentService
through the TrustManager when the token is activated. So, the trust
agent doesn't have to query, it just gets notified.
Bug: 124312230
Test: Observe the onTokenStateReceived() callback received on the trust
agent.
Change-Id: I0ac674219fd7925ba36f50bb695c9998c18226f7
mChooserListAdapter will be null if there are no apps that can perfrom
the action (Share, Open With).
Bug:127305716
Test: Flashed and got the appropriate behavior: https://screenshot.googleplex.com/VcJFGHadspN
Change-Id: I5ca647cd974a02041522409fc070c27df2bdc9c4
Also removed emeritus accounts ek@ and silberst@ from various places.
A cleanup using 'include' would probably be in order...
Test: N/A
Change-Id: I575e60dd5e600e42d9571ce8e8d7661d30e99bfe
This allows us to expose both system-only and app available APIs for
role in RoleControllerService.
Bug: 127691087
Test: manual
Change-Id: I86fe3736fc28516aae25d48efe3ba599ffdf45d5
Add an internal method to ApplicationInfo to get all APK files that may
be required by an application. This moves assumptions about how apps are
constructed out of Zygote.allowAppFilesAcrossFork and into a more
appropriate place where it can be shared.
Bug: 124116212
Test: atest android.webkit.cts.WebViewTest
Change-Id: I79add98c4922c4f97263bff78cf808bc38274755
Because the layout looks pretty much the same as when awake, we're
going back to the regular group layout.
Test: atest SystemUiTests
Fixes: 127697886
Change-Id: I5eafaf74435151faab13d8f84850b4939196edd9
Add single direct share row this is always present, prepare for
expanding to 2. Show message about missing direct share targets
if none are found in the first XX seconds. Use animations to
transition between the states. Add border dividers between sections
Bug: 126565347
Test: atest ChooserActivityTest
Change-Id: I31963375530433c3d6e9069402b5a20df5766034
* changes:
Check for empty arguments in setWhitelist().
Implemented a WhitelistHelper for whitelisting packages/activities for Augmented Autofill and Content Capture.
Displays Settings button instead of always button for all intents that
have http or https scheme, as opposed to only intents that have
BROWSABLE as category.
This fixes an inconsistent and confusing behaviour that users were
experiencing, as sometimes they saw the Always button and sometime the
Settings button.
Fixes: 126499502
Test: open a mail.google.com from Facebook Messenger - used to display
Always button and now displays Settings button
Test: use shell command to send https intent without BROWSABLE category
- used to display Always button and now displays Settings button
Change-Id: I1084fd716ba8e584c2b17d8fe1500dbc641cab46
The resolver prompt now redirects users to the Default Browser page when
they tap a browser app and choose [Settings]. In that page, they can
choose the default browser (even if the tapped browser app is already
the default browser).
Bug: 124721947
Test: manual
Change-Id: I31518510fa382bd49c61ee494bf585dec0c762f8
The latest plan is only system apps with a certain privilege permission
could become NAS. And DeviceConfig could specify any of these valid
candidate to be the default NAS.
So the logic would be like this:
1. If user has set the NAS manually, NMS will persist the user_set bit
and never mess with it.
2. If it is not the case, NMS will try the NAS defined in DeviceConfig,
and then the one defined in config.xml
Also added some new shell commands for easy debugging.
Test: atest NotificationAssistantTest.java
Test: atest NotificationManagerServiceTest.java
Test: Use "device_config put" command to set a valid one. Observe that
NAS is updated and persisted across reboot.
Test: Repeat the command with an invalid one, observe that NAS is not
updated.
Test: Go to settings, set a NAS, and repeat the device_config command,
observe that NAS is not changed.
Test: Go to settings, set NAS to be none. Reboot the device, and "none"
is persisted.
FIXES: 123566150
Change-Id: Ibf8e498944afd5d1fa8659a856a8abdcce41f092
The logic was only there for the system server before, it is now
moved to ProcessList (the correct location).
Test: manual
Bug: 123524494
Bug: 124437687
Change-Id: Ie259a13617981bcbced144f1514c43f32d06102b
