gsl-firmware
gsl-firmware copied to clipboard
onitake
tools/fw_extractor my_android_gslx680.ko firmware.fw
my tablet onda v891w，8.9 inch，copy this /lib/modules/gslx68x_ts.ko ，isn't system/vendor/modules/，tools/fw_extractor gslx68x_ts.ko firmware.fw，not success，https://drive.google.com/open?id=0B1HDhURlGNctM3hxSF8xTE55aDA ，modules，can you help me extract firmware.fw ?
Umm... No success?
I get this:
tools/fw_extractor gslx68x_ts.ko
Found fw_index offset 100340 count 4
Found gsl_load_fw offset 63040 count 933
Found GSLX680_FW_TEST offset 62240 count 7656
Found GSLX680_FW_gsl_customer offset 69952 count 39336
Found GSLX680_FW_I81_GSL3676B_8 offset 109312 count 37224
Found GSLX680_FW_I802_GSL3676B_ offset 146560 count 36960
Found GSLX680_FW_I802_GSL3676B_ offset 183520 count 40392
Found GSLX680_FW_I100_GSL3692_1 offset 223936 count 38808
Found GSLX680_FW_I89_GSL3676B_1 offset 262752 count 37224
Found GSLX680_FW_I71_GSL1686F_1 offset 300000 count 36960
Found FW_I89_GSL3676B_19201200_ offset 455296 count 40392
Found GSLX680_FW_I86_GSL3676B_8 offset 536128 count 39336
Found gslx680_fw_grp offset 62272 count 152
All the GSLX680_FW* files look like proper firmware files. To find out which one to use, check which chip you have (you may have to open the device), then test the matching ones. The I89 may hint to the panel size, so try those first, perhaps.
Aaah, now I see your problem. The documentation is wrong. Sorry. Will fix that in a moment.
./fwtool -c FW_I89_GSL3676B_19201200_.fw -w 1920 -h 1200 -t 10 silead_ts.fw，it is correct ？ developer options，show touches，show visual feedback for touches，enable，the finger click position, touchscreen White dot ，Offset to the right，to the right side，why?
but i use chuwi hi8 's firmware.fw，convert silead_ts.fw，the finger click position, touchscreen White dot ，Offset to the left，why? it's not calibration problem，can't calibration touchscreen
please see here， https://sourceforge.net/p/android-x86/kernel/ci/3f1bd4aea203b8a1f279da53c9c24bb00df5badc/
I can't tell you if it's correct. I don't know the exact specs of your device. You need to test and find them out yourself.
Offsets or inaccessible areas are probably caused by incorrect touchscreen dimensions. These can be different from the display resolution. There is currently no reliable way to determine them, you need to do some experimentation.
If calibration using xinput_calibrator is not an option, then you need to set the correct parameters in the firmware. Use xinput test <device number> (find the number with xinput list) to see the all touch events, then move your finger around the corners a bit. This should give you an idea what the dimensions of the touchscreen are. Set those using fwtool -w <width> -h <height>.
If you don't get multitouch events, or if the axes seem to be swapped or mirrored, set the corresponding parameters using fwtool -f.
oh，no，i don't know how to do，-m -w -h ，correct parameters，oh ，no，i don't know
As I said, some experimentation is necessary.
Convert the firmware using default parameters, then test using xinput test. Once you've found out the approximate width and height of the the touch panel, set those parameters using fwtool -w <width> -h <height>. If you encounter any problems like a mirrored axis or broken multitouch, set the appropriate flag using fwtool -f <flag>.
I'm sorry if I can't help you any further.
Let's say your touchscreen is mirrored on the horizontal axis, i.e. when you touch on the left, it registers on the right and vice-versa. In this case, you would use: fwtool -f xflip
Or, you notice that multitouch does not work. In this case, you can try enabling finger tracking: fwtool -f track
If you want to combine the options, separate them by a comma: fwtool -f xflip,track
The other options are:
-f Sets flags, separated by commas (optional, supported flags: xflip, yflip, swap, track)
xflip enables horizontal flipping
yflip enables vertical flipping
swap enables axis swapping
track enables in-driver finger tracking (use for controllers that don't support it)
Each flag may be prefixed with 'no' to disable it.
Up and down，Upside down ; left right，not Upside down. how to fix ? I can't speak english，I do not proficient linux，you say fwtool -f and more，Please tell me for each terminal command，i only can install Ubuntu and Androidx86 on my tablet
Ok, I think I'm beginning to understand what your problem is. You seem to be experiencing a mirrored y axis.
Try this:
./fwtool -c FW_I89_GSL3676B_19201200_.fw -w 1920 -h 1200 -t 10 -f yflip silead_ts.fw
sudo cp silead_ts.fw /lib/firmware
Do you also need help with the driver installation?
Ah, very good.
So, just create silead_ts.fw, copy to /lib/firmware, and you should be good to go. If it doesn't work, try the same procedure with the other firmwares.
ok，already vertical flipping，but -w -h parameter still incorrect，i can't understand xinput test result.
oh，yes，-w 1920 -h 1200 -f yflip ，correct parameter，when vertical flipping later，then use calibrate touchscreen calibration，click Precision，nice
not perfect，click not Precision . I do these，in order to on Android x86 6.0.1，use touchscreen，still has problem，already use calibration app ，Quick Settings drop-down and Side slide，can't do this in order to use touchscreen do these，http://i.imgur.com/fcUALEc.png http://i.imgur.com/oKPQBWr.png
on Android x86 6.0.1，only 1 point，not 10 point，already fwtool -t 10，why ? on Ubuntu ，i don't know how many point on Android x86 6.0.1，has Small offset
This is Android x86 6.0.1，http://i.imgur.com/ZDq4PKB.png http://i.imgur.com/fcUALEc.png This is dual os 4.4.4，http://i.imgur.com/hBrmVNi.png http://i.imgur.com/KMdpGyL.png
Descriptor: 495f7600ab44ccf2f22632815fb4ad7206c5bdbd Generation: 19 Location: built-in Keyboard Type: non-alphabetic Has Vibrator: false Sources: 0x1103 ( keyboard touchscreen ) AXIS_X: source=0x1002 min=0.0 max=1919.0 flat=0.0 fuzz=0.0 resolution=0.0 AXIS_Y: source=0x1002 min=0.0 max=1199.0 flat=0.0 fuzz=0.0 resolution=0.0 AXIS_PRESSURE: source=0x1002 min=0.0 max=1.0 flat=0.0 fuzz=0.0 resolution=0.0 AXIS_SIZE: source=0x1002 min=0.0 max=1.0 flat=0.0 fuzz=0.0 resolution=0.0 AXIS_TOUCH_MAJOR: source=0x1002 min=0.0 max=2264.1555 flat=0.0 fuzz=0.0 resolution=0.0 AXIS_TOUCH_MINOR: source=0x1002 min=0.0 max=2264.1555 flat=0.0 fuzz=0.0 resolution=0.0 AXIS_TOOL_MAJOR: source=0x1002 min=0.0 max=2264.1555 flat=0.0 fuzz=0.0 resolution=0.0 AXIS_TOOL_MINOR: source=0x1002 min=0.0 max=2264.1555 flat=0.0 fuzz=0.0 resolution=0.0
Descriptor: bf3a50f04508c0299f0267030b0f364565672e93 Generation: 28 Location: built-in Keyboard Type: none Has Vibrator: false Has mic: false Sources: 0x1002 ( touchscreen ) AXIS_X: source=0x1002 min=0.0 max=1919.0 flat=0.0 fuzz=0.0 resolution=0.0 AXIS_Y: source=0x1002 min=0.0 max=1199.0 flat=0.0 fuzz=0.0 resolution=0.0 AXIS_PRESSURE: source=0x1002 min=0.0 max=1.0 flat=0.0 fuzz=0.0 resolution=0.0
Nice, at least there's some progress.
xinput test will print the coordinates of all input events. If you move your finger across the screen, especially around the edges, you will see the maxima for the pixel coordinates. That way, you should be able to determine the accurate values for -w and -h.
I don't have a working test device right now, so I can't provide you with example output. But I'll post here when I have some.
can't find correct parameters，it must be -w 1920 -h 1200，because “This is Android x86 6.0.1，http://i.imgur.com/ZDq4PKB.png http://i.imgur.com/fcUALEc.png This is dual os 4.4.4，http://i.imgur.com/hBrmVNi.png http://i.imgur.com/KMdpGyL.png ” whatever i do ，every time boot Ubuntu，must calibration touchscreen every time boot Androidx86 6.0.1，also need calibration touchscreen，but it can't，can't calibration
oh，no，The left side，not offset，the finger from left side to right side，offset bigger and bigger
If you have an offset or scaling Problem, then the -w 1920 -h 1200 is most likely NOT correct.
Try smaller values, like -w 1024 -h 600 for example. Or test using xinput test as I described above to determine the correct values.
i find my tablet SileadTouch.fw，I890_3676B_19201200_PG_WJ_WJ888_Drivers-20150604.zip，then ./fwtool -c SileadTouch.fw -3 -w 1920 -h 1200 -t 10 silead_ts.fw， Up and down，Upside down ; left right，also Upside down；how to do ? -w 1920 -h 1200 -f yflip xclip ?what terminal command ?
To enable both horizontal and vertical mirroring, use this:
./fwtool -c SileadTouch.fw -3 -w 1920 -h 1200 -t 10 -f xflip,yflip silead_ts.fw
This SileadTouch.fw has more problem，Not as good as FW_I89_GSL3676B_19201200_.fw when xflip yflip later，I can only describe，Sliding screen on the left ， display on the right ，Sliding screen on the right , display on the left . ok，Still study FW_I89_GSL3676B_19201200_.fw
FW_I89_GSL3676B_19201200_.fw，no matter what parameters，Before calibration， xinput test ， top left corner ，a[0]=20，bottom left corner ，a[0]=40 use xinput，only can get probably parameters，Inaccurate, imprecise，This is not enough；you know，The touch screen on Androidx86 is must be more accurate than the mouse，must Precise and accurate parameters，can't get. I say，can't do this ，http://i.imgur.com/oKPQBWr.png ，because parameters is Inaccurate ，imprecise
Hmm I see... But that could just mean that the firmware does not work with your chip.
Can you open your device and check if you really have a GSL3676B?
what mean ? extract gslx68x_ts.ko，get GSL3676B firmware，gslx68x_ts.ko from onda v891w dual-os Android 4.4.4，what mean “open your device” ?
I mean, you should disassemble your tablet physically and look inside what chips you have on the circuit board. Check which Silead chip you have exactly (GSL3676B, GSL2681, GSL1680, ....) to make sure you use the correct firmware.
yes，onda v891w，gsl 3676，Disassemble is my hobby，Just bought，first to do disassemble like this， http://i3.bbs.fd.zol-img.com.cn/t_s800x5000/g2/M00/0E/04/Cg-4WVWuCTqISLsCAAIWZNEp7FUAAHclAOOEHwAAhZ8023.jpg http://bbs.zol.com.cn/quanzi/d26_795_uid_a757338903.html
also like this，http://bbs.mydigit.cn/read.php?tid=1107465
Ok, ok. Very good! :)
If you use the wrong firmware for the chip, you will get very strange results. Inaccuracy is normal, however. The chip sends out touch events without much interpolation, and gslx680-acpi doesn't interpolate either. I know that this leads to all kinds of problems, but I assumed that user space would handle this better. Unfortunately, that's not the case.
My test environment is Ubuntu 15.10, where basic stuff like touching buttons and typing work more or less, but dragging is a big problem, and I had lots of reliability problems close to the edges.
Unfortunately, I don't know a good way to solve these.
If you need a quicker solution, better try this driver here: https://github.com/rastersoft/gsl1680 It uses the FW_I89_GSL3676B_19201200_.fw firmware directly (no need to convert with fwtool), but runs in user space and requires some manual setup for the GPIO pins.
offset 109312 count 37224 offset 146560 count 36960 offset 183520 count 40392 offset 223936 count 38808 offset 262752 count 37224 offset 300000 count 36960 offset 455296 count 40392 offset 536128 count 39336 what mean ?
Found <n> offset <x> count <y>
That means it found a firmware image at file offset <x>, of length <y> bytes. The firmware will then be written out to <n>.fw.
Found FW_I89_GSL3676B_19201200_ offset 455296 count 40392， ./fwtool -c FW_I89_GSL3676B_19201200_.fw -w ？ -h ？，Is there any relationship between the two?
I don't know, really.
The only known fact is that the limit for -w and -h is 4095, because they're 12 bit values. Other than that - unknown...
https://github.com/sigboe/gslX68X ， “You will need to place a firmware file at /lib/firmware/[hid].fw where you replace [hid] with the HID ID of your device.” ，I can't understand
Yes, that part is a bit unfortunate. [HID] is the ACPI or DT ID of the device.
In most cases, this is mssl1680, but you'll have to check.
See my comment on https://github.com/sigboe/gslX68X/issues/3 for more info.
Please don't mix up the drivers.
gslx680_ts_acpi.ko (from gslx680-acpi) needs silead_ts.fw created with fwtool.
silead.ko (from gslX68X) needs the firmware directly as it comes out of fw_extractor, and you need to rename it to [hid].fw, where [hid] is usually mssl1680. If mssl1680.fw does not work, look at the dmesg output. It will tell you which file it's expecting.
https://github.com/rastersoft/gsl1680 ，how to launch the driver ?
gslx680_ts_acpi.ko and silead_ts.fw，only one point，can't Multi-touch；OK，I don't ask for more，Then basic Double finger zoom，I want this.
If only touch it at one point, then need track flag when you are generating firmware for gslx680_ts_acpi.ko.
as superuser (linux normally sudo or su)
modprobe gslx680_ts_acpi
if the module is installed correctly than it would load
during our discussion on android-x86 i would say you shall open the terminal app
type in su to get super user permissions and type in the command (modprobe....)
tanks for the tip with flag to get multitouch working will try it also on my side
regards Mario
I can't speak english，I do not proficient linux，you say fwtool more，Please tell me for each terminal command，i only can install Ubuntu and Androidx86 on my tablet，，barni2000
Linux:
sudo modprobe gslx680_ts_acpi
Android: terminal app
su
modprobe gslx680_ts_acpi
holzingerm ， I know who are you，The basic load drive command, I knew ；now the problem，Double finger zoom，xposed GravityBox [MM] pie control……
Something like this: ./fwtool -c SileadTouch.fw -3 -w 1920 -h 1200 -t 10 -f xflip,yflip,track silead_ts.fw
is the -3 really correct?? i try to help youling257 but with android drivers I need to convert the android drivers like
./fwtool -c GSLX680_FW_I81_GSL3676B_8.fw -1 -m 3676 -h 1920 -w 1200 -t 10 -f xflip,yflip,track silead_ts.fw
to get a valid output
use xinput，only can get probably parameters，Inaccurate, imprecise，This is not enough；you know，The touch screen on Androidx86 is must be more accurate than the mouse，must Precise and accurate parameters，can't get. I say，can't do this ，http://i.imgur.com/oKPQBWr.png ，because parameters is Inaccurate ，imprecise
i can tell your these，repeat
my tablet，onda v891w 32GB，single Windows 8.1，copy This file，/Windows/system32/drive/SileadTouch.fw，then ./fwtool -c SileadTouch.fw -3 -w 1920 -h 1200 -t 10 -f yflip,track silead_ts.fw，This silead_ts.fw ./fwtool -c FW_I89_GSL3676B_19201200_.fw -w 1920 -h 1200 -t 10 -f yflip,track silead_ts.fw ， Two silead_ts.fw, the same problem, the same effect
using screen resolution on my tablet for fwtool needs also a calibration that is far away from beeinng perfect
today I played around with width and high valuses to get gslx working without calibration now the accuracy is near perfect also on the edges for swipe in commands let us play with these value
on my side when the value is to large the touch input is slower than the real finger ==> reduce the value when the touch input is faster ==> increase the value
on my Trekstor tablet wit 1024x600 screen resolution I need to mad the values to 900x640 to work best
gslx680_ts_acpi.ko and silead_ts.fw，Basic click、long press、up and down around the slide，can do this，I Have to say，No practical significance . I need Sliding edge， Double finger zoom. gslx680_ts_acpi.ko and silead_ts.fw ，Not as good as with the mouse.
holzingerm，please add https://github.com/rastersoft/gsl1680 https://github.com/sigboe/gslX68X to https://sourceforge.net/p/android-x86/kernel/ci/kernel-4.4/tree/ ，test these on Androidx86
sorry but I'm only a little user not an admin of android-x86. :-D
I got some hardware and try to get it work by combining solutions from others like this acpi driver. only sometimes I try to adopt simple code fraqments for my situation.
staging 2016-01-27 Mario Holzinger Mario Holzinger [81c4f1] staging: add GSLx680 I2C touch controller，like this，add gsl1680、gslx68x to Androidx86 kernel 4.4 tree.
let us first create a working firmware file for you and after that I will try to write an patch for android-x86 to push the correct firmware file depending on the device code to the kernel module
so from your comments I see that you get the driver working also the directions shall work so far, am I right only the accuracy is bad for booth touch axes
-3 is for Windows driver firmware. -1 is for firmware extracted from Android drivers using fw_extractor.
silead.ko does not support software finger tracking, so if you have a chip/firmware that doesn't do finger tracking by itself, you can't use silead.ko.
thanks, to all
@onitake I know because I use a windows driver as base for my GSL1680 chip but I want to help youling and terefor I extracted everithing from the android driver like you did at the beginning and give him some hints how to get a valid firmware file
on my side I rplaced my firmware with an version with finger tracking and it is working as expected. :-)
./fwtool -c SileadTouch.fw -3 -w 1920 -h 1200 -t 10 -f yflip,track silead_ts.fw ./fwtool -c FW_I89_GSL3676B_19201200_.fw -w 1920 -h 1200 -t 10 -f yflip,track silead_ts.fw OK，enable multi touch，can Double finger zoom now，can't do xposed GravityBox [MM] pie control，need Precise and accurate -w -h parameters ，isn't calibration problem.
so again how is the touch controller responding to your input when tip on the left top corner (0,0 position) the accuracy should be fine when tip on the right bottom corner (approx. 1920,1200 position) wher is the respond?
is it mor in the center of the screen then the finger input or did you reach the the screen corner when you tip at the center of the screen.
this information will help to adjust the values for fwtool
no matter what parameters，Before calibration， xinput test ， top left corner ，a[0]=20，probably，bottom left corner ，a[0]=40，probably
-w 1920，-h 1200，xinput test，Win button，a[0]=1696，a[1]=592； -w 1696，-h 1184，xinput test，Win button，a[0]=1696，a[1]=576； http://g02.a.alicdn.com/kf/HTB10neVLXXXXXbaXXXXq6xXFXXX9/Original-New-for-ONDA-V891w-9-inch-Capacitive-Touch-Screen-FPCA-89A05-v02-glass-External-screen.jpg_640x640.jpg win button is a part of the touch screen.
Finger on the edge，http://i.imgur.com/KUtnGMH.png ，this is dual-os Android 4.4.4 Finger on the edge，http://i.imgur.com/yGJyBCh.png ，landscape screen，gslx680_ts_acpi.ko and silead_ts.fw ；left ，right ，http://imgur.com/a/zaXny ，portrait screen，Looks like the touch screen and the display, the physical installation of crooked，physical offset，look like developer options，show touches，show visual feedback for touches，enable
I recently found out that input_set_abs_params() (which is what the -w and -h parameters are fed into) does not actually calibrate anything, it merely specifies the expected limits for the axis. You still need to calibrate the range with xinput_calibrator or corresponding Android tools.
Since there's an apparent problem with accuracy, I'm going to increase the fuzz parameter a bit and see if it improves.
Hi youling257!
I think by slightly reduce/decrease your values the behaviour can be improved: 1200 ==> ~1100 1920 ==> ~1900 and check again
./fwtool -c GSLX680_FW_I81_GSL3676B_8.fw -1 -m 3676 -h 1900 -w 1100 -t 10 -f xflip,yflip,track silead_ts.fw
BTW: I'm not sure if you are really using this Android firmwaree as base. :-)
The Windows firmware command would be
./fwtool -c SileadTouch.fw -3 -m 3676 -h 1900 -w 1100 -t 10 -f xflip,yflip,track silead_ts.fw
holzingerm ，Please don't guess the parameters, need precise calculation，This issues 13 days ago，still don't know Precise and accurate parameters .
holzingerm，https://github.com/onitake/gslx680-acpi ，has update ； how to update Android x86 kernel 4.4 tree ? https://sourceforge.net/p/android-x86/kernel/ci/81c4f10d67b016285762efc343aa8ee6736cc395/ I downloaded kernel 4.4 tree，how to update? copy new gslx680_ts_acpi.c to kernel 4.4 tree 's /drivers/staging/gslx680，replace old gslx680_ts_acpi.c ，？？？
Yes, I'm working on the code of gslx680-acpi at the moment. There are still issues, but it's working a bit better now.
As far as I can tell, getting precise parameters is impossible. There is no documentation, and I haven't found anything in the firmware that gives a clue. If guessing the values through try and error is not good enough, you have to ask Silead...
how to Cross compiler gslx680_ts_acpi.ko ？ make ARCH=x86 CROSS_COMPILE=i686-linux-android- ？
I added CROSS_COMPILE and ARCH flags to the Makefile, but never tested them. ARCH should be i386 for 32 bit or x86_64 64 bit Intel, respectively.
copy new gslx680_ts_acpi.c to kernel 4.4 tree 's /drivers/staging/gslx680，replace old gslx680_ts_acpi.c ，then
root@youling257-ONDA-Tablet:/home/youling257/desktop/i686-linux-android-4.7-master# export ARCH=x86 root@youling257-ONDA-Tablet:/home/youling257/desktop/i686-linux-android-4.7-master# export SUBARCH=x86 root@youling257-ONDA-Tablet:/home/youling257/desktop/i686-linux-android-4.7-master# export PATH=~/desktop/i686-linux-android-4.7-master/bin:$PATH root@youling257-ONDA-Tablet:/home/youling257/desktop/i686-linux-android-4.7-master# export CROSS_COMPILE=i686-linux-android- root@youling257-ONDA-Tablet:/home/youling257/desktop/i686-linux-android-4.7-master#
root@youling257-ONDA-Tablet:/home/youling257/desktop/android-x86-kernel-d492a48442a e0e068d8749f7c2ab828806c6c298# make android-x86_defconfig root@youling257-ONDA-Tablet:/home/youling257/desktop/android-x86-kernel-d492a48442a e0e068d8749f7c2ab828806c6c298# make root@youling257-ONDA-Tablet:/home/youling257/desktop/android-x86-kernel-d492a48442a e0e068d8749f7c2ab828806c6c298# make targz-pkg -i
This is recompile Androidx86 kernel 4.4 tree，but I want to Cross compiler gslx680_ts_acpi.ko ，how to do ?
Sorry, that should be KSRC, not KDIR. KSRC is the directory with the kernel source or kernel headers for the target system.
Edit: Updated the README.
Can you explain or show graphically what exactly you mean with Sliding edge?
If it is what I think it is, try lowering the -w and -h values. According to https://www.kernel.org/doc/Documentation/input/input-programming.txt the maximum should always be equal to or below the maximum value the hardware can deliver. See what you get with xinput test when you slide off the edge and set the -w and -h to the lowest value.
My tablet showed values between 939 and 950 when I moved off the right edge (see some example output below), so I set -w to 939. After calibration with xinput_calibrator, this seems to give very good results.
button press 1 a[0]=939 a[1]=479
motion a[0]=940 a[1]=479
motion a[0]=939 a[1]=479
motion a[0]=939 a[1]=479
motion a[0]=941 a[1]=479
motion a[0]=939 a[1]=479
motion a[0]=939 a[1]=479
button release 1 a[0]=939 a[1]=479
Side slide、Sliding edge ，example， Androidx86 xposed GravityBox [MM] pie control Ubuntu、Windows and other linux，needn't touchscreen，needn't Sliding edge developer options，show touches，show visual feedback for touches，enable. From the beginning, the discussion is Androidx86 touchscreen problem Finger on the edge，should be this，http://i.imgur.com/KUtnGMH.png ，Half white spots
please you create https://github.com/onitake/gsl-firmware/tree/master/firmware/onda/v891w ， Android firmware FW_I89_GSL3676B_19201200_.fw ， ./fwtool -c FW_I89_GSL3676B_19201200_.fw -w 1665 -h 1140 -t 10 -f yflip,track silead_ts.fw I didn't test it, I have deleted ubuntu on my tablet.
Firmware is up: https://github.com/onitake/gsl-firmware/tree/master/firmware/onda/v891w I have marked it as untested. If you can test it on your device and get good results, please notify me and I'll update the readme.
hi i have clone tablet, hardware is the same as the Onda V891w, change resolution 1200x800. I,m running remix os. How can i identify model touchscreen?
@Salvat0res ，the new remix os for pc，has gslx680_ts_acpi.ko，now，you need suited silead_ts.fw you must install Ubuntu on you tablet，copy Windows/system32/drive/SileadTouch.fw this file，use ./fwtool -c SileadTouch.fw -3 ………… may be need xflip，or yflip，or track，You can only own tuning parameters . what you tablet ?
@onitake ，my tablet，-w 1620，-h 1140，suited ；-w 1620，on Android ，right edge，has Half white spots，but left edge，will offset little area . in order to Sliding right edge，left edge never mind，doesn't matter
My tablet is that https://www.energysistem.com/es/products/tablet/serie_tablet__windows/39903-energy_tablet_10_1%22_pro_windows
No disassemble. if there is any way of knowing without unmounting? Intel bay-trail Z3735 as chuwi. Thanks for your answer
Hi, first step would be to check windows hardware manager. Search for input HID devices (Human Interface Devices) if you find your Touchcontroller. Properties==>Details==>Hardware IDs
In my case I find a KMFD HID Minidriver for Touch I2C Devices. HW-ID a line with MSSL1680
This told me that I have a GSL1680 touch controller. Am 28.03.2016 9:00 vorm. schrieb "Salvat0res" [email protected]:
No disassemble. if there is any way of knowing without unmounting? Intel bay-trail Z3735 as chuwi. Thanks for your answer
— You are receiving this because you commented. Reply to this email directly or view it on GitHub https://github.com/onitake/gsl-firmware/issues/6#issuecomment-202269929
@youling257 I have generated silead_ts.fw using the -w and -h parameters you gave me, should I change them? Which are the best values for you?
About the left offset, I'm going to add xmin and ymin parameters so you can specify the left and top start coordinates. This should help a lot of people.
now，I use -w 1625 -h 1135 ，left edge offset no matter what parameters， xinput test ， top left corner ，a[0]=27，probably，bottom left corner ，a[0]=43，probably；top left corner ，can't 0,0 -h 1150 ，top right corner，a[1]=14，bottom right corner，a[1]=1136 -h 1140 ，a[1]=3， -h 1135 ，top right corner，a[0]=0，bottom right corner，a[1]=1122 -h 1000，a[0]=0，a[1]=986 -h 500， a[0]=0，a[1]=488
sliding finger From the left bottom ，right bottom，center bottom，left edge，right edge http://imgur.com/a/KAP16