SettingsProvider: fix load protected sms setting logic

The method assumed a string resource, but we are working with
string-arrays.

Change-Id: I7d03821c5f5ac5d24445e5c03f7911c3a81c16dd
Signed-off-by: Roman Birg <roman@cyngn.com>

1 files changed, 4 insertions, 4 deletions

diff --git a/packages/SettingsProvider/src/com/android/providers/settings/DatabaseHelper.java b/packages/SettingsProvider/src/com/android/providers/settings/DatabaseHelper.java
index 7639a31c378..2ff2b5a8b77 100644
--- a/packages/SettingsProvider/src/com/android/providers/settings/DatabaseHelper.java
+++ b/packages/SettingsProvider/src/com/android/providers/settings/DatabaseHelper.java
@@ -2078,10 +2078,10 @@ public class DatabaseHelper extends SQLiteOpenHelper {
     }
 
     private void loadProtectedSmsSetting(SQLiteStatement stmt) {
-        String regAddresses = mContext.getResources()
-                .getString(R.array.def_protected_sms_list_values);
-        if (!TextUtils.isEmpty(regAddresses)) {
-            loadSetting(stmt, Settings.Secure.PROTECTED_SMS_ADDRESSES, regAddresses);
+        String[] regAddresses = mContext.getResources()
+                .getStringArray(R.array.def_protected_sms_list_values);
+        if (regAddresses.length > 0) {
+            loadSetting(stmt, Settings.Secure.PROTECTED_SMS_ADDRESSES, TextUtils.join("|", regAddresses));
         }
     }