screen responsiveness

[Guest zbych00]

Hello everyone.

I just bought this phone and I'm quite happy with it, however, I'm a bit surprised how poor is the touch screen sensitivity comparing to my Motorola Defy. I often need to tap more than once to get response. It doesn't happen all the time though. I noticed that this usually happen when I tap with the tip of my finger. It doesn't happen when I keep my finger flat but it's difficult to type or select precisely that way.

Do you experience the same? Do you think this is a software/firmware or hardware related issue?

In one of the other topics someone suggested the "SGS Touchscreen Booster" app but it didn't help much.

Thanks for your help.

[Guest Patrick73]

I found if you run the app MultiTouch Visualizer 2 off the google play store. I have found on the first touch on the screen the amount of touch vairys depending on how hard you press it.

Its also in one of my videos showing how it works too.

Cheers

[Guest KillerMackem]

Is it ridiculously noticeable? How is the responsiveness compared to the San Francisco?

[Guest Davidoff59]

I don't notice any difference to the blade personally. A factory reset seems to fix a few issues that have been posted

[Guest punjabi]

Yes I agree about the screen responsiveness it's clearly an issue. I'm typing using my iPhone and have no problem but the G300 is like an old Blade compared to this.

I would have thought this to be improved with a 1ghz processor, surely....? Or is it software related I wonder.... Let's hope so.

[Guest dejan.m]

I'm running ICS B944 and I still have this problem. I usually have to tap more than once to get response. Does anyone have solution for this problem?

[Guest Hogweed]

Still on Paul's Gr2 Modaco GB ROM (B888 based). Touchscreen response is great as it always has been. Probably not the answer you want to hear though.

[Guest Magnets]

My Blade was more sensitive than this device (in fact all my other touchscreen devices are more sensitive) but you get used to touching with slightly more pressure.

[Guest fr0do]

Dazzo has managed to get the touch screen to respond like it's on steroids on his CM builds. Allegedly.

[Guest PaulMilbank]

Do you have a synaptics or melfas digitiser? Check with an app like elixir 2. Go to information>input devices>more information and scroll until you see atmel, synaptics or melfas.

My kernel I am playing with seems pretty good, but I still want to try DAZ's touchscreen drivers or porting the original 2.6.38 drivers forward to the 3.08 kernel. You do get used to using a slightly longer touch after a while, but I still miss some keys when typing on the keyboard sometimes.

[Guest dejan.m]

I have synaptics digitiser. I suppose that problem is with touchscreen drivers used with 3.08 kernel.

[Guest b4da55]

Which was the better screen pls as i seem to remember reading one was better than the other

Thx

[Guest Davidoff59]

Suppose its like the camera issues earlier in the year, Huawei got people to post pics and were like look there is nothing wrong with the camera, the images are pin sharp. The twats failed to mention that different camera sensors were put in the device

[Guest LMariachi]

This happens in every version of this mobile, had 2 G300, happens on both, tried a lot of roms and still hapenning, i think in Infusion is a little better....

I've also recalibrated with SmartKeyboardPro but it's useless the issue is always there.

Dazzo has managed to get the touch screen to respond like it's on steroids on his CM builds. Allegedly.

Waiting for this fix impatiently....

[Guest dejan.m]

When I enter engineering menu it tells that touch screen type is synaptics-CMI.3 and lcd type is CHIMEI RSP61408. Which one digitizer is better synaptics or melfas?

[Guest dejan.m]

I made screen more responsive with disabling CPU rendering. Process to disable CPU rendering is:

- with a file manager with root access go to system/lib/eg

- open the file egl.cfg. DELETE everything inside the file but keep this line: 0 1 adreno200

- rename libGLES_android.so from egl folder.

Add these to your Build.prop file:

debug.qctwa.statusbar=1

debug.qctwa.preservebuf=1

debug.qc.hardware=true

com.qc.hardware=true

To improve scrolling add this to build.prop

ro.max.fling_velocity=4000

Reboot phone.

I found this method originally on http://forum.xda-developers.com/showthread.php?t=1575984