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

Commit 9a660991 authored by Amith Yamasani's avatar Amith Yamasani
Browse files

No need to check WRITE_SETTINGS permission in ContentProvider

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
parent dd7705bb
Loading
Loading
Loading
Loading
+0 −1
Original line number Diff line number Diff line
@@ -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>