Couldn't turn off alarm

[GoogleCodeExporter]

What steps will reproduce the problem?
1. don't know how to reproduce,  Calibrated b4 going to bed (0.0 and 0.45).  
Started sleep action and verified recording and that motion was registering 
(good).  Slept.  Awakened by independent clock radio.  Moved..no alarm.  Moved 
more..no alarm.  Picked up phone..alarm  after a slight but notable delay (1/2 
sec?).  Display all green, showing current minute, not all night history.
2.  tried to turn down the volume on the very annoying rooster while I tried to 
figure out how to get the turn off alarm window  only got ring volume..not 
media volume
3. Started sleep again in the hope that I would get the alarm off option.  I 
got a constipated rooster for about a second and then the alarm continued...but 
no off option.  Did that twice.   

4.  Tried to turn off the app with "Advanced task killer".  The app doesn't 
show in the list.
5. Tried to turn off the alarm in the app's settings.  Didn't work.
6.  Had to turn off phone  lost history (my SD card is not working...waiting 
for a replacement)

What is the expected output? What do you see instead?
Didn't get the turn off alarm option.  Saw sleep history screen for the minute 
of waking up.  Had to turn off phone to get alarm to stop.

What version of the product are you using? On what operating system?
Beta version, android 2.2  motorola droid X.

Please provide any additional information below.

Woke up in the middle of the night and checked to see that the history was 
working...looked reasonable.

Original issue reported on code.google.com by pegbat...@gmail.com on 2 Nov 2010 at 10:05

[GoogleCodeExporter]

The alarm has been getting stuck on for me as well, I've been looking for the 
reason why... It seems to be somewhat random.

As for the reason why your phone wasn't setting off your alarm when you moved- 
your calibration was too high (probably.) I'm working on a fix for that.

I also recommend not using task killers- at all. They don't save battery, and 
only slow down your phone and screw with the normal lifecycle of apps. This 
could be part of the reason why the chart was discarded before you were awake/ 
able to save it.

Original comment by jondwil...@gmail.com on 2 Nov 2010 at 4:45

• Changed state: Accepted

[GoogleCodeExporter]

For this problem, the calibration was set at 0.45, and seemed to be creating a 
reasonable graph when I checked it in the middle of the night.  I could see 
where it started - (very large green spike on left) and then it dropped.

With respect to Task killers - I get pissed when I look at my list of tasks and 
there are a bunch of apps that I don't (and never) want on - they get turned on 
automatically - hence the task killer.  It auto-kills about every half hour. I 
can't believe my battery doesn't get drained by all these things running - and 
who knows what they are sending out!! I would like the TK to kill them as soon 
as they start - or better yet disable them altogether. ( and yes, i realize TK 
is also draining my battery)

However, the graph was fine several hours after I went to sleep for the first 
time, so I don't *think* task killer was the issue.  And When I looked at the 
task killer the electricsleep didn't even show up in the list of apps that was 
running.  Interesting, though, it does now.  Maybe that is a clue to the 
constant alarm?

Thanks
Peggy

Original comment by pegbat...@gmail.com on 2 Nov 2010 at 6:14

[GoogleCodeExporter]

A little off topic, but you may want to read this: 
http://geekfor.me/faq/you-shouldnt-be-using-a-task-killer-with-android/

Only services can run in the background, and the activities that you're seeing 
in your task manager are all paused - and CANNOT do anything, but left in 
memory to make them load faster when you actually want to use them. Android is 
usually why they are brought back to life even after you've killed them with 
your task killer.

ElectricSleep, when monitoring sleep, has a "foreground service", which means 
it will be able to do things in the background, and has a high priority so that 
android will try very hard not to kill it. Unless you exclude it from your task 
manager, it could potentially be killed by your task manager.

All that aside, this is partly a different problem, and I'm looking into it!

Original comment by jondwil...@gmail.com on 2 Nov 2010 at 9:58

[GoogleCodeExporter]

Thanks for the link to the you-shouldnt-be-using...  
I still want a way to keep apps from running that I never started, don't want, 
and can't remove  (e.g. blockbuster).  Sometimes I long for the "good ole days" 
when computers responded to your commands, not the other way around!

Original comment by pegbat...@gmail.com on 5 Nov 2010 at 12:16

[GoogleCodeExporter]

This also is off-topic, but I figure it's OK because jondwillis started it.

pegbates5, check out Autostarts for Android (needs root). It allows you to 
adjust which events start which programs. So, for example, I recently installed 
Winamp, and I see in Autostarts that it is set to launch whenever the phone is 
connected to USB. But I don't use Winamp to sync music and don't need it to 
launch when USB is connected. So I disable it. Rather than running a separate 
task to kill tasks, I have used Autostarts once to remove the hook that 
launches Winamp in the first place.

As for the good old days, you're describing the reason that I and many others 
use Android devices (and particularly rooted "Google experience" devices). I 
have an iPad and it's fun, but it's never really "mine" in the sense that I can 
muck around with, oh, say, the system records for which events launch which 
programs.

Original comment by aquarium...@gmail.com on 5 Nov 2010 at 3:07

[GoogleCodeExporter]

I rooted my droid x before I upgraded to 2.2, however didn't have the time to 
play much, and the little I did still wouldn't let me remove the blockbuster 
app.  

Unfortunately, my droid decided it didn't want to interface with any SD card 
this week, so a new one is being shipped (should arrive today).  I expect it to 
ship with froyo - and the last time I looked (before I upgraded before) you had 
to root before froyo was installed.  Do you know if I will be able to root my 
new X with froyo pre-installed?

Thanks

Original comment by pegbat...@gmail.com on 5 Nov 2010 at 9:17

[GoogleCodeExporter]

Issue 13 has been merged into this issue.

Original comment by jondwil...@gmail.com on 11 Nov 2010 at 12:02

[GoogleCodeExporter]

Original comment by jondwil...@gmail.com on 15 Nov 2010 at 2:02

• Changed state: Fixed