From 72aa131486a25d809a8d132aea0aab53976361b8 Mon Sep 17 00:00:00 2001 From: Kevin Hufnagle Date: Mon, 27 Apr 2020 15:19:44 -0700 Subject: [PATCH] docs: Clarify class definition of Settings.Secure Explain that all apps can read the Settings.Secure database, but only system apps can write to this database Test: make ds-docs -j32 Bug: 124360993 Change-Id: I79fadfe02dfedf403b2da0243f4f209431c9aa0a --- core/java/android/provider/Settings.java | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/core/java/android/provider/Settings.java b/core/java/android/provider/Settings.java index fbd6cbae47d92..97e98aeca1df2 100755 --- a/core/java/android/provider/Settings.java +++ b/core/java/android/provider/Settings.java @@ -5200,8 +5200,9 @@ public final class Settings { /** * Secure system settings, containing system preferences that applications * can read but are not allowed to write. These are for preferences that - * the user must explicitly modify through the system UI or specialized - * APIs for those values, not modified directly by applications. + * the user must explicitly modify through the UI of a system app. Normal + * applications cannot modify the secure settings database, either directly + * or by calling the "put" methods that this class contains. */ public static final class Secure extends NameValueTable { // NOTE: If you add new settings here, be sure to add them to