Spica Multitouch driver BUGREPORTS

[cXhristian]

Gabriel, I reported pretty much the same bug earlier. Just take a look at the previous pages.

[wrathian]

The touchpanel goes berserk with singletouch too, so there's no reason for that. The only way to avoid it is to charge with original charger, that works for me.

[Gabriel-LG]

Gabriel, I reported pretty much the same bug earlier. Just take a look at the previous pages.

check (meaning confirmed)

[cXhristian]

Not my last post, but my post before that.
About swipes when tapping screen with two fingers.

[cmykola]

Reviewed code of V2.0b. Is it a feature that on action behavior "If two fingers were on the screen and the one that arrived first is lifted then report both fingers before continuing" the ::input_sync() can be called two times? On Multi touch test it looks like some movement of the second touch circle after releasing first touch.

[Gabriel-LG]

Reviewed code of V2.0b. Is it a feature that on action behavior "If two fingers were on the screen and the one that arrived first is lifted then report both fingers before continuing" the ::input_sync() can be called two times? On Multi touch test it looks like some movement of the second touch circle after releasing first touch.

Yes it is a feature; When the first finger is lifted, both finges will be reported lifted momentarely (followed by input_sync), then the second finger is reported touching the screen (followed by input_sync). I do this because Eclair will otherwise report a swipe...

About the slight movement of the second contact when releasing the first; I think this is due to a small capacative fluctuation when lifting a finger.

btw, I really appreciate someone reviewing my sourcecode

[kenshin]

Free audit eh?

[cmykola]

OK. Thanks. Now understood. The last but not least is the static place to store touch information. Is there guarantee that ::qt5480_work_func is called after ::input_sync() (otherwise there can be a mix of touch data)?

[tgpraveen]

@Gabriel_LG

few more bugs.
1. while using stock android keyboard particularly in landscape mode two errors happen:-
a. when typing fast some letters are missed ie not shown as typed. this used to occur in samsung rouch driver also and might be fault of android os or andorid keyboard.
b. BUT second problem is that while again typing somewhat fast with two hands it seems that many letters are displayed as pressed twice though i only pressed them once. this is not a multi touch problem and occurs with sngle touch also but is noticeable more as with multitouch ie 2 fingers one is typing faster. this did NOT occur in samsung driver so i think it should be looked at. others also share your experience.

2. is there a time limit for which a touch is recognized as active i mean in a racing game i play i have to keep one on screen button pressed continuously but after some time few mins ie 2-3 min that touch is lost and i have to again lift my finger and press it again. if so can this time limit be increased?

---------- Post added at 08:01 PM ---------- Previous post was at 07:59 PM ----------

could you enable it in the next version?
I will have a look at it, but no promises

what will this if enabled help us in? i mean what feature will it provide? talking about "The QT5480 has a register named REG_TOUCH_SIZE_RESOLUTION_CONTROL (currently set to 0)"

and just btw the battery problem is indeed fixed. thanks a ton for your work Gabriel_LG.

[Gabriel-LG]

OK. Thanks. Now understood. The last but not least is the static place to store touch information. Is there guarantee that ::qt5480_work_func is called after ::input_sync() (otherwise there can be a mix of touch data)?

input_sync() is only called from the qt5480_work_func() stack. qt5480_work_func() on its turn is only called from a work_queue. So it is guaranteed that none of the input reports can get mixed up. The tuoch information needs to be stored in static space, because multiple calls to qt5480_work_func() may be combined before sending out an input report.

@Gabriel_LG
few more bugs.
1. while using stock android keyboard particularly in landscape mode two errors happen:-
a. when typing fast some letters are missed ie not shown as typed. this used to occur in samsung rouch driver also and might be fault of android os or andorid keyboard.
b. BUT second problem is that while again typing somewhat fast with two hands it seems that many letters are displayed as pressed twice though i only pressed them once. this is not a multi touch problem and occurs with sngle touch also but is noticeable more as with multitouch ie 2 fingers one is typing faster. this did NOT occur in samsung driver so i think it should be looked at. others also share your experience.

2. is there a time limit for which a touch is recognized as active i mean in a racing game i play i have to keep one on screen button pressed continuously but after some time few mins ie 2-3 min that touch is lost and i have to again lift my finger and press it again. if so can this time limit be increased?

---------- Post added at 08:01 PM ---------- Previous post was at 07:59 PM ----------



what will this if enabled help us in? i mean what feature will it provide? talking about "The QT5480 has a register named REG_TOUCH_SIZE_RESOLUTION_CONTROL (currently set to 0)"

and just btw the battery problem is indeed fixed. thanks a ton for your work Gabriel_LG.

1a+b: the stock android keyboard does not support multitouch, so I think you might want to try a better keyboard
1b: this is an effect of my Eclair-swipe-bug workaround. Hopefully this will be fixed in Froyo. If I were to disable this workaroud then you would swipe across the keyboard missing a keys, so I had to choose bteween two evils.

I think you might want to try my upcoming release that fixes the issue with rapidly alternating touches resulting in swipes. I think it will partially resolve issue 1a

2: I think that either the QT5480 or Android discardes a contact pressed for 2-3min is a false positive. Would you care to test this with multitouch vis test?
Press and hold one finger until it is reported released, then add a second and third finger to the screen. If you see two contacts the screen, then it is the qt5480 discarding your first contact, if you see only one then it is Android.