Multitouch possible in theory?

[Guest xangma]

What system.img are you using? I'm confused. All i'm doing is taking out my kernel, then merging the ramdisk and zImage, then booting again. using 1.7 MCR.

EDIT: Using the normal ones

make ARCH=arm CROSS_COMPILE=arm-eabi-

and

mkbootimg --cmdline "mem=128M console=ttyMSM2,115200n8 no_console_suspend=0" --kernel /root/pulsek/arch/arm/boot/zImage --ramdisk /root/boot/pulsebackup/newramdisk.cpio.gz -o mynewimage.img

It's something to do with that buf you changed from 8 to 15? Maybe? That seems to change the offset.

Edited March 5, 2010 by xangma

[Guest BigBearMDC]

What system.img are you using? I'm confused. All i'm doing is taking out my kernel, then merging the ramdisk and zImage, then booting again. using 1.7 MCR

I used:

MCR 1.7

Andr. 1.5

Andr. 1.6

But yours is booting?!

You've got to be a magician!

:mellow:

Could you please post the commands you used to compile your kernel and how you're making your ramdisk?

BTW I also know why there's an offset:

replace

input_set_abs_params(ts->input_dev, ABS_TOOL_WIDTH, 0, 1, 0, 0);

with

input_set_abs_params(ts->input_dev, ABS_TOOL_WIDTH, 0, 15, 0, 0);

and it will work <_<

Edited March 5, 2010 by BigBearMDC

[Guest xangma]

Still offset =/

EDIT: From the still severely messed up pattern lock screen, it looks like its functioning =/

mynewimage.img.zip

Edited March 5, 2010 by xangma

[Guest BigBearMDC]

Still offset =/

EDIT: From the still severely messed up pattern lock screen, it looks like its functioning =/

Yap. I'll patch the driver to eliminate the offset <_<

[Guest xangma]

Yap. I'll patch the driver to eliminate the offset <_<

Out of interest, what would you be changing? is it uint8_t buf[15]; ?

[Guest BigBearMDC]

Out of interest, what would you be changing? is it uint8_t buf[15]; ?

Nope.

Normally the coordinates of the touch and the ABS_TOOL_WIDTH get divided by 15.

But if we want that MT works properly, we have to set the divisor to 1.

I now patched the driver to set the divisor only to1 if there are 2 fingers on the screen.

BTW I installed MTVisualizer from Luke Hutch, but it doesn't show two fingers <_<

Maybe because of the offset?

We'll see when the new kernel is finished!

Edited March 5, 2010 by BigBearMDC

[Guest xangma]

Nope.

Normally the coordinates of the touch and the ABS_TOOL_WIDTH get divided by 15.

But if we want that MT works properly, we have to set the divisor to 1.

I now patched the driver to set the divisor only to1 if there are 2 fingers on the screen.

BTW I installed MTVisualizer from Luke Hutch, but it doesn't show two fingers <_<

Maybe because of the offset?

We'll see when the new kernel is finished!

can I please have patched driver? =P

[Guest BigBearMDC]

can I please have patched driver? =P

NO!

NEVER!

<_<

synaptics_i2c_rmi_tm1319.c.zip

[Guest xangma]

I'm thinking the whole screen has been doubled in size. It takes twice the movement for your finger to get half the distance.

[Guest BigBearMDC]

I'm thinking the whole screen has been doubled in size. It takes twice the movement for your finger to get half the distance.

I feel like somebody is playing games with me =[

My phone still reboots.

What toolchain version are you using?

4.3.1?

BTW the android source dir is not in my path, so my command looks like this:

make ARCH=arm CROSS_COMPILE=~/android-1.5-source/prebuild/linux-x86/toolchain/arm-eabi-4.3.1/bin/arm-eabi-

Edited March 5, 2010 by BigBearMDC

[Guest xangma]

I feel like somebody is playing games with me =[

My phone still reboots.

What toolchain version are you using?

4.3.1?

4.4.0

Do check your mkbootimg line too =]

[Guest BigBearMDC]

4.4.0

Do check your mkbootimg line too =]

Thanks!

I used your mkbootimg command <_<

[Guest xangma]

prebuilt*

but it wouldn't compile without it anyway?

/root/bin:/root/2.0/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin

Edited March 5, 2010 by xangma

[Guest BigBearMDC]

prebuilt*

but it wouldn't compile without it anyway?

/root/bin:/root/2.0/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin

Sorry, spelling-mistake <_<

Yap I added this dir now to my path, but I'd have to restart my PC for this to take effect, and I don't want to restart it now.

[Guest xangma]

Sorry, spelling-mistake <_<

Yap I added this dir now to my path, but I'd have to restart my PC for this to take effect, and I don't want to restart it now.

Nah just restart the terminal.

[Guest xangma]

It's definitely working I think. Just need to sort out the offset.

[Guest BigBearMDC]

It's definitely working I think. Just need to sort out the offset.

Just out-comment "w = 0;" in "if(!finger2_pressed)".

This should fix it I think.

Damn it!

Mine is still rebooting!

What am I doing wrong?

I'm using exactly the same commands you're using.

<_<

[Guest xangma]

Just out-comment "w = 0;" in "if(!finger2_pressed)".

This should fix it I think.

Damn it!

Mine is still rebooting!

What am I doing wrong?

I'm using exactly the same commands you're using.

<_<

Nooope. Still doesn't work. Still thinks it's like 2 times as big as the screen actually is.

[Guest BigBearMDC]

Nooope. Still doesn't work. Still thinks it's like 2 times as big as the screen actually is.

I think I know whats causing the problem.

Have a look at the 1167 driver, maybe the values get stored in different places in the bigfer buf array.

Do you have an idea what I could do to get my kernels booting or what I'm doing wrong?

[Guest jmmL]

I think I know whats causing the problem.

Have a look at the 1167 driver, maybe the values get stored in different places in the bigfer buf array.

Do you have an idea what I could do to get my kernels booting or what I'm doing wrong?

The only thing I can think of is wiping before applying the update...?

[Guest BigBearMDC]

The only thing I can think of is wiping before applying the update...?

Unfortunately the problem is my compiler.

Xangma compiles the kernel exactly the same way and his kernels work on my phone too <_<

Thanks anyway!

[Guest CHN-michael]

Unfortunately the problem is my compiler.

Xangma compiles the kernel exactly the same way and his kernels work on my phone too :mellow:

Thanks anyway!

SO could it worked well? <_<

[Guest BigBearMDC]

SO could it worked well? <_<

It works, yes. But it needs to be heavily modified to be usable.

[Guest Spooke]

So the phone now supports multitouch using ur drivers etc.

But ofc as you say its not useable.. but it still works right?

[Guest BigBearMDC]

So the phone now supports multitouch using ur drivers etc.

But ofc as you say its not useable.. but it still works right?

It works, at leasr it boots fine wothout problems.

But there is a offset when you click on the screen.

The real and the virtual touch point don't match, but thats a problem we can resolve <_<

The bigger problem for me is that my compiled kernels don't work.

I can't continue until I find a solution for this :mellow:

Greetings,

BigBear

Edited March 5, 2010 by BigBearMDC