Re: Miix 2 Touchscreen failure

EDIT NOTE: This post was moved to the top of the thread in order to assist us with an escalation. For all future post and comments please continue posting in this thread.
I am having an identical problem with the Miix 2 10 I just received. The Touchscreen will stop responding but a driver reset will get it back 100% of the time. Unfortunately I can easily get it to stop responding again by wailing on the OS keyboard or playing a game. This seems like a software issue (likely firmware or BIOS) but I am returning the unit and getting a new one to try and rule out hardware issues. Also, I am happy to make such a catastrophic quality control issue as costly as possible for Lenovo. Hopefully there will be drivers or firmaware posted soon to update this but in the mean time I hope they like shipping brand new hardware, free of charge, ad infinitum.
EDIT NOTE: This post was moved to the top of the thread in order to assist us with an escalation. For all future post and comments please continue posting in this thread.

Just get another Miix 2 if the current one is deffective and Lenovo is not going to fix it using SW update in timely fashion.
I did it as I loved some aspects of Miix 2 and there was no suitable alternative at the monent.
The 1st one was deffective in screen / backlight area. Screen clouding, weird patterns on back of the screen, like someone pushed a palm with spreaded fingers from the back when mounting in factory. Unacceptable.
The 2nd one was deffective in touch screen area as described in this thread. Unacceptable.
The 3rd and possibly final one is relatively ok so far. Volume rocker has issues and tends to stay in + position but that's negligible compared to previous show stopper issues.
All three tablets are affected by low volume cracking problem as pointed out in other thread. Tablets were purchased in Czech Republic. I wonder whether other batches / production series are as bad as ours. I am even tempted to say they used us as guinea pigs and sold us pre-production samples. Given the fault rate what else I could conclude?
Still, i am overly disapponted with how Lenovo treated this tablet and it's launch. By the time of launch in my country, there were no specs at Lenovo site, no data sheets, no papers, nothing, void. Pure and blatant ignorance. All retailers in my area listed tablet with incomplete or downright invalid specs, like that GPS is included (it is not!), like display is 1920x1080 (it is not), like miniHDMI is present (whereas microHDM is). I blame Lenovo for not providing those specs in time and adequate precision.
That's not all. In my area Miix 2 10" is only available without dock / keyboard. Keyboard is not even purchasible separately, still not one month after the launch. No single other accessory is purchasible as well. This is just frustrating and dissapoing.
Tomas
Moderator comment: Remark(s) contravening the Community Rules removed - profanity/implied profanity. Keep it clean.

Similar Messages

  • Support warranty Lenovo Miix 2 10" Touchscreen failure

    Dear Lenovo Support!I have purchased 01 Lenovo Miix 2 form Amazon with S/N: QB08221114Now, the Touchscreen will stop respondingIn Control Panel, Device Manager show: I2C HID Device with note Yellow (picture att)I checked it in the device manager: Touchscreen is not listed under HID-Devices and the I2C HID-Device got an error I had try worked all help in topic: https://forums.lenovo.com/t5/Windows-based-Tablets/Re-Miix-2-Touchscreen-failure/td-p/1441509, it's not workingMy Lenovo Miix 2 is using in Vietnam, I had call Lenovo in Vietnam, not support Lenovo Miix 2 10". I want to Lenovo help me support warranty Miix 2. Best Regard Khanh Trinh 

    Hi
    I have a same problem
    For me it s not a touchad with this simple feature...
    Is not possible to install Synaptics Drivers (standard touchpad...)...
    It s a simple mouse device
    It s a strange technical choice, but we have a tactil screen for that... (stupid monkey engineer)
    Aida64 says; Mouse HID
    Field Value
    Mouse Properties
    Mouse Name Souris HID
    Mouse Buttons 2
    Mouse Hand Right
    Pointer Speed 1
    Double-Click Time 500 msec
    X/Y Threshold 6 / 10
    Wheel Scroll Lines 3
    Mouse Features
    Active Window Tracking Disabled
    ClickLock Disabled
    Hide Pointer While Typing Enabled
    Mouse Wheel Not Present
    Move Pointer To Default Button Disabled
    Pointer Trails Disabled
    Sonar Disabled

  • Lenovo Ideatab Miix 10 Touchscreen funtioniert nicht

    Ich habe Probleme mit dem Touchsreen vom Miix 10, er reagiert nicht mehr auf touch und gesten. Wenn ich im Geräte-Manager die beiden Treiber für I2C HID lösche geht der Touchscreen wieder, ab und zu muß ich aber neu booten. Auch meine Lautsprecher hören sich auf einmal sehr schrill an. Vieleicht wissen Sie eine Lösung dieser Probleme.
    VG Wilfried

    Hallo Wilfried,
    für das Miix 10 (nicht Miix 2 10) ist ein Firmware-Update für den Touchscreen verfügbar:
    http://support.lenovo.com/us/en/downloads/ds036944
    Fällt der Touchscreen nach Installation des Updates weiterhin aus, nimm bitte Kontakt zum Support auf, da es auch ein technisches Problem geben kann.
    Gruß - Sebastian
    → Wenn Du eine Lösung auf Deine Frage erhalten hast, markiere diese bitte als gelöst - Hilfreiche Beiträge verdienen Kudos. Zögere nicht Kudos zu vergeben.   

  • Miix 8 touchscreen issue

    Typing fast on the keyboard frequently results in strange characters, the kind that are supposed to require a press and hold to select. This issue is discussed in the following review and show around 6:10 in the video.
    http://www.techspot.com/review/779-lenovo-miix-2-8/
    Any plans to fix this lenovo?

    Lenovo hasn't done anything or made any specific updates for this device since its release, looking at the dates on its website:
    http://support.lenovo.com/en_US/downloads/detail.page?DocID=DS038319
    Rather disappointed at no support at all right after the device is released while there clearly have been problems.
    https://www.youtube.com/watch?v=4aM77rqR0KQ&t=6m9s

  • [SOLVED] Kernel 3.2.1 and USB Touchscreen Failure

    With the upgrade from linux 3.1.9 to 3.2.1, my touchscreen device is no longer recognised.
    Hoping someone may be able to shed some light on the situation.
    Here are my Xorg logs for both kernels:
    http://home.exetel.com.au/padfoot/logs/xorg.log.3.1.9
    http://home.exetel.com.au/padfoot/logs/xorg.log.3.2.1
    xinput list for 3.1.9
    ⎡ Virtual core pointer id=2 [master pointer (3)]
    ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
    ⎜ ↳ SONiX USB Keyboard id=12 [slave pointer (2)]
    ⎜ ↳ eGalaxTouch Virtual Device for Multi id=14 [slave pointer (2)]
    ⎜ ↳ eGalaxTouch Virtual Device for Single id=15 [slave pointer (2)]
    ⎣ Virtual core keyboard id=3 [master keyboard (2)]
    ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
    ↳ Power Button id=6 [slave keyboard (3)]
    ↳ Video Bus id=7 [slave keyboard (3)]
    ↳ Power Button id=8 [slave keyboard (3)]
    ↳ 1.3M Rear id=9 [slave keyboard (3)]
    ↳ 1.3M Front id=10 [slave keyboard (3)]
    ↳ SONiX USB Keyboard id=11 [slave keyboard (3)]
    ↳ AT Translated Set 2 keyboard id=13 [slave keyboard (3)]
    xinput list for 3.2.1
    ⎡ Virtual core pointer id=2 [master pointer (3)]
    ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
    ⎜ ↳ SONiX USB Keyboard id=12 [slave pointer (2)]
    ⎣ Virtual core keyboard id=3 [master keyboard (2)]
    ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
    ↳ Power Button id=6 [slave keyboard (3)]
    ↳ Video Bus id=7 [slave keyboard (3)]
    ↳ Power Button id=8 [slave keyboard (3)]
    ↳ 1.3M Rear id=9 [slave keyboard (3)]
    ↳ 1.3M Front id=10 [slave keyboard (3)]
    ↳ SONiX USB Keyboard id=11 [slave keyboard (3)]
    ↳ AT Translated Set 2 keyboard id=13 [slave keyboard (3)]
    ↳ Acer WMI hotkeys id=14 [slave keyboard (3)]
    dmesg extract for 3.1.9
    [ 4.920911] input: eGalax Inc. USB TouchController as /devices/pci0000:00/0000:00:13.0/usb5/5-1/5-1:1.0/input/input10
    [ 4.923565] generic-usb 0003:0EEF:7302.0001: input,hiddev0,hidraw0: USB HID v2.10 Pointer [eGalax Inc. USB TouchController] on usb-0000:00:13.0-1/input0
    [ 7.701218] input: eGalaxTouch Virtual Device for Multi as /devices/virtual/input/input13
    [ 7.701692] input: eGalaxTouch Virtual Device for Single as /devices/virtual/input/input14
    dmesg extract for 3.2.1
    [ 3.853443] usb 5-1: new full-speed USB device number 2 using ohci_hcd
    [ 3.990164] usb 5-1: device descriptor read/64, error -62
    [ 4.226771] usb 5-1: device descriptor read/64, error -62
    [ 4.460091] usb 5-1: new full-speed USB device number 3 using ohci_hcd
    [ 4.593421] usb 5-1: device descriptor read/64, error -62
    [ 4.830326] usb 5-1: device descriptor read/64, error -62
    [ 5.063660] usb 5-1: new full-speed USB device number 4 using ohci_hcd
    [ 5.470315] usb 5-1: device not accepting address 4, error -62
    [ 5.600320] usb 5-1: new full-speed USB device number 5 using ohci_hcd
    [ 6.006989] usb 5-1: device not accepting address 5, error -62
    [ 6.256982] usb 5-5: new full-speed USB device number 6 using ohci_hcd
    Holding off on upgrading to kernel 3.2 until this can be resolved
    Appreciate your help.
    Cheers.
    Last edited by Padfoot (2012-01-21 01:35:03)

    Ok, I have the solution. Multitouch is now working with kernel 3.2.1. It seems the kernel devs are separating multitouch devices from the generic input stack as they can cause issues. Here is the reply I got from the linux-input mailing list:
    Well, many eGalax devices are multitouch devices, and can not be
    handled by the generic input hid layer without having strange issues.
    We have a patch in 3.2 that auto detect such devices and release them
    from the generic input stack.
    Then, it's easier for people to handle the devices through
    hid-multitouch as the recompilation of the kernel is not required
    anymore.
    I also submitted a patch to catch multitouch devices in
    hid-multitouch, but it has not been accepted as it would require
    everybody to load hid-multitouch for every hid device.
    To enable your device, do (as root)
    # modprobe hid-multitouch
    # echo 3 VID PID 104 >
    /sys/module/hid_multitouch/drivers/hid\:hid-multitouch/new_id
    where:
    - 3 is the bus, usb here
    - VID: vendor ID (must be 0eef in your case)
    - PID: product ID
    - 104 is the number of the right class of multitouch device to use
    (see MT_CLS_* definitions in hid-multitouch)
    VID/PID  can be retrieved from lsusb.
    If it's working, then you should also give us your PID so that we can
    add it in the source of hid-multitouch.
    So, I did the following to enable multitouch:
    1. Before upgrading your kernel (should also work after, but may as well be prepared):
    # lsusb
    Bus 005 Device 002: ID 0eef:7302 D-WAV Scientific Co., Ltd
    VID is 0eef
    PID is 7302
    2. Now we need to get the MT_CLS_* definition for our device (extracted from http://lxr.free-electrons.com/source/dr … titouch.c)
    86
    87 /* classes of device behavior */
    88 #define MT_CLS_DEFAULT 0x0001
    89
    90 #define MT_CLS_SERIAL 0x0002
    91 #define MT_CLS_CONFIDENCE 0x0003
    92 #define MT_CLS_CONFIDENCE_MINUS_ONE 0x0004
    93 #define MT_CLS_DUAL_INRANGE_CONTACTID 0x0005
    94 #define MT_CLS_DUAL_INRANGE_CONTACTNUMBER 0x0006
    95 #define MT_CLS_DUAL_NSMU_CONTACTID 0x0007
    96
    97 /* vendor specific classes */
    98 #define MT_CLS_3M 0x0101
    99 #define MT_CLS_CYPRESS 0x0102
    100 #define MT_CLS_EGALAX 0x0103
    101
    I have an eGalax device, so I need MT_CLS_* = 0x0103 (259 in decimal)
    3. We have all we need to set up the device. Install kernel 3.2.1
    # pacman -S linux
    4. Start the hid-multitouch module on boot
    # nano /etc/rc.conf
    # HARDWARE
    # MODULES: Modules to load at boot-up. Blacklisting is no longer supported.
    # Replace every !module by an entry as on the following line in a file in
    # /etc/modprobe.d:
    # blacklist module
    # See "man modprobe.conf" for details.
    MODULES=(hid-multitouch)
    Now reboot to see if your device is auto configured with the hid-multitouch module. If so, you are all good to go. If not, continue as follows:
    5. Ensure your device details are passed to the hid-multitouch module
    # nano /etc/rc.local
    echo 3 0eef 7302 259 > /sys/module/hid_multitouch/drivers/hid\:hid-multitouch/new_id
    The command above contains my device details, replace with your details obtained from steps 1 & 2 above:
    echo 3 VID PID MT_CLS_*
    (If someone can point me in a better direction for setting up these details at boot, it would be appreciated)
    Reboot again to see if the device is now working. If not, you may need binary drivers from the vendor. I know in my case, my device needs the eGalax touch daemon driver. A package for this is available in the AUR https://aur.archlinux.org/packages.php?ID=55050
    Of course, as the email states, if you have a device that is not automatically configured with the hid-multitouch module, yet it does work after step 5, submit your device details to the linux-input mailing list so it may be added to the source.
    Cheers.
    Last edited by Padfoot (2012-01-21 01:34:42)

  • Miix 2 10 Touchscreen funktioinert plötzlich nicht mehr

    Hallo,
    bin seit einigen Tagen Besitzer eines Lenovo Miix 2 10. Bios-Version: 95CN12WW, Date: 25.12.2013
    Bisher kam es 2 mal zu dem Problem, das plötzlich der Touchscreen nicht mehr funktioinert. (Touchscreen Unresponsive)
    Hier hilft dann nur ein Neustart, dann funktioinert der Touchscreen auch wieder ordnungsgemäß.
    Maus und Tastatur funktioineren in dem Fall nach wie vor normal, Windows lässt sich hiermit dann normal bedienen. (keine Performanceeinbrüche zu erkennen, etc.) Die Windows-Taste am Touscreen funktioniert auch noch, allerdings kommt man hiermit ja nur wieder ins Metro-Startmenü.
    Irgendwo habe ich gelesen das auch andere User ähnliche Probleme mit dem Touchscreen haben und hier via Software/Treiberupdates nachgebessert werden kann und das es kein HW-Problem ist.
    Noch kann ich damit leben, da es bei mir bisher erst 2 mal aufgetreten ist und hoffe das die Häufigkeit des Auftretens nicht zunimmt.
    Haben andere User vlt. ähnliche Probleme festgestellt?
    VG,
    Bernd

    Hi,
    um Mojoscosco aus dem emgl.sprachrigen Community-Thread, wo die gleichen Probleme gemeldet werden,
    http://forums.lenovo.com/t5/Idea-Windows-based-Tablets-and/Miix-2-Touchscreen-failure/td-p/1419889/p...
    zu zitieren:
    I am having an identical problem with the Miix 2 10 I just received. The Touchscreen will stop responding but a driver reset will get it back 100% of the time. Unfortunately I can easily get it to stop responding again by wailing on the OS keyboard or playing a game. This seems like a software issue (likely firmware or BIOS) but I am returning the unit and getting a new one to try and rule out hardware issues. Also, I am happy to make such a catastrophic quality control issue as costly as possible for Lenovo. Hopefully there will be drivers or firmaware posted soon to update this but in the mean time I hope they like shipping brand new hardware, free of charge, ad infinitum.
    Dem kann ich (bis auf eine kleine Ausnahme, siehe Durchstreichung) nur zustimmen!
    Mit dem Spiel "Jetpack Joyride" (Freeware aus dem Microsoft Store) kann ich den Touchscreen freeze noch schneller und jederzeit reproduzieren
    Deaktivieren und Aktivieren des Gerätest (der Touchscreen Device/Driver) im Geräte-Manager erweckt den Touchscreen wieder zum Leben. (manchmal muss man diese Wiederbelebung auch mehrmals hintereinander durchführen)
    Wann wird das endlich eingestanden und behoben?

  • Notebook Touchscreen is non responsive

    There is NO title "HID-Compliant Touch Screen" under "Human Interface Devices".
    Human Interface Devices: 
                    - HID-Compliant wireless radio controls
                    - HP Wireless Button Driver
                    - USB Input Device
    That is it.  NO "HID-Compliant Touch Screen" at all.
    Scan for hardware changes (right click on the Human Interface Devices) doesn't help.
    Please help to get back my touch screen.
     

    V720 wrote:
    Actually, the touch screen is turned on and off from time to time (mostly it's off).
    Could it be mechanical issue?It could be an issue caused by an imperfect connection at the systemboard header or the touchscreen itself. The diagnostic code you provided tells me there is indeed an actual  i/o device (touchscreen) failure.  Failure code 80C Is your notebook still in warranty?Check your warranty status Here. I would use warranty service to have the issue taken care of. The failure error message from the Touch screen test means it is definitely a hardware issue even f it is intermittent. I will ask to have your issue escalated. Done! Please advise whomever from HP contacts you by PM of the exact error message from the test. 

  • Touch Screen Failures

    Apparently, the touchscreens on the iPhones are starting to fail for a lot of people. Mine failed yesterday (the bottom 1/4 stopped responding) so I took it into an Apple store and they said they'd replace it in 1 to 5 days. At my store, they said they're starting to get a bunch in that are failing and when I searched on the 'net I see a lot of reports but couldn't find any official acknowledgement by Apple as to the issue.
    Does anybody hear have anything definitive about touchscreen failures and how Apple plans to address them moving forward?

    Max is the NI interface for all the drivers. It may be a specific driver that is causing problems, perhaps NI-VISA. I would try installing things one piece at a time. Might want to start by uninstalling everything so that you start with a clean system. First install LabVIEW with no drivers at all. See if the Micro touch screen still works. Then try installing NI-DAQ. Install each of the drivers you need one at a time. If you don't need something, leave it out.

  • Droid 2 Keyboard Issues

    Bottom line, the Droid 2 is just a POC.  Motorola, Verizon, and the Droid OS, as well as D2 owners here on this site seem content to "just clear the keyboard cache" when the keyboard acts up instead of Motorola and/or Droid OS actually correcting the problem with a long term fix.  For as much as we pay for this phone (and the loaded OS), we should not have to do a Kabuki dance every month or so when the keyboard cache interferes with the function of the keyboard.  It is total ****  And the same goes with the systemic touchscreen failure where the outer edges of the touchscreen fails to function.  And Verizon's answer is "we'll send you a refurbished one just like it and you can return the one that isn't working".  Does that really solve anything?  All you are getting is the same POC phone/OS that nobody has solved the problems it has.  As soon as my contract is up for this POC, I'm switching to the Iphone OS.  I don't know any of my friends who own an Iphone that have these systematic OS troubles like the Droid OS.

    Bottom line, the Droid 2 is just a POC.  Motorola, Verizon, and the Droid OS, as well as D2 owners here on this site seem content to "just clear the keyboard cache" when the keyboard acts up instead of Motorola and/or Droid OS actually correcting the problem with a long term fix.  For as much as we pay for this phone (and the loaded OS), we should not have to do a Kabuki dance every month or so when the keyboard cache interferes with the function of the keyboard.  It is total ****  And the same goes with the systemic touchscreen failure where the outer edges of the touchscreen fails to function.  And Verizon's answer is "we'll send you a refurbished one just like it and you can return the one that isn't working".  Does that really solve anything?  All you are getting is the same POC phone/OS that nobody has solved the problems it has.  As soon as my contract is up for this POC, I'm switching to the Iphone OS.  I don't know any of my friends who own an Iphone that have these systematic OS troubles like the Droid OS.

  • Yoga 2 Pro: boot failure and touchscreen unresponsive

    I've had my Yoga 2 for about a week and a half and for the most part I love it. First problem has been occasional (maybe 4-5 times) "Boot Failure", or something along those lines, on startup. Every time after restarting it it has worked fine. Also just earlier today I had a problem where the touchscreen went unresponsive for around 20 minutes before working fine again. I was in class so didn't do anything to try to fix it (taking notes so couldn't restart or anything), and it just starting working again by itself. Other than this, I have had no other problems. I have a few days left on my return/exchange with Best Buy, so wondering if these are problems that I should be seriously concerned about. Thanks.

    If it were me, I would definitely exchange it. Boot failure may indicate some permanent failure about to happen, not to mention a flakey touch screen. Neither sounds like a software issue on a brand new computer.

  • Miix 2 8" unresponsive touchscreen

    The tablet sometimes has an unresponsive touchscreen. Waiting for it for 5 minutes sometimes makes it stop. The touchscreen also sometimes thinks it's being touched: with the Windows u lock screen requiring a swipe up, the screen doesn't respond to that fluidly. (And thus can't be unlocked since the screen isn't being flinged.) This also requires a reboot to fix.
    Semi related is the touchscreen recognizing fast taps across the screen as swipes, for example, when typing. This switches apps and its annoying. This faulty behavior is consistent and doesn't do away with a reboot.
    Lenovo, these problem appears to be widespread, with another person on this forum having the typing issue, as well as a reviewer. The said reviewer also has had troubles with the unresponsive touchscreen and reported it persisting after having requested another sample. Please fix the touchscreen issue. It makes the device unusable.

    There hasn't been a solution yet, however, I have found the culprit, using a separate keyboard and mouse to navigate the tablet. System reports no touch input devices being found.Windows Device Manager reports the one of the I2C HID devices to have stopped working. Uninstalling this driver and rescanning for new hardware re-activates the touchscreen. I don't know why it doesn't work when it has crashed, even in BIOS. Since this problem can be resolved in software and affects non-Windows components, I think it is possible to make a driver patch or firmware patch for this problem. The problem is hard to reproduce since it occurs randomly, but once it occurs it usually persists for an uncertain time. Temperature might seem to have influence on it, since picking it up in the morning sometimes gives this problem, but more often, when I am commuting, this problem occurs. Because of this, I'm hesitant to contact customer support and since it apparently appears throughout other devices, I am fairly certain a new tablet won't fix it, unless it's a new iteration. Summary - the touchscreen can be re-activated inside Windows by uninstaling the faulty I2C HID driver (with the warning icon) and rescanning for hardware, but it's not a permanent solution and merely a workaround for people who happen to own a USB-OTG cable.

  • Miix 2 8 screen freeze/driver failure

    Hi,
    I and like many others have been having issues with the been freezing and requiring a force reset to get things moving again.
    I have found the same fault every time.
    Can anyone tell me what th "I2C HID DEVICE" is? I have absolutely no idea what this driver is for but it always seems to have the little yellow exclamation mark next to it.
    I have uninstalled the driver and windows fixed it like it should but I am wondering if this is going to have any other ramifications.
    So  any techies could let me know what this is it would be greatly appreciated!

    Having factory reset the item continues with the same problems. It is being boxed up and sent back for repair. 

  • Failures on keyboard and touchscreen

    Good evening, members of this marvellous forum! My Xperia Z3 Compact is a problem with the keyboard, apparently after I performed the download of  some themes for this phone. Actually, It was after the download that I began to realize this problem. Sometimes, when I'm writing or I delete something I wrote, the phone activates a writing mode, which allows you to use only the keyboard by dragging the characters with your finger, as if I were doing this gesture, but in a way totally crazy. If I lock the phone and then unlock it, the touch does not work properly. How to solve this batch of problems?

    Don't forget to backup
    Alternatives on How to backup Xperias
    http://talk.sonymobile.com/thread/36355
    "I'd rather be hated for who I am, than loved for who I am not." Kurt Cobain (1967-1994)

  • Hello, the perennial question on getting the Touchsmart touchscreen to work with WIndows 7

    My IQ526 touchscreen does not work after upgrading to Win 7 Ultimate, using the upgrade software provided by HP.
    I have a good installation of Win 7, diagnostics run fine, and installed the touchscreen drivers from the HP website in the recommonded order.
    The Touchsmart software seems to be installed OK, and the screen "pings" when touched, but the touchscreen functionality does not work.
    Any ideas on where I go from here, please?
    Thank you.

    CoburnStreet wrote:
    My IQ526 touchscreen does not work after upgrading to Win 7 Ultimate, using the upgrade software provided by HP.
    I have a good installation of Win 7, diagnostics run fine, and installed the touchscreen drivers from the HP website in the recommonded order.
    The Touchsmart software seems to be installed OK, and the screen "pings" when touched, but the touchscreen functionality does not work.
    Any ideas on where I go from here, please?
    Thank you.
    hey Coburn,  if you've done all of that ... it's either a touch failure or some type of software failure.  have you tried performing a system recovery?  if it works after the system  recovery then it's like a software problem but if it doesn't, it's a hardware problem.  at that point you should contact HP.

  • How can I resolve a Keypad: Sensor communication failure ?

    My Xfinity Home security system has been reporting a Keypad: Sensor communication failure message, and I can n ot arm or disarm the system with the keypad. It works fine if I use the touchscreen.Does anyone know any DIY ways to resolve this problem?Thanks,Jack

    Hi dkreil,
    Please refer the KB : http://helpx.adobe.com/x-productkb/global/digital-certificate-revoked-aam.html
    Regards,
    Ravi.

Maybe you are looking for