Clock App Settings Reset

pinetree_raccoon

anybody having trouble with the clock app? my settings get reset (gradually increase volume for both alarm and timer, vibrate on timer) and my saved timers.

happens pretty much every day.

Fhggyy5767

pinetree_raccoon I've been using my alarm like crazy lately for waking up, antibiotics 4 times a day and other things for family. My alarm has been solid as well

mythodical

I use the clock app daily for both alarms and timers, and I haven't experienced either of these issues. I too use gradual increase for the alarm and timer, as well as timer vibrate. I only ever use one timer, so I can't speak to that one.

The only thing I can suggest is to verify whether you have a secondary clock app installed which might be conflicting with the GrapheneOS clock. Failing that, you can try resetting the clock app:

Settings > Apps > Clock > Storage and cache > Clear storage

Note, this will wipe your existing alarms, timers and preferences.

pinetree_raccoon

I only have the stock clock app. I just cleared the storage and setup my alarms and timers again. I will check in and let you know how it works. thank you.

pinetree_raccoon

this is still happening. reset phone completely a few times. tried different profiles. same thing. this also doesn't save the dim setting for the screensaver which I think is part of the clock. it always defaults back to dim even though I don't want that...

mythodical

I was just thinking about this post earlier today. I'm sorry to hear it hasn't resolved. I've seen a few posts here this week from folks having issues with other system settings resetting on their own after a reboot (all file access, wifi control, etc.).

I am wondering if there's any chance you've changed the default app settings (not the in-app settings) for the clock or any other system apps. I'm grasping at straws here, but for example the option, Pause app activity if unused is disabled by default for the clock, and the Battery should be set to Unrestricted. Not that I can see how either of these settings would result in what you're experiencing, but just trying to eliminate possible factors.

For what it's worth, your post had me checking my clock app daily for any changes...and none seen so far.

f13a-6c3a

count me in for the issue: from time to time app permissions get reset to defaults. But... not all permissions and not every reboot. I set battery to Restricted for most apps and disable background data for majority. After some reboots, sometimes after installing system update, sometimes after regular reboot, battery permissions get reset to default (Optimized). But I dont think this is GOS issue, I've had the same happened on stock Android 12 and 13. I think I've read somewhere that it's a bug in ASOP.

Fhggyy5767

f13a-6c3a I hear ya. Just never happened on my 3A running GOS

Fhggyy5767

I take that back. It did happen but not this often

f13a-6c3a

I just now rebooted my phone after installing an update and .... permissions were NOT reset

Fhggyy5767

f13a-6c3a Well your case is different or you already have the those permissions set to the reset configuration. Daniel explained yesterday on GitHub that it's a known upstream problem. I'm glad you don't have to reset after every update like us others

dcd-graphenediscuss

I suspect it might be a corrupted storage issue, because for a while, each and every GrapheneOS upgrade would reset my clock and I lost all my alarms. Also, I could force the Clock app to reset its settings using the following steps:

Settings > Display > Screen Saver > When to Start: Select "While charging or docked"
Settings > Display > Screen Saver > Clock > Customize: Removed the check mark for "Night Mode".

Start the Clock App and my settings would be reset, that is, I lost the following Settings:

"Display time with seconds" - turned off (I had turned it on)
Automatic home clock" - turned on (I had turned it off)
Alarm > Silence After: 10 minutes (I had changed it to 1 minute)
Alarm > Gradually increase volume > turned off (I had turned it on to 15 seconds)
Timer > Gradually increase volume> turned off (I had turned it on to 20 seconds)

This problem went away back in September 2022, but at that time, I cleared the Cache and Memory (see steps below) and haven't had any problems since.
Settings > Apps > Clock > Storage & cache > "Clear Cache" then "Clear Storage"
Clock > Settings: I reset all my standard settings and alarms.

dcd-graphenediscuss

Fhggyy5767 Yes, I believe it's an AOSP issue, not GrapheneOS.