Improper handling of phone calls

[GoogleCodeExporter]

What version of ElectricSleep are you using?  0.6.2

On what android device and android version? Droid x, android 2.2

What steps will reproduce the problem?
1.  I had alarm set for 10 am.  
2.  Around 9:40 a call came in.  As I attempted to answer the phone (should 
have been one swype to answer) E.S. Alarmed due to movement.  I dismissed the 
alarm (i know I dismissed instead of"snooze because the "rate your sleep" 
message came up), but there was no way to answer the incoming call.

3.  After the kerfuffle (i returned the call)  I finished, returned to the app 
and rated the sleep.  The alarm then went off at 10.

What is the expected output? What do you see instead?
     I expected to be able to answer the phone
    I haven't thought about how E.S. Should react in this case...  Probably keep recording, but otherwise not interfere.

I don't know if the alarm not dismissing l was due to this circumstance, or a 
re-occurence of the previously reported issue.

HAPPY NEW YEAR!

Please provide any additional information below.

Original issue reported on code.google.com by pegbat...@gmail.com on 1 Jan 2011 at 3:22

[GoogleCodeExporter]

Original comment by jondwil...@gmail.com on 12 Jan 2011 at 1:42

• Changed state: Accepted

[GoogleCodeExporter]

"I haven't thought about how E.S. Should react in this case...  Probably keep 
recording, but otherwise not interfere."

Me neither. Your suggestion would work well because there's a chance a call 
could come in the middle of the night, and a groggy user will probably forget 
to re-start ES if it always stops on calls. Otherwise, if it is within the 
light sleep alarm window, I may just stop recording and push the save sleep 
request into the background/notification bar.

Original comment by jondwil...@gmail.com on 13 Jan 2011 at 2:13

[GoogleCodeExporter]

Original comment by jondwil...@gmail.com on 14 Jan 2011 at 1:31

• Changed title: Improper handling of phone calls