Add initial stopped state packages for AOSP products.

AOSP starts with all apps exempt from the stopped state; apps without a
launcher entry aren't stopped by default, and all AOSP apps that do have
a launcher entry are contained in this sysconfig.

Bug: 269129704
Test: Manually inspect
Ignore-AOSP-First: Merge conflict from AOSP to internal master (and this needs to go to UDC, als)
Change-Id: I752f986a210621510f694b3f62bb5c6151db55d6
This commit is contained in:
Martijn Coenen
2023-04-03 10:58:18 +00:00
parent d33ef7391f
commit 8a1cdb8e95
3 changed files with 58 additions and 0 deletions

View File

@@ -29,6 +29,7 @@ PRODUCT_PRODUCT_PROPERTIES += \
# More AOSP packages
PRODUCT_PACKAGES += \
initial-package-stopped-states-aosp.xml \
messaging \
PhotoTable \
preinstalled-packages-platform-aosp-product.xml \

View File

@@ -55,3 +55,9 @@ prebuilt_etc {
src: "preinstalled-packages-platform-telephony-product.xml",
}
prebuilt_etc {
name: "initial-package-stopped-states-aosp.xml",
product_specific: true,
sub_dir: "sysconfig",
src: "initial-package-stopped-states-aosp.xml",
}

View File

@@ -0,0 +1,51 @@
<?xml version="1.0" encoding="utf-8"?>
<!--
~ Copyright (C) 2023 The Android Open Source Project
~
~ Licensed under the Apache License, Version 2.0 (the "License");
~ you may not use this file except in compliance with the License.
~ You may obtain a copy of the License at
~
~ http://www.apache.org/licenses/LICENSE-2.0
~
~ Unless required by applicable law or agreed to in writing, software
~ distributed under the License is distributed on an "AS IS" BASIS,
~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
~ See the License for the specific language governing permissions and
~ limitations under the License.
-->
<!--
This XML defines an allowlist for packages that should not be scanned in a "stopped" state.
When this feature is turned on (indicated by the config config_stopSystemPackagesByDefault in
core/res/res/values/config.xml) packages on the system partition that are encountered by
the PackageManagerService for the first time are scanned in the "stopped" state. This allowlist
is also considered while creating new users on the device. Stopped state is not set during
subsequent reboots.
Example usage
1. <initial-package-state package="com.example.app" stopped="false"/>
Indicates that a system package - com.example.app's initial stopped state should not be set
by the Package Manager. By default, system apps are marked as stopped.
2. <initial-package-state package="com.example.app" stopped="true"/>
Indicates that a system package - com.example.app's initial state should be set by the
Package Manager to "stopped=true". It will have the same effect on the
package's stopped state even if this package was not included in the allow list.
3. <initial-package-state package="com.example.app"/>
Invalid usage.
-->
<config>
<initial-package-state package="com.android.calendar" stopped="false"/>
<initial-package-state package="com.android.camera2" stopped="false"/>
<initial-package-state package="com.android.contacts" stopped="false"/>
<initial-package-state package="com.android.deskclock" stopped="false"/>
<initial-package-state package="com.android.dialer" stopped="false"/>
<initial-package-state package="com.android.documentsui" stopped="false"/>
<initial-package-state package="com.android.gallery3d" stopped="false"/>
<initial-package-state package="com.android.messaging" stopped="false"/>
<initial-package-state package="com.android.quicksearchbox" stopped="false"/>
<initial-package-state package="com.android.settings" stopped="false"/>
<initial-package-state package="com.android.stk" stopped="false"/>
<initial-package-state package="org.chromium.webview_shell" stopped="false"/>
</config>