OSDN Git Service

No need to check WRITE_SETTINGS permission in ContentProvider
authorAmith Yamasani <yamasani@google.com>
Wed, 24 Jun 2015 22:46:09 +0000 (15:46 -0700)
committerAmith Yamasani <yamasani@google.com>
Wed, 24 Jun 2015 22:46:09 +0000 (15:46 -0700)
Permission checks are enforced within the SettingsProvider specifically
for SECURE/SYSTEM/GLOBAL. Now WRITE_SETTINGS is runtime, so it shouldn't
apply to all the settings types.

Bug: 22044704
Change-Id: I9ed25d96b2fa4f46d3d049efa4300cd1d37bbd24

packages/SettingsProvider/AndroidManifest.xml

index 469b776..71aefad 100644 (file)
@@ -15,7 +15,6 @@
         <provider android:name="SettingsProvider" android:authorities="settings"
                   android:multiprocess="false"
                   android:exported="true"
-                  android:writePermission="android.permission.WRITE_SETTINGS"
                   android:singleUser="true"
                   android:initOrder="100" />
     </application>