Re: [QTmoko] Qx problems
On Tuesday, April 23, 2013 09:21:04 PM Neil Jerram wrote: Can you point me more precisely to the relevant code? I'll take a look at it. The code is in openmoko's git or on my github. I really havent looked if it can be applied to GTA04, but here are some references: https://github.com/radekp/linux-2.6/commit/d082ca932a9d03105fe26881ee860e7ff7025a9d https://github.com/radekp/linux-2.6/tree/qtmoko-v26/drivers/input/touchscreen Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [QTmoko] Qx problems
Radek Polak pson...@seznam.cz writes: Maybe after installing it from sid it would work better. Well, it appears that tslib is dead and that evdev is the consensus future. But there seems to be no mainstream Linux discussion of whether / how to add filtering into the evdev stack. (I did see an Android-context discussion, which seems to confirm that something is needed.) I also think that we need some touchscreen filtering - maybe use the filters from 2.6.28 Freerunner's image - they were really good. Can you point me more precisely to the relevant code? I'll take a look at it. Thanks, Neil ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [QTmoko] Qx problems
Radek Polak pson...@seznam.cz writes: you have to try more hard ;-) First explore the Favourites menu item. That way you can add installed X applications and configure them. There are many options that you can configure - e.g. for xterm it's important to enable window manager and virtual keyboard. I recommend also checking use matchbox. What X server and config are you using? With Xfbdev, I find that I don't have mouse/touchscreen input at all. With Xorg, I do have mouse/touchscreen input, using evdev, but it's quite inaccurate and jumpy. Thanks, Neil ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [QTmoko] Qx problems
On Monday, April 22, 2013 09:11:29 PM Neil Jerram wrote: What X server and config are you using? With Xfbdev, I find that I don't have mouse/touchscreen input at all. With Xorg, I do have mouse/touchscreen input, using evdev, but it's quite inaccurate and jumpy. Hi, last time i tried it yesterday. Got the same issue with Xfbdev and Xorg. I wonder what happened with xserver-xorg-input-tslib for wheezy - it looks the package is missing: http://packages.debian.org/sid/xserver-xorg-input-tslib Maybe after installing it from sid it would work better. I also think that we need some touchscreen filtering - maybe use the filters from 2.6.28 Freerunner's image - they were really good. You can try compare Freerunner touschreen and GTA04 touchscreen and you'll notice how much better Freerunner is now. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [QTmoko] Qx problems
On Tue, Apr 23, 2013 at 1:16 PM, Radek Polak wrote: I wonder what happened with xserver-xorg-input-tslib for wheezy - it looks the package is missing: It got removed because the RC bug did not get fixed in time: http://packages.qa.debian.org/x/xf86-input-tslib.html http://bugs.debian.org/674821 -- bye, pabs http://bonedaddy.net/pabs3/ ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [QTmoko] Qx problems
On Thursday, April 18, 2013 07:15:35 PM Rainer Glaschick wrote: Tried to use Qx, installed xglamo, and got only trouble: Lauching xterm gives press AUX to leave in the middle, takes some time, then a terminal in the middle. But no keyboard to enter anything. The done button still visible, but does not work. Only way to get rid of it is using AUX twice and stop instead of resume. Anybody out who has a useful application for Qx? xclock works, but overlaps with the top status line. Trying a python script (xgps) just shows the boot console output for a while, then a message tells that Qx terminated due to application error. Starting Qx from the command line then give the reason for fail. Seems to me that Qx is nothing for normal use, only for debug, and thus should be removed from the normal applist and go either to the system debug menu, or should be, even better, started from the command line only to see the error messages that are likely to occur. Hi, you have to try more hard ;-) First explore the Favourites menu item. That way you can add installed X applications and configure them. There are many options that you can configure - e.g. for xterm it's important to enable window manager and virtual keyboard. I recommend also checking use matchbox. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [QTmoko] Qx problems
Rainer Glaschick ra...@g-pb.de writes: Tried to use Qx, installed xglamo, and got only trouble: Lauching xterm gives press AUX to leave in the middle, takes some time, then a terminal in the middle. But no keyboard to enter anything. The done button still visible, but does not work. Only way to get rid of it is using AUX twice and stop instead of resume. Anybody out who has a useful application for Qx? xclock works, but overlaps with the top status line. Trying a python script (xgps) just shows the boot console output for a while, then a message tells that Qx terminated due to application error. Starting Qx from the command line then give the reason for fail. Seems to me that Qx is nothing for normal use, only for debug, and thus should be removed from the normal applist and go either to the system debug menu, or should be, even better, started from the command line only to see the error messages that are likely to occur. I would really like QX to work well, because I think it would cool to be able to seamlessly run X and Gtk applications as well as Qt. At the moment, however, my observations (in my case on GTA04) are broadly similar to yours, i.e. it doesn't really work. I'm planning to work a bit on this, but time for it is limited so please don't hold your breath. In terms of overall structure, I'd prefer if a QX-requiring application could be launched normally from the app (or games) menu - instead of specially via the QX application - and also that the business of any required installation or configuration was separated out from simply running a particular application. Does anyone have thoughts on that? Thanks, Neil ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
