Re: pointer (touchpad) aceleration and threshold too low in 11.3.* builds
"Eduardo H. Silva" writes: > P.S.- is there a script that is run when Sugar starts where I could > place the xset command? ~/.xsession is usually a good place to stick X session customisations. On OLPC OS, ~/.xsession works differently than on most systems (it's behaving more like ~/.xsessionrc does on systems where that file is supported), but it's still a good place for your xset. While not meant for this kind of usage, ~/.sugar/debug should also work currently. It may break with future Sugar versions, though. Sascha -- http://sascha.silbe.org/ http://www.infra-silbe.de/ pgpyNSyXaK8Hk.pgp Description: PGP signature ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: USB cameras
Mr. W: We have had lots of success doing simple things using uvc compliant cameras on 1.5 using both cheese and guvcview on Build 883. Our use is mainly for microscopes, but for all intents and purposes they are 'a camera'. Mikus did a lot of work for us to help getting the guvcview parameters part set up if you want to use that as the control mechanism. If cheese is good enough, it works pretty well right out of the box, as long as the USB device is recognized by the XO as a compliant USB camera. Total effort on the gnome side: Yum install cheese. Plug the microscope in after boot, dmesg and lsusb will tell you in advance if it has been recognized. If it is, start cheese, select the camera device and have fun. Better for stills than video, sometimes a stutter in the video stream. Especially problematic if you also have a USB2VGA adapter plugged in and are using an external monitor. It seems to freeze regularly in that case O, and since lsusb doesn't ship by default you may have to yum install usbutils too, to get that beast. We haven't done the 12.1.0 testing yet, but can accelerate that if you'd like us to. Cheers KG On Fri, May 18, 2012 at 10:20 AM, John Watlington wrote: > > Does anyone have experience trying to use a USB camera with > an XO1.5/1.75 ? > > Cheers, > wad > > ___ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel > ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
USB cameras
Does anyone have experience trying to use a USB camera with an XO1.5/1.75 ? Cheers, wad ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: pointer (touchpad) aceleration and threshold too low in 11.3.* builds
On Wed, May 16, 2012 at 8:17 PM, Eduardo H. Silva wrote: > xset q tells that in 11.3.1, the pointer is configured with the values: > > acceleration 7/4 threshold: 1 > > This takes 2, 3 and sometimes 4 swipes to move across the screen. Strange! That's one of our explicit tests -- we test that a quick diagonal swipe can get you across the screen from one corner to another. Falling a tad short may be acceptable, this has to be balanced with aiming for small UI elements in eToys, for example. Of course, with slow swipes, it can take many tries to move across the screen :-) I am sure that if this was widely broken we'd have been up in arms about it way earlier. I'm interested to know about your XO -- model and TP model, perhaps in some cases our touchpad settings are bad. See the wikipage at http://wiki.laptop.org/go/Touchpad/Testing -- it also has additional diagnostic tests that can shed light on the topic. cheers, m -- martin.langh...@gmail.com mar...@laptop.org -- Software Architect - OLPC - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: pointer (touchpad) aceleration and threshold too low in 11.3.* builds
eduardo h. silva wrote: > 2012/5/18 Eduardo H. Silva : > > 2012/5/17 Paul Fox : > >> eduardo h. silva wrote: > >> > 2012/5/17 Paul Fox : > >> > > eduardo h. silva wrote: > >> > > > xset q tells that in 11.3.1, the pointer is configured with the > >> values: > >> > > > > >> > > > acceleration 7/4 threshold: 1 > >> > > > > >> > > > This takes 2, 3 and sometimes 4 swipes to move across the screen. > >> It's > >> > > > quite a difference with a typical touchpad on bigger laptops, and > >> > > > although the experience can't be duplicated because we can't > >> expect > >> > > > kids to be already highly trained with a touchpad, I think it > >> could be > >> > > > improved. > >> > > > > >> > > > I think the balance is to have a larger threshold, so that slow > >> > > > movements are allways acurate, and a higher acceleration, so that > >> > > > movements across the screen are sufficiently fast (very important > >> in > >> > > > Sugar to access the frame for example). Managing to drop down the > >> > > > amount of swipes needed to move across the screen (like 2 swipes) > >> > > > would be excellent and more in par with the older pre 11.3.* > >> behavior. > >> > > > >> > > so you think it was better, previously? > >> > > > >> > > i wonder what has changed. those xset values were chosen > >> specifically > >> > > to be appropriate for the original ALPS touchpad on XO-1. it's > >> > > entirely possible, now that we're two laptops and at least as many > >> > > touchpads beyond that, those numbers are incorrect. > >> > > >> > I meant to compare between the setting of the builds back in 2008 and > >> > 2011 when I began using the XO after a hiatus of years. > >> > > >> > I found a discussion started about the change from "acceleration 7/4 > >> > threshold: 1" to "acceleration 7/4 threshold: 0) > >> > (http://lists.laptop.org/pipermail/devel/2010-January/027245.html ). A > >> > few messages later, it's shown in xset man page: > >> > > >> > "If the `threshold' parameter is provided and 0, the > >> > `acceleration' parameter will be used in the exponent of a > >> > more natural and continous formula, giving precise control > >> > for slow motion but big reach for fast motion, and a > >> > progresive transition for motions in between. Recommended > >> > `acceleration' value in this case is 3/2 to 2, but not > >> > limited to that range " > >> > > >> > Which is exactly what I was looking for. A bit later, Richard A. Smith > >> tells: > >> > > >> > "2 of the apps that our deployments spend a lot of time in are scratch > >> > and etoys. Both of these are not completely sugarized apps and thus > >> > some of the UI elements on the 200 dpi screen are quite small and hard > >> > to use with a fast accel." Though I don't know if he used higher > >> > acceleration values, or with threshold set to 0. > >> > > >> > So the thread ends with: > >> > > >> > "Find someone with kids and figure out whats the best settings for > >> them." > >> > > >> > Next time I am with my nephews I'll be sure to do this, but I already > >> > find threshold 0 a lot better. Perhaps the problem Richard was having > >> > could be solved with a lower acceleration, like 3/2, but still with > >> > threshold 0. > >> > >> i'm sure you're right, and i think we had consensus around that > >> several years ago. it's my belief (after skimming old mail) that the > >> very earliest X servers shipped on XO-1 a) did treat a threshold of 0 > >> as special, but b) did not do it correctly. so using '1' at that time > >> was deliberate. but after a time we (i, certainly) agreed that we > >> should be using 0. > >> > >> we also had a discussion about lowering the 7/4 -- at the time i thought > >> 3/2 was too slow, and suggested 165/100, but i suspect that that's > >> splitting hairs. (i.e. 1.5 vs. 1.65). > >> > >> after verifying, we should at least fix the '0' threshold as a bug, in > >> 12.1.0. > >> > > If it's to be fixed, can't it be changed for the upcoming 11.3.1 as well? it's getting a little late for 11.3.1. > > P.S.- is there a script that is run when Sugar starts where I could > place the xset command? So that I could the new 0 threshold setting > run automatically, and thus use it without thinking about it and be > able to get a better feeling of the behavior. i think /usr/bin/olpc-session is what you're looking for. note that this runs for both sugar and gnome. paul > > Eduardo =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Announcing Q4D14 for XO-1.75
http://wiki.laptop.org/go/OLPC_Firmware_q4d14 Note: the saved volume setting for the startup sound will be lost when reflashing to Q4D14 from an older version. It will revert to the default. Changes in Q4D14: - manufacturing test, fix over-current threshold register value in audio codec, - manufacturing, initialise the RTC SRAM if the contents are invalid, such as on initial connection or reconnection of RTC battery, - fixes to metacompiler. Changes in Q4D13 (which were not announced on devel@): - new EC firmware to turn off USB power during suspend, - tidy-up of the serial port output during game key pause. -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
