TechTablets › Forums › Teclast Forums › X98 Air 3G / Air II – Single and dual boot › no touchscreen in android C9J8
Tagged: c9j8 touchscreen
- This topic has 15 replies, 3 voices, and was last updated 10 years, 11 months ago by
Art Maker.
-
AuthorPosts
-
June 15, 2015 at 12:58 pm #5973
Am I the only one in the world with a C9J8 model?
June 16, 2015 at 1:12 am #5999Trevor,
The problem you are describing is very odd. Usually the touchscreen will either work (in all OSes) or it won’t work.
I can give you some information about how the touchscreen device is defined in Android and some commands to try that may shed some light on the problem.
Note: This will require you to connect the Air 3G to a Windows PC that has adb installed.
1. Power up your Air 3G and let it boot into Android.
2. Connect your Air 3G to the Windows PC using a USB cable. If you have not connected the tablet to the PC before, Windows may have to identify the tablet and load device drivers. Let this process complete.
3. On the windows PC, bring up a CMD prompt.
4. type adb devices followed by ENTER
You should see:List of devices attached
Baytrail0000000000 device5. type adb shell + ENTER
You should see:shell@x98air3g:/ $
6. type su + ENTER
You should see:root@x98air3g:/ #
7. Make sure the kernel modules have been loaded for the touchscreen.
type insmod /lib/modules/atmel_mxt_ts.ko + ENTER
and
type insmod /lib/modules/gt9xx_ts.ko + ENTER
After each command you should see:insmod: init_module ‘/lib/modules/xxxxxx.ko’ failed (File exists)
If either insmod succeeds, you may find that the touchscreen now functions.
8. Now we are going th check the status of the low level touchscreen device.
Type cat /sys/devices/virtual/input/input7/uevent + ENTER
I get:PRODUCT=18/dead/beef/28bb
NAME=”goodix_ts”
PHYS=”input/ts”
PROP=0
EV=b
KEY=400 0 0 0 0 0 0 0 0 0 0
ABS=2650000 0
MODALIAS=input:b0018vDEADpBEEFe28BB-e0,1,3,k14A,ra30,32,35,36,39,mlsfwLet me know what you get and we will continue from there.
June 16, 2015 at 3:40 am #6000Hi Randy,
I am ecstatic that you are helping me. I did as you said, except the tablet had to be in debug mode before it would show, I hope that doesn’t change things. The shell prompt shows “shell@x98air3g_c9j8:/#”. My results are exactly as you said above. What does that mean and what next? And thanks again for your help.June 16, 2015 at 4:14 am #6003OK, if you got the same results as I did, that means that your kernel modules are loading at boot time and that your touchscreen device is being recognized as well. I am kinda surprised that the touchscreen device is being recognized and then not working.
Give me a few minutes to come up with some more commands to run.
RandyJune 16, 2015 at 4:39 am #6004Hi Randy, Just a thought, in my Googling someone suggested that the boot.img file in v1.10 is different to v1.12. And the problem could be there. I could not find a v1.10 to try.
Regards,
Trevor JJune 16, 2015 at 5:10 am #6005Yes the BIOS images are different, but my touchscreen worked fine under 1.10 and 1.12 as it did for a lot of other people.
I don’t see the BIOS versions being your issue, unless your flash of 1.12 was bad. You might try reflashing 1.12 under Android.June 16, 2015 at 5:13 am #6006June 16, 2015 at 7:05 am #6007Thank you, I will try soon, I’ll let you know tomorrow how it goes.
June 16, 2015 at 8:19 am #6009Great. Thanks.
June 16, 2015 at 9:04 am #6010Trevor,
I found something.
This post:
http://forum.xda-developers.com/showpost.php?p=59663361&postcount=7189
reports that Teclast has a modified android boot.img
that you can download here:
http://www.mediafire.com/download/vxxcb5n1zuq8m8b/boot.img
You then replace the boot.img file in the android image you are flashing with the new downloaded boot.img and flash it.June 17, 2015 at 4:36 am #6019FYI,
The Android boot.img is not the same as the BIOS. The BIOS functions outside of all OSes, in fact both Windows and Android use BIOS functions to perform certain tasks. The Android boot.img apparently contains the low level drivers for some devices, including the touchscreen.
Also, the boot.img I linked above is reported to work with the Android 4.4 ROMs, but not with the Android 5 (Lollipop) ROMs.June 18, 2015 at 7:34 am #6025Hi Randy,
I used flash.bat in adb in windows 7, choose flash bios only, all proceeded, flash successful, press power button to power off device and closed command prompt. Then tried to power up, nothing, no bios no boot screen not even the charging icon. I suppose it is bricked. It was worth a go as Win8.1 was no good to me.
Regards,
Trevor JJune 18, 2015 at 8:33 pm #6031Wow, that is surprising. I flashed 1.12 to mine using adb and it worked perfectly. In fact the “Boot to Windows” icon in Android started working as well as the “Boot to Android” from Windows. Pretty much all the bricks I had heard about were people that flashed the BIOS under Windows.
Really sorry to hear that. Another way to check is to connect the tablet to a PC via a usb cable, then power it up and see if any devices show up under Windows device manager. Sometimes the display stops working, but the device is in fastboot mode where you can re-flash itJune 22, 2015 at 2:05 pm #6122Hi I tried that, but nothing, in windows 7 or Linux mint 17. No power no screen no usb nothing. What about inside is there a reset button like on the outside of Ramos tablets? Is there anything I can do on the inside?
July 10, 2015 at 12:42 am #6728I had the same problem with my C5J6 model. only android without touchscreen. could somebody help me??? please
-
AuthorPosts
- You must be logged in to reply to this topic.
