jimitpatel / electricsleep

Automatically exported from code.google.com/p/electricsleep
Other
0 stars 0 forks source link

Message "Sleep to short..." when waking up #84

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What version of ElectricSleep are you using?
0.6.2
On what android device and android version?
Sony Ericsson X10 

What steps will reproduce the problem?
1. Wake up and press the stop button in electricsleep

What is the expected output? What do you see instead?
I get the message "Sleep to short to analyse", but everything seems fine.

Please provide any additional information below.

Original issue reported on code.google.com by marcel.v...@gmail.com on 31 Jan 2011 at 1:25

GoogleCodeExporter commented 8 years ago
Do you know how much internal space you have left? "Sleep too short" likely 
means that:

1) No data was picked up

2) The data that was picked up could not be saved to disk, or was somehow 
deleted during the night

Original comment by jondwil...@gmail.com on 3 Feb 2011 at 7:32

GoogleCodeExporter commented 8 years ago
I'm using the X10 as well on 2.1 and I'm getting this exact same problem as 
well.

The sleep data is recorded, I see the graph and it's in my sleep history, and 
everything seems to work.

I have plently of space left as well, both internally (over 200mb) and on my sd 
card (8GB+).

Original comment by laiks.jo...@gmail.com on 4 Feb 2011 at 6:16

GoogleCodeExporter commented 8 years ago
Same problem on nexus one (2.3 cm7). Plenty of space left.

Original comment by moes1...@gmail.com on 5 May 2011 at 6:25

GoogleCodeExporter commented 8 years ago
Version 0.7.0
Got the same problem
"sleep to short"

Original comment by denne...@gmail.com on 28 Jun 2011 at 12:49

GoogleCodeExporter commented 8 years ago
Issue 122 has been merged into this issue.

Original comment by jondwil...@gmail.com on 14 Aug 2011 at 5:58

GoogleCodeExporter commented 8 years ago

Original comment by jondwil...@gmail.com on 14 Aug 2011 at 5:59

GoogleCodeExporter commented 8 years ago
Issue 133 has been merged into this issue.

Original comment by jondwil...@gmail.com on 14 Aug 2011 at 6:06