Jump to content

Recommended Posts

Guest ShakeyB
Posted

After hearing a rumour that Froyo would fix the multitouch swapping issue a while ago (which it doesn't) I noticed that someone had come up with a fix for the Acer Liquid here.. Anyone know if this is possible for the Blade? Would make gaming far less frustrating!

Guest Matty-p
Posted (edited)
After hearing a rumour that Froyo would fix the multitouch swapping issue a while ago (which it doesn't) I noticed that someone had come up with a fix for the Acer Liquid here.. Anyone know if this is possible for the Blade? Would make gaming far less frustrating!

'multitouch swapping issue' expand ? what are the bad things that happen ? i.e what do you thin is wrong

Edited by Matty-p
Guest Treacles
Posted

I think its that, when you go past a certain point with both fingers on the screen, coordinates get flipped for both fingers, so the touch registers in an opposite side of the screen (Either over X or Y axis)

Guest AceOfSpades
Posted

Is this fixed on the newer tft blades? apparantly they have better touch screens, can anyone test?

Also is the blade only able to register 2 inputs or can it do more?

Posted

I'd love to see some work put in to this. It's one of those niggles that really annoys me.

Guest BigBearMDC
Posted

Basically this happens becuase we only have support for DualTouch, not MultiTouch. I don't really know what causes this, but I know what happens: if your fingers pass the same X or Y coordinate on the screen, the touchscreen controller gets crazy and might start swapping the coordinates of your fingers. Further, if you put your fingers close enough together on either X or Y axis the controller isn't able to differentiate the coordinates. If the Liquid has a DualTouch (and not MultiTouch!) controller we might be able to port the fix to the Blade. But this will require kernel modding so we'll only be able to patch the .29 kernel (meaning the fix will be for 2.1 only).

Best regards,

BB

Guest oh!dougal
Posted (edited)
Basically this happens becuase we only have support for DualTouch, not MultiTouch. I don't really know what causes this, but I know what happens: if your fingers pass the same X or Y coordinate on the screen, the touchscreen controller gets crazy and might start swapping the coordinates of your fingers. Further, if you put your fingers close enough together on either X or Y axis the controller isn't able to differentiate the coordinates. ... If the Liquid has a DualTouch (and not MultiTouch!) controller we might be able to port the fix to the Blade. But this will require kernel modding...

Check out Finnish Fillyjonk. (Damn good rom, btw.)

It has custom pressure-proportional touch and a 'multi'touch demonstration app, which incidentally very clearly shows up this 'swapover' glitch (as I commented last night before seeing this thread).

KK's touch driver would seem a great candidate for augmenting with any existing swap-fix logic ...

Edited by oh!dougal
Posted
Is this fixed on the newer tft blades? apparantly they have better touch screens, can anyone test?

Also is the blade only able to register 2 inputs or can it do more?

No, TFT ones are the same.

Posted
Basically this happens becuase we only have support for DualTouch, not MultiTouch. I don't really know what causes this, but I know what happens:

That's because the Synaptics controller used in at least some of our sfs is a dualtouch controller, not multitouch.

Guest gameSTICKER
Posted
Basically this happens becuase we only have support for DualTouch, not MultiTouch. I don't really know what causes this, but I know what happens: if your fingers pass the same X or Y coordinate on the screen, the touchscreen controller gets crazy and might start swapping the coordinates of your fingers. Further, if you put your fingers close enough together on either X or Y axis the controller isn't able to differentiate the coordinates. If the Liquid has a DualTouch (and not MultiTouch!) controller we might be able to port the fix to the Blade. But this will require kernel modding so we'll only be able to patch the .29 kernel (meaning the fix will be for 2.1 only).

Best regards,

BB

Synaptics equals closed source, but still, can this be fixed if we fix the drivers in Kernel?

Guest BigBearMDC
Posted
Synaptics equals closed source, but still, can this be fixed if we fix the drivers in Kernel?

Maybe

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.