Songchun Fan ce18c5e1f6 [SettingsState] fix boot loop due to corrupted database file
Use an explicit fallback file for each settings file. If the original file
is corrupted and fails to be parsed, use the fallback file instead.

The fallback files are updated once daily if the original files are
changed.

BUG: 119723324
Test: manual by pushing a malformed xml file
Change-Id: I1deb203cd1f53649a5675ad90290075fce6ca942
2020-04-27 16:10:26 -07:00

31 lines
1.2 KiB
XML

<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="com.android.providers.settings"
coreApp="true"
android:sharedUserId="android.uid.system">
<application android:allowClearUserData="false"
android:label="@string/app_label"
android:process="system"
android:backupAgent="SettingsBackupAgent"
android:killAfterRestore="false"
android:restoreAnyVersion="true"
android:icon="@mipmap/ic_launcher_settings"
android:defaultToDeviceProtectedStorage="true"
android:forceQueryable="true"
android:directBootAware="true">
<provider android:name="SettingsProvider"
android:authorities="settings"
android:multiprocess="false"
android:exported="true"
android:singleUser="true"
android:initOrder="100"
android:visibleToInstantApps="true" />
<service
android:name="WriteFallbackSettingsFilesJobService"
android:permission="android.permission.BIND_JOB_SERVICE"
android:exported="true"/>
</application>
</manifest>