g-sensor calibration problem
Carl-Daniel Hailfinger
c-d.hailfinger.devel.2006 at gmx.net
Fri Jun 20 11:32:39 CEST 2008
Hi,
On 20.06.2008 11:02, John Lee wrote:
> Hi,
>
> If I use the enclosed python code to test g-sensor on gta02 (read
> /dev/input/event3) while holding the neo vertically, normally the
> result looks like this:
>
> x = -72, y = -990, t = 1.976891 pi
> x = -72, y = -990, t = 1.976891 pi
> x = -54, y = -990, t = 1.982655 pi <=======================
> x = -72, y = -990, t = 1.976891 pi
> x = -72, y = -990, t = 1.976891 pi
>
> It's quite reasonable. However,
>
> * sometimes after booting
> * always after resume (apm -s)
>
> the result will look like this:
>
> x = 1620, y = -36, t = 0.492928 pi
> x = 1620, y = -18, t = 0.496463 pi <=======================
> x = 1620, y = -36, t = 0.492928 pi
> x = 1620, y = -36, t = 0.492928 pi
> x = 1620, y = -36, t = 0.492928 pi
>
> I wonder what's the cause? Any more information I could provide?
>
I can't help you with your direct problem, but the deviations I marked
look similar to the touchscreen deviations. John, can you give us a
longer line of measurements with the neo lying flat on a table?
Andy?
Regards,
Carl-Daniel
More information about the openmoko-kernel
mailing list