Jump to content

Multitouch possible in theory?


Guest lemmyc

Recommended Posts

Guest onlyyouzl

Pulse is said to have mini market, using the 2.1 kernel andriod, do not know whether we can resolve your doubts, he transplanted to pulse on, as did 8230rom

Link to post
Share on other sites
Guest BigBearMDC
What does the "SYNAPITICS_DEBUG(...)" statement show for "finger"?

Unfortunately nothing.

Neither logcat nor bugreport shows anything.

Am I looking in the wrong place?

I don't know.

I think "SYNAPITICS_DEBUG(...)" does mostly the same as "printk(...)".

Maybe I have to look at the kernel log, but where is it?

Greetings,

BigBear

Link to post
Share on other sites
Guest McSpoon

You can use dmesg to view the printk statements.

adb shell dmesg

The last time I tried, 'finger' would easily reach 3 by having 3 fingers on the screen (but I don't remember it ever getting to 4). However your x2 and y2 co-ordinates will be probably stay at 0 regardless. I don't know how to persuade it to give us those co-ordinates.

Link to post
Share on other sites
Guest BigBearMDC
You can use dmesg to view the printk statements.

adb shell dmesg

The last time I tried, 'finger' would easily reach 3 by having 3 fingers on the screen (but I don't remember it ever getting to 4). However your x2 and y2 co-ordinates will be probably stay at 0 regardless. I don't know how to persuade it to give us those co-ordinates.

I'm pretty sure that we get the coordinates of the second point.

I now know that neither the buf array nor the i2c_transfer function caused the problems.

The problem I have is that the MCR seems not to work with an 'unmodified' pulse kernel.

Thats why i recompile android 1.5 atm. The kernel should work then, and we should have mutitouch :(

I have the kernel aready finished and lying arround.

Greetings,

BigBear

Link to post
Share on other sites
Guest xangma
I'm pretty sure that we get the coordinates of the second point.

I now know that neither the buf array nor the i2c_transfer function caused the problems.

The problem I have is that the MCR seems not to work with an 'unmodified' pulse kernel.

Thats why i recompile android 1.5 atm. The kernel should work then, and we should have mutitouch :(

I have the kernel aready finished and lying arround.

Greetings,

BigBear

What command line are you using to make it? like $ mkbootfs ......... etc?

Link to post
Share on other sites
Guest BigBearMDC
What are your ... usages? arguments? Not sure what they're called. The words and numbers you put after mkbootimg =P

I don't know :(

I use the commands from the 1.6 ROM development thread :(

Greetings,

BigBear

Link to post
Share on other sites
Guest xangma

I hope I'm not teaching you to suck eggs here ... but hopefully it looks something like this?

mkbootimg --cmdline "mem=128M console=ttyMSM2,115200n8 no_console_suspend=1" --kernel KERNEL1/zImage --ramdisk newramdisk.cpio.gz -o mynewimage.img

Link to post
Share on other sites
Guest BigBearMDC
I hope I'm not teaching you to suck eggs here ... but hopefully it looks something like this?

mkbootimg --cmdline "mem=128M console=ttyMSM2,115200n8 no_console_suspend=1" --kernel KERNEL1/zImage --ramdisk newramdisk.cpio.gz -o mynewimage.img

Exactly :(

And i think uts not necessary to know how to suck eggs if you want to compile a kernel :(

Link to post
Share on other sites
Guest xangma
Exactly :(

And i think uts not necessary to know how to suck eggs if you want to compile a kernel :(

Fair point, it's just if you miss out bits it just wont boot and stay on the Tmobile logo.

Link to post
Share on other sites
Guest BigBearMDC
Fair point, it's just if you miss out bits it just wont boot and stay on the Tmobile logo.

Yap, thanks :(

The kernel should be fine, as it boots up.

But it restarts when it should show the enter PIN screen.

I'll try it tomorrow with my fresh android 1.5 build :-)

Greetings,

BigBear

Link to post
Share on other sites
Guest xangma
Yap, thanks :(

The kernel should be fine, as it boots up.

But it restarts when it should show the enter PIN screen.

I'll try it tomorrow with my fresh android 1.5 build :-)

Greetings,

BigBear

upload? =]

Link to post
Share on other sites
Guest BigBearMDC

Okay, that didn't work :(

Maybe I used an incorrect .config?

You can never be sure what kconfig makes with you .config file...

I'm recompiling it again now.

BTW the phone is now stuck at the kernel boot screen...

Greetings,

BigBear

Link to post
Share on other sites
Guest BigBearMDC
We will always support you, maybe you can from the pulse mini's 2.1rom be inspired by

Thanks <_<

The Pulse should get 2.1 also soon.

Okay, recompiled the kernel, flashed android 1.6 and 1.5 and its still not working :(

Not even the standard Huawei kernel...

I don't know what I'm doing wrong.

Could somebody upload a 1.5 system.img that works, please?

Upload the drivers and I'll have a go =]

One moment, just eating a pizza :mellow:

Edit: Uploadet.

Greetings,

BigBear

synaptics_i2c_rmi_tm1319.c.zip

Edited by BigBearMDC
Link to post
Share on other sites
Guest BigBearMDC

Hell, no!

Just tried it with the MCR, it boots up fine - no freeze at the kernel logo - but restarts then as usual.

Looks like my system.img is a piece of s***, and just refuses to work with my wonderfull (Phoenix - that would be the name of my CROM :( ) boot.img <_<

Please, please, please upload a working 1.5 system.ing :mellow:

Link to post
Share on other sites
Guest BigBearMDC
Mine boots, massively offset though. Can't draw pattern.

How did you compile the kernel?

(I mean the commands)

Could you upload your nandroid backup/boot.img, so I can test it?

Edited by BigBearMDC
Link to post
Share on other sites

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.