Closed GoogleCodeExporter closed 8 years ago
7.5 is really, really high. This makes me feel like there's something else
going on with the calibration. Also, 0.01 is really low. Can you provide any
more detail about what you did when calibrating? Where did you place your
phone, how much did you move, etc.?
The sliders will be re-enabled in a future release.
Original comment by jondwil...@gmail.com
on 1 Nov 2010 at 3:16
My phone was placed in the desktop docking station, sitting on my bed about 10
- 14 inches from my right shoulder. Perhaps being in the docking station with
the phone at about an 80 degree angle affects the equations you may be using?
One of the other smart alarm applications (not Kosenkov's - Smart Alarm Lite)
has a calibration process where you could see the effects of different
movements, and then adjust with the slider the sensitivity.
I tried to simulate movement of turning from my side to my back, both times.
One time I did get the level to go from 0.01 to 0.03.
I'll be happy to keep on beta testing - I'm glad you took this challenge on!
Thanks
Original comment by pegbat...@gmail.com
on 1 Nov 2010 at 3:59
Placed the phone flat on the bed last night, and it calibrated to 0.45 - and
seemed to be making a reasonable graph.
but then -- the unstoppable alarm (see issue 6)
thanks
Peggy
Original comment by pegbat...@gmail.com
on 2 Nov 2010 at 6:15
FYI - calibrated to .41 last night. Phone didn't go off when I did a major
body shift within the correct time frame. Thumped the bed right next to the
phone to make it go off - made a reasonable graph (small blips - larger blips),
but don't know the scale or see a threshold line.
Will try to make the cal go to .2 or thereabouts tonight - does that seem
reasonable?
Original comment by pegbat...@gmail.com
on 3 Nov 2010 at 4:14
I'm changing the way ElectricSleep monitors movement... it really should fix
these problems you're experiencing this time.
Original comment by jondwil...@gmail.com
on 4 Nov 2010 at 11:44
Looking forward to the next release.
Thanks!
Original comment by pegbat...@gmail.com
on 5 Nov 2010 at 3:56
Original comment by jondwil...@gmail.com
on 15 Nov 2010 at 2:12
Original issue reported on code.google.com by
pegbat...@gmail.com
on 1 Nov 2010 at 10:52