sumit-719 / smart-alarm-clock

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

Alarm cannot be disabled #3

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Alarm goes off even if user clicks Diable in alarm time dialog.
Critical issue on weekends.

Workaround:
- Set different time, when you will be deinetely awake, so alarm will not 
disturb you
or re-install application

Original issue reported on code.google.com by a.kosenkov on 30 Jan 2010 at 9:20

GoogleCodeExporter commented 9 years ago
Work stared

Original comment by a.kosenkov on 30 Jan 2010 at 1:23

GoogleCodeExporter commented 9 years ago
I have a similar problem, but it seems that the alarm goes off during random 
times
during the day. It goes off at it's designated time and I will dismiss it. Then 
later
during the day it will randomly go off. I slide the slider and it simply 
disables it
for a few seconds then restarts again, so the phone is stuck in an infinite 
loop.

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

GoogleCodeExporter commented 9 years ago
the alarm starts even if i disabled it on my Milestone 
When will this be fixed?

Original comment by bryce2071 on 7 Feb 2010 at 2:17

GoogleCodeExporter commented 9 years ago
This happened to me this morning.  I woke up before the alarm, disabled 
tracking, and
then the alarm went off anyway?!  No matter how good the motion-based sleep 
cycle
tracking stuff is, an alarm clock needs to be above all 100% reliable in basic
functionality.

Original comment by adam.spi...@gmail.com on 12 Feb 2010 at 11:05

GoogleCodeExporter commented 9 years ago
Fixed. Will be included in the nearest update (today or tomorrow)

Original comment by a.kosenkov on 14 Feb 2010 at 10:46

GoogleCodeExporter commented 9 years ago
Thanks a lot, I will try.  Will that be 1.0.14?  By the way it would be useful 
if the
blog showed timestamps of when each entry was posted (currently you have to 
click on
the post title to find out).

Original comment by adam.spi...@gmail.com on 15 Feb 2010 at 9:38

GoogleCodeExporter commented 9 years ago
This is not fixed.  It happened to me again this morning with 1.6.8 (please 
ignore my
previous question about 1.0.14, I got confused).

It might be better if you do not mark issues as fixed until you get feedback 
from
users that they are definitely fixed?  Thanks :)

Original comment by adam.spi...@gmail.com on 18 Feb 2010 at 10:15

GoogleCodeExporter commented 9 years ago

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