Dell Duo Setup Guide

[variona]

Meaning to tell you: Please call me with a parameter. Like

touchrotate_dell toleft

and if your devices are really not recognized you will have to change thhe script to your needs.
(see my llast post on how to identify your devices)

[cmongini]

i think i got it now but it doesnt seem to work

i changed lines 21 with
then EG=$(xinput list|grep -E 'eGalaxTouch Virtual Device for Single')

and line 16 with
then LV=$(xrandr|grep -i 'LVDS1')

the outcome of
xrandr -q:
Screen 0: minimum 320 x 200, current 1366 x 768, maximum 4096 x 4096
LVDS1 connected 1366x768+0+0 (normal left inverted right x axis y axis) 223mm x 125mm
1366x768 60.0*+ 40.0
1360x768 59.8 60.0
1024x768 60.0
800x600 60.3 56.2
640x480 59.9
VGA1 disconnected (normal left inverted right x axis y axis)

and claudia@claudia-Inspiron-1090:~$ xinput --list
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ SynPS/2 Synaptics TouchPad id=12 [slave pointer (2)]
⎜ ↳ eGalaxTouch Virtual Device for Multi id=13 [slave pointer (2)]
⎜ ↳ eGalaxTouch Virtual Device for Single id=14 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
↳ Power Button id=6 [slave keyboard (3)]
↳ Video Bus id=7 [slave keyboard (3)]
↳ Power Button id=8 [slave keyboard (3)]
↳ Sleep Button id=9 [slave keyboard (3)]
↳ Integrated Webcam id=10 [slave keyboard (3)]
↳ AT Translated Set 2 keyboard id=11 [slave keyboard (3)]
↳ Dell WMI hotkeys id=15 [slave keyboard (3)]

the result is that wenn i call the script with the command toleft ( for example) it kicks me out of the session!

[cmongini]

@ unuse_bagels yes i have the same problem with the hold to right click!

[unused_bagels]

I can make a few guesses, but most of them involve hid-multitouch being excessively new and needing a lot more testing.

No, not multi-touch, I mean good old-fashioned double clicking. Like for opening files.

@ unuse_bagels yes i have the same problem with the hold to right click!

Sucks that it happens to you, but glad I'm not the only one.

[teh603]

KenBW2 (#697),
No, it still crashes if you plug/unplug power - for me the workaround is to suspend first, then it seems to handle the switch okay

Ok, so having finally gotten up off my butt to test this, I've got some pretty good news.

On Lubuntu, at least, the power manager issues seem to be intermittently fixed. I say intermittently because I still get the black screen of kerneloops death from time to time, and plugging/unplugging while suspended is unreliable. That having been said, an intermittent fix is better than no fix and shows a step in the right direction.

[variona]

@cmongini

Try the different parts of the script to find out where and why you get kicked out

xrandr --output LVDS1 --rotate left

xinput set-prop '14' 'Coordinate Transformation Matrix' 0 -1 1 1 0 0 0 0

if your session dies you can append >error.txt to see if any useful debug output is generated and of course /var/log/ could hold some info you need to find the reason for crashing.

I'm not using 12.04 yet so all I can do is guessing - maybe someone who uses it can help?


Oops: The $INPUTDEV parameter is not used in the xinput function call! (quickhack - sorry you would have to change it to:

xinput set-prop $INPUTDEV 'Coordinate Transformation Matrix' 0 -1 1 1 0 0 0 0

and so forth) In your case the script tries to apply the Transformation Matrix on the keyboard (id 11)!

As you found out your eGalax touch has id 13 and id 14!

HTH

[cmongini]

yes the porblem lies by xinput. i let you know if i find a solution!

[Bray90820]

for some reason every time i plug or unplug the charger the system hangs

IMG_20120603_225338.jpg

[teh603]

for some reason every time i plug or unplug the charger the system hangs

IMG_20120603_225338.jpg

That's a running issue. tl;dr is that some nimrods way far upstream are sticking their fingers in their ears and refusing to issue a patch, and claiming that its Dell's problem to fix.

[Bray90820]

That's a running issue. tl;dr is that some nimrods way far upstream are sticking their fingers in their ears and refusing to issue a patch, and claiming that its Dell's problem to fix.

i know for a fact it is not dell i was using joli os which is based off of ubuntu and this problem does not exist