GUI unresponsive in morning

[GoogleCodeExporter]

On my T-Mobile G2 running Modaco Custom Rom 2.2, the alarm will ring in the
morning (having set the screen to not turn off whilst charging) as
expected. However, when attempting to 'swipe' to disable the alarm, the GUI
will not respond, and several attempts (with no visual feedback, i.e. the
swipe button does not move) are required before the alarm is cancelled.

Thanks for all the hard work so far.

Original issue reported on code.google.com by daniel.p...@gmail.com on 30 Jan 2010 at 10:46

• Blocked on: #4

[GoogleCodeExporter]

Exactly same problem. Though sometimes I also get the gui showing up randomly 
during
the day and can't disable them, as I described in a previous bug.

Perhaps just use a single "disable" button instead of the "swipe to disable"? I 
have
never been a fan of that anyway.

Original comment by dpastu...@gmail.com on 1 Feb 2010 at 6:32

[GoogleCodeExporter]

I really think this is the same problem as issue #4 Force Close window in the 
morning.
Usually pepople never see a difference between real exception and temporary 
glitch.

I think, application does too much work unpon button click (incliding 
re-scheduling 
alarm for the next day). That's should be easy to fix.

Original comment by a.kosenkov on 1 Feb 2010 at 6:42

[GoogleCodeExporter]

Something I've recently noticed is if the alarm goes off without being 
explicitly
'activated' (and falls back to the latest possible time for activation), the 
alarm
can easily be turned off.

This could imply that the problem is to do with the movement detection 
functionality,
rather than scheduling?

Thanks,

Original comment by daniel.p...@gmail.com on 12 Feb 2010 at 3:00

[GoogleCodeExporter]

Thanks for the reports!

I've moved all heavy calculations to backgroud thread, so user interface will 
have 
higher priority now.

Please report if you still see any problems with this.

Original comment by a.kosenkov on 23 Feb 2010 at 12:46

• Changed state: Fixed

[GoogleCodeExporter]

Original comment by a.kosenkov on 23 Feb 2010 at 12:59

• Added labels: Milestone-Release1.7

[GoogleCodeExporter]

This has also not been entirely fixed in the new release for me. Responsiveness 
is
better, but still not what I'd expect. I wonder if this is due to the phone 
being
handled, and therefore lots of movement sensor events being detected? If it 
isn't
already, could listening for this event be disabled when the alarm is activated?

Thanks,

Original comment by daniel.p...@gmail.com on 24 Feb 2010 at 2:23

[GoogleCodeExporter]

Indeed. I was going to report the same.
Responsiveness is better but I still had to swipe several times to stop the 
alarm.

(HTC Hero)

Original comment by 2sa...@gmail.com on 24 Feb 2010 at 2:44