sumit-719 / smart-alarm-clock

Automatically exported from code.google.com/p/smart-alarm-clock
0 stars 0 forks source link

Cannot stop alarm in the morning #33

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
I'm having difficulty turning the alarm off on my T-Mobile G1 with Smart 
Alarm Clock version 1.7.2.

The morning ritual goes (I think) roughly like this:
- The screen lights up and the wake-up screen is shown;
- The 'dismiss' button does not respond;
- The home/back keys and the power button do not respond;
- After ~20 seconds Android shows a 'not responding' dialog;
- Clicking 'force close' will close the wake-up screen;
- The alarm keeps going;
- Going into Smart Alarm and performing an "Emergency stop" will stop the 
alarm.

I might not remember correctly (after all, I performed these steps in a 
groggy morning state). I will pay close attention to the exact steps 
tomorrow morning and report back on their accuracy.

I'm using version 1.7.2 from the market on my G1 with Android 1.6. It's a 
Dutch phone which has the latest official OTA update (build number DRC92). 
My locale is set to English and I keep the phone closed and in portrait-
mode during the night.

Also, I have 'Toggle Settings' installed, which includes a task manager, 
but it is not configured to auto-kill any application.

Original issue reported on code.google.com by peter-pa...@gtempaccount.com on 4 Mar 2010 at 10:26

GoogleCodeExporter commented 9 years ago
Exactly same problem on my magic

Original comment by ambhe...@gmail.com on 17 Mar 2010 at 1:20

GoogleCodeExporter commented 9 years ago
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

GoogleCodeExporter commented 9 years ago
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

GoogleCodeExporter commented 9 years ago
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

GoogleCodeExporter commented 9 years ago
Same Problem, need 'force close' to stop alarm.

Original comment by tklau...@googlemail.com on 17 Jun 2010 at 8:10

GoogleCodeExporter commented 9 years ago
Same on Galaxy S

Original comment by JSauva...@gmail.com on 30 Jul 2010 at 5:43

GoogleCodeExporter commented 9 years ago
Issue 32 has been merged into this issue.

Original comment by a.kosenkov on 31 Oct 2010 at 10:38

GoogleCodeExporter commented 9 years ago

Original comment by a.kosenkov on 31 Oct 2010 at 10:39