[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gsmd-devel
Subject:    Accelerometer problems
From:       "Paul-Valentin Borza" <paulvalentin () borza ! ro>
Date:       2008-06-28 16:42:35
Message-ID: 70013cc80806280942y55779417p13e850e4d4f9e1d7 () mail ! gmail ! com
[Download RAW message or body]

Hi guys,

There are some problems with the accelerometers. I've tested reading the
accelerometer with
hexdump /dev/input/event2 (top accelerometer)
hexdump /dev/input/event3 (bottom accelerometer)

The DEVEL IMAGE behaves weird when it comes to accelerometers.
You can only read one accelerometer, and the other one blocks when you start
reading.
The biggest problem is that you don't know which one is working and which
one is not; because at each new restart of the phone, the accelerometer that
is working becomes the non-working one, and the one that wasn't working
before the restart, is working after a new restart.
I really don'r understand this behaviour, but there is clearly a problem
here.

Now, the FSO IMAGE... both accelerometer work!
But you can't read them both at the same time. When you start reading the
other accel (while you're reading an accelerometer) it blocks after a few
seconds.

Hope this helps, and someone can figure it out. It's critical for the
accelerometer-based gestures project - I have to know that at least one
accelerometer is working for sure.
The gesture daemon reads the top accelerometer, but it sometimes work and
sometimes it fails, as described above.

Paul

-- 
http://www.borza.ro

[Attachment #3 (text/html)]

<div>Hi guys,</div>
<div>&nbsp;</div>
<div>There are some problems with the accelerometers. I&#39;ve tested reading the \
accelerometer with</div> <div>hexdump /dev/input/event2 (top accelerometer)</div>
<div>hexdump /dev/input/event3 (bottom accelerometer)</div>
<div>&nbsp;</div>
<div>The DEVEL IMAGE behaves weird when it comes to accelerometers.</div>
<div>You can only read one accelerometer, and the other one blocks when you start \
reading.</div> <div>The biggest problem is that you don&#39;t know which one is \
working and which one is not; because&nbsp;at&nbsp;each new restart of the phone, the \
accelerometer that is working becomes the non-working one, and the one that \
wasn&#39;t working before the restart, is working after a new restart.</div>

<div>I really don&#39;r understand this behaviour, but there is clearly a problem \
here.</div> <div>&nbsp;</div>
<div>Now, the FSO IMAGE... both accelerometer work!</div>
<div>But you can&#39;t read them both at the same time. When you start reading the \
other accel (while you&#39;re reading an accelerometer) it blocks after a few \
seconds.</div> <div>&nbsp;</div>
<div>Hope this helps, and someone can figure it out. It&#39;s critical for the \
accelerometer-based gestures project - I have to know that at least one accelerometer \
is working for sure.</div> <div>The gesture daemon&nbsp;reads the top accelerometer, \
but it sometimes work and sometimes it fails, as described above.</div> \
<div>&nbsp;</div> <div>Paul</div>
<div><br>-- <br><a href="http://www.borza.ro">http://www.borza.ro</a> </div>



[prev in list] [next in list] [prev in thread] [next in thread]