Announcement

Collapse
No announcement yet.

Announcement

Collapse
No announcement yet.

Touchscreen

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    #46
    Many thanks for all the detail. I'm running into a few issues trying to setup a TD2420 from Viewsonic and would appreciate any ideas/thoughts.

    Here's what I've done so far
    The lsusb command indicates the touchscreen has the following product/vendor numbers which show up only after I plug in the usb from the monitor:
    Product: 093a
    Vendor: 8002

    I've created the file in multiple ways with multiple names - all owned by root/root and with permissions 644:
    Product_093A_Vendor_8002.idc
    Product_093a_Vendor_8002.idc

    For the content, I initially tried in vi but the system file system is mounted ro (as an aside - I'd really appreciate the mount command / options to mount that as rw... I thought it was in the mnttab file, but I don't recall where that lives). I created it using the ES File Editor and confirmed that the trailing newline feed was present through a cat command from terminal editor. I also emailed the txt file to my google account, saved it locally, and copied and renamed (twice - using the names above).

    After every idc file change, I reboot and then unplug my mouse and plug in the monitor. I try using a single touch to move the cursor around the screen and activate apps - but do not appear to be getting any input.

    Still no luck. Thanks for any suggestions!

    Comment


      #47
      MK808B support

      I am using MK808B dongle.

      - Can this mod work in the stock kernel? I am not able to flash the rom with Finless 1.7 till now (http://www.freaktab.com/showthread.p...Flashing-issue)

      - Can this mod work on a usb touch screen module listed in **** (http://www.****.com/itm/7inch-4-Wire...item27c9355f9b)

      Thanks in advance.

      Comment


        #48
        in theory yes.
        if it gives a white ring you can drag around it sould work.
        but if this panel is supported i have no idea.

        regards
        mark

        Comment


          #49
          ...but you will need root to add the file I think.

          Comment


            #50
            I am using eGalax generic digitizer and controller with VendorID : 0eef and ProductID : 0001. I tried adding the vendor_0eef_product_0001.idc file to the system/usr/idc folder with the following content:


            touch.deviceType=touchScreen
            device.internal=1


            On rebooting its not responding to any touch input. I suspect the touch screen driver is missing. What else could be the reason?
            How can we check whether the touchscreen driver is already installed? Also is there any way to install the driver alone similar to Windows?

            Comment


              #51
              I'm having the same issue. Egalax touchscreen 0eef:0001. It is registered when inserted in USB, but not recognized by the system. So probably not driver...

              @Bob
              Is it possible to recompile a driver into the kernel?

              Comment


                #52
                I just flashed the 4.2.2 kernel on an MK808B - I was going to repeat the update process to see if that helped with the touchscreen recognition. I'll post success/failure...

                Do we even know what driver is required (or if the driver exists for Androids)?

                Comment


                  #53
                  A little help over here..

                  Guys, I made the same exact steps below, read the whole thread, even read also the help stuff on source.android.com and I have nothing working here.

                  First of all, my hardware is an MK802 (im not really sure which version, but looking at the images i might say that is the first hardware they released) and i have an Acer T231H monitor. Now it's plugged like this:




                  I made the lsusb thing and got the same vid and pid as in the post is described, vendor is 0408 and product is 3001, so the file is "Vendor_0408_product_3001.idc" and into the file there is the same string as in the first post.

                  Even though I made the same exact steps as described, as I explained, I cannot manage to make this touchscreen work.

                  Can anybody help me?

                  Thank you guys in advance.

                  PS: about the hub, i know it works with the touchscreen, because i tried it with my pc and it worked fine (trough the hub)

                  Comment


                    #54
                    ok

                    Comment


                      #55
                      @agusttt I can't see the picture you posted.

                      A couple of things to check - even before you add the file but plug in the monitor can you see a ring which you can drag around on the screen? If you can't then the ROM kernel probably doesn't have the driver built in - but do try plugging it in direct to the USB on the stick as well.

                      Just check that you've put the idc file in the right place as step 11 in the very first post has the path wrong - it should be /system/usr/idc I think.

                      Check post 25 for some useful command lines - I'm probably teaching you to suck eggs but you have got root and mounted the /system/ partition read/write and changed the permissions - and best to check it is there after reboot - it does need a reboot to take affect.

                      Finally did you create the idc file on the android stick or use windows - you need to use an editor that creates unix text file because of Windows CR/LF.

                      Comment


                        #56
                        I have a lenovo LI2341T 23" touchscreen monitor

                        [ 3574.061174] usb 3-4: new high-speed USB device number 116 using xhci_hcd
                        [ 3574.077491] usb 3-4: New USB device found, idVendor=058f, idProduct=6254
                        [ 3574.077502] usb 3-4: New USB device strings: Mfr=0, Product=0, SerialNumber=0
                        [ 3574.078031] hub 3-4:1.0: USB hub found
                        [ 3574.078119] hub 3-4:1.0: 4 ports detected

                        [ 3574.364840] usb 3-4.3: new full-speed USB device number 117 using xhci_hcd
                        [ 3574.383488] usb 3-4.3: New USB device found, idVendor=1926, idProduct=0336
                        [ 3574.383499] usb 3-4.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
                        [ 3574.383505] usb 3-4.3: Product: Touchscreen
                        [ 3574.383509] usb 3-4.3: Manufacturer: NextWindow
                        [ 3574.388000] input: NextWindow Touchscreen as /devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4.3/3-4.3:1.0/input/input16

                        [ 3574.388350] hid-multitouch 0003:1926:0336.000A: input,hiddev0,hidraw0: USB HID v1.11 Mouse [NextWindow Touchscreen] on usb-0000:00:14.0-4.3/input0
                        [ 3574.389800] input: NextWindow Touchscreen as /devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4.3/3-4.3:1.1/input/input17
                        [ 3574.390051] hid-generic 0003:1926:0336.000B: input,hiddev0,hidraw1: USB HID v1.11 Device [NextWindow Touchscreen] on usb-0000:00:14.0-4.3/input1
                        [ 3574.391202] input: NextWindow Touchscreen as /devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4.3/3-4.3:1.2/input/input18
                        [ 3574.391509] hid-generic 0003:1926:0336.000C: input,hidraw2: USB HID v1.11 Mouse [NextWindow Touchscreen] on usb-0000:00:14.0-4.3/input2

                        This is what I get when I connect my touchscreen to the USB hub.

                        It seems, that two devices are getting created.
                        058f:6254
                        1926:0336

                        I created both the files, and ofcourse using vi - so no issues of windows CR/EOL coming into the file.
                        The permissions are as suggested 06775

                        However, inspite of this - there seems to be no change. Even without these files in place, when one touches the screen the mouse cursor appears on the extreme left top corner of the screen. It cannot be moved, changed or any other operation for that matter. The same behaviour remains, even when the files are created.

                        Any thoughts ?

                        Alok

                        Comment


                          #57
                          WHere is the file todownload

                          Hi, Where is the download file Everyone is talking about, I havent's seen any file to download

                          Thanks

                          I have a acer T232 HLadn wich to enalble support for Android. Any body make it wirk?

                          Comment


                            #58
                            Re: Touchscreen

                            In the beginning of the tread second post or something

                            Comment


                              #59
                              @aloksinha2001

                              The cursor not moving would suggest that your touch interface is not supported in the android kernel. You would normally see a circle that you can drag around if it is.

                              Comment


                                #60
                                Originally posted by maphaneuf View Post
                                Hi, Where is the download file Everyone is talking about, I havent's seen any file to download

                                Thanks

                                I have a acer T232 HLadn wich to enalble support for Android. Any body make it wirk?
                                It is in post #1 just under the quote bubble - hover over the filename or http://www.freaktab.com/attachment.p...9&d=1351462387

                                As far as I know the T232HL is a newer 10 point touch that supports Windows 8 (edgeless) AFAIK I have not seen any newer 10 point screen supported in the Android kernel.

                                Comment

                                Working...
                                X