Acer One 10 not detecting touch driver

[Zeeshan Ahmed P]

I am running 5.1 release on my tablet and the touch isn't working, when I try to run the same build on my notion ink cain tablet, it works perfectly.

So I checked device manager on both the tablets for touchscreen and found out that both touch screen are same. 

Also on my notion ink cain tablet touch works only when the type cover is unplugged, when i boot to android with the keypad plugged then the touch doesn't work. Have to restart it with the keypad unplugged to get it working again.

So I kinda concluded that it might be a problem with my tablet not detecting the driver properly even though its already there but I'm not sure. Please help me out somebody

I wanna know if there's a way I can test which driver file is running on my cain tablet which makes the touch work there and also is there a method that I can use to install the driver manually and make the touch work.

Thank you..

[Zeeshan Ahmed P]

I ran cat /proc/bus/input/devices on my Notion Ink Cain and the result is attached 

[pstglia]

Hi,

Fisrt, you should check if you can have touchscreen working on a linux distro, which means it's supported. If so, you can list which kernel module is being loaded.

 Also, you should check the device id's from your Acer Device. Getting from a different working device won't help in this case (unless you are 100% sure they share the same touchscreen brand/model)

Regards,

Pstglia

[Zeeshan Ahmed P]

Thank you very much for your reply
I ran lsusb and lspci on my tablet and I didn't see the touch screen there..
And I ran the same commands on my other tablet in which touch is working.. Still found the exact same results... No touchscreen.. I'm attaching the output files and the screen shots from the device manager of both devices
I'm damn sure the touch screens are same, what do I do now to detect the drivers on my Notion Ink and load the same on my acer tablet
And again thanks a lot for your response..

--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86...@googlegroups.com.
To post to this group, send email to andro...@googlegroups.com.
Visit this group at http://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.

[Zeeshan Ahmed P]

My bad, Attached the wrong screenshot, 

[pstglia]

Thank you very much for your reply
I ran lsusb and lspci on my tablet and I didn't see the touch screen there..
And I ran the same commands on my other tablet in which touch is working.. Still found the exact same results... No touchscreen.. I'm attaching the output files and the screen shots from the device manager of both devices
I'm damn sure the touch screens are same, what do I do now to detect the drivers on my Notion Ink and load the same on my acer tablet
And again thanks a lot for your response..

Apparently your touchscreen on both tablets is a goodix one. Maybe it's not detecting it due non match supported device id list (they can have different i2c / acpi id's). 

You can try the following: Boot Android-x86 under debug mode and before the 2nd exit message, try looking if goodix module is loaded:

lsmod 

OR

busybox lsmod

If not listed, try loading it:

modprobe goodix

OR 

busybox modprobe goodix

Once driver is loaded type exit and continue booting.

If your touchscreen continues not working, most probably the driver doesn't currently support your device

Here's some lines from goodix.c where with the compatible device ids:

static const struct i2c_device_id goodix_ts_id[] = {

        { "GDIX1001:00", 0 },

        { }

};

#ifdef CONFIG_ACPI

static const struct acpi_device_id goodix_acpi_match[] = {

        { "GDIX1001", 0 },

        { }

};

MODULE_DEVICE_TABLE(acpi, goodix_acpi_match);

#endif

#ifdef CONFIG_OF

static const struct of_device_id goodix_of_match[] = {

        { .compatible = "goodix,gt911" },

        { .compatible = "goodix,gt9110" },

        { .compatible = "goodix,gt912" },

        { .compatible = "goodix,gt927" },

        { .compatible = "goodix,gt9271" },

        { .compatible = "goodix,gt928" },

        { .compatible = "goodix,gt967" },

        { }

};

MODULE_DEVICE_TABLE(of, goodix_of_match);

#endif

static struct i2c_driver goodix_ts_driver = {

        .probe = goodix_ts_probe,

        .id_table = goodix_ts_id,

        .driver = {

                .name = "Goodix-TS",

                .owner = THIS_MODULE,

                .acpi_match_table = ACPI_PTR(goodix_acpi_match),

                .of_match_table = of_match_ptr(goodix_of_match),

        },

};

module_i2c_driver(goodix_ts_driver);

[Zeeshan Ahmed P]

Thank you so much sir,
I tried what you said, loaded the module by typing
modprobe goodix
But the touch still didn't work.. I saw another module in lsmod output of the other tablet, hid_multitouch..
Even this didn't work!  :(

[pstglia]

Thank you so much sir,
I tried what you said, loaded the module by typing
modprobe goodix
But the touch still didn't work.. I saw another module in lsmod output of the other tablet, hid_multitouch..
Even this didn't work!  :(

Does dmesg shows anything after loading the module?

If you can, list your i2c/acpi devices from Acer:

ls -l /sys/bus/i2c/devices

ls -l /sys/bus/acpi/devices

[Zeeshan Ahmed P]

I tried dmesg after loading the modules it still says 

i2c_hid i2c-FTSC1000:00: hid_descr_cmd failed

and I ran the two cmds that you told and the results are attched

--

[pstglia]

 

I tried dmesg after loading the modules it still says 

i2c_hid i2c-FTSC1000:00: hid_descr_cmd failed

and I ran the two cmds that you told and the results are attched

Thanks for provided info. Can I ask you a few more questions?

1) Are you trying the ISO img (android-x86-5.1-rc1.iso) or the EFI one (android-x86_64-5.1-rc1.img)? If you are using the EFI image, please try the ISO one.

They share the same code, but ISO img (x86 target) has some kernel options that EFI img (64 bits) doesn't. 

In this case, something that could interfere is CONFIG_OF (open firmware)

Note: To boot ISO img, make sure changing your boot to "Legacy BIOS" on setup (see http://acer.custhelp.com/app/answers/detail/a_id/27045/~/changing-bios-mode-from-uefi-to-legacy)

2) Can you also get these extra infos?

cd /sys/bus/acpi/devices/FTSC1000\:00/

cat *

cd /sys/bus/i2c/devices/i2c-FTSC1000\:00/

cat *

3) Can you post the same contents for your other tablet? (motion ink)?

ls -l /sys/bus/i2c/devices

ls -l /sys/bus/acpi/devices

Thanks

[Zeeshan Ahmed P]

First up! Thank you so much for following up my problem and helping me so much, really great full

I ran the iso image, there's no legacy boot option in the bios though but I managed to flash the image with android-x86 installer for windows and changed androidboot.hardware=android_x86_64 to x86 and it booted up just fine but the touch still wasn't working. 

Anyways I managed to get all the outputs that you asked for, and I've attached them

[Zeeshan Ahmed P]

Also I found something interesting, like I've mentioned in the OP that the touch on my notion ink works only when its booted with the type cover connected..

I just booted it up with the cover off and the touchscreen wasn't working I ran a dmesg and it shows the exact same error that shows up on my tablet 

i2c_hid i2c-FTSC1000:00: hid_descr_cmd failed

I'm attaching that dmesg file too.. Don't know if that's gonna help,

On Sunday, December 6, 2015 at 5:26:13 PM UTC+5:30, pstglia wrote:

[pstglia]

Hi

First up! Thank you so much for following up my problem and helping me so much, really great full

I ran the iso image, there's no legacy boot option in the bios though but I managed to flash the image with android-x86 installer for windows and changed androidboot.hardware=android_x86_64 to x86 and it booted up just fine but the touch still wasn't working. 

Anyways I managed to get all the outputs that you asked for, and I've attached them

Thanks for provided info. I found a topic on xda that suggests that reloading the kernel module (i2c_hid) could make it work. See here (post #1770)

http://forum.xda-developers.com/windows-8-rt/general/cube-i7-stylus-t3151563/post64178212#post64178212 

Can you test it please? On debug mode, before 2nd exit message, reload the i2c_hid module:

rmmod i2c_hid

OR

busybox rmmod i2c_hid

modprobe i2c_hid

OR

busybox modprobe i2c_hid

If you make it work, maybe i2c_hid should be loaded after other modules. 

Regards,

pstglia

[pstglia]

Thanks for provided info. I found a topic on xda that suggests that reloading the kernel module (i2c_hid) could make it work. See here (post #1770)

http://forum.xda-developers.com/windows-8-rt/general/cube-i7-stylus-t3151563/post64178212#post64178212 

Now checking user from original question (zeetherocker), I'm guessing is you, am I right? :)

[Zeeshan Ahmed P]

Yes you are right.. That was me
And the solution works... Thank you so much..
The touch started working!
Is there a way I can make a script and run this on boot..?
And also how to debug other things that aren't working like sound and stuff..
It'd help me if you tell me about some commands that are gonna help..

Thanks for provided info. I found a topic on xda that suggests that reloading the kernel module (i2c_hid) could make it work. See here (post #1770)

http://forum.xda-developers.com/windows-8-rt/general/cube-i7-stylus-t3151563/post64178212#post64178212 

Now checking user from original question (zeetherocker), I'm guessing is you, am I right? :)

--

[pstglia]

Yes you are right.. That was me
And the solution works... Thank you so much..
The touch started working!
Is there a way I can make a script and run this on boot..?

You can add these cmds inside /system/etc/init.sh (think you can put it inside init_misc function)

Note: Your /system filesystem must have write permissions (this can be select during instalation)

 

And also how to debug other things that aren't working like sound and stuff..
It'd help me if you tell me about some commands that are gonna help..

First check "dmesg" and "logcat" cmd outputs. If you find something suspicious, try searching on web.

Also get ids from non working devices (10EC:5640 is your sound card, according to the outputs you provided above) and search those with Android / Android-x86 keys.

Many solutions to my problems were already asked and answered on web.

Regards

Pstglia

[Zeeshan Ahmed P]

I've installed the 5.1 iso through the win installer
The system is read only.. I don't know how to make it writable..
OR is there a way to install the iso directly without the win installer.. I don't have the right bootia32 file... Any file I copy to my Bootable disk takes me to the grub console..
I tried searching for it none of them seem to work..
And also.. What I meant earlier was when I find out that one of the device drivers isn't working from dmesg, where do I look for it..
Is there a similar command like
cat /proc/bus/input/devices which you asked me to run for touch screen.
The power button is listed there but not working.. So I wanna list the device and check if the driver is loaded proper..
Thank you again sir!

[Povilas Staniulis]

Since the system partiton isn't created, I assume the installer just copies system.sfs file to somewhere.
To make /system writable you need to unsquashfs system.sfs to get system.img.

[Zeeshan Ahmed P]

How do I do that? Is there a particular com command that I've to run?

[Povilas Staniulis]

CD to system.sfs location and run this command (on the host system, not Android):

unsquashfs system.sfs

You should get a folder called squashfs-root with system.img file in it.
Move system.img to the same location as system.sfs. Then delete system.sfs.

You can download Windows versions of squashfs-tools here:
http://fragilematter.blogspot.com/2010/02/squashfs-tools-40-windows-binaries.html

[Zeeshan Ahmed P]

Thank you for the link... I'll try this!

[Mauro Rossi]

Hi,
If you want to propose a patch to integrate the change in init.sh,
DMI product label and a check about Hal sensors section would be needed, are i2c sensors currently working on your Acer One?

If not we could try to add a new entry for Acer One in function init_hal_sensors()

M.

[Zeeshan Ahmed P]

Yes I'd like to propose the path.. But how to check if i2c sensors are working...
By i2c sensors u mean only touch or something.. Also as of now sound (both headphones and audio jack) , power button, Bluetooth are the only things not working... Orientation is working but inverted.. Haven't searched for a solution yet..
For submitting the patches I've to download the sources right.. I'm planning to do that after my exams this month..

[Paulo Sergio]

Hi Nasam

Sir,
I installed 5.1 efi image on 2in1 but touch is unstable even though I removed my finger it stay on screen I need to touch the screen 2- 3 times to select an option .kindly help me

Please try the group instead of private help. 

We need also that you provide dmesg and logcat outputs

Regards

Pstglia

[Sparsh Kumar]

Hi, can u tell me how to reload kernel module? I too have a non working touch screen

[Zeeshan Ahmed P]

Use - 

rmmod i2c_hid

OR

busybox rmmod i2c_hid

modprobe i2c_hid

OR

busybox modprobe i2c_hid

For automating this on every boot you must add this lines in  /system/etc/init.sh (inside init_misc function)

You need root access for this 

Please thank @pstglia for this. He helped me a lot 

To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+unsubscribe@googlegroups.com.

To post to this group, send email to andro...@googlegroups.com.

Visit this group at https://groups.google.com/group/android-x86.

[Sparsh Kumar]

Thank you both @Zeeshan and @pstglia :) :) Zeeshan have you solved the problem of incorrect battery status?

On Saturday, December 5, 2015 at 1:50:00 AM UTC+5:30, Zeeshan Ahmed P wrote: