Revision history [back]

Alarm UI doesn't always sync with the hardware state.

Because of other apps I had a unresponsive UI when trying to modify my alarms. I tapped an existing (set to 5:30 am) alarm to enable it. But nothing happened, so I tapped it again. I tapped it multiple times before realizing it was no use and waited until the UI was responsive again and then I choose to enable another alarm (set to 7:30 am) instead (because I got information that I didn't have to get up that early.

In the UI the 5:30 am alarm was disabled, but the next morning it went of. 5 times in a row!I had no idea why it went of again and again, though I choose to dismiss it every time. Not until I rebooted the phone some time later. Then there were 5 instances of the 5:30 am alarm. Apparently the taps had gone through to some logic that controlled the hardware, but the callback to the UI wasn't triggered (or something to that effect) so that the frontend logic didn't know.

Alarm UI doesn't always sync with the hardware state.

Because of other apps I had a unresponsive UI when trying to modify my alarms. I tapped an existing (set to 5:30 am) alarm to enable it. But nothing happened, so I tapped it again. I tapped it multiple times before realizing it was no use and waited until the UI was responsive again and then I choose to enable another alarm (set to 7:30 am) instead (because I got information that I didn't have to get up that early.

In the UI the 5:30 am alarm was disabled, but the next morning it went of. of anyway. 5 times in a row!I times! I had no idea why it went of again and again, though I choose to dismiss it every time. Not until I rebooted the phone some time later. Then there were 5 instances of the 5:30 am alarm. Apparently the taps had gone through to some logic that controlled the hardware, but the callback to the UI wasn't triggered (or something to that effect) so that the frontend logic didn't know.