On Mon, Dec 7, 2009 at 12:44 PM, Paul Fox-2 [via OLPC]
<br><<a href="http://n2.nabble.com/user/SendEmail.jtp?type=node&node=4127517&i=0" target="_top" rel="nofollow">[hidden email]</a>> wrote:
<div class='shrinkable-quote'><br>> milan wrote:
<br>> >
<br>> > On Fri, Dec 4, 2009 at 7:34 AM, Martin Langhoff
<br>> > <[hidden email]> wrote:
<br>> > >
<br>> > > With these changes, the touchpads should move a little bit slower,
<br>> > > have a bit more precision, and be a lot less 'jumpy'. In fact, when
<br>> > > they data gets jumpy, the driver ignores the data instead of jumping
<br>> > > wildly.
<br>> > >
<br>> > > Is the kangaroo mode gone? Is it more usable now? Are other effects
<br>> > > creeping in?
<br>> >
<br>> > I have ALPS touchpad.
<br>> >
<br>> > The mouse movement is perhaps a bit less jumpy then in old 802, but
<br>> > overall not very useable. There are times when it's ok (just slower
<br>> > then on the default 802 version), but there are times when it stops
<br>> > almost completely to respond to moving finger. Sometimes it has to be
<br>> > nudged 10 times to move the width or height of the screen. I cannot
<br>> > really tell why it is ok and why it starts behave like that. It comes
<br>> > and goes. Several times it moved slowly by itself. In a way it appears
<br>> > better when I do a continuos line draw (like when drawing spirals),
<br>> > but when using it in an application (does not seem to matter which
<br>> > app), and move the mouse quite a bit, it starts exhibit the "no
<br>> > respond" behavior.
<br>>
<br>> as with the old touchpad driver, the best thing to do when the
<br>> touchpad is behaving badly is to remove your finger from it for a
<br>> few seconds. it will usually detect the condition, and
<br>> recalibrate. the tricky part is that if your finger is still on
<br>> or very near the touchpad while the recalibration occurs, the
<br>> problem probably won't get better, and may get worse.
<br>>
<br>> it's very frustrating that the laptops have such a crippled input
<br>> device. all we can do in the driver is try and notice when things
<br>> "go bad", and make teh best of it, but we can't _prevent_ them
<br>> from going bad.
</div><br>yes i understand the hardware device is, well, quite bad...
<br><div class='shrinkable-quote'><br>>
<br>> thanks very much for your testing.
<br>>
<br>> >
<br>> > >
<br>> > > Comparison test drawing spirals:
<br>> > >
<br>> > > - Grab 2 XOs with the same touchpad type, load the old stable 802 on
<br>> > > one, and my test build (802B1) on the other. If you only have one XO,
<br>> > > try one OS after the other...
<br>> > >
<br>> > > - Open Paint and draw spirals
<br>> > >
<br>> > > 1) try to keep it reasonably tight
<br>> > > 2) stop if you collide or get sloppy
<br>> > > 3) count the number of cycles
<br>> > > 4) try again N times
<br>> > > 5) use the average cycles as a measure
<br>> >
<br>> > well, I only have one XO 1 and did not go back to old 802. With 802b1,
<br>> > I typically managed to do about 5 spiral cycles before it drew into
<br>> > the previous line. But after changing brush size I got a completely
<br>> > unpredictable behavior (non-responding or jumpy)
<br>> >
<br>> > I can also tell that the right part of the pad is much less sensitive
<br>> > (going up and down on the right does not move the mouse), this seems a
<br>> > hardware issue i wonder what others see.
<br>>
<br>> when you say "right part of the pad", i assume your finger is still in
<br>> the middle section, and not all the way into the right section.
</div><br>yes, still in the middle section. the righmost 1/2cm of the middle
<br>section basically does not respond at all. I assume this is hardware,
<br>however, I will go back to old 802 and double check and report back if
<br>it behaves differently. . I have not noticed it explicitly before, but
<br>when I think about it, finger drawing large circles was always funny.
<br><br>> the right
<br>> and left sections will definitely not respond. if your finger is just
<br>> at the righthand edge of the middle section, then your touchpad may truly
<br>> be faulty. you can run a diagnostic: hold the "Check" gamepad key while
<br>> booting, and then hit ESC to get an "ok" prompt. then type "test /mouse".
<br><br>yes, thanks. I am pretty sure I ran test way in the past, and it was
<br>OK, but will try again.
<br><br>milan
<br><div class='shrinkable-quote'><br>>
<br>> paul
<br>> =---------------------
<br>> paul fox, [hidden email]
<br>> _______________________________________________
<br>> Devel mailing list
<br>> [hidden email]
<br>> <a href="http://lists.laptop.org/listinfo/devel" target="_top" rel="nofollow">http://lists.laptop.org/listinfo/devel</a><br>>
<br>>
<br>> ________________________________
<br>> View message @
<br>> <a href="http://n2.nabble.com/8-2-2-Beta-1-test-request-tp4112256p4127361.html" target="_top" rel="nofollow">http://n2.nabble.com/8-2-2-Beta-1-test-request-tp4112256p4127361.html</a><br>> To unsubscribe from Re: 8.2.2 Beta-1 test request, click here.
<br>>
<br></div>
<br><hr align="left" width="300">
View this message in context: <a href="http://n2.nabble.com/8-2-2-Beta-1-test-request-tp4112256p4127517.html">Re: 8.2.2 Beta-1 test request</a><br>
Sent from the <a href="http://n2.nabble.com/Software-development-f396211.html">Software development mailing list archive</a> at Nabble.com.<br>