Alarm history graph shows 100% motion all night

[GoogleCodeExporter]

Due to the movement sensor bug on my Hero, I leave the screen on all night,
and place the phone face down on my bed.

The main application functionality appears to be okay: the alarm usually
rings in the middle of the wakeup period, suggesting it is at least
processing the movement data correctly.

However, viewing the "Sleep history" page shows a solid blue bar from
activating the alarm until approximately the time I wake up, followed by a
steep downward gradient to nothing (solid black) followed shortly after by
a vertical red line. I presume this is not the intended functionality!

Thanks,

Original issue reported on code.google.com by daniel.p...@gmail.com on 1 Feb 2010 at 12:58

[GoogleCodeExporter]

Daniel, thanks for sharing this.
Could you please attach a file with the data?

it is on your SD card:
/sdcard/com.kosenkov.alarmclock/data/Dream-{number1}-{number2}.data

number1 is your installation number and the number2 is a record number.
file with the problem should have the largest number2.
It contains movements records which is plotted on a picture.

It is the first time you see this problem? I'm afraid it is cauesd by your 
hardware 
accelerometer - some of them might be very noisiy and report of movements while 
the 
phone is staying still.
I'll try to create a test to find such devices and report to users.

Original comment by a.kosenkov on 1 Feb 2010 at 1:45

[GoogleCodeExporter]

Hi there,

I've attached three files. Dream-942540052-3.data is from my current 
installation
(post recent update), and the previous two are ones I believe also to contain 
faulty
data (though I haven't tried to verify this) from before the update.

The problem seems to happen every time I set the alarm and leave the screen on 
(in
order for the accelerometer functionality to work). If the alarm is set and the
screen turned off, then the graph is just black. 

Please also note that I have not tried leaving the phone face up (due to the 
light
from the screen) yet: I'll give that a go tonight, and see if that makes a 
difference.

As I mentioned before, the movement detection does seem to work, as I'm being 
woken
up before the last possible alarm time: whether this is fluke or indicates a 
fault
purely with the graphing, I don't know.

If there is a problem with a noisy accelerometer, would it not be possible to 
add a
calibration process? For example, leave the phone in the position it will be in
whilst you sleep, then after a signal mimic rolling over. This would allow a 
reliable
reading of both background noise and the intensity of an average genuine signal,
allowing the application to differentiate between the two?

Thanks again,

Original comment by daniel.p...@gmail.com on 1 Feb 2010 at 8:27

Attachments:

• Dream-942540052-3.data
• Dream-1558674632-2.data
• Dream-1558674632-4.data

[GoogleCodeExporter]

Had a go with the phone face-up, and the problem is still occurring in exactly 
the
same way. I won't upload the datafile unless you want it, as I can't believe 
it'll
show anything different.

Thanks,

Original comment by daniel.p...@gmail.com on 3 Feb 2010 at 8:10

[GoogleCodeExporter]

I have the exact same issue on my Hero.
The wakeup happens within the 30-minutes wakeup-period when I start to move in 
the
morning (so the sensor works), but all my history graphs are also solid blues.
I have also tried both face up and down with no difference.

Original comment by jan.ande...@gmail.com on 4 Feb 2010 at 11:11

[GoogleCodeExporter]

I have the same issue on the Galaxy. It seems I'm moving the whole night 
through. I've 
even placed it on a desk. It still shows a solid bar of movement. Either 
there's 
something wrong with my sensor or with the app.

Original comment by Enno.Wei...@gmail.com on 9 Feb 2010 at 12:45

[GoogleCodeExporter]

The log of approx one hour just lying on the desk.

Original comment by Enno.Wei...@gmail.com on 9 Feb 2010 at 1:45

Attachments:

• Dream-30850951-15.data

[GoogleCodeExporter]

Have the same problem on Nexus One. And alarm rings always at the red line. 
Maybe you 
can add some sensitivity option for accelerometer to drop out noise or very low 
movement.

Original comment by anton.ve...@gmail.com on 11 Feb 2010 at 9:07

[GoogleCodeExporter]

I attended Android Labs event in Zurich and Google has given Nexus One to 
everybody!
Now I also see this result on my own brand-new phone, I could definetely fix it.

Thanks for your reports!

Original comment by a.kosenkov on 12 Feb 2010 at 4:30

• Changed state: Started
• Added labels: Priority-High
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Thanks for your comments! It seems that Nexus One has not-so-good ("noisiy") 
accelerometer chips inside. So I decreased sensitivity alogside with better 
filtering 
process.
Now it should work okay.

BUT, please note that it works only while the screen is on.

On Nexus One, Droid and Hero phones backlight will be turned on during the last 
30 
minutes. Keep your battery charded.

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

• Changed state: Fixed

[GoogleCodeExporter]

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

• Added labels: Milestone-Release1.7

[GoogleCodeExporter]

Hi,

This does not seem to be fixed in the latest release on my G2. The problem is 
now the
opposite however: no movement is displayed at all on the graph except for at 
the very
end and start of the night (leaving the screen on to ensure detailed recording) 
which
is presumably me picking up the phone to enable/disable the alarm and the phone
vibrating.

Thanks,

Original comment by daniel.p...@gmail.com on 24 Feb 2010 at 2:22

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Doesn't work on HTC Hero either.
Even though I got up (!) from the bed at night there is just one spike on the 
graph at 
the time when alarm started.

Original comment by 2sa...@gmail.com on 24 Feb 2010 at 2:48

[GoogleCodeExporter]

Same here on my Galaxy. Please allow manual adjustment.

Original comment by Enno.Wei...@gmail.com on 24 Feb 2010 at 2:52