<div>Hi guys,</div>
<div> </div>
<div>There are some problems with the accelerometers. I've tested reading the accelerometer with</div>
<div>hexdump /dev/input/event2 (top accelerometer)</div>
<div>hexdump /dev/input/event3 (bottom accelerometer)</div>
<div> </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'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.</div>
<div>I really don'r understand this behaviour, but there is clearly a problem here.</div>
<div> </div>
<div>Now, the FSO IMAGE... both accelerometer work!</div>
<div>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.</div>
<div> </div>
<div>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.</div>
<div>The gesture daemon reads the top accelerometer, but it sometimes work and sometimes it fails, as described above.</div>
<div> </div>
<div>Paul</div>
<div><br>-- <br><a href="http://www.borza.ro">http://www.borza.ro</a> </div>