Revision history [back]

Alarm clock doesn't alert when it should. Instead it starts alerting few minutes after the screen has been unlocked.

Example of the problem:

1. Set alarm to next morning 8:00 at evening
2. Leave the device plugged in to a charger over night
3. Wake up at 10:00, no alarm has gone off
4. Unlock the screen
5. The phone starts alerting few minutes later, showing the original alarm time and the current time

Few times device has also started alerting over an hour too late from the original alarm time.

This started happening on my device about an week ago while I have had the device for about 2 months. I'm running 1.0.2.5, timezone Finland, Helsinki.

Alarm clock doesn't alert when it should. Instead it starts alerting few minutes after the screen has been unlocked.

Example of the problem:

1. Set alarm to next morning 8:00 at evening
2. Leave the device plugged in to a charger over night
3. Wake up at 10:00, no alarm has gone off
4. Unlock the screen
5. The phone starts alerting few minutes later, showing the original alarm time and the current time

Few times device has also started alerting over an hour too late from the original alarm time.

This started happening on my device about an week ago while I have had the device for about 2 months. I'm running 1.0.2.5, timezone Finland, Helsinki.

Alarm clock doesn't alert when it should. Instead it starts alerting few minutes after the screen has been unlocked.

Example of the problem:

1. Set alarm to next morning 8:00 at evening
2. Leave the device plugged in to a charger over night
3. Wake up at 10:00, no alarm has gone off
4. Unlock the screen
5. The phone starts alerting few minutes later, showing the original alarm time and the current time

Few times device has also started alerting over an hour too late from the original alarm time.

This started happening on my device about an week ago while I have had the device for about 2 months. I'm running 1.0.2.5, timezone Finland, Helsinki.