From 5e0368f4c776d45afb65fe8517d652ea2a8ea75d Mon Sep 17 00:00:00 2001
From: Rubin Xu <rubinxu@google.com>
Date: Tue, 30 Mar 2021 11:29:11 +0100
Subject: [PATCH] Disable write-ahead log on LockSettingsStorage

As WAL is suspected to be causing data loss on F2FS filesystem.

Bug: 170438530
Test: atest com.android.server.locksettings
Change-Id: I4a7e7e9960a08a7f3f1ce7c2ef9498d4a8f8747f
---
 .../com/android/server/locksettings/LockSettingsStorage.java    | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/services/core/java/com/android/server/locksettings/LockSettingsStorage.java b/services/core/java/com/android/server/locksettings/LockSettingsStorage.java
index b92a83f34e8ca..f69a3bd9d7ce7 100644
--- a/services/core/java/com/android/server/locksettings/LockSettingsStorage.java
+++ b/services/core/java/com/android/server/locksettings/LockSettingsStorage.java
@@ -800,7 +800,7 @@ class LockSettingsStorage {
 
         public DatabaseHelper(Context context) {
             super(context, DATABASE_NAME, null, DATABASE_VERSION);
-            setWriteAheadLoggingEnabled(true);
+            setWriteAheadLoggingEnabled(false);
             // Memory optimization - close idle connections after 30s of inactivity
             setIdleConnectionTimeout(IDLE_CONNECTION_TIMEOUT_MS);
         }