"Unfortunately, Clock has stopped" when trying to create or edit alarm Recently I started to face a very weird bug.

Whenever I try to tap on Create alarm button, or on existing alarm

I am getting this "Unfortunately, Clock has stopped"

This is a system app I don't know what to do now.

What it could be?

What I tried:


Delete Data from App Manager
Clear cache
Restart the smartphone


Some info:


default (but upgraded) firmware  - Android 4.1.2
Device Galaxy Note II GT-N7100
I had a similar problem but on another device, though try if it can fix your problem this is the what I did:

I opened the Terminal Emulator and typed:

$ su 
# logcat 


Then I held 'Volume down' (a.k.a. Ctrl) and 'c' to stop the output. I scrolled a bit up in the output and found a line that said:

E/SQLiteOpenHelper( 5231): Couldn't open alarms.db for writing (will try read-only): 
E/SQLiteOpenHelper( 5231): android.database.sqlite.SQLiteException: Can't downgrade database from version 7 to 5 


OK, so this is where it's breaking. I wasn't really interested in finding out what should the proper combination of ownership/permissions for the file as I didn't really trust it would end just here, downgrading database version offers a range of situations that can go wrong. And since I don't really care for my past alarm clock times, I got rid of the old database:

# cd /data/data/com.android.deskclock/databases 
# mv alarms.db alarms.db.bak 


otherwise at the time I looked out for this problem the only other solution I saw was to wipe and restore my phone.
If you do so, don't forget to backup all your data first!

Good luck, I hope it helped you or someone.