Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 52c7408b authored by Bookatz's avatar Bookatz
Browse files

Fix typos in preinstalled-packages-platform.xml 

Test: N/A (just comments)
Change-Id: Id383cba37379dc94fe5cb2b81a5bb70acbe7f614
parent 793bc3bd

data/etc/preinstalled-packages-platform.xml

+9 −9
Original line number Diff line number Diff line
@@ -17,7 +17,7 @@ 
<!--

This XML file declares which system packages should be initially installed for new users based on

their user type. All system packages on the device should ideally have an entry in an xml file

(keys by its manifest name).

(keyed by its manifest name).



Base user-types (every user will be at least one of these types) are:

  SYSTEM    (user 0)
@@ -46,7 +46,7 @@ The following three examples should cover most normal cases: 
1. For a system package to be pre-installed only in user 0:



   <install-in-user-type package="com.android.example">

       <install-in user-type="SYSTEM">

       <install-in user-type="SYSTEM" />

   </install-in-user-type>
@@ -54,8 +54,8 @@ The following three examples should cover most normal cases: 
installed on any user of type type FULL or PROFILE (since this covers all human users):



   <install-in-user-type package="com.android.example">

       <install-in user-type="FULL">

       <install-in user-type="PROFILE">

       <install-in user-type="FULL" />

       <install-in user-type="PROFILE" />

   </install-in-user-type>
@@ -63,22 +63,22 @@ installed on any user of type type FULL or PROFILE (since this covers all human 
wallpaper app, since profiles cannot display wallpaper):



   <install-in-user-type package="com.android.example">

       <install-in user-type="FULL">

       <install-in user-type="FULL" />

   </install-in-user-type>





Some system packages truly are required to be on all users, regardless of type, in which case use:

   <install-in-user-type package="com.android.example">

       <install-in user-type="SYSTEM">

       <install-in user-type="FULL">

       <install-in user-type="PROFILE">

       <install-in user-type="FULL" />

       <install-in user-type="PROFILE" />

   </install-in-user-type>



More fine-grained options are also available by specifying individual user types.

E.g.

   <install-in-user-type package="com.android.example">

       <install-in user-type="android.os.usertype.profile.MANAGED">

       <install-in user-type="android.os.usertype.full.GUEST">

       <install-in user-type="android.os.usertype.profile.MANAGED" />

       <install-in user-type="android.os.usertype.full.GUEST" />

       <install-in user-type="SYSTEM">

   </install-in-user-type>

which installs this package on any user whose user type is a managed profile or a guest, or is of