Hi all,

I've been using GrapheneOS on my Pixel 7 Pro for a few years now and it's been running great, but a couple times in the past few months, the device will reboot overnight (I believe due to an update) and afterwards, there are three settings related to display scaling that end up getting changed to what I assume are their default values.

The three settings being reset are:
Settings -> Display -> Display size and text -> Font size
Settings -> Display -> Display size and text -> Display size
Settings -> Wallpaper & style -> Home screen -> App grid

Prior to the reboot, Font size and Display size set to their lowest setting, and the App grid was 5x5. Afterwards, the Font size was increased, the Display size was maxed out, and the App grid was 4x5. I do not recall exactly when this reset happened before (only that it was at least two times in the past several months, each time after an update/reboot) but it happened again just a couple hours ago today, so I wanted to drop by and see if this was a known bug. I didn't see any other threads about it for Pixel 7 or Pixel 7 Pro, so I'm not sure if it's just me.

I took a look through the log file for anything obvious; I'd rather not share the entire thing publicly (very verbose, 52k lines, might contain PII) but I did see an info during what appears to be system services startup that appears to reference a lack of display settings being found:

08-16 23:54:48.792 1000 1438 1438 I SystemServiceManager: Starting com.android.server.devicestate.DeviceStateManagerService
08-16 23:54:48.793 1000 1438 1438 E DeviceStateManagerService: Cannot notify device state info change before the initial state has been committed.
08-16 23:54:48.793 1000 1438 1438 I DeviceStateManagerService: Cannot notify device state info change when pending state is present.
08-16 23:54:48.794 1000 1438 1438 D SystemServerTiming: StartCameraServiceProxy
08-16 23:54:48.794 1000 1438 1438 I SystemServiceManager: Starting com.android.server.camera.CameraServiceProxy
08-16 23:54:48.795 1000 1438 1438 D SystemServerTiming: StartWindowManagerService
08-16 23:54:48.795 1000 1438 1438 I SystemServiceManager: Starting phase 200
08-16 23:54:48.795 1000 1438 1438 D SystemServerTiming: OnBootPhase_200
(48 lines of debug omitted; just appears to be a list of other services)
08-16 23:54:48.796 1000 1438 1438 D SystemServerTiming: OnBootPhase_200_com.android.server.devicestate.DeviceStateManagerService
08-16 23:54:48.796 1000 1438 1438 D SystemServerTiming: OnBootPhase_200_com.android.server.camera.CameraServiceProxy
08-16 23:54:48.797 1000 1438 1438 I WindowManager: No existing display settings, starting empty
08-16 23:54:48.806 1000 1438 1438 D SystemServerTiming: SetWindowManagerService
08-16 23:54:48.806 1000 1438 1438 V Configuration: Updating configuration, locales updated from [] to [en_US]
08-16 23:54:48.806 1000 1438 1438 V DisplayManagerService: FrozenStateChangeCallback not supported for pid 1438

And prior to the above snippet, there was also a warn that referenced a lack of settings, though it didn't specify display:

08-16 23:54:48.696 1000 1438 1438 D SystemServerTiming: InstallSystemProviders
08-16 23:54:48.697 1000 1438 1438 V Configuration: Updating configuration, locales updated from [] to [en_US]
08-16 23:54:48.701 1000 1438 1899 I PackageManager: Deferred reconcileAppsData finished 257 packages
08-16 23:54:48.715 1000 1438 1438 W SettingsState: No settings state /data/system/users/0/settings_config.xml
08-16 23:54:48.739 1000 1438 1438 I SettingsState: 0 flag override requests created
08-16 23:54:48.745 1000 1438 1438 D SettingsProvider: SETTINGS_GLOBAL: initialized add_users_when_locked with immutable value 0
08-16 23:54:48.745 1000 1438 1438 D SettingsProvider: SETTINGS_GLOBAL: initialized enable_ephemeral_feature with immutable value 0
08-16 23:54:48.745 1000 1438 1438 D SettingsProvider: SETTINGS_SECURE (user 0): initialized instant_apps_enabled with immutable value 0
08-16 23:54:48.749 1000 1438 1438 V Configuration: Updating configuration, locales updated from [] to [en_US]

Both snippets above were about 6200 lines into the log which I believe started after the most recent update/reboot.

Let me know if there's any other info I could provide. Thanks!