Open GoogleCodeExporter opened 9 years ago
Exactly same problem on my magic
Original comment by ambhe...@gmail.com
on 17 Mar 2010 at 1:20
My apologies for not reporting back earlier as I had promised. I seem to have
trouble
'paying close attention' in the morning. ;)
A slight correction:
The full problem I described before only happens occasionally. Most of the time
the
alarm screen is just slow and takes a few seconds to respond. If it does happen
(i.e.
it's TOO slow to respond) and the user chooses 'wait' instead of 'force close',
the
alarm functions correctly. Choosing 'force close' will still break the alarm as
described.
-------------------------------------------
So, in summary, the problem seems to be this:
The alarm screen is very slow to respond. If it doesn't respond within a few
seconds,
the system determines it's 'not responding'. If this happens, choosing 'force
close'
will kill the alarm screen but not the alarm and an "Emergency stop" is
required to
stop it.
Original comment by peter-pa...@gtempaccount.com
on 22 Mar 2010 at 11:03
Same exact problem on my Samsung Galaxy (Android 1.6)
worked when i ran Android 1.5.
HAve another symptom as well. sometimes but not so often the alarm dont ring at
all
because the process have died. Smells like some kind of memmory leak to me.
Original comment by markus.r...@gmail.com
on 29 Mar 2010 at 3:54
Still problem with Smart Alarm Clock v1.7.3 (on my G1)
Original comment by banko.a...@gmail.com
on 5 Apr 2010 at 3:32
Same Problem, need 'force close' to stop alarm.
Original comment by tklau...@googlemail.com
on 17 Jun 2010 at 8:10
Same on Galaxy S
Original comment by JSauva...@gmail.com
on 30 Jul 2010 at 5:43
Issue 32 has been merged into this issue.
Original comment by a.kosenkov
on 31 Oct 2010 at 10:38
Original comment by a.kosenkov
on 31 Oct 2010 at 10:39
Original issue reported on code.google.com by
peter-pa...@gtempaccount.com
on 4 Mar 2010 at 10:26