sumit-719 / smart-alarm-clock

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

Movement sensitivity too high #29

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Sleep history graph on my Droid is full scale all 
night. This occurred after yesterday's update. 
Worked fine before that.
2.
3.

What is the expected output? What do you see 
instead?

Which phone model do you have? Droid

Please provide any additional information below.

Original issue reported on code.google.com by sierra14ers on 26 Feb 2010 at 9:55

GoogleCodeExporter commented 9 years ago
I have the same issue on the milestone (see attached)

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

Attachments:

GoogleCodeExporter commented 9 years ago
I recommend changing the priority to high. 
Knowing the input to the algorithm is saturated 
we can be sure sleep motion is not being used 
making it no different than a time based alarm 
clock. (Unless the plotting module is the cause)

Original comment by sierra14ers on 1 Mar 2010 at 4:14

GoogleCodeExporter commented 9 years ago
This is really connteced with 'Movement sensitivity too low' problem.
In fact, sensitivity should be adjusted on per-device basis.

Working on this right now.

Thanks for the screenshots!

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

GoogleCodeExporter commented 9 years ago
Hello.

Just wanted to tell that I got exactly the same issue with my milestone using 
Android
2.01, the graph is full scale always I don't even have any decrease in the 
level. the
result is that it always play the ringtone at H-30.

Cheers.

Aurelien

Original comment by avandoor...@gmail.com on 2 Mar 2010 at 12:03

GoogleCodeExporter commented 9 years ago
I have been having the same problem. According to my sleep history I have been 
moving 
nonstop all night everynight for the last few nights... I find this hard to 
believe and I feel 
like my roommate would have mentioned something to me if that was the case. 
Please fix 
this.

Original comment by icef...@gmail.com on 4 Mar 2010 at 5:50

GoogleCodeExporter commented 9 years ago
Hello, I have the same probleme of JonEdwinCage on my Milestone (French Droid !)

Thank You.

Thierry

Original comment by thierry....@gmail.com on 4 Mar 2010 at 8:04

GoogleCodeExporter commented 9 years ago
Hi,

since the last update, I have the same problem like no. 4. 
And my Milestone (german, vodafone, 2.0.1) is lying on a table, 
don't think we have earthquakes that intensive the whole night :-)

Before the update everything was ok...

Torsten

Original comment by torsten....@gmail.com on 4 Mar 2010 at 10:11

GoogleCodeExporter commented 9 years ago
Do you know if it is possible to have the last 
version before the update?
thanks

Original comment by thierry....@gmail.com on 5 Mar 2010 at 9:38

GoogleCodeExporter commented 9 years ago
It's the same issue on my device.
Unfortunately the last version has been released really a long time ago so I 
thougt I should 
mention it again.
Switching back to the last version would be a good idea, I guess.
Thanks!

Original comment by michael....@gmail.com on 18 Mar 2010 at 5:23

GoogleCodeExporter commented 9 years ago
Hey =)

i use a Milestone and i ve this problem, there is normaly no black interrupt at 
all. 
Except fore one time. I dont know what i did diffrent, but one single time it 
looked 
normal. Only a few blue peaks as intended. 
I still try to figure out and reconstruct but untill today, no result. :(

Original comment by nbt.ta.d...@googlemail.com on 6 Apr 2010 at 4:43

GoogleCodeExporter commented 9 years ago
same problem with a milestone informe argentina. No black spaces. Any 
possibilities of fixing this? 

Original comment by mairavy...@gmail.com on 14 May 2010 at 3:09

GoogleCodeExporter commented 9 years ago
I am having a Hero with a custom Android 2.1.

I'm also experiencing lot's of movement.....

Original comment by wijns...@gmail.com on 16 May 2010 at 6:00

GoogleCodeExporter commented 9 years ago
I am having a Hero with a custom Android 2.1.

I'm also experiencing lot's of movement.....

Original comment by wijns...@gmail.com on 16 May 2010 at 6:00

GoogleCodeExporter commented 9 years ago
I have graph always at maximum.
Samsung Spica I5700 - Samdroid Mod 1.0.2

Original comment by rog...@gmail.com on 18 May 2010 at 10:09

GoogleCodeExporter commented 9 years ago
It would be nice to let User change app sensitivity. For example some people 
sleep 
almost not moving or moving too light and then app works bad because it can not 
detect 
much movement (as last version for me).

Original comment by anton.ve...@gmail.com on 18 May 2010 at 10:27

GoogleCodeExporter commented 9 years ago
Dont want this to come out wrong way, but when can we expect update ?
Would it include calibartion or will you just try to apply some spot-on changes?

Original comment by rog...@gmail.com on 18 May 2010 at 10:49

GoogleCodeExporter commented 9 years ago
Motorola Milestone, Android 2.1
all sleep time - filled rectangle ;)

Original comment by bormo...@gmail.com on 2 Jun 2010 at 4:16

GoogleCodeExporter commented 9 years ago
I've the same problem on the Galaxy i7500 (running a custom 1.6 ROM)
Practically all night solid colour with a few down spikes, i had the phone 
awake all night screen down, as i know this rom is very aggressive when its in 
sleep mode (drops the cpu speed to 19mhz and kills almost everything bar the 
actual phone functions(calls,texts etc))

Original comment by Teknikal...@gmail.com on 18 Jun 2010 at 11:35

GoogleCodeExporter commented 9 years ago
I have the same problem on my Acer betouch e400

Original comment by bauner1...@gmail.com on 5 Jul 2010 at 9:04

GoogleCodeExporter commented 9 years ago
Same for my Evo, graph is totally filled to the top with no spikes down!

Original comment by Mushroo...@gmail.com on 26 Jul 2010 at 7:43

GoogleCodeExporter commented 9 years ago
@a.kosenkov,

Rather than adjusting on a per-device basis, why not adjust the sensitivity 
dynamically (& automatically) on a per-night basis, so that the (smoothed) 
highest level of movement is deemed the "near-waking" state and is adjusted to 
be 100%, and the lowest level is the "deep sleep" state and is adjusted to be 
0%?

Original comment by tloflinp...@gmail.com on 9 Sep 2010 at 6:43

GoogleCodeExporter commented 9 years ago
Or make it so that when you start the alarm you just tap your phone on the side 
of the bed then lie it down to set the calibration up.

Original comment by Teknikal...@gmail.com on 10 Sep 2010 at 11:14

GoogleCodeExporter commented 9 years ago
My HTC Desire has the same problem with this app. Nothing but flat our blue. 
Alarm goes off same time every day. Given the problem was reported back in May 
its a shame it is still outstanding. Like the idea but it does not work for 
many of us.

Original comment by FrankACP...@gmail.com on 13 Oct 2010 at 7:22

GoogleCodeExporter commented 9 years ago
Also on my milestone, tried the app for the first time tonight. All filled 
rectangle on my phone too. Had it just next to my pillow tonight.

Original comment by guidowe...@gmail.com on 27 Oct 2010 at 6:18

GoogleCodeExporter commented 9 years ago
Movement sensitivity depends on device placement.
When i put device under the pillow - graph is extremelly filled.
But when i put device 30-40 cm. away - graph is quite right.

Original comment by paulm...@gmail.com on 8 Nov 2010 at 9:39

GoogleCodeExporter commented 9 years ago
The same problem on my HTC Desire. I put my phone near my pillow. I have a 
"solid" bed, so phone can't react as shown in these graphs... It shows like I 
jump on the bad all the night, but i isn't so :)

I have HTC Desire with Android 2.2(2.10.405.2) onboard. Version of Smart Alarm 
Clock is 1.7.3

Would be nice to have a fix. Thank you.

Original comment by jpro....@gmail.com on 17 Jan 2011 at 8:20

Attachments:

GoogleCodeExporter commented 9 years ago
Tonight I used version 1.7.2 on the same device. They graph is below. Why there 
is such a difference?

Original comment by jpro....@gmail.com on 18 Jan 2011 at 3:57

Attachments: