Jump to content

Multitouch possible in theory?

Guest lemmyc

By Guest lemmyc
in T-Mobile Pulse

 Share

Recommended Posts

Guest John Hamelink

Guest John Hamelink

Posted
Posted

Gripping stuff guys. Keep up the excellent work, and we'll have multitouch on our beloved pulses :(

  • Replies 1k
  • Created
  • Last Reply

Popular Days

Popular Days

Posted Images

Guest xangma

Guest xangma

Posted
Posted
Gripping stuff guys. Keep up the excellent work, and we'll have multitouch on our beloved pulses :(

Well we don't know yet. Huawei included all this synaptics debug stuff and changed all the classes or whatever, so i'm guessing either we rewrite the multitouch code ... or rewrite the whole driver =/

Guest xangma

Guest xangma

Posted
Posted
Again,

think positive :(

Heres the patched driver, lets see if it works :(

Greetings,

BigBear

Not to be rude or doubt your work or anything, but did you edit this by hand or just patch it?

Guest BigBearMDC

Guest BigBearMDC

Posted
Posted
Not to be rude or doubt your work or anything, but did you edit this by hand or just patch it?

I used meld to edit it :(

Let me guess ... errors?

Sorry, if there are some.

Could you upload the if there are some, please?

Greetings,

BigBear

Guest xangma

Guest xangma

Posted
Posted
I used meld to edit it :(

Let me guess ... errors?

Sorry, if there are some.

Could you upload the if there are some, please?

Greetings,

BigBear

It's just I patched it too in that kinda way and it didnt work =/ I will try it though. But I just got Bioshock 2 and I wanna play it =P

Guest BigBearMDC

Guest BigBearMDC

Posted
Posted
It's just I patched it too in that kinda way and it didnt work =/ I will try it though. But I just got Bioshock 2 and I wanna play it =P

Thats the first time i used Meld.

I'm used to patch them by hand - but I thought why not, just try it.

Sit down, relax, kick some big daddys' asses and let me compile the kernel :(

Greetings,

BigBear

Guest BigBearMDC

Guest BigBearMDC

Posted
Posted (edited)

BTW if you guys want to test a custom boot.img, don't flash it to the device, but just boot it with this command:

fastboot-linux boot "...path/boot.img"
or if youre using windows 
fastboot-windows boot "...path/boot.img"

without ".

Edited by BigBearMDC
Guest BigBearMDC

Guest BigBearMDC

Posted
Posted

Okay, I'll patch it by hand.

Otherwise that won't work - I get too many errors.

But not until tomorrow.

I just don't have enough time today :(

Greetings,

BigBear

Guest xangma

Guest xangma

Posted
Posted
Okay, I'll patch it by hand.

Otherwise that won't work - I get too many errors.

But not until tomorrow.

I just don't have enough time today :(

Greetings,

BigBear

That's fair =] Thanks for the tip too.

Guest BigBearMDC

Guest BigBearMDC

Posted
Posted

- patched synaptics driver... I hope it works!

Greetings,

BigBear

Guest xangma

Guest xangma

Posted
Posted
- patched synaptics driver... I hope it works!

Greetings,

BigBear

Ooooo where?

Guest BigBearMDC

Guest BigBearMDC

Posted
Posted
Ooooo where?

I'll attach the logfile (with the patchfile in it :( )

And the boot.img :(

Haven't tested it yet, as my Ubuntu does not recognize my pulse :(

Greetings,

BigBear

boot.img

MT_Hack_LOG.txt

Guest xangma

Guest xangma

Posted
Posted
I'll attach the logfile (with the patchfile in it :( )

And the boot.img :(

Haven't tested it yet, as my Ubuntu does not recognize my pulse :(

Greetings,

BigBear

just got a restart when it's just about to go to homescreen.

Guest jmmL

Guest jmmL

Posted
Posted
I'll attach the logfile (with the patchfile in it :( )

And the boot.img :(

Haven't tested it yet, as my Ubuntu does not recognize my pulse :(

Greetings,

BigBear

I'm extremely interested in the work you guys are doing. I've given up this year so far (although I might restart when 2.1 is released, as my university's term will have finished around then).

Are you using fastboot to boot your image? If ubuntu is just reporting "waiting for device..." run fastboot as a superuser, that always fixed my problem.

Guest BigBearMDC

Guest BigBearMDC

Posted
Posted

Wohoo its booting on my device :(

I'm extremely interested in the work you guys are doing. I've given up this year so far (although I might restart when 2.1 is released, as my university's term will have finished around then).

Are you using fastboot to boot your image? If ubuntu is just reporting "waiting for device..." run fastboot as a superuser, that always fixed my problem.

You can have a look at the Logfile :(

I also asked Luke Hutchinson at twitter what he did to get MT working, but I haven't got an answer yet :(

Yap I'm using fastboot, but my device isn't even listed in lsusb :(

I don't have a clue why... works like a charm on win 7 RC...

Greetings,

BigBear

Guest David Horvath

Guest David Horvath

Posted
Posted
Wohoo its booting on my device :(

You can have a look at the Logfile :(

I also asked Luke Hutchinson at twitter what he did to get MT working, but I haven't got an answer yet :(

Yap I'm using fastboot, but my device isn't even listed in lsusb :(

I don't have a clue why... works like a charm on win 7 RC...

Greetings,

BigBear

You are using native Ubuntu, not in VB or similar, right? Maybe with another kernel? What do you see in dmesg after plugging in?

Guest BigBearMDC

Guest BigBearMDC

Posted
Posted
You are using native Ubuntu, not in VB or similar, right? Maybe with another kernel? What do you see in dmesg after plugging in?

I'm using Ubuntu on my 2nd PC - i set this one up only for android developing :(

I'm using the standard kernel - I did not make an update.

I can't run dmesg right now, but in a few mins :(

Greetings,

BigBear

Guest BigBearMDC

Guest BigBearMDC

Posted
Posted (edited)

BTW I now flashed the boot.img to my device - reboot -.-

But I noticed that i have a kernel.img with Touchscreen_Gesture=y and this one works fine.

forget it :(

Hmm...

Edited by BigBearMDC
Guest BigBearMDC

Guest BigBearMDC

Posted
Posted

It's getting even more and more and more complicated ...

I'm now again trying to compile the kernel with the other driver from Huawei (...tm1167 instead of tm1319).

Greetings,

BigBear

Guest BigBearMDC

Guest BigBearMDC

Posted
Posted (edited)

- compiled without errors.

(using sysaptics_i2c_rmi_tm_1167 instead of synaptics_i2c_rmi_tm1319

and using cypress_byd_i2c_ts instead of cypress_cpt_i2c_ts)

But I guess that won't work either...

We'd have to edit the android source too for this to work...

But at least we have a kernel that supports multitouch.

Greetings,

BigBear

Edited by BigBearMDC
Guest BigBearMDC

Guest BigBearMDC

Posted
Posted (edited)

Hey, I just noticed a very important mistake I made!

In the 2nd touchscreen driver from Huawei, the code for the second touch input is out-commented!

I'll now recompile the kernel.

Edit:

Okay, recompiled.

Here's the new kernel.

Greetings,

BigBear

zImage.zip

boot.img

Edited by BigBearMDC
Guest HunteronX

Guest HunteronX

Posted
Posted
Hey, I just noticed a very important mistake I made!

In the 2nd touchscreen driver from Huawei, the code for the second touch input is out-commented!

I'll now recompile the kernel.

Edit:

Okay, recompiled.

Here's the new kernel.

Greetings,

BigBear

Can you flash this image as a boot image? (e.g. boot.img)

Guest BigBearMDC

Guest BigBearMDC

Posted
Posted (edited)
Can you flash this image as a boot image? (e.g. boot.img)

Nope, but I'll upload the boot.img too, if you want :(

But beware, if you flash that boot.img, you will end up in a boot-loop!

Edit:

Added boot.img to previous post.

Greetings,

BigBear

Edited by BigBearMDC
Guest BigBearMDC

Guest BigBearMDC

Posted
Posted (edited)

Okay, guys.

Lets make a short summary:

What we have:

A kernel with multitouch.

We used therefore 2 drivers that Huawei fortunately delivered us.

(synaptics_i2c_rmi_tm1167 and cypress_byd_i2c_ts)

What we don'thave (yet):

A KeyInputQueue.java that receives the 2nd touch event.

the driver now returns

if (z) {

	input_report_abs(ts->input_dev, ABS_X, pos[0][0]);

	input_report_abs(ts->input_dev, ABS_Y, pos[0][1]);

}


input_report_abs(ts->input_dev, ABS_PRESSURE, z);

input_report_abs(ts->input_dev, ABS_TOOL_WIDTH, w);

input_report_key(ts->input_dev, BTN_TOUCH, finger);

finger2_pressed = finger > 1 && finger != 7;

input_report_key(ts->input_dev, BTN_2, finger2_pressed);


printk("ABS_X, pos[0][0] = %d\n"

	"ABS_Y, pos[0][1] = %d\n"

	"ABS_PRESSURE, z = %d\n"

	"ABS_TOOL_WIDTH, w = %d\n"

	"BTN_TOUCH, finger = %d\n"

	"BTN_2, finger2_pressed = %d\n"

	,pos[0][0], pos[0][1], z, w, finger, finger2_pressed);


if (finger2_pressed) {

	input_report_abs(ts->input_dev, ABS_HAT0X, pos[1][0]);

	input_report_abs(ts->input_dev, ABS_HAT0Y, pos[1][1]);

}

input_sync(ts->input_dev);[/code]




instead of


[code]input_report_abs(ts->input_dev, ABS_X, x);

input_report_abs(ts->input_dev, ABS_Y, 5880-y);

input_report_abs(ts->input_dev, ABS_PRESSURE, z);

input_report_abs(ts->input_dev, ABS_TOOL_WIDTH, w);

input_report_key(ts->input_dev, BTN_TOUCH, finger);

input_sync(ts->input_dev);

So, it should boot, even without a modified KeyInputQueue...

Greetings,

BigBear

Edited by BigBearMDC

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
 Share
Go to topic listing
×
×
  • Create New...

Important Information

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

  I accept