Spica Multitouch driver BUGREPORTS

[pixiejoe]

I am afraid I will need to rewrite Samsung's entire qt5480_work_func (because it is *CRAP*) and part of the issues are due to bad coding in this function. So fixing the issues will take some time...

you might be right but even so you have been able to give us multitouch i am sure that if you go for improving the performance you will be able to do it

[buneech]

I am not sure if this was already written, but i get sporadic movement when holding a single touch on the screen while charging from the outlet (with spica's wall charger), not from the computer. Also, multitouch isn't really usable at that time, because if you touch the screen with two fingers, both points are unregistered.
I'll attach a video of it.

Video: http://www.youtube.com/watch?v=BY5EOiqpLe0

[NOS]

Hey, big trouble.
I've had spica since march. so far no problems.
now installed multitouch. after 2 days suddenly, out of nowhere notification came: "SD Card removed. Insert new one". did nothing with the phone, just was charging from USB.
tried fatory reset, older firmwares but nothing helped. same card works well in other phones. it doesnt recognize any card at all. inserting doesn`t play sound onr accepts the cards any more.
Please help should i bring it to warranty ?

[tgpraveen]

Hey, big trouble.
I've had spica since march. so far no problems.
now installed multitouch. after 2 days suddenly, out of nowhere notification came: "SD Card removed. Insert new one". did nothing with the phone, just was charging from USB.
tried fatory reset, older firmwares but nothing helped. same card works well in other phones. it doesnt recognize any card at all. inserting doesn`t play sound onr accepts the cards any more.
Please help should i bring it to warranty ?

strange 2 days back all of a sudden for the first time ever i got message "sd card damaged". then i restarted my phone 2 times and removed and reinserted sd card and then from then it is working normally. googling for that error message threw up some results of people long time ago on G1 having the same issue though no body could pinpoint the cause.
also i had not connected the phone to computer quite a few hours before the error msg came so it was not due to improper ejection from computer.
if more people get this type of erro then pls report.

[chiaz]

still there is some delay when we touch the screen simultaneously

[NOS]

is there any way to test the SD Card slot ?
to ensure is it firmware or hardware problem..

[tgpraveen]

sd card slot is not having problem. i was getting error msg sd card damaged. the card got his sd card corrupted. and we are not even sure this is due to multitouch driver.

[Gabriel-LG]

I have just finished rewriting the entire qt5480_work_func (including my initial multi-touch patch) .
I am running some preleminary tests right now. The new driver feels more responsive so far.

I was able to fix the following issues :
Third finger on screen will cause loss of the first two touches confirmed fixed
The qt5480 can track only up to 2 contacts. The new driver will ignore all contacts while there are more than two. This results in not loosing the first two contacts, however you cannot move the first two contacts while 3 or more fingers are touching the screen.

Overlapping tabs (finger1, finger2, finger1 release) result in a swipe confirmed fixed
This is an issue with Eclair, other manufacturers also implemented work-arounds for this. I implemented the following: when two contacts are on the screen and the contact that fist arrived leaves, the second contact will be reported leaving immediately reentering.

Decreased performance with MT driver confirmed fixed (dual touch generates too much output)
Decreased battery life with MT driver confirmed fixed (dual touch generates too much uoutput)
The new driver will combine multiple i2c messages until it can form a full input-report, and will then only send the input-report if it contains changes.

The following issues remain unresolved :
Two fingers close to eachother are sensed as a single touch confirmed
This is a qt5480 firmware/hardware issue. I think it can be solved by modifying the QT5480 configuration registers. But it remains a question of "if" and "how".

Touchscreen may go beserk when connected to micro-USB confirmed
This is a hardware issue. I think Samsung made a design fault with the shielding and signal ground of the USB and the touchscreen. I was hoping that my three finger solution would decrease this issue somewhat, but it didn't.

[tgpraveen]

I have just finished rewriting the entire qt5480_work_func (including my initial multi-touch patch) .
I am running some preleminary tests right now. The new driver feels more responsive so far.

I was able to fix the following issues :
Third finger on screen will cause loss of the first two touches confirmed fixed
The qt5480 can track only up to 2 contacts. The new driver will ignore all contacts while there are more than two. This results in not loosing the first two contacts, however you cannot move the first two contacts while 3 or more fingers are touching the screen.

Overlapping tabs (finger1, finger2, finger1 release) result in a swipe confirmed fixed
This is an issue with Eclair, other manufacturers also implemented work-arounds for this. I implemented the following: when two contacts are on the screen and the contact that fist arrived leaves, the second contact will be reported leaving immediately reentering.

Decreased performance with MT driver confirmed fixed (dual touch generates too much output)
Decreased battery life with MT driver confirmed fixed (dual touch generates too much uoutput)
The new driver will combine multiple i2c messages until it can form a full input-report, and will then only send the input-report if it contains changes.

The following issues remain unresolved :
Two fingers close to eachother are sensed as a single touch confirmed
This is a qt5480 firmware/hardware issue. I think it can be solved by modifying the QT5480 configuration registers. But it remains a question of "if" and "how".

Touchscreen may go beserk when connected to micro-USB confirmed
This is a hardware issue. I think Samsung made a design fault with the shielding and signal ground of the USB and the touchscreen. I was hoping that my three finger solution would decrease this issue somewhat, but it didn't.

awesome work man!!
about the beserk when charging it happens with spica single touch fw from samsung also.
and the funny thing is that it happened to me on original fw with charging usb cable (but not data usb cable) when i initially bought spica for a few days and suddenly stopped happening after that. it is a real quirk. though then it happened for a few days when usb data cable was connected (but no problem with charging usb cable) but then even that went away after some days.
so indeed weird.

[Gabriel-LG]

Could somebody check if the Touchscreen may go beserk when connected to micro-USB issue also occurs in the ORIGINAL samsumg rom?
Thank you tgpraveen for confirming (I was still typing when you posted your reply)

And if anyone is running an original samsung rom could you please connect with ADB and make a dump of the QT5480 configuration registers?

# cat /sys/class/sec/ts/setup
# dmesg

This will give a list of 241 numbers. Please post them in this thread...