Revision history [back]

This morning, my alarm went off at 6:20, like it is supposed do.

I could not silence it however. - The home screen was active, but pressing the power button did not return the phone to lock-mode - I tried opening and closing the alarm application without luck. - The usual overlay for alarm notification was nowhere to be found.

When it finally shut up, I was awake and so was my girlfriend who wasn't planning on getting up at the time.

This morning, my alarm went off at 6:20, like it is supposed do.

I could not silence it however. - The home screen was active, but pressing the power button did not return the phone to lock-mode - I tried opening and closing the alarm application without luck. - The usual overlay for alarm notification was nowhere to be found.

When it finally shut up, I was awake and so was my girlfriend who wasn't planning on getting up at the time.

This morning, my alarm went off at 6:20, like it is supposed do.

I could not silence it however. - however.

• The home screen was active, but pressing the power button did not return the phone to lock-mode - lock-mode
• I tried opening and closing the alarm application without luck. - luck.
• The usual overlay for alarm notification was nowhere to be found.

When it finally shut up, I was awake and so was my girlfriend who wasn't planning on getting up at the time.

Edit: Worth mentioning, that I've been using Jolla as my primary phone since 19th of December. Never had this issue before upgrading to 1.0.4.20

This morning, my alarm went off at 6:20, like it is supposed do.

I could not silence it however.

• The home screen was active, but pressing the power button did not return the phone to lock-mode
• I tried opening and closing the alarm application without luck.
• The usual overlay for alarm notification was nowhere to be found.

When it finally shut up, I was awake and so was my girlfriend who wasn't planning on getting up at the time.

Edit: Worth mentioning, that I've been using Jolla as my primary phone since 19th of December. Never had this issue before upgrading to 1.0.4.20