Author Topic: Touchscreen driver for A13B  (Read 45585 times)

0 Members and 1 Guest are viewing this topic.

Offline nyioo7

  • Jr. Member
  • **
  • Thank You
  • -Given: 15
  • -Received: 51
  • Posts: 69
  • Karma: +54/-0
  • Uber-Noobie
  • Tablet / Size / Model: A13 7" Allwinner
Touchscreen driver for A13B
« on: October 26, 2012, 02:18:48 AM »
While I was comparing the codes in boot.img, I saw something weird that is making my touchscreen works but top and bottom reversed. Touchscreen drivers are all commented out. So, is it not there or how is it working? I checked all the other *.rc files. There's no call to touchscreen driver anywhere. Any idea?

Here's the code from init.sun5i.rc that works in reverse on my tablet.

Code: [Select]
on boot
chmod 0777 /sys/class/misc/sunxi-reg/rw/value
chmod 0777 /sys/class/misc/sunxi-reg/rw/address
#insmod key & tp driver
#insmod /system/vendor/modules/sun4i-ts.ko
#insmod /system/vendor/modules/ft5x_ts.ko

#insmod mali driver
insmod /system/vendor/modules/ump.ko
insmod /system/vendor/modules/mali.ko

#szg_start
insmod /suzhiguo.ko

#szg_end
    #insmod video driver
    insmod /system/vendor/modules/cedarx.ko

    # insmod vibrator
#    insmod /system/vendor/modules/sun4i-vibrator.ko
#    chmod 777 /sys/class/timed_output/sun4i-vibrator/enable
#csi module
#insmod /system/vendor/modules/videobuf-core.ko
#insmod /system/vendor/modules/videobuf-dma-contig.ko
#insmod /system/vendor/modules/gc0308.ko
#insmod /system/vendor/modules/sp0838.ko
#insmod /system/vendor/modules/sun5i_csi0.ko

#network module
insmod /system/vendor/modules/usbnet.ko
insmod /system/vendor/modules/asix.ko
insmod /system/vendor/modules/qf9700.ko
insmod /system/vendor/modules/mcs7830.ko
insmod /system/vendor/modules/rtl8150.ko
#insmod gsensor driver
insmod /system/vendor/modules/mecs.ko
    insmod /system/vendor/modules/mxc622x.ko
    chmod 777 /system/bin/memsicd
    mkdir /data/misc/sensors 0777 system system


# usb tether function
    insmod /system/vendor/modules/cdc_ether.ko
insmod /system/vendor/modules/cdc_eem.ko
insmod /system/vendor/modules/cdc_subset.ko

EDIT: Also, gsensor works perfectly when I comment out this code??? What???

Code: [Select]
#insmod gsensor driver
insmod /system/vendor/modules/mecs.ko
    insmod /system/vendor/modules/mxc622x.ko
    chmod 777 /system/bin/memsicd
    mkdir /data/misc/sensors 0777 system system

EDIT: Ok. Never mind. I found it at the bottom. G-sensor for my tablet is using mc32x0.ko driver.
« Last Edit: October 26, 2012, 02:27:27 AM by nyioo7 »

Offline satcomranger

  • Administrator
  • Uber Member
  • *****
  • Thank You
  • -Given: 299
  • -Received: 4467
  • Posts: 16498
  • Karma: +4921/-52
  • I'm old - But still Learning
  • Tablet / Size / Model: VIA WM8650/ 7" / Option 8 / MID-703
Re: Touchscreen driver for A13B
« Reply #1 on: October 26, 2012, 02:44:38 AM »
I have seen this once before .. matter a fact i asked one of the moderators if they knw what insmod /suzhiguo.ko was .. as it doesnt look like a normal driver name ..

these two lined only show up on VERY few tablets 2 so far that i have seen ..

   chmod 0777 /sys/class/misc/sunxi-reg/rw/value
   chmod 0777 /sys/class/misc/sunxi-reg/rw/address

so i am very curious as to what they do .. just havent had a chance to run this down .. you see how they do these things ..  it is almost like they use one file and then comments out what they dont need .. the two you see commented out are a pair of drivers that go together I think .. 


 
Tab 1-Via WM8650 Option 8,Green Power/Red Charge, Black Audio - Vibrate No - 2 Point Touch Uberoid V12B2
Tab 2-Flytouch 3/Superpad 3 - Axlien (Based on Tim4e)
Tab 3-Dell Streak 7 Wifi Stock Honeycomb 3.2
Tab 4-M799CA V2.0 Running TKT3.2A
Retired Electronics Tech / Network Engineer

Offline nyioo7

  • Jr. Member
  • **
  • Thank You
  • -Given: 15
  • -Received: 51
  • Posts: 69
  • Karma: +54/-0
  • Uber-Noobie
  • Tablet / Size / Model: A13 7" Allwinner
Re: Touchscreen driver for A13B
« Reply #2 on: October 26, 2012, 02:50:50 AM »
   chmod 0777 /sys/class/misc/sunxi-reg/rw/value
   chmod 0777 /sys/class/misc/sunxi-reg/rw/address

These two lines are giving full read/write permission to value and address location. But it doesn't seem to be doing anything in those folders. Nothing is being written or removed.

The weird thing is, I have two different ROMs that works touchscreen on my tablet. One works top and bottom flip and one works left and right flip. But they are both using the same init.sun5i.rc. They are both exact copy of each other. I don't understand where it is being called now.

Also, that suzhiguo.ko is in root folder. Not in the modules. So, that definitely is strange. Is there any documentation about this? I can't seem to find one tho.

Offline satcomranger

  • Administrator
  • Uber Member
  • *****
  • Thank You
  • -Given: 299
  • -Received: 4467
  • Posts: 16498
  • Karma: +4921/-52
  • I'm old - But still Learning
  • Tablet / Size / Model: VIA WM8650/ 7" / Option 8 / MID-703
Re: Touchscreen driver for A13B
« Reply #3 on: October 26, 2012, 02:56:27 AM »
   chmod 0777 /sys/class/misc/sunxi-reg/rw/value
   chmod 0777 /sys/class/misc/sunxi-reg/rw/address

These two lines are giving full read/write permission to value and address location. But it doesn't seem to be doing anything in those folders. Nothing is being written or removed.

The weird thing is, I have two different ROMs that works touchscreen on my tablet. One works top and bottom flip and one works left and right flip. But they are both using the same init.sun5i.rc. They are both exact copy of each other. I don't understand where it is being called now.

Also, that suzhiguo.ko is in root folder. Not in the modules. So, that definitely is strange. Is there any documentation about this? I can't seem to find one tho.

I wonder if the calls are coming out of the bootloader?  Have you looked at the script.bin and script0.bin? ..  maybe look in every darned  file that has   int.       and ends in .rc .. who know with the tablets ..
and i have no idea about that file .. is there any game or anyhting like that with the name ?  I couldnt find anything either ..
Tab 1-Via WM8650 Option 8,Green Power/Red Charge, Black Audio - Vibrate No - 2 Point Touch Uberoid V12B2
Tab 2-Flytouch 3/Superpad 3 - Axlien (Based on Tim4e)
Tab 3-Dell Streak 7 Wifi Stock Honeycomb 3.2
Tab 4-M799CA V2.0 Running TKT3.2A
Retired Electronics Tech / Network Engineer

Offline nyioo7

  • Jr. Member
  • **
  • Thank You
  • -Given: 15
  • -Received: 51
  • Posts: 69
  • Karma: +54/-0
  • Uber-Noobie
  • Tablet / Size / Model: A13 7" Allwinner
Re: Touchscreen driver for A13B
« Reply #4 on: October 26, 2012, 03:03:23 AM »
Haha. That's pretty much what I'm doing. Going through line by line on every *.rc files.

No. I haven't seen any game or anything so far. I'm gonna look at script.bin and script0.bin. There's gotta be a reason for using chmod to those locations.

I was checking this one ROM I found of A13B ICS 4.0.4, model : JSA_MID, and that code is even more sloppy. They were calling drivers without any comments and it's all over the place. Weird thing is, it seems to be working fine on my tablet except there's no touchscreen. I can't find anything on that because it's poorly commented. I guess someone sat at home with source code and started changing thing before going to sleep and selling them the next day on ebay.  :android-lol:

Offline satcomranger

  • Administrator
  • Uber Member
  • *****
  • Thank You
  • -Given: 299
  • -Received: 4467
  • Posts: 16498
  • Karma: +4921/-52
  • I'm old - But still Learning
  • Tablet / Size / Model: VIA WM8650/ 7" / Option 8 / MID-703
Re: Touchscreen driver for A13B
« Reply #5 on: October 26, 2012, 03:06:08 AM »
Haha. That's pretty much what I'm doing. Going through line by line on every *.rc files.

No. I haven't seen any game or anything so far. I'm gonna look at script.bin and script0.bin. There's gotta be a reason for using chmod to those locations.

I was checking this one ROM I found of A13B ICS 4.0.4, model : JSA_MID, and that code is even more sloppy. They were calling drivers without any comments and it's all over the place. Weird thing is, it seems to be working fine on my tablet except there's no touchscreen. I can't find anything on that because it's poorly commented. I guess someone sat at home with source code and started changing thing before going to sleep and selling them the next day on ebay.  :android-lol:

noo  you are almost correct  "home with the source code  and started changing things WHILE they were sleeping and sold them the next day ................too funny !
Tab 1-Via WM8650 Option 8,Green Power/Red Charge, Black Audio - Vibrate No - 2 Point Touch Uberoid V12B2
Tab 2-Flytouch 3/Superpad 3 - Axlien (Based on Tim4e)
Tab 3-Dell Streak 7 Wifi Stock Honeycomb 3.2
Tab 4-M799CA V2.0 Running TKT3.2A
Retired Electronics Tech / Network Engineer

Offline nyioo7

  • Jr. Member
  • **
  • Thank You
  • -Given: 15
  • -Received: 51
  • Posts: 69
  • Karma: +54/-0
  • Uber-Noobie
  • Tablet / Size / Model: A13 7" Allwinner
Re: Touchscreen driver for A13B
« Reply #6 on: October 26, 2012, 03:08:00 AM »
Only if we can have access to the documentations that these cloners have about the devices .........

Offline nyioo7

  • Jr. Member
  • **
  • Thank You
  • -Given: 15
  • -Received: 51
  • Posts: 69
  • Karma: +54/-0
  • Uber-Noobie
  • Tablet / Size / Model: A13 7" Allwinner
Re: Touchscreen driver for A13B
« Reply #7 on: October 26, 2012, 05:51:24 AM »
Ok. So, I don't understand those values inside the binary files. I see the hardware configuration but they are in values. Any knowledge of them? Like for LCD, what values are for what? I'm guessing that script.bin and script0.bin are just to load up the bootloader such as, giving the power to parts of the device and keeping it in check. After it's loaded, kernel takes over. Kernel loads the drivers from root and follow by loading the ROM. I can't however get into zImage. For some reason, I'm getting just one file called "sizes" that is only 18 bytes. I think something's wrong with the unpacking.

Offline nyioo7

  • Jr. Member
  • **
  • Thank You
  • -Given: 15
  • -Received: 51
  • Posts: 69
  • Karma: +54/-0
  • Uber-Noobie
  • Tablet / Size / Model: A13 7" Allwinner
Re: Touchscreen driver for A13B
« Reply #8 on: October 26, 2012, 06:12:38 AM »
Still have no clue about touchscreen but here are the parameters for working gsensor vs not working gsensor. On my tablet of course.

Working gsensor
Code: [Select]
[gsensor_para]
gsensor_used = 1
gsensor_name = "mc32x0"
gsensor_twi_id = 1
gsensor_twi_addr = 0x4c
gsensor_int1 =
gsensor_int2 =

Not working gsensor
Code: [Select]
[gsensor_para]
gsensor_used = 1
gsensor_name = "mxc622x"
gsensor_twi_id = 2
gsensor_twi_addr = 0x15
gsensor_int1 =
gsensor_int2 =

The difference is the id and the address. This means that the setup of the hardware and their pin assignments are different? This is still trying to find a needle in the haystack........

Offline nyioo7

  • Jr. Member
  • **
  • Thank You
  • -Given: 15
  • -Received: 51
  • Posts: 69
  • Karma: +54/-0
  • Uber-Noobie
  • Tablet / Size / Model: A13 7" Allwinner
Re: Touchscreen driver for A13B
« Reply #9 on: October 26, 2012, 07:31:07 AM »
Ok. So, script.bin also control the position of the display. Mine got shifted a bit while messing around.

Code: [Select]
[ctp_para]
ctp_used = 1
ctp_name = "elan_ts"
ctp_twi_id = 1
ctp_twi_addr = 0x15
ctp_screen_max_x = 800
ctp_screen_max_y = 480
ctp_revert_x_flag = 0   <-------------------------------
ctp_revert_y_flag = 0   <-------------------------------
ctp_exchange_x_y_flag = 0
ctp_int_port = port:PG11<6><default><default><default>
ctp_reset = port:PB03<1><default><default><1>
ctp_io_port = port:PG11<0><default><default><default>

This is where it shift the position. So, if anyone got working touchscreen with shifted screen, it can be fixed easily.
« Last Edit: October 26, 2012, 07:40:21 AM by nyioo7 »

Offline HardcoreHacker

  • Administrator
  • Uber Member
  • *****
  • Thank You
  • -Given: 6619
  • -Received: 1968
  • Posts: 8145
  • Karma: +3000/-99
Re: Touchscreen driver for A13B
« Reply #10 on: October 26, 2012, 11:42:26 AM »
Hey nyioo7,

this is a very interesting observation! so the script bin handles a lot of ts related settings/values. Maybe you also have the problem that the TS isn't 100%, like my model here has problems detecting my presses on the edges. I use a ts test app to see where the ts is able to track my presses, on the top for example it's not fully able to detect presses. Maybe we can fix this by altering the script.bin.

Cheers,

HcH

Offline nyioo7

  • Jr. Member
  • **
  • Thank You
  • -Given: 15
  • -Received: 51
  • Posts: 69
  • Karma: +54/-0
  • Uber-Noobie
  • Tablet / Size / Model: A13 7" Allwinner
Re: Touchscreen driver for A13B
« Reply #11 on: October 26, 2012, 11:59:17 AM »
Hey HCH,

Yes. That is what I've been doing with my tablet. Some ROMs I found has working TS but the touch is either top and bottom reversed or left and right reversed. But here's a good news. I opened up my tablet. Took it apart and read the chips models inside. I found the exact numbers for my TS and my G-sensor. So, now, I am able to make G-sensor works on no matter what ROM by modifying the init.sun5i.rc, script.bin and script0.bin. It seems that script0.bin or script.bin, either one of them are working as backup. They need to be match to work. So I edit one and copy paste into another. Seems working well.

G-sensor issue is very easy to fix since it's only a one line code. TS issue, I still cannot figure it out. Especially because I can't find any ROMs that uses my TS chip gsl1680. So, I don't know the address of this chip. I'm shooting in the dark. I found ft5x_ts works in opposite position so I tried using that address and it didn't work for me. I am wondering if there might be another dependent driver. I can't tell unless I see a similar code for this chip. That's my observation so far. Working on it as I type. If you want to know anything, let me know. I will be posting detail step by step on how to check your tablet individual chips later when I got my TS working.

Also, if you find any ROM that uses gsl1680.ko driver, please let me know.

Thank you.

EDIT: EDIT: About testing the TS, I use the USB mounse to get to "Developer Options" in Settings and check pointer location. It shows you a line of where your touch is going at what position.
« Last Edit: October 26, 2012, 12:09:27 PM by nyioo7 »

Offline HardcoreHacker

  • Administrator
  • Uber Member
  • *****
  • Thank You
  • -Given: 6619
  • -Received: 1968
  • Posts: 8145
  • Karma: +3000/-99
Re: Touchscreen driver for A13B
« Reply #12 on: October 26, 2012, 12:15:32 PM »
Hey nyioo7,

Thanks for the details on fixing the issue, as for your "gsl1680" driver, I'll have a look in my downloaded a13 firmwares, brb.

HcH

Offline HardcoreHacker

  • Administrator
  • Uber Member
  • *****
  • Thank You
  • -Given: 6619
  • -Received: 1968
  • Posts: 8145
  • Karma: +3000/-99
Re: Touchscreen driver for A13B
« Reply #13 on: October 26, 2012, 12:17:29 PM »
I got these new ROMs that are not downloadable from TechKnow:

a13 Vi60F_v1.4rc3.rar
A13-MID_nuclear_pfdq88c-eng-IMM76D-Factory_Image.img
A13_D50N_4.0.4ø‘.zip
a13_F9_00_[TechKnowForum.net].img
A13_jsaQ88_CPT4GB_20120908_a13b_new.img
A13_M-726_TIA_06_27_3.img
jsaQ88_??_?????_V1.....rar
Q8_2127-V4_0309_0912_20120918.img
Yeahpad A13 ROM.rar
???CPTsun5i_android_a13-pfdq88_??_CPT_??_0....img.7z

I'll have a look in these for that .ko driver you seek.

Offline nyioo7

  • Jr. Member
  • **
  • Thank You
  • -Given: 15
  • -Received: 51
  • Posts: 69
  • Karma: +54/-0
  • Uber-Noobie
  • Tablet / Size / Model: A13 7" Allwinner
Re: Touchscreen driver for A13B
« Reply #14 on: October 26, 2012, 12:21:48 PM »
Wow. I have to check with my ROM collection. Haha. Thanks. Also, I have the gsl1680.ko file. It is already in the ROM. It's just that I don't know how to call it. I think I need to know the address and maybe dependent driver. So far, I've tried 3 different addresses and no luck. So, if you could look into the init.sun5i.rc under tp driver I'd be really appreciated.


Offline HardcoreHacker

  • Administrator
  • Uber Member
  • *****
  • Thank You
  • -Given: 6619
  • -Received: 1968
  • Posts: 8145
  • Karma: +3000/-99
Re: Touchscreen driver for A13B
« Reply #15 on: October 26, 2012, 12:47:52 PM »
Hey nyioo7,

in my attempt to get a multi ts supported ROM I learnt that you can just insmod the .ko driver in the init.sun5i.rc, however, you will need to comment the current ts .ko driver out, e.g.

on boot

   #insmod key & tp driver
   #insmod /system/vendor/modules/ft5x_ts.ko
   insmod /system/vendor/modules/sw-keyboard.ko

change to:

on boot

   #insmod key & tp driver
   insmod /system/vendor/modules/ft5x_ts.ko
   #insmod /system/vendor/modules/sw-keyboard.ko

just an example ofc on howto swap.

The attached file to the post is the driver you'll need, add this line to the init.sun5i.rc :

   insmod /system/vendor/modules/gsl1680.ko

After you dumped this .ko in /system/vendor/modules

Good luck!

HcH

Offline nyioo7

  • Jr. Member
  • **
  • Thank You
  • -Given: 15
  • -Received: 51
  • Posts: 69
  • Karma: +54/-0
  • Uber-Noobie
  • Tablet / Size / Model: A13 7" Allwinner
Re: Touchscreen driver for A13B
« Reply #16 on: October 26, 2012, 12:50:16 PM »
Hey. I tried that. It didn't work for me. That's why I started looking into the bootloader. In the bootloader, it calls the TS driver using the address. That's what I'm trying to figure out. I'll check this file you attached.

EDIT. The file you attached is just the driver file. These ROMs are built with every single drivers already included for all the clones. The only changes were done are hardware and how they are being called. That's why it seems harder especially because TS seems to be several different models. G-sensor is easy to fix because I think there's only 3 different models for that.
« Last Edit: October 26, 2012, 12:52:12 PM by nyioo7 »

Offline HardcoreHacker

  • Administrator
  • Uber Member
  • *****
  • Thank You
  • -Given: 6619
  • -Received: 1968
  • Posts: 8145
  • Karma: +3000/-99
Re: Touchscreen driver for A13B
« Reply #17 on: October 26, 2012, 12:54:05 PM »
Ah, I see, so that is the address you are searching for. I've indeed have seen that all the drivers are present in most, if not all, a13 roms.

Would it help you if I upload all the firmwares I have ?

Offline nyioo7

  • Jr. Member
  • **
  • Thank You
  • -Given: 15
  • -Received: 51
  • Posts: 69
  • Karma: +54/-0
  • Uber-Noobie
  • Tablet / Size / Model: A13 7" Allwinner
Re: Touchscreen driver for A13B
« Reply #18 on: October 26, 2012, 01:03:49 PM »
If you see init.sun5i.rc has insmod to gsl1680.ko, then yes. I would like to have that ROM please. It would be kind of time consuming to check each and every ROM like that. So, to narrow it down, my device is A13B. Android 4.0.4. If it's 4.0.3, don't bother with it. Thank you for doing this.

The address I'm looking for is, inside the script.bin and script0.bin, ctp_twi_addr value. I am not sure about ports since I see all the same about them. I need to confirm that. I am going to try to use 2 parameters at once to see if it will somehow work.

EDIT: Oh. I just realized that if you have fast upload connection, then it'd be faster for you to upload them and I can download them quickly to test them on my device to see what works what.

Offline HardcoreHacker

  • Administrator
  • Uber Member
  • *****
  • Thank You
  • -Given: 6619
  • -Received: 1968
  • Posts: 8145
  • Karma: +3000/-99
Re: Touchscreen driver for A13B
« Reply #19 on: October 26, 2012, 01:28:07 PM »
You will need to unpack the main IMG file of a rom, then the script files are in the bootfs.fex, you can use WinImage to open this file or Diskinternals's Linux Reader:
http://www.diskinternals.com/files/Linux_Reader.exe

Thanks to Twjordo I can now batch upload to mediafire, I've just renamed all the ROMs properly and now am packing them, upload will start in 10mins, but my upload is just 90KBps so it will take a while!

HcH

Offline nyioo7

  • Jr. Member
  • **
  • Thank You
  • -Given: 15
  • -Received: 51
  • Posts: 69
  • Karma: +54/-0
  • Uber-Noobie
  • Tablet / Size / Model: A13 7" Allwinner
Re: Touchscreen driver for A13B
« Reply #20 on: October 26, 2012, 01:36:20 PM »
Whattt? You can just read the files using LinuxReader?? I tried to open them using ext2explorer and it didn't work. So, I found this script for A10 and been using it. It's slow. Lol. Well, glad to know this.

Anyways, thanks for the uploads in advance. I'm gonna get some sleep. It almost 5 a.m. Haha. I'll try again tomorrow.

Offline HardcoreHacker

  • Administrator
  • Uber Member
  • *****
  • Thank You
  • -Given: 6619
  • -Received: 1968
  • Posts: 8145
  • Karma: +3000/-99
Re: Touchscreen driver for A13B
« Reply #21 on: October 26, 2012, 01:40:08 PM »
Glad to have helped you a little, good night mate!

I will take some time before these are done uploading:

A13_D50-sc3038n_sdk1.4_20120709_v1_[TechKnowForum.net].7z
A13_F9_00_[TechKnowForum.net].7z
A13_goodix811_with_mxc622x_[TechKnowForum.net].7z
A13_jsaQ88_CPT4GB_20120908_a13b_new_[TechKnowForum.net].7z
A13_jsaQ88_V1_[TechKnowForum.net].7z
A13_M-726_TIA_06_27_3_[TechKnowForum.net].7z
A13_MID_nuclear_pfdq88c-eng-IMM76D-Factory_Image_[TechKnowForum.net].7z
A13_pfdq88_CPT_0_[TechKnowForum.net].7z
A13_Q8_2127-V4_0309_0912_20120918_[TechKnowForum.net].7z
A13_Vi60_v1.4rc3_[TechKnowForum.net].7z
A13_Yeahpad_20120803-cpt_[TechKnowForum.net].7z
2,58 GB (2.776.563.242 bytes)

;) Cheers,

HcH

Offline HardcoreHacker

  • Administrator
  • Uber Member
  • *****
  • Thank You
  • -Given: 6619
  • -Received: 1968
  • Posts: 8145
  • Karma: +3000/-99
Re: Touchscreen driver for A13B
« Reply #22 on: October 26, 2012, 10:54:49 PM »
All have been uploaded mate:

http://www.techknow.t0xic.nl/forum/index.php?board=131.0

Good luck!

HcH

Offline nyioo7

  • Jr. Member
  • **
  • Thank You
  • -Given: 15
  • -Received: 51
  • Posts: 69
  • Karma: +54/-0
  • Uber-Noobie
  • Tablet / Size / Model: A13 7" Allwinner
Re: Touchscreen driver for A13B
« Reply #23 on: October 26, 2012, 10:58:57 PM »
Hey HCH,

Wow. Thanks. I just got home and I'll start working on this asap! Can't wait to see what waits for me. :)

Thank you.

Offline HardcoreHacker

  • Administrator
  • Uber Member
  • *****
  • Thank You
  • -Given: 6619
  • -Received: 1968
  • Posts: 8145
  • Karma: +3000/-99
Re: Touchscreen driver for A13B
« Reply #24 on: October 26, 2012, 11:00:38 PM »
You're welcome mate! I'll keep my fingers crossed for you ;-)

Cheers!

HcH

Offline nyioo7

  • Jr. Member
  • **
  • Thank You
  • -Given: 15
  • -Received: 51
  • Posts: 69
  • Karma: +54/-0
  • Uber-Noobie
  • Tablet / Size / Model: A13 7" Allwinner
Re: Touchscreen driver for A13B
« Reply #25 on: October 26, 2012, 11:11:46 PM »
Nice uploads. Love the download speed. This is how I have ROMs organized. Lol. Based on the test of course. There are more ROMs downloading in progress.


Offline nyioo7

  • Jr. Member
  • **
  • Thank You
  • -Given: 15
  • -Received: 51
  • Posts: 69
  • Karma: +54/-0
  • Uber-Noobie
  • Tablet / Size / Model: A13 7" Allwinner
Re: Touchscreen driver for A13B
« Reply #26 on: October 27, 2012, 02:58:53 AM »
Ok. So, script.bin also control the position of the display. Mine got shifted a bit while messing around.

Code: [Select]
[ctp_para]
ctp_used = 1
ctp_name = "elan_ts"
ctp_twi_id = 1
ctp_twi_addr = 0x15
ctp_screen_max_x = 800
ctp_screen_max_y = 480
ctp_revert_x_flag = 0   <-------------------------------
ctp_revert_y_flag = 0   <-------------------------------
ctp_exchange_x_y_flag = 0
ctp_int_port = port:PG11<6><default><default><default>
ctp_reset = port:PB03<1><default><default><1>
ctp_io_port = port:PG11<0><default><default><default>

This is where it shift the position. So, if anyone got working touchscreen with shifted screen, it can be fixed easily.

I was completely wrong about this. This time, I confirmed this 100%. This is the touchscreen X and Y vectors. This is to be adjust if you have upside down or left and right touchscreen issue. I've completely fixed my tablet's touchscreen by adjusting this on a ROM that works touchscreen.

Another information I've found is that, just because I have the certain chip, doesn't mean that chip driver will work. For example, my touchscreen chip is gsl1680 but I got my touchscreen working with ft5x_ts.ko driver. That means, we are gonna have more trouble finding the right driver for right model since they are mismatching......

On the other hand, G-sensor is another issue. I am moving on to G-sensor now. To be able to understand the Touchscreen completely, I need a volunteer with known working touchscreen ROM. anyway it works is ok. Doesn't matter. That's a minor adjustment. Being said that, I will need as many different touchscreen as possible since they are all mismatch to document it based on the model number.....

My new theory is that kernel causes the driver problem and bootloader holds the properties of these devices. So, to fix the issues, we need to find the correct driver first, make it work anyway as possible and change or add the properties in bootloaders.


Offline nyioo7

  • Jr. Member
  • **
  • Thank You
  • -Given: 15
  • -Received: 51
  • Posts: 69
  • Karma: +54/-0
  • Uber-Noobie
  • Tablet / Size / Model: A13 7" Allwinner
Re: Touchscreen driver for A13B
« Reply #27 on: October 27, 2012, 01:01:49 PM »
Ok. I think I figured out the G-sensor issue. But I'm not so sure as I can't test this theory right now. My brother mistakenly took the tablet thinking it's working. I have to get it back tomorrow. Lol.

If by any chance reni10 is on and be able to test the ROM I uploaded for him, and if it works, then I can confirm the theory on G-sensor. My theory is that, G-sensors are not working on certain devices is because driver files are missing. In reni10's case, his G-sensor is mc32x0. But mc32x0.ko is not in the ROM he claimed to have everything working except G-sensor. We'll see how that turns out.

Offline c345y

  • Full Member
  • ***
  • Thank You
  • -Given: 91
  • -Received: 32
  • Posts: 142
  • Karma: +36/-3
  • Uber-Noobie
  • Tablet / Size / Model: A13-MID/7/A13
Re: Touchscreen driver for A13B
« Reply #28 on: October 27, 2012, 01:12:57 PM »
Ok. I think I figured out the G-sensor issue. But I'm not so sure as I can't test this theory right now. My brother mistakenly took the tablet thinking it's working. I have to get it back tomorrow. Lol.

If by any chance reni10 is on and be able to test the ROM I uploaded for him, and if it works, then I can confirm the theory on G-sensor. My theory is that, G-sensors are not working on certain devices is because driver files are missing. In reni10's case, his G-sensor is mc32x0. But mc32x0.ko is not in the ROM he claimed to have everything working except G-sensor. We'll see how that turns out.
I'm downloading now.
I'm glad to test it too. My tablet not using this driver, but i will try this too.
I hope your theory is true. :android-lol:
thanks anyway. I will report as soon as i'm done uploading this rom to my tablet.
WM8650 - Uberoid ROM / Green Led / Android 2.2 / 7" / 3000mAh
Ainovo Paladin - Original Rom / Android 4.0.3 / 7" A8 512MB RAM 4GB ROM/ 4200mAh
Cube U9GT2 - Original Rom / Android 4.0.3 / 9.7" A9 1GB ROM 8GB RAM / 10000mAh
A13/Q88 - Goodix811+Mxc622x / Android 4.0.4 / 7" A13B 512MB RAM 4GB ROM / 4000mAh
Vimicro - Original Rom / Android 2.3 / 8" A8 1GB RAM 8GB ROM / 5000mAh

Offline codric

  • Newbie
  • *
  • Thank You
  • -Given: 0
  • -Received: 0
  • Posts: 1
  • Karma: +0/-0
  • Uber-Noobie
  • Tablet / Size / Model: A13 Yeahpad
Re: Touchscreen driver for A13B
« Reply #29 on: October 28, 2012, 09:22:50 AM »
<4>[ 277.940000]
<4>[ 277.940000] +================new driver========================
<4>[ 277.940000]
<4>[ 277.940000] +================new driver========================
<4>[ 277.950000]
<4>[ 277.950000] +================new driver========================
<4>[ 277.960000]
<4>[ 277.960000] ssd253x v1.0
<6>[ 277.960000] ssd253x_ts_init
<4>[ 277.970000] [jicky]===========================ssd253x_ts_init============
========
<4>[ 277.970000] ssd253x_ts_init: after fetch_sysconfig_para: normal_i2c: 0x4
. normal_i2c[1]: 0xfffe
<4>[ 278.020000] [i2c1] incomplete xfer (0x20)
<4>[ 278.220000] SSL Touchscreen I2C Address: 0x48
<4>[ 278.220000] [i2c1] incomplete xfer (0x20)
<4>[ 278.230000] [i2c1] incomplete xfer (0x20)
<4>[ 278.230000] [i2c1] incomplete xfer (0x20)
<4>[ 278.240000] [i2c1] incomplete xfer (0x20)
<4>[ 278.240000] SSL Touchscreen Device ID : 0xFFFF
<4>[ 278.240000] SSL Touchscreen Version ID : 0xFFFF
<4>[ 278.250000] [i2c1] incomplete xfer (0x20)
<4>[ 278.250000] [i2c1] incomplete xfer (0x20)
<4>[ 278.260000] [i2c1] incomplete xfer (0x20)
<4>[ 278.260000] [i2c1] incomplete xfer (0x20)
<4>[ 278.270000] [i2c1] incomplete xfer (0x20)
<4>[ 278.270000] [i2c1] incomplete xfer (0x20)
<4>[ 278.270000] [i2c1] incomplete xfer (0x20)
<4>[ 278.280000] [i2c1] incomplete xfer (0x20)
<4>[ 278.280000] [i2c1] incomplete xfer (0x20)
<4>[ 278.290000] ttyS0: 1 input overrun(s)
<4>[ 278.290000] [i2c1] incomplete xfer (0x20)
<4>[ 278.300000] [i2c1] incomplete xfer (0x20)
<4>[ 278.300000] [i2c1] incomplete xfer (0x20)
<4>[ 278.310000] [i2c1] incomplete xfer (0x20)
<4>[ 278.320000] [i2c1] incomplete xfer (0x20)
<4>[ 278.330000] [i2c1] incomplete xfer (0x20)
<4>[ 278.330000] [i2c1] incomplete xfer (0x20)
<4>[ 278.340000] [i2c1] incomplete xfer (0x20)
<4>[ 278.340000] [i2c1] incomplete xfer (0x20)
<6>[ 278.350000] init: waitpid returned pid 146, status = 00000100
<5>[ 278.350000] init: process 'console', pid 146 exited
<5>[ 278.360000] init: process 'console' killing any children in process group
<5>[ 278.360000] init: starting 'console'
<4>[ 278.370000] [i2c1] incomplete xfer (0x20)
<4>[ 278.370000] [i2c1] incomplete xfer (0x20)
<4>[ 278.380000] [i2c1] incomplete xfer (0x20)
<4>[ 278.380000] [i2c1] incomplete xfer (0x20)
<4>[ 278.390000] [i2c1] incomplete xfer (0x20)
<4>[ 278.390000] [i2c1] incomplete xfer (0x20)
<4>[ 278.400000] [i2c1] incomplete xfer (0x20)
<4>[ 278.400000] [i2c1] incomplete xfer (0x20)
<4>[ 278.410000] [i2c1] incomplete xfer (0x20)
<4>[ 278.410000] [i2c1] incomplete xfer (0x20)
<4>[ 278.410000] [i2c1] incomplete xfer (0x20)
<4>[ 278.420000] [i2c1] incomplete xfer (0x20)
<4>[ 278.430000] [i2c1] incomplete xfer (0x20)
<4>[ 278.430000] [i2c1] incomplete xfer (0x20)
<4>[ 278.440000] [i2c1] incomplete xfer (0x20)
<4>[ 278.440000] [i2c1] incomplete xfer (0x20)
<4>[ 278.450000] [i2c1] incomplete xfer (0x20)
<4>[ 278.450000] [i2c1] incomplete xfer (0x20)
<6>[ 278.460000] init: waitpid returned pid 690, status = 00000100
<5>[ 278.460000] init: process 'console', pid 690 exited
<5>[ 278.470000] init: process 'console' killing any children in process group
<4>[ 278.470000] [i2c1] incomplete xfer (0x20)
<4>[ 278.480000] [i2c1] incomplete xfer (0x20)
<4>[ 278.480000] [i2c1] incomplete xfer (0x20)
<4>[ 278.490000] [i2c1] incomplete xfer (0x20)
<4>[ 278.490000] [i2c1] incomplete xfer (0x20)
<4>[ 278.500000] [i2c1] incomplete xfer (0x20)
<4>[ 278.500000] [i2c1] incomplete xfer (0x20)
<4>[ 278.500000] [i2c1] incomplete xfer (0x20)
<4>[ 278.510000] [i2c1] incomplete xfer (0x20)
<4>[ 278.510000] [i2c1] incomplete xfer (0x20)
<4>[ 278.520000] [i2c1] incomplete xfer (0x20)
<4>[ 278.520000] [i2c1] incomplete xfer (0x20)
<4>[ 278.520000] [i2c1] incomplete xfer (0x20)
<4>[ 278.530000] [i2c1] incomplete xfer (0x20)
<4>[ 278.530000] [i2c1] incomplete xfer (0x20)
<4>[ 278.540000] [i2c1] incomplete xfer (0x20)
<4>[ 278.540000] [i2c1] incomplete xfer (0x20)

what am i doing wrong? is it hardware error or just not using or not setting well the touch screen driver?

The problem, i have no backup at all, tryed yeahpad_hi firmware, whitch is ok exerpt touch screen. Chip must be ssd253x because other ts driver inti says operation not permitted. Can somebody help me to identify the correct TS chip/driver and settings? Thanx

 

Powered by EzPortal