Guest amdnikos Posted February 25, 2010 Report Posted February 25, 2010 Well overall as all of you have already noticed,liquid's touch sensitivity somehow cant compared with htc or motorolla (droid) sensitivity.Especially some days ago i had the luck to play a bit with a Nexus.I could interact with screen even if i didnt touch it!!i kept my finger like 1mm away from screen. My question is: Is that a driver or hardware issue the non good sensitivity compared with htc's android phones?
Guest erto90 Posted February 25, 2010 Report Posted February 25, 2010 Well overall as all of you have already noticed,liquid's touch sensitivity somehow cant compared with htc or motorolla (droid) sensitivity.Especially some days ago i had the luck to play a bit with a Nexus.I could interact with screen even if i didnt touch it!!i kept my finger like 1mm away from screen. My question is: Is that a driver or hardware issue the non good sensitivity compared with htc's android phones? a good part is driver issue...
Guest chingy1788 Posted February 25, 2010 Report Posted February 25, 2010 (edited) if you have the kernel source its all in this file <AcerKernelDir>\kernel\drivers\input\touchscreen\auo_ts.c but we need some one to compile and test... two things I would like to see no midpoint when pressing 2 fingers and sensitivity boost both dont look hard to do but pretty much all the devs are working on Android 2.1 beta... so we'll probably wont see these fixes any time soon Edited February 25, 2010 by chingy1788
Guest amdnikos Posted February 25, 2010 Report Posted February 25, 2010 if you have the kernel source its all in this file <AcerKernelDir>\kernel\drivers\input\touchscreen\auo_ts.c but we need some one to compile and test... two things I would like to see no midpoint when pressing 2 fingers and sensitivity boost both dont look hard to do but pretty much all the devs are working on Android 2.1 beta... so we'll probably wont see these fixes any time soon well the midpoint matter is 100% software issue.Now about sensitivity tbh my opinion is prolly screen hardware issue because we ll had already a screen boost from a developer on donut os from a developer here since the kernel is out that long.
Guest chingy1788 Posted February 25, 2010 Report Posted February 25, 2010 (edited) well the midpoint matter is 100% software issue.Now about sensitivity tbh my opinion is prolly screen hardware issue because we ll had already a screen boost from a developer on donut os from a developer here since the kernel is out that long. which kernel has that? disc0 didn't mention that in his kernels Edited February 25, 2010 by chingy1788
Guest amdnikos Posted February 25, 2010 Report Posted February 25, 2010 which kernel has that? disc0 didn't mention that in his kernels maybe disco didnt,but overall capacitive screen technology supports multitouch.
Guest chingy1788 Posted February 25, 2010 Report Posted February 25, 2010 multi touch enabled kernel has been done by disc0 removing the mid point and using one finger point instead, will make typing on the keyboard easier touch screen sensitivity, there are a couple of values that can be changed in the source to maybe up the sensitivity i haven't read about any one trying that on these forums
Guest Angio Posted February 25, 2010 Report Posted February 25, 2010 there is a settings where we can edit this, but i have not located it yet.... when i do, i will set that to MAX!!!!!!!!!
Guest chingy1788 Posted February 25, 2010 Report Posted February 25, 2010 i reckon its in this file <AcerKernelDir>\kernel\drivers\input\touchscreen\auo_ts.c #define SENSITIVITY_REG 0x67 #define SENSITIVITY 75 those are used by this function static ssize_t set_ts_sensitivity(struct device *device, struct device_attribute *attr, const char *buf, size_t count) { uint8_t sensitivity[3] = {SENSITIVITY_REG,ts_atoi(buf),ts_atoi(buf)}; pr_info("[TS] Sensitivity : X = %d Y = %d\n",sensitivity[1],sensitivity[2]); if (3 != i2c_master_send(h353_data->client, sensitivity, 3)) pr_err("[TS] Set sensitivity error\n"); return count; } I'm sure messing with those values will do something Unfortunately I have no idea on how to compile the kernel... Another thing to look at is if (!finger2_pressed) { /* No multitouch -- force width to zero */; width = 0; x = coord[0][0]; y = coord[0][1]; } else { /* (x,y) coords for multitouch are at midpt between fingers */ x = (coord[0][0] + coord[1][0]) / 2; y = (coord[0][1] + coord[1][1]) / 2; /* Report the width according to the abs distance of x-axis */ width = abs((coord[0][0] - coord[1][0])); } If we make the driver report one finger's location instead of the mid point when two fingers are pressed, the keyboard should be easier to use (It's done this way on cyanogen's mod) whether this is the right file to change or not, I don't know for sure
Guest amdnikos Posted February 25, 2010 Report Posted February 25, 2010 i reckon its in this file <AcerKernelDir>\kernel\drivers\input\touchscreen\auo_ts.c #define SENSITIVITY_REG 0x67 #define SENSITIVITY 75 those are used by this function static ssize_t set_ts_sensitivity(struct device *device, struct device_attribute *attr, const char *buf, size_t count) { uint8_t sensitivity[3] = {SENSITIVITY_REG,ts_atoi(buf),ts_atoi(buf)}; pr_info("[TS] Sensitivity : X = %d Y = %d\n",sensitivity[1],sensitivity[2]); if (3 != i2c_master_send(h353_data->client, sensitivity, 3)) pr_err("[TS] Set sensitivity error\n"); return count; } I'm sure messing with those values will do something Unfortunately I have no idea on how to compile the kernel... Another thing to look at is if (!finger2_pressed) { /* No multitouch -- force width to zero */; width = 0; x = coord[0][0]; y = coord[0][1]; } else { /* (x,y) coords for multitouch are at midpt between fingers */ x = (coord[0][0] + coord[1][0]) / 2; y = (coord[0][1] + coord[1][1]) / 2; /* Report the width according to the abs distance of x-axis */ width = abs((coord[0][0] - coord[1][0])); } If we make the driver report one finger's location instead of the mid point when two fingers are pressed, the keyboard should be easier to use (It's done this way on cyanogen's mod) whether this is the right file to change or not, I don't know for sure good job mate :( , it refers on multitouch too.
Guest chingy1788 Posted February 25, 2010 Report Posted February 25, 2010 Multi touch... kinda has been enabled the driver only supports single touch right now (hence mid point, and width) need alot of changes to get multi touch working... right now with disc0's kernel theres pinch zoom support with dolphin browser
Guest Squide Posted February 26, 2010 Report Posted February 26, 2010 (edited) Well overall as all of you have already noticed,liquid's touch sensitivity somehow cant compared with htc or motorolla (droid) sensitivity.Especially some days ago i had the luck to play a bit with a Nexus.I could interact with screen even if i didnt touch it!!i kept my finger like 1mm away from screen. My question is: Is that a driver or hardware issue the non good sensitivity compared with htc's android phones? I think this is related to the CPU speed. When I use 1GHz kernel, the touch screen is more sensitive. Edited February 26, 2010 by Squide
Guest Quipeace Posted February 26, 2010 Report Posted February 26, 2010 The sensitivity might be set lower to hide the flaws of a cheaper/budget screen? Like to seperate the noise from actual touch. I've made a LLP touch screen a year or so back and it required quite alot of filtering to get rid of the noise and while that is a whole different technique it does make sense right? I suppose the only way is to test it, just make sure you aren't biased.
Guest Angio Posted February 26, 2010 Report Posted February 26, 2010 does anyone know what will happen if noise is not matched with sensitivity?
Guest chingy1788 Posted February 27, 2010 Report Posted February 27, 2010 you will get random touches everywhere even though you didnt touch the screen
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now