Touch screen resolution

[Guest chingy1788]

If you havent noticed already, the Acer liquid has a fairly low resolution touch screen

To see this

Just pull down the notification bar slowely, you will notice that it does not move smoothly, but in steps

Compare this to... basically any other phone, and you will find that other phones' notification bar will move smoothly when pulled down slowely.

This applies not only to the notification bar but in scrolling menus, homescreen, web pages, photos, playing games, etc etc.

A very clear demonstration of this issue is when using one of those apps that turn your phone into a track pad for PC, the mouse cursor moves in steps, not smooth at all.

So

I am wondering now, with the kernel source of 2.1 released, is it possible to increase the resolution of the touch screen? Or is this issue purely a hardware problem?

[Guest Rajit]

you have no idea what ure talking about... the problem is not related to the "resolution" of the screen

[Guest phhusson]

If you havent noticed already, the Acer liquid has a fairly low resolution touch screen

To see this

Just pull down the notification bar slowely, you will notice that it does not move smoothly, but in steps

Compare this to... basically any other phone, and you will find that other phones' notification bar will move smoothly when pulled down slowely.

This applies not only to the notification bar but in scrolling menus, homescreen, web pages, photos, playing games, etc etc.

A very clear demonstration of this issue is when using one of those apps that turn your phone into a track pad for PC, the mouse cursor moves in steps, not smooth at all.

So

I am wondering now, with the kernel source of 2.1 released, is it possible to increase the resolution of the touch screen? Or is this issue purely a hardware problem?

I'd never noticed that, still it's true, BUT unoticeable for must uses.

Try "Multitouch Vis Test" app to understand what's going on:

At first sight, it indeed seems to have a 8pixel resolution on y axis, and 6 pixel on x axis.

BUT, take note of one of those positions, then move your finger smoothly/quickly, like for normal use and then try to go back to your previous position, that's impossible ! (unless you're unlucky)

So what does that mean ?

It's just that our TS does anti-noise filtering.

There is a noise setting available in the TS driver, but it doesn't seem to change anything in that problem.

[Guest dennerjw]

you have no idea what ure talking about... the problem is not related to the "resolution" of the screen

He doesn't mean the resolution of the lcd panel . Resolution can be used to describe the sensitivity of things like touch screens. If you look very very closely at your screen on a white background you will see rows of small dark dots, about eight or so in a row. They are the sensors for the screen, and sometimes when you try to drag something like the notification bar up and you touch between the sensors and not on one, it won't register. I've never used another Android so I wouldn't know the difference, but I don't think it would be anything to lose sleep over. If other more expensive phones are more sensitive, well, you get what you pay for:P

Edited July 22, 2010 by dennerjw

[Guest xaueious]

I think you would modify the noise setting, but then it will start jumping all over the place...

[Guest jayziac]

Using the notification bar to judge the touchscreen resolution is not a good idea. There are a lot of other things going on when you drag the notification bar down that possibly makes it jerkier. Using the app "multitouch screen test" that phhhuson mentioned is a more accurate way. It tracks pretty smoothly since it doesn't have extra code processing running.

[Guest phhusson]

Using the notification bar to judge the touchscreen resolution is not a good idea. There are a lot of other things going on when you drag the notification bar down that possibly makes it jerkier. Using the app "multitouch screen test" that phhhuson mentioned is a more accurate way. It tracks pretty smoothly since it doesn't have extra code processing running.

No, there is the same problem in that app, I also mentioned that /o\