search

sumit-719 / smart-alarm-clock

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

Always starts alarm at the end of the timespan set... #13

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1.Well, I suppose a Samsung Galaxy
2.Using smart-alarm-clock
3.

What is the expected output? What do you see instead?
Always starts alarm at the end of the timespan set...

What version of the product are you using? On what operating system?
Samsung Galaxy with Android 1.5 and latest Version of smart-alarm-clock

Please provide any additional information below.

Original issue reported on code.google.com by Fliegera...@gmail.com on 2 Feb 2010 at 7:24

GoogleCodeExporter commented 9 years ago 
I think this is by design. 

If you do not finish a sleep cycle in the timespan, the alarm will wake you up 
nevertheless to avoid oversleeping (I hope :)).

Original comment by bjarteu...@gmail.com on 4 Feb 2010 at 7:21

GoogleCodeExporter commented 9 years ago 
Also, after feb 23 revision, sensitivity on htc magic seems very low ... almoat 
no blue parts in sleep 
history. This would peoduce the same effect: that the alarm doesnt go of until 
last minute coz it thinks 
youre fast asleep ...

Original comment by kimberte...@gmail.com on 28 Feb 2010 at 12:39

GoogleCodeExporter commented 9 years ago 
If you've already turned it off, it would be good if it didn't then start 
ringing.
Maybe there should be a snooze button to give people the option of lying in 
after the
alarm has gnoe off, but having it always ring is rather annoying for me :-/

Original comment by JonEdwin...@gmail.com on 1 Mar 2010 at 12:28

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

Original comment by a.kosenkov on 1 Mar 2010 at 4:26

GoogleCodeExporter commented 9 years ago 
I have the same problem on my HTC Magic (Vodafone UK).  It used to work just 
fine,
but since the last Smart Alarm Clock update the accelerometer doesn't register 
much
all night except for the first few minutes where I'm getting comfortable.  The 
alarm
goes off at the latest possible time.

Is it possible to reinstall an old version?

Original comment by badgercr...@gmail.com on 2 Mar 2010 at 10:29

GoogleCodeExporter commented 9 years ago 
I think I'm having the same issue with G1, but not sure.  I've used the app for 
3
nights now.  For first 2 nights I kept at the foot of my bed, for the most 
recent
night I kept it next to my pillow.  The alarm always goes of at the specified 
time,
rather than at the end of sleep cycle.  

The graph shows large peaks at each end of the chart (i.e. going to sleep and 
waking
up) the rest of the graph shows some sporadic much (much!) smaller peaks, with 
zero
activity inbetween.

I've tried changing the tolerance from 30 to 50 mins (perhaps the option of even
longer tolerance would help?).

It would be good if you could put some sample sleep history graphs on your site 
to
show what they should look like when the app is properly functioning.

Also, a bit more involved, but maybe it needs some kind of 'calibration' 
period, so
that over a few nights the software can learn how high a peak indicates
awake/dreaming/deep sleep (like the SleepCycle app for iPhone - where I 
originally
heard of this idea).

Awesome idea and free (!) so cant complain, only hope.

[btw, I also added a star to the problem with it crashing when the alarm goes 
off on
the G1]

Original comment by dfelt...@gmail.com on 6 Mar 2010 at 12:43

GoogleCodeExporter commented 9 years ago 
I see similar behavior on nexus one with the 
screen set to stay on while charging.  Only sees 
movement during the first hour of sleep, even 
when placed on pillow and manually moved 
during night.

Original comment by wolfl...@gmail.com on 9 Mar 2010 at 3:09