TechTablets › Forums › Teclast Forums › X16 Pro / X16 Power Forum › Try my touchscreen fix
- This topic has 23 replies, 1 voice, and was last updated 3 years, 5 months ago by Bananaman.
-
AuthorPosts
-
January 28, 2016 at 6:34 pm #24168
Like others, I HATE the slow response on the X16 touchscreen. It made it very difficult to use the on-screen keyboard among other things.
I finally gave up fighting with GearBest (won’t be ordering from them again) and dug into the spec sheet for the touchscreen hardware.
For some reason the “debounce” parameter was set to 2, whereas on all the other configurations I could find, it was set to 1. The touch filter was also set very high (maybe something to do with the weird multi-touch behavior when plugged in?).
ANYWAY…..
I created a new config string to put into C:\WINDOWS\INF\touchsetting.gt , it made a huge difference in mine, try it out and see if it fixes yours. The file is attached to this posting, but you really only need to change 3 values, and I’ve detailed them below along with my entire config string.
I only changed values 9 (debounce) and 10 (filter) to 0x01 and 0x03 respectively. The next to last value is the CheckSum, and it needs to be changed to 0x76 for the hardware to take the new config string.
You must reboot after changing the config file for it to take effect.
****MAKE SURE YOU HAVE AN EXTERNAL KB/MOUSE HANDY, THE TOUCHSCREEN WILL BECOME INOPERATIVE IF IT DOES NOT ACCEPT THE NEW CONFIG****
There is a chance that it is TOO sensitive with those settings, so if you want to experiment with your own values, the checksum is an offset. So lets say you increase the filter value by 2, then you need to reduce the checksum value by 2.
The datasheet is in Chinese, but it is here: http://www.wpgholdings.com/uploads/bu/bu_3/MID_20141112/GT9110P_Datasheet_20130731.pdf
DefaultCFG=0x00,0x80,0x07,0x38,0x04,0x0A,0x7D,0x41,0x01,0x03,0x50,0x0F,0x41,0x32,0x03,0x01,0x00,0x00,0x00,0x00,0x00,0x00,0x04,0x18,0x1A,0x1E,0x14,0x95,0x15,0xFF,0x17,0x15,0xA6,0x22,0x00,0x00,0x00,0x84,0x03,0x1D,0x00,0x00,0x00,0x80,0x82,0x02,0x1E,0x23,0x14,0x0F,0x00,0x0F,0x23,0x94,0xC5,0x02,0x07,0x00,0x00,0x04,0xA0,0x10,0x00,0x8F,0x13,0x00,0x83,0x16,0x00,0x75,0x1B,0x00,0x6D,0x20,0x00,0x6D,0xF0,0x00,0x00,0x00,0x23,0xF0,0xB0,0xFF,0xFF,0x27,0x00,0x00,0x00,0x0F,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x1D,0x1C,0x1B,0x1A,0x19,0x18,0x17,0x16,0x15,0x14,0x13,0x12,0x11,0x10,0x0F,0x0E,0x0D,0x0C,0x0B,0x0A,0x09,0x08,0x07,0x06,0x05,0x04,0x03,0x02,0x01,0x00,0x01,0x02,0x03,0x04,0x05,0x06,0x07,0x08,0x09,0x0A,0x0B,0x0C,0x0D,0x0E,0x0F,0x10,0x11,0x12,0x13,0x14,0x15,0x16,0x17,0x18,0x19,0x1B,0x1C,0x1D,0x1E,0x1F,0x20,0x21,0x22,0x23,0x24,0x25,0x26,0x27,0x28,0x29,0x2A,0x00,0x76,0x01
Attachments:
You must be logged in to view attached files.January 29, 2016 at 7:14 am #24214I’ve always noticed the delay more obvious on the Android side, and only a little slow on the Windows. I’m typing this right now after loading your touch file and I must say the keyboard is definitely keeping up!
Good work
January 29, 2016 at 11:24 am #24234Wow,
Oh my god, what a difference, its almost perfect. possibly just a minor tweak. I knew it was software related. I was going to throw the tablet, cos whoever owns it knows the lag touch in unbearable you cannot even play games on it.
Now we need the same fix for android, we fix android and this touch plague and this tablet will rock.
Ps there is the back camera issue that everybody knows about but nobody mentions. But the priority is the touch and now it is almost perfect in windows and it needs fixing in android.
Jesus why do teclast not update the firmware, i thought it was a serious company like xioami but it turns out to be a crappy company. They should give the source so at least smart ppl can do custom roms.
Thanks Philip cline
January 29, 2016 at 12:49 pm #24279Absolutely awesome, i’ll your fix on my XDA thread (with credits of course). Thank you for your contribution.
-----------
XDA-Developers Forum: https://forum.xda-developers.com/member.php?u=2386505January 29, 2016 at 1:52 pm #24295I’m happy to hear that it’s working for other people!
I’m afraid that the first thing that I did when I got mine was to wipe out the Android partition and reload Win10. I don’t think I even booted into Android on the X16. I have two other Android tablets and I just never use them. It isn’t a firmware issue. You could maybe call it a driver issue. It’s just a config string that is sent to the hardware after the drivers load. I’ve done a little programming for Android, but I’ve never worked with the drivers. I’m almost certain it would be an easy fix for the Android side. That is assuming that the config file is easy to access and not compiled into something else. When you find it, the config string will follow the same format since that’s the only way the chip will accept it.
Pang, what minor tweak would you suggest?
January 29, 2016 at 2:09 pm #24299I don’t want to sound picky, I am happy how it is its 99.9% perfect which has made my day. You have made my day.
If only we can fix the android site and that pesky back camera. I think you also have a problem with the back camera.
Ps.
Can you make an easy to follow tutorial even on youtube video on how to install windows 10 only from scratch. There are other tutorials but not as detailed and they always have steps missing. A comprehensive tutorial would be great. I will get another tablet for android. PS did you check if the tablet throttles if you stress it. Since i heard in android cpu keeps cool but in windows for some unknown reason it does not?
Super thanks again, and i believe I am speaking for all owners of a teclast x16
This is a super tablet that unfortunately the supplies don’t make good firm wares for
January 29, 2016 at 3:53 pm #24308OK, here is another update if you’d like to try it. I’ve set the filtering to a minimum and increased the touch sensitivity a little. I was afraid the filters were set high to compensate for some shortcomings in the hardware, but mine appears to work fine this way.
Attachments:
You must be logged in to view attached files.January 29, 2016 at 6:20 pm #24317Could a mod remove that first file link?
I’ve been using the 2nd version for most of the day and it is definitely better than what I put in my first post.
January 29, 2016 at 8:38 pm #24343Great work!
January 30, 2016 at 9:42 pm #24496nice touch is very much responsive now. thanks
January 31, 2016 at 1:32 pm #24541AnonymousInactive- Posts: 23
Could a mod remove that first file link? I’ve been using the 2nd version for most of the day and it is definitely better than what I put in my first post.
Great work man, I had always figured it was a driver/software problem in Windows because I found the Android on screen keyboard to be comparatively fantastic compared to the incredibly useless windows onscreen touch keyboard setup.
I my self am a tad surprised to see some not happy with the Android keyboard setup as well..
January 31, 2016 at 4:49 pm #24561good job just amazing
February 21, 2016 at 9:14 pm #26626thanks for brain storming this issue like noone did so far! I just cut paste the old file in a back up folder in case and replaced it by yours edited and it’s definitely efficient! definitely more precise and responsive also i noticed that the stylus is more fluid and smooth on photoshop!
in adnroid it will be more tricky i guess but i hope we can find a way for this fix there too
life's an hologram of life's an hologram of life's an hologram of life's an hologram of life's an hologram of life's an hologram of life's an hologram of life.
February 21, 2016 at 9:25 pm #26629and now i tried the second version and it’s jsut perfect in all sketchup application, thank you very much Phil!
life's an hologram of life's an hologram of life's an hologram of life's an hologram of life's an hologram of life's an hologram of life's an hologram of life.
February 21, 2016 at 11:17 pm #26643tried it, what a huge difference!I love it! Great work! Thank you!
-
AuthorPosts
- You must be logged in to reply to this topic.