Apr 05, 2013  [HOW TO] modding touchscreen drivers on allwinner a13 JB ROM 4.1.1. 279 posts Thanks Meter: 297. If you still have non responsive touch screen then you have the wrong driver or the driver was not injected correctly. Modding touchscreen drivers on allwinner a13 JB ROM 4.1.1.

A13_TouchScreen_Driver_Changer_[www.TechKnow.me] Enables a user to change the touchscreen driver on A13. Included TS drivers for A13: byd693x-ts ct360_ts elan_ts goodix811 goodix_touch gsl1680 gslx680 gt811 gt818_ts gt828_ts mg8698s restore_stock ssd253x-ts zet6221-ts zet6221_ts Instructions: 1. Adb 'root' 2. Adb remount 3. Adb push ft5x_ts.ko /system/lib/modules 4.

Adb shell chmod 644 /system/lib/modules/ft5x_ts.ko 5. Adb push ft5x_ts.idc /system/usr/idc 6. Adb shell chmod 644 /system/usr/idc/ft5x_ts.idc 7. Adb push 07touchscreen /system/etc/init.d 8. Adb shell chmod 644 /system/etc/init.d/07touchscreen HcH. Hopefully this nice tool does work for you since it does have most of the common known drivers afaik you can not change your hardware's needed resources. If your ts controller needs a certain driver you must have that driver for proper ts function remember you can always resort to your devices original factory firmware - it will have all your devices needed drivers also if you are not sure which driver you need you can pull that info from the stock rom after you have flashed it if needed you can try searching your device model for relative info and factory rom / firmware links archived in the forums.

This is a common tablet with several topics about it and i do see you have been reading some of the old threads already. Kumpulan soal program linear. Ok, so let me fill you in.

Long story short, this doesn't do anything for me. I have a Mach Speed Stealth Trio Pro 7c, 4GB storage, NO HDMI. My capacative touch screen is a FT5306. I originally received the tablet as a gift, the previous owner thought it was broken because they tried their password for their Google ID too many times, and it locked them out. I used Android Multitools to revert it back to stock, and was successful. So my idea for using the tablet was to get google play and play services running on it so I can install Chromecast for my father whose laptop died (I got him a Chromecast for Christmas, and he hasn't been able to use it for the last month).

I orignally tried to get google play on by installing an APK from Aptoide. I had moderate success, but after a restart of the tablet Google Play wouldn't install any applications. Upon researching I discovered another user who said his stock ROM removed Google Play and put it on a different partition without any space available, so that maybe was why I was getting the 'Not enough spavce available on SD card' error. So I tried to flash a new ROM.

I first installed CWM and attempted to create a backup of my current config. That only partially completed, looks like it backed up DATA, CACHE, SYSTEM, and.android_secure. It also made.img files for boot.img and recovery.img, but there's no other files. I decided I was going to reboot, and wait while I researched more things. This is before I knew about the awesome Uberizer. The tablet wouldn't reboot into anything except for recovery, and after trying and trying I finally found LiveSuite and the faaastJBv1 ROM. After trying and trying to get LiveSuite to load on my Win 7 x64 computer with no results, I was able to install it and get it to run on an old Vista 32 bit laptop.

I flashed JB v1, and everything was working again. Joy and happiness! Then I decided to play. I don't have enough dev knowhow to get everything to work as I intend it to on the first try.

But I've gotten better in the past 2 weeks due to trying to get this tablet back to working. I tried to flash CyanogenMOD from here for a13 tablets, and touch screen didn't work. So I tried some touch screen drivers, and they didn't work. Finally I found one that worked, but I have the same issue that's in another closed thread called a13 Touch Screen Calibration. Sorry, I'm typing this on another tablet so I'm not adept at providing links, but I can tell you I have the SAME EXACT PROBLEM as the others who were in that thread.