DV6-1030US paint coming off left touchpad button

A small rice-sized irregular piece of the chrome paint has come off the plastic left button after only two months. It's not a nice smooth wear spot but with rough edges and is annoying.
I know it's just a cosmetic problem but it seems that the coating should not be coming off a two-month-old laptop that cost $700.
After about 90 minutes with HP Online Chat (who actually suggested I bring it in to the local Wal-mart for some reason !?), the Chat guy gave me a phone number and I talked with a Mumbai-based tech who was only willing to write up a service order for me to send it in which would entail unacceptable loss of use, risk of damage and the shipping expense.  
I don't understand why they can't just send a new button cover. It would be cheaper than having me send in a functional laptop for a simple cosmetic repair. With 25 years of hardware & software development, I could easily change the part myself. If anyone has any clue as to how to get a replacement cover (even at my own expense), please let me know.
Meanwhile, I'll continue to be dismayed at the lack of common sense exhibited in my dealings with corporate America. 
Cheers,
-pc 

You're welcome! If there is anything else we can assist with, let us know!
*Remember to mark your questions solved and click the "Kudos" star to show your thanks!

Similar Messages

  • HP Pavilion DV6-1264CA Artist Edition 2 left touchpad button is screwed up

    I'm a proud owner of an Artist Edition DV6 laptop, but a few months ago the left touchpad button suffered a bit of a failure. Through normal use, the left side of the left button (the one you use to click on just about everything) seems to have broken down. I am not familiar with the inner workings of this device, but it feels like there are two underlying supports that hold the button up and allow it to be clicked down on, one on each side of the button.
    A while ago, the left side of the button started squeaking while clicking, and now it sags down, and the button can be rocked from side to side. The right side of the button is still up, and it now sits on a slant. Visually it is just a minor annoyance, but what is driving me batty is that now the button essentially "clicks" on its own. It can still be used normally, but often the button will click multiple times within a fraction of a second. I only use the laptop for entertainment, but it's still annoying as hell, especially when playing games where unintended clicking can lead to irreversible actions.
    I have looked into the HP catalog for repair parts, but as other Artist Edition owners have discovered, there are no specific parts for the AE model, and the only relevant part is a complete touchpad with the whole palm rest attached to it. Of course, the palm rest doesn't have the Artist Edition graphics on it, which I absolutely intend to keep.
    So I was wondering, if i can locate another palm rest with the touchpad, is the touchpad transferrable to my palm rest? Or is it inseparable? Are all DV6 touchpads the same? Or alternately, if I disassemble my touchpad, what are the chances that it is repairable? Maybe something just popped out of place?
    Oh, and before you ask, the laptop is out of warranty, and I'm not sure I trust the clowns at Best Buy to be able to fix it, and to do so in a timely manner. I'd rather explore all options and see if I can fix it myself first.
    Any help would be appreciated.
    Thanks,
    Phil

    Does anybody have any input? I see tons of sellers selling HP DV6 parts on eBay, I just need to know if I can swap over a touchpad from one palmrest to another, and if all touchpads are the same in the DV6-7 range.

  • Laptop paint coming off around touchpad

    Hi, I have an HP 1a30us and the warranty ran out about 2 months ago.  Right before the warranty ended, I had the laptop sent in to be fixed because the paint around the touchpad area kept chipping off. When I got it back, the parts where the paint had came off were gone and it looked like they replaced those parts. 
    Within the first couple weeks that I got it back repaired, the paint started chipping of again, and in the same area. I'm not using the touchpad area it with long, sharp fingernails or anything, just normal use, so I can't understand how the paint keeps chipping off.  It would be great if HP could repair it again even though its out of warranty, because its the same problem I had before, and it hasn't stayed fix.
    Thanks.

    Is it on the right button, too? It is happening right where you touch it the most, but should be able to withstand normal wear. But replacing those parts is expensive and likely not worth it unless there is a functional issue.

  • Paint coming off Compaq Touchpad

    Hello
    Ive had my Compaq Presario CQ60-203NR Notebook for more than a year, and only in the last few months have I noticed a small spot on my touchpad get bigger. It seems to be in the same place that I touch, so I understand it's wear and tear. I was wondering if there's anything I can do to cover/fix/protect it?
    Thank You
    This question was solved.
    View Solution.

    Wear and tear, you could get a replacement top cover.
    ________________________________________________________________________________________________________ I Love Kudos! If you feel my post has helped you please click the White Kudos! Star just below my name
    If you feel my answer has fixed your problem please click 'Mark As Solution' and make it easier for others to find help quickly

  • Paint coming off black iPhone 5

    Hi i have black iphone 5 and been in a case since i bought it in sept 2012 & after reading this forum i checked mine and the paint is all off edges front & rear
    What Are My Chances Of Getting It Exchanged It Looks like A 5yr old phone ,i have iphone 3 & 4 and they dont have a mark lol any help welcome

    Waist of my Time ,Why Tell You Over Phone Ooh That Not Right make You Appointment To Visit Apple Store .
    On Arrival I Was Met With Rep At Door ,And She Said What A Nice Case You Have On Your Phone .
    Then Manager Met Me And Said Did You Read Apples Report On Nov 2012  About Paint Coming Off , I Said No ,She Then Said Apple Are Not Covering This Cosmetic Defect As The Are Calling It Normal Ware And Tare
    I Advised Her We Are Supposed To Be Advancing Forward Not Going Back ,If A 5yr Old Phone Looks Better Than A 5 Month Old Phone.
    I Showed Her My First Iphone 3 Without A Mark To Prove I Look After My Phone ,She Then Said It Was My Case , I Showed Her Mi Wife's White Phone Same cover Without A Mark On it ,
    She Just Told Me There's Nothing I Can Do She Is Not Replacing It And To E-mail Complaint To Apple If I Want But It Wont Get Me Anywhere .
    Last Penny Apple Will Get Off Me
    I Thing Samsung Have Right Idea Stick To Plastic Case's

  • Curve w/ paint coming off return key and call key

    curve w/ paint coming off return key and call key...anyone else? i don't think being 6 mo old it should look yrs old! by the way u have to replace the intermediate board...
    o z
    oz
    in god we trust
    god bless the world

    Nope, mines good! IF you have time on warranty maybe a replacement?
    Just a thought.
    Click Accept as Solution for posts that have solved your issue(s)!
    Be sure to click Like! for those who have helped you.
    Install BlackBerry Protect it's a free application designed to help find your lost BlackBerry smartphone, and keep the information on it secure.

  • Left touchpad button delay in web browsers

    I'm at a loss to figure out what could be causing my left button on my touchpad to delay intermittently. On both Google Chrome (whether stable, beta or dev) and Firefox, the left button when pressed may not respond for up to a few seconds. This is most noticeable when using Google Street View and Google Maps, which refuse to change viewpoint when holding down the left button. It isn't a Flash fault because there is also a delay when highlighting text.
    I can rule out the possibility of any hardware fault as the left button on the touchpad works fine elsewhere, within KDE (ie. drag and dropping works without delay or fault) and other applications.
    Output of my X log:
    [ 5.365]
    X.Org X Server 1.14.1
    Release Date: 2013-04-17
    [ 5.365] X Protocol Version 11, Revision 0
    [ 5.365] Build Operating System: Linux 3.8.7-1-ARCH x86_64
    [ 5.365] Current Operating System: Linux TGHE 3.8.10-1-ARCH #1 SMP PREEMPT Sat Apr 27 12:36:59 CEST 2013 x86_64
    [ 5.365] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=99d5896f-0144-4c5c-8c54-c11229ef01eb ro quiet
    [ 5.365] Build Date: 17 April 2013 02:37:06PM
    [ 5.365]
    [ 5.365] Current version of pixman: 0.28.2
    [ 5.365] Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    [ 5.365] Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    [ 5.365] (==) Log file: "/var/log/Xorg.0.log", Time: Sun Apr 28 21:34:03 2013
    [ 5.367] (==) Using config directory: "/etc/X11/xorg.conf.d"
    [ 5.368] (==) No Layout section. Using the first Screen section.
    [ 5.368] (==) No screen section available. Using defaults.
    [ 5.368] (**) |-->Screen "Default Screen Section" (0)
    [ 5.368] (**) | |-->Monitor "<default monitor>"
    [ 5.368] (==) No monitor specified for screen "Default Screen Section".
    Using a default monitor configuration.
    [ 5.368] (==) Automatically adding devices
    [ 5.368] (==) Automatically enabling devices
    [ 5.368] (==) Automatically adding GPU devices
    [ 5.369] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
    [ 5.369] Entry deleted from font path.
    [ 5.370] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
    [ 5.371] Entry deleted from font path.
    [ 5.371] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
    [ 5.371] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
    [ 5.371] Entry deleted from font path.
    [ 5.371] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
    [ 5.371] (==) FontPath set to:
    /usr/share/fonts/misc/,
    /usr/share/fonts/TTF/,
    /usr/share/fonts/Type1/
    [ 5.371] (==) ModulePath set to "/usr/lib/xorg/modules"
    [ 5.371] (II) The server relies on udev to provide the list of input devices.
    If no devices become available, reconfigure udev or disable AutoAddDevices.
    [ 5.371] (II) Loader magic: 0x7fcc20
    [ 5.371] (II) Module ABI versions:
    [ 5.371] X.Org ANSI C Emulation: 0.4
    [ 5.371] X.Org Video Driver: 14.1
    [ 5.371] X.Org XInput driver : 19.1
    [ 5.371] X.Org Server Extension : 7.0
    [ 5.373] (--) PCI:*(0:1:0:0) 10de:0dcd:1028:04b7 rev 161, Mem @ 0xd4000000/16777216, 0xc0000000/268435456, 0xd0000000/33554432, I/O @ 0x00004000/128, BIOS @ 0x????????/524288
    [ 5.498] Initializing built-in extension Generic Event Extension
    [ 5.498] Initializing built-in extension SHAPE
    [ 5.498] Initializing built-in extension MIT-SHM
    [ 5.498] Initializing built-in extension XInputExtension
    [ 5.498] Initializing built-in extension XTEST
    [ 5.498] Initializing built-in extension BIG-REQUESTS
    [ 5.498] Initializing built-in extension SYNC
    [ 5.498] Initializing built-in extension XKEYBOARD
    [ 5.498] Initializing built-in extension XC-MISC
    [ 5.498] Initializing built-in extension SECURITY
    [ 5.498] Initializing built-in extension XINERAMA
    [ 5.498] Initializing built-in extension XFIXES
    [ 5.498] Initializing built-in extension RENDER
    [ 5.498] Initializing built-in extension RANDR
    [ 5.498] Initializing built-in extension COMPOSITE
    [ 5.498] Initializing built-in extension DAMAGE
    [ 5.498] Initializing built-in extension MIT-SCREEN-SAVER
    [ 5.498] Initializing built-in extension DOUBLE-BUFFER
    [ 5.498] Initializing built-in extension RECORD
    [ 5.498] Initializing built-in extension DPMS
    [ 5.498] Initializing built-in extension X-Resource
    [ 5.498] Initializing built-in extension XVideo
    [ 5.498] Initializing built-in extension XVideo-MotionCompensation
    [ 5.498] Initializing built-in extension XFree86-VidModeExtension
    [ 5.498] Initializing built-in extension XFree86-DGA
    [ 5.498] Initializing built-in extension XFree86-DRI
    [ 5.498] Initializing built-in extension DRI2
    [ 5.498] (II) LoadModule: "glx"
    [ 5.499] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
    [ 5.560] (II) Module glx: vendor="NVIDIA Corporation"
    [ 5.560] compiled for 4.0.2, module version = 1.0.0
    [ 5.560] Module class: X.Org Server Extension
    [ 5.560] (II) NVIDIA GLX Module 313.30 Wed Mar 27 15:51:21 PDT 2013
    [ 5.560] Loading extension GLX
    [ 5.560] (==) Matched nouveau as autoconfigured driver 0
    [ 5.560] (==) Matched nvidia as autoconfigured driver 1
    [ 5.560] (==) Matched nv as autoconfigured driver 2
    [ 5.560] (==) Matched vesa as autoconfigured driver 3
    [ 5.560] (==) Matched modesetting as autoconfigured driver 4
    [ 5.560] (==) Matched fbdev as autoconfigured driver 5
    [ 5.560] (==) Assigned the driver to the xf86ConfigLayout
    [ 5.560] (II) LoadModule: "nouveau"
    [ 5.562] (WW) Warning, couldn't open module nouveau
    [ 5.562] (II) UnloadModule: "nouveau"
    [ 5.562] (II) Unloading nouveau
    [ 5.562] (EE) Failed to load module "nouveau" (module does not exist, 0)
    [ 5.562] (II) LoadModule: "nvidia"
    [ 5.563] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
    [ 5.569] (II) Module nvidia: vendor="NVIDIA Corporation"
    [ 5.569] compiled for 4.0.2, module version = 1.0.0
    [ 5.569] Module class: X.Org Video Driver
    [ 5.570] (II) LoadModule: "nv"
    [ 5.571] (WW) Warning, couldn't open module nv
    [ 5.571] (II) UnloadModule: "nv"
    [ 5.571] (II) Unloading nv
    [ 5.571] (EE) Failed to load module "nv" (module does not exist, 0)
    [ 5.571] (II) LoadModule: "vesa"
    [ 5.571] (WW) Warning, couldn't open module vesa
    [ 5.571] (II) UnloadModule: "vesa"
    [ 5.571] (II) Unloading vesa
    [ 5.571] (EE) Failed to load module "vesa" (module does not exist, 0)
    [ 5.571] (II) LoadModule: "modesetting"
    [ 5.571] (WW) Warning, couldn't open module modesetting
    [ 5.571] (II) UnloadModule: "modesetting"
    [ 5.571] (II) Unloading modesetting
    [ 5.571] (EE) Failed to load module "modesetting" (module does not exist, 0)
    [ 5.571] (II) LoadModule: "fbdev"
    [ 5.571] (WW) Warning, couldn't open module fbdev
    [ 5.571] (II) UnloadModule: "fbdev"
    [ 5.571] (II) Unloading fbdev
    [ 5.571] (EE) Failed to load module "fbdev" (module does not exist, 0)
    [ 5.571] (II) NVIDIA dlloader X Driver 313.30 Wed Mar 27 15:33:21 PDT 2013
    [ 5.571] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
    [ 5.572] (++) using VT number 7
    [ 5.596] (II) Loading sub module "wfb"
    [ 5.596] (II) LoadModule: "wfb"
    [ 5.596] (II) Loading /usr/lib/xorg/modules/libwfb.so
    [ 5.597] (II) Module wfb: vendor="X.Org Foundation"
    [ 5.597] compiled for 1.14.1, module version = 1.0.0
    [ 5.597] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 5.597] (II) Loading sub module "ramdac"
    [ 5.597] (II) LoadModule: "ramdac"
    [ 5.597] (II) Module "ramdac" already built-in
    [ 5.598] (II) NVIDIA(0): Creating default Display subsection in Screen section
    "Default Screen Section" for depth/fbbpp 24/32
    [ 5.598] (==) NVIDIA(0): Depth 24, (==) framebuffer bpp 32
    [ 5.598] (==) NVIDIA(0): RGB weight 888
    [ 5.598] (==) NVIDIA(0): Default visual is TrueColor
    [ 5.598] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
    [ 5.599] (**) NVIDIA(0): Enabling 2D acceleration
    [ 6.276] (WW) NVIDIA(GPU-0): Unable to read EDID for display device DFP-2
    [ 6.283] (II) NVIDIA(0): NVIDIA GPU GeForce GT 555M (GF106) at PCI:1:0:0 (GPU-0)
    [ 6.283] (--) NVIDIA(0): Memory: 3145728 kBytes
    [ 6.283] (--) NVIDIA(0): VideoBIOS: 70.06.32.00.03
    [ 6.283] (II) NVIDIA(0): Detected PCI Express Link width: 16X
    [ 6.521] (--) NVIDIA(0): Valid display device(s) on GeForce GT 555M at PCI:1:0:0
    [ 6.521] (--) NVIDIA(0): DFP-0
    [ 6.521] (--) NVIDIA(0): DFP-1
    [ 6.521] (--) NVIDIA(0): LGD (DFP-2) (connected)
    [ 6.521] (--) NVIDIA(0): DFP-3
    [ 6.521] (--) NVIDIA(0): DFP-0: 165.0 MHz maximum pixel clock
    [ 6.521] (--) NVIDIA(0): DFP-0: Internal Single Link TMDS
    [ 6.521] (--) NVIDIA(0): DFP-1: 165.0 MHz maximum pixel clock
    [ 6.521] (--) NVIDIA(0): DFP-1: Internal Single Link TMDS
    [ 6.521] (--) NVIDIA(0): LGD (DFP-2): 480.0 MHz maximum pixel clock
    [ 6.521] (--) NVIDIA(0): LGD (DFP-2): Internal DisplayPort
    [ 6.521] (--) NVIDIA(0): DFP-3: 480.0 MHz maximum pixel clock
    [ 6.521] (--) NVIDIA(0): DFP-3: Internal DisplayPort
    [ 6.521] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 6.521] (**) NVIDIA(0): device LGD (DFP-2) (Using EDID frequencies has been
    [ 6.521] (**) NVIDIA(0): enabled on all display devices.)
    [ 6.530] (==) NVIDIA(0):
    [ 6.530] (==) NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select"
    [ 6.530] (==) NVIDIA(0): will be used as the requested mode.
    [ 6.530] (==) NVIDIA(0):
    [ 6.530] (II) NVIDIA(0): Validated MetaModes:
    [ 6.530] (II) NVIDIA(0): "DFP-2:nvidia-auto-select"
    [ 6.530] (II) NVIDIA(0): Virtual screen size determined to be 1920 x 1080
    [ 6.534] (--) NVIDIA(0): DPI set to (128, 130); computed from "UseEdidDpi" X config
    [ 6.535] (--) NVIDIA(0): option
    [ 6.535] (--) Depth 24 pixmap format is 32 bpp
    [ 6.535] (II) NVIDIA: Using 3072.00 MB of virtual memory for indirect memory
    [ 6.535] (II) NVIDIA: access.
    [ 6.637] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
    [ 6.637] (II) NVIDIA(0): may not be running or the "AcpidSocketPath" X
    [ 6.637] (II) NVIDIA(0): configuration option may not be set correctly. When the
    [ 6.637] (II) NVIDIA(0): ACPI event daemon is available, the NVIDIA X driver will
    [ 6.637] (II) NVIDIA(0): try to use it to receive ACPI event notifications. For
    [ 6.637] (II) NVIDIA(0): details, please see the "ConnectToAcpid" and
    [ 6.637] (II) NVIDIA(0): "AcpidSocketPath" X configuration options in Appendix B: X
    [ 6.637] (II) NVIDIA(0): Config Options in the README.
    [ 6.657] (II) NVIDIA(0): Setting mode "DFP-2:nvidia-auto-select"
    [ 6.747] Loading extension NV-GLX
    [ 6.788] (==) NVIDIA(0): Disabling shared memory pixmaps
    [ 6.788] (==) NVIDIA(0): Backing store disabled
    [ 6.788] (==) NVIDIA(0): Silken mouse enabled
    [ 6.789] (==) NVIDIA(0): DPMS enabled
    [ 6.789] Loading extension NV-CONTROL
    [ 6.789] Loading extension XINERAMA
    [ 6.789] (II) Loading sub module "dri2"
    [ 6.789] (II) LoadModule: "dri2"
    [ 6.789] (II) Module "dri2" already built-in
    [ 6.789] (II) NVIDIA(0): [DRI2] Setup complete
    [ 6.789] (II) NVIDIA(0): [DRI2] VDPAU driver: nvidia
    [ 6.789] (--) RandR disabled
    [ 6.794] (II) Initializing extension GLX
    [ 6.891] (II) config/udev: Adding input device Power Button (/dev/input/event4)
    [ 6.891] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [ 6.891] (**) Power Button: Applying InputClass "Keyboard Defaults"
    [ 6.891] (II) LoadModule: "evdev"
    [ 6.891] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
    [ 6.892] (II) Module evdev: vendor="X.Org Foundation"
    [ 6.892] compiled for 1.14.0, module version = 2.8.0
    [ 6.892] Module class: X.Org XInput Driver
    [ 6.892] ABI class: X.Org XInput driver, version 19.1
    [ 6.892] (II) Using input driver 'evdev' for 'Power Button'
    [ 6.892] (**) Power Button: always reports core events
    [ 6.892] (**) evdev: Power Button: Device: "/dev/input/event4"
    [ 6.892] (--) evdev: Power Button: Vendor 0 Product 0x1
    [ 6.892] (--) evdev: Power Button: Found keys
    [ 6.892] (II) evdev: Power Button: Configuring as keyboard
    [ 6.892] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input4/event4"
    [ 6.892] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
    [ 6.893] (**) Option "xkb_rules" "evdev"
    [ 6.893] (**) Option "xkb_model" "evdev"
    [ 6.893] (**) Option "xkb_layout" "gb"
    [ 6.936] (II) config/udev: Adding input device Video Bus (/dev/input/event7)
    [ 6.936] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
    [ 6.936] (**) Video Bus: Applying InputClass "Keyboard Defaults"
    [ 6.936] (II) Using input driver 'evdev' for 'Video Bus'
    [ 6.936] (**) Video Bus: always reports core events
    [ 6.936] (**) evdev: Video Bus: Device: "/dev/input/event7"
    [ 6.936] (--) evdev: Video Bus: Vendor 0 Product 0x6
    [ 6.936] (--) evdev: Video Bus: Found keys
    [ 6.936] (II) evdev: Video Bus: Configuring as keyboard
    [ 6.936] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:2b/LNXVIDEO:00/input/input7/event7"
    [ 6.936] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 7)
    [ 6.936] (**) Option "xkb_rules" "evdev"
    [ 6.936] (**) Option "xkb_model" "evdev"
    [ 6.936] (**) Option "xkb_layout" "gb"
    [ 6.937] (II) config/udev: Adding input device Power Button (/dev/input/event1)
    [ 6.937] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [ 6.937] (**) Power Button: Applying InputClass "Keyboard Defaults"
    [ 6.937] (II) Using input driver 'evdev' for 'Power Button'
    [ 6.937] (**) Power Button: always reports core events
    [ 6.937] (**) evdev: Power Button: Device: "/dev/input/event1"
    [ 6.937] (--) evdev: Power Button: Vendor 0 Product 0x1
    [ 6.937] (--) evdev: Power Button: Found keys
    [ 6.937] (II) evdev: Power Button: Configuring as keyboard
    [ 6.937] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1/event1"
    [ 6.937] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 8)
    [ 6.937] (**) Option "xkb_rules" "evdev"
    [ 6.937] (**) Option "xkb_model" "evdev"
    [ 6.938] (**) Option "xkb_layout" "gb"
    [ 6.939] (II) config/udev: Adding input device Lid Switch (/dev/input/event3)
    [ 6.939] (II) No input driver specified, ignoring this device.
    [ 6.939] (II) This device may have been added with another device file.
    [ 6.939] (II) config/udev: Adding input device Sleep Button (/dev/input/event2)
    [ 6.939] (**) Sleep Button: Applying InputClass "evdev keyboard catchall"
    [ 6.939] (**) Sleep Button: Applying InputClass "Keyboard Defaults"
    [ 6.939] (II) Using input driver 'evdev' for 'Sleep Button'
    [ 6.939] (**) Sleep Button: always reports core events
    [ 6.939] (**) evdev: Sleep Button: Device: "/dev/input/event2"
    [ 6.939] (--) evdev: Sleep Button: Vendor 0 Product 0x3
    [ 6.939] (--) evdev: Sleep Button: Found keys
    [ 6.939] (II) evdev: Sleep Button: Configuring as keyboard
    [ 6.939] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input2/event2"
    [ 6.939] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 9)
    [ 6.939] (**) Option "xkb_rules" "evdev"
    [ 6.939] (**) Option "xkb_model" "evdev"
    [ 6.939] (**) Option "xkb_layout" "gb"
    [ 6.941] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=9 (/dev/input/event14)
    [ 6.941] (II) No input driver specified, ignoring this device.
    [ 6.941] (II) This device may have been added with another device file.
    [ 6.941] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=8 (/dev/input/event15)
    [ 6.941] (II) No input driver specified, ignoring this device.
    [ 6.941] (II) This device may have been added with another device file.
    [ 6.942] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event16)
    [ 6.942] (II) No input driver specified, ignoring this device.
    [ 6.942] (II) This device may have been added with another device file.
    [ 6.942] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event17)
    [ 6.942] (II) No input driver specified, ignoring this device.
    [ 6.942] (II) This device may have been added with another device file.
    [ 6.943] (II) config/udev: Adding input device Laptop_Integrated_Webcam_2HDM (/dev/input/event6)
    [ 6.943] (**) Laptop_Integrated_Webcam_2HDM: Applying InputClass "evdev keyboard catchall"
    [ 6.943] (**) Laptop_Integrated_Webcam_2HDM: Applying InputClass "Keyboard Defaults"
    [ 6.943] (II) Using input driver 'evdev' for 'Laptop_Integrated_Webcam_2HDM'
    [ 6.943] (**) Laptop_Integrated_Webcam_2HDM: always reports core events
    [ 6.943] (**) evdev: Laptop_Integrated_Webcam_2HDM: Device: "/dev/input/event6"
    [ 6.943] (--) evdev: Laptop_Integrated_Webcam_2HDM: Vendor 0x408 Product 0x2fb1
    [ 6.943] (--) evdev: Laptop_Integrated_Webcam_2HDM: Found keys
    [ 6.943] (II) evdev: Laptop_Integrated_Webcam_2HDM: Configuring as keyboard
    [ 6.943] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb2/2-1/2-1.4/2-1.4:1.0/input/input6/event6"
    [ 6.943] (II) XINPUT: Adding extended input device "Laptop_Integrated_Webcam_2HDM" (type: KEYBOARD, id 10)
    [ 6.943] (**) Option "xkb_rules" "evdev"
    [ 6.943] (**) Option "xkb_model" "evdev"
    [ 6.943] (**) Option "xkb_layout" "gb"
    [ 6.944] (II) config/udev: Adding input device HDA Digital PCBeep (/dev/input/event10)
    [ 6.944] (II) No input driver specified, ignoring this device.
    [ 6.944] (II) This device may have been added with another device file.
    [ 6.945] (II) config/udev: Adding input device HDA Intel PCH Mic (/dev/input/event11)
    [ 6.945] (II) No input driver specified, ignoring this device.
    [ 6.945] (II) This device may have been added with another device file.
    [ 6.945] (II) config/udev: Adding input device HDA Intel PCH Headphone (/dev/input/event12)
    [ 6.945] (II) No input driver specified, ignoring this device.
    [ 6.945] (II) This device may have been added with another device file.
    [ 6.946] (II) config/udev: Adding input device HDA Intel PCH Headphone (/dev/input/event13)
    [ 6.946] (II) No input driver specified, ignoring this device.
    [ 6.946] (II) This device may have been added with another device file.
    [ 6.946] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
    [ 6.946] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
    [ 6.946] (**) AT Translated Set 2 keyboard: Applying InputClass "Keyboard Defaults"
    [ 6.946] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
    [ 6.946] (**) AT Translated Set 2 keyboard: always reports core events
    [ 6.946] (**) evdev: AT Translated Set 2 keyboard: Device: "/dev/input/event0"
    [ 6.946] (--) evdev: AT Translated Set 2 keyboard: Vendor 0x1 Product 0x1
    [ 6.946] (--) evdev: AT Translated Set 2 keyboard: Found keys
    [ 6.946] (II) evdev: AT Translated Set 2 keyboard: Configuring as keyboard
    [ 6.946] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
    [ 6.946] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 11)
    [ 6.946] (**) Option "xkb_rules" "evdev"
    [ 6.946] (**) Option "xkb_model" "evdev"
    [ 6.946] (**) Option "xkb_layout" "gb"
    [ 6.947] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/event9)
    [ 6.947] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "evdev touchpad catchall"
    [ 6.947] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "touchpad catchall"
    [ 6.947] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "Default clickpad buttons"
    [ 6.947] (II) LoadModule: "synaptics"
    [ 6.947] (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so
    [ 6.948] (II) Module synaptics: vendor="X.Org Foundation"
    [ 6.948] compiled for 1.14.0, module version = 1.7.0
    [ 6.948] Module class: X.Org XInput Driver
    [ 6.948] ABI class: X.Org XInput driver, version 19.1
    [ 6.948] (II) Using input driver 'synaptics' for 'SynPS/2 Synaptics TouchPad'
    [ 6.948] (**) SynPS/2 Synaptics TouchPad: always reports core events
    [ 6.948] (**) Option "Device" "/dev/input/event9"
    [ 6.967] (II) synaptics: SynPS/2 Synaptics TouchPad: ignoring touch events for semi-multitouch device
    [ 6.967] (--) synaptics: SynPS/2 Synaptics TouchPad: x-axis range 1472 - 5398 (res 42)
    [ 6.967] (--) synaptics: SynPS/2 Synaptics TouchPad: y-axis range 1408 - 4728 (res 70)
    [ 6.967] (--) synaptics: SynPS/2 Synaptics TouchPad: pressure range 0 - 255
    [ 6.967] (--) synaptics: SynPS/2 Synaptics TouchPad: finger width range 0 - 15
    [ 6.967] (--) synaptics: SynPS/2 Synaptics TouchPad: buttons: left right double triple
    [ 6.967] (--) synaptics: SynPS/2 Synaptics TouchPad: Vendor 0x2 Product 0x7
    [ 6.967] (**) Option "VertEdgeScroll" "on"
    [ 6.967] (**) Option "TapButton1" "1"
    [ 6.967] (**) Option "TapButton2" "2"
    [ 6.967] (**) Option "TapButton3" "3"
    [ 6.967] (**) Option "CoastingSpeed" "0"
    [ 6.967] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
    [ 6.967] (**) SynPS/2 Synaptics TouchPad: always reports core events
    [ 6.986] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input9/event9"
    [ 6.997] (II) XINPUT: Adding extended input device "SynPS/2 Synaptics TouchPad" (type: TOUCHPAD, id 12)
    [ 6.997] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MinSpeed is now constant deceleration 2.5
    [ 6.997] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MaxSpeed is now 1.75
    [ 6.997] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) AccelFactor is now 0.039
    [ 6.997] (**) SynPS/2 Synaptics TouchPad: (accel) keeping acceleration scheme 1
    [ 6.998] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration profile 1
    [ 6.998] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration factor: 2.000
    [ 6.998] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration threshold: 4
    [ 6.998] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
    [ 6.998] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/mouse0)
    [ 6.998] (**) SynPS/2 Synaptics TouchPad: Ignoring device from InputClass "touchpad ignore duplicates"
    [ 6.999] (II) config/udev: Adding input device PC Speaker (/dev/input/event5)
    [ 6.999] (II) No input driver specified, ignoring this device.
    [ 6.999] (II) This device may have been added with another device file.
    [ 7.000] (II) config/udev: Adding input device Dell WMI hotkeys (/dev/input/event8)
    [ 7.000] (**) Dell WMI hotkeys: Applying InputClass "evdev keyboard catchall"
    [ 7.000] (**) Dell WMI hotkeys: Applying InputClass "Keyboard Defaults"
    [ 7.000] (II) Using input driver 'evdev' for 'Dell WMI hotkeys'
    [ 7.000] (**) Dell WMI hotkeys: always reports core events
    [ 7.000] (**) evdev: Dell WMI hotkeys: Device: "/dev/input/event8"
    [ 7.000] (--) evdev: Dell WMI hotkeys: Vendor 0 Product 0
    [ 7.000] (--) evdev: Dell WMI hotkeys: Found keys
    [ 7.000] (II) evdev: Dell WMI hotkeys: Configuring as keyboard
    [ 7.000] (**) Option "config_info" "udev:/sys/devices/virtual/input/input8/event8"
    [ 7.000] (II) XINPUT: Adding extended input device "Dell WMI hotkeys" (type: KEYBOARD, id 13)
    [ 7.000] (**) Option "xkb_rules" "evdev"
    [ 7.000] (**) Option "xkb_model" "evdev"
    [ 7.000] (**) Option "xkb_layout" "gb"
    [ 24.896] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 24.896] (**) NVIDIA(0): device LGD (DFP-2) (Using EDID frequencies has been
    [ 24.896] (**) NVIDIA(0): enabled on all display devices.)
    And my 50-synaptics.conf file (ignore the do not edit this file warning, it's been copied and pasted into the /etc/X11/xorg.conf.d/ directory):
    # Example xorg.conf.d snippet that assigns the touchpad driver
    # to all touchpads. See xorg.conf.d(5) for more information on
    # InputClass.
    # DO NOT EDIT THIS FILE, your distribution will likely overwrite
    # it when updating. Copy (and rename) this file into
    # /etc/X11/xorg.conf.d first.
    # Additional options may be added in the form of
    # Option "OptionName" "value"
    Section "InputClass"
    Identifier "touchpad catchall"
    Driver "synaptics"
    MatchIsTouchpad "on"
    Option "TapButton1" "1"
    Option "TapButton2" "2"
    Option "TapButton3" "3"
    Option "VertEdgeScroll" "on"
    Option "CoastingSpeed" "0"
    # This option is recommend on all Linux systems using evdev, but cannot be
    # enabled by default. See the following link for details:
    # http://who-t.blogspot.com/2010/11/how-to-ignore-configuration-errors.html
    MatchDevicePath "/dev/input/event*"
    EndSection
    Section "InputClass"
    Identifier "touchpad ignore duplicates"
    MatchIsTouchpad "on"
    MatchOS "Linux"
    MatchDevicePath "/dev/input/mouse*"
    Option "Ignore" "on"
    EndSection
    # This option enables the bottom right corner to be a right button on
    # non-synaptics clickpads.
    # This option is only interpreted by clickpads.
    Section "InputClass"
    Identifier "Default clickpad buttons"
    MatchDriver "synaptics"
    Option "SoftButtonAreas" "50% 0 82% 0 0 0 0 0"
    # To disable the bottom edge area so the buttons only work as buttons,
    # not for movement, set the AreaBottomEdge
    # Option "AreaBottomEdge" "82%"
    EndSection
    # This option disables software buttons on Apple touchpads.
    # This option is only interpreted by clickpads.
    Section "InputClass"
    Identifier "Disable clickpad buttons on Apple touchpads"
    MatchProduct "Apple|bcm5974"
    MatchDriver "synaptics"
    Option "SoftButtonAreas" "0 0 0 0 0 0 0 0"
    EndSection
    Thanks in advance

    Hello kal33,
    Welcome to the HP Forums!
    I understand the left part of the clickpad is not working. To assist you, please try all of the steps in this HP document: Using and Troubleshooting the TouchPad or ClickPad (Windows 8)
    If these steps do not help, then there could be a hardware issue. Since the computer is in warranty, I would contact HP phone support for hardware assistance. You can utilize this website to learn how to contact HP appropriately, based on your region: Contact HP Worldwide
    Please let me know if you have any other questions or concerns. Thanks for bringing this issue to the HP Forums. Have a great day!
    Mario
    I worked on behalf of HP.

  • NB250-10G - left touchpad button does not work

    I have a NB250 10G that until a couple of days ago had worked perfectly.
    However, I then found that I could not operate the netbook with the touchpad.
    However, all works fine with my USB plug-in mouse.
    Everything seemed to be going haywire with the touch pad, but I now know what is wrong.
    The right-hand touch-pad button works fine, but the left-hand button is producing the same result as the right-hand one. In other words, I have no working left-hand button - I can't click to open any icons, I can't close down - all that happens is that I get a mini-menu appearing just as with the right-hand button.
    An online note to Toshiba has so far not been answered.
    Can anyone help please? John

    Thanks for your suggestion. Have been into the control panel and changed the touchpad keys from right-hander use to left-hander, applied change - No result. Then back to right-hander set up again - still both keys give the same results, ie a normal right-hand key result. But thanks for the help. You also suggest re-installing the mouse driver. I have no idea how to go about this - are you able to advise? Many thanks. John

  • Left touchpad button sticks on Pavilion DM4

    My wife has a DM4 2180us Pavilion notebook and lately the left button stick or does not register a click. Looking at it I believe the problem is that its rubbing against the chassis frame around the button. Have tried cleaning around it with a cotton swab and rubbing alcohol. But although it helped a little it still is sticking. Kind of upset that we have not even had this PC a year and already have replaced the WiFi card and have had issues with it shutting down randomly. Fan runs all the time and seems to be struggling to keep it cool. But that's yet another issue that I can't find a solution for.

    The touchpad is probably dead. The driver can be installed on your notebook with a non-functional touchpad, that is why you are seeing it in the device manager. I would recommend calling HP support at 1-800-474-6836 to have it repaired or replaced.
    -------------How do I give Kudos? | How do I mark a post as Solved? --------------------------------------------------------

  • How to replace touchpad buttons? Hp hdx18 1010ea

    Hi
    I hope some one can help.... i have lost my left touchpad button on my HP hdx18 1010ea..My laptop is out of warranty and i cannot find any info on how to replace it or where to obtain the spare parts...I have spent ages on the HP site and it's useless i enter my part number of my pc then it confirms the model ..but then when i click parts i need it just goes back to asking my model number?..
    Hope some one can help...
    Robert
    This question was solved.
    View Solution.

    sasman1964 wrote:
    Hi
    I hope some one can help.... i have lost my left touchpad button on my HP hdx18 1010ea..My laptop is out of warranty and i cannot find any info on how to replace it or where to obtain the spare parts...I have spent ages on the HP site and it's useless i enter my part number of my pc then it confirms the model ..but then when i click parts i need it just goes back to asking my model number?..
    Hope some one can help...
    Robert
    Hi,
    According to a service manual, the touchpad is a part of the top cover. You have to replace whole top cover..
    Top cover part number: 496881-001
    Service manual: http://h10032.www1.hp.com/ctg/Manual/c01705400.pdf
    See page 71 how to replace it..
    http://www.amazon.com/gp/product/B004VEPK60/ref=as_li_ss_tl?ie=UTF8&tag=heaprcom05-20&linkCode=as2&c...
    Have look on ebay or use google to find the cheapest one..
    Dv6-7000 /Full HD/Core i5-3360M/GF 650M/Corsair 8GB/Intel 7260AC/Samsung Pro 256GB
    Testing - HP 15-p000
    HP Touchpad provided by HP
    Currently on Debian Wheeze
    *Please, help other users with the same issue by marking your solved topics as "Accept as Solution"*

  • DV5-1000 touchpad buttons, premature wear

    After about a year of using my DV5-1000, the silver coated left touchpad button began to wear through to the black plastic underneath.  Also, the button became noticeably loose, especially when compared to the right touchpad button.  It eventually got to the point where the button would click unreliably.
    I managed to buy a replacement palmrest part for the DV5, which contains the touchpad assembly (you cannot buy the assembly separately).  Unfortunately, the palmrest is an integral part of the laptop, requiring 75% of it to be disassembled to remove the original part.  I downloaded a service manual and went to work... and I got it done after 2 long hours.  The new part fit properly and the laptop appeared as new.
    A year later, I'm faced with the same problem yet again!  I am not abusive to the touchpad buttons.  This kind of wear should not be happening.  I dread having to take apart the laptop again... but I am worried that the button will start developing click problems as the previous one did.  I wonder if some kind of protective coating added to the button would help it.  Anybody else here suffer premature wear to the left touchpad button?
    "If you keep an open mind, life will give you more possibilities."

    I had a look at some of the newer DV5 models and... I'm rather taken aback with how HP solved the touchpad button problem.  They no longer have tactile keys.  Instead, there's a soft touch membrane.  This makes it very difficult to control sustained pressing of the button, as the travel from on to off is so short.  It was a real cop-out in my mind, that HP didn't stick with tactile buttons.  Sure, there were some problems with how they were intially implemented, but c'mon--so many other laptop makers have tactile buttons that don't wear out.  Why couldn't HP have gone that route of just improving the button?
    Also, what's with all of the wacky patterns that HP is now slathering over their laptop casings?  It makes the laptop look a lot less professional.  If they want to appeal to kids, make it so that there's an optional shell you can get with the laptop with whatever zany pattern you wish.  Or instead, just opt for something conservative and wear resistant.
    "If you keep an open mind, life will give you more possibilities."

  • Lower touchpad button failing

    My left touchpad button, the one down at the lower edge of the pad, is now only working when I press at the right 40% of the bar, pushing it anywhere else does nothing. How do I get access to this area?

    LOL I tried to clean the dust out of a massive 17" SONY laptop my aunt had. I had to take off, like, 30 screws, the baseplate, the HDD assembly (???) and the optical drive.
    Yeah, I had some trouble figuring out how to word "Average Battery Life". It's what it predicts you while you're doing basic word processing-like tasks. A rough range would work.
    And the little tidbit on calculating works like: 80% predicts you 4 hours, then 4/0.80 (the decimal equivalent for a percent) gets you 5 hours. That extrapolation suggests that at 100% it would predict 5 hours.
    I know my survey is a bit complex, but so far it seems that OS architecture, HDD manufacturer, and browser seem to have an effect on battery life.
    W520: i7-2720QM, Q2000M at 1080/688/1376, 21GB RAM, 500GB + 750GB HDD, FHD screen
    X61T: L7500, 3GB RAM, 500GB HDD, XGA screen, Ultrabase
    Y3P: 5Y70, 8GB RAM, 256GB SSD, QHD+ screen

  • How to deal with those pesky touchpad buttons

    The Pavilion series laptops are really well made in a lot of respects.  I have owned my DV5t for almost 4 years now and I've been quite happy with it (except for rather anemic battery life).  There is one thing that became a nasty problem for me, that being the left touchpad button.  It is the most commonly used touchpad button and unfortunately these buttons were not well designed.  They can easily break after a certain number of hits, whereby there's no longer any spring to it.  Pressing the button ends up getting double-taps like mad.  Also, the silver coating on them tends to wear away, looking rather unsightly over time. Once you start seeing the black plastic beneath, it won't be long before the button breaks.  It's really a shame, because these tactile feel buttons work well--they just don't last.  The newer HP laptops have those "lite touch" buttons which I do not like.  The tactile feel is so much better.  Unfortunately, it seems like most laptop makers are going with those solid state buttons to avoid another component that might go wrong.  It's a shame, because with just a little more effort they could have been designed to last a very long time.
    As of this writing, I have now gone through TWO of these touchpads.  How did I manage to get another two chances?  Well, they can be replaced but unfortunately they require you to disassemble more than half of the laptop.  You see, the touchpad is integrated into the palm bezel, and the palm bezel is a piece of plastic coated metal that runs all the way to the back of the laptop.  To get at it requires about an hour of taking the laptop apart.  It's not for the faint of heart either.  However, there is a service manual available that shows you what to do and I was able to follow it... thrice.  Yes, the first button wore out after just under 2 years.  The second one held up about as long.  I use the touchpad buttons frequently, so... well, needless to say, now that I've got the 3rd bezel in place, I am going to rely mostly on an external mouse.  And when I have to use the touchpad, I am going to use it very carefully, not exerting too much pressure (note that you can also tap the touchpad itself for a single click, something good to get into the habit of doing).  Additionally, I'm going to put a sheet of protector plastic on the left mouse button to help avoid wearing out the surface.
    So... one hour to disassemble it and a little more than an hour to reassemble it.  It looked daunting to do at first, but believe me if you're patient and can follow instructions it is definitely doable.  You don't need to be an HP tech to do it.
    As for the parts, I obtained them from eBay.  Apparently there are a lot of excellent condition used parts available from a variety of sources.  I got the bezel for just under $30 shipped.  Also, the speaker grille part is metal and tends to dent, so this time around I replaced it as well as the keyboard (the original was fine, but just a little touchy on one or two keys).  With all 3 of these parts replaced, my laptop feels like new all over again.  As for obtaining parts, you'll need to do your homework with the HP parts finder.  There are many variants of the Pavilion laptop models with many parts in common, so the part you need can vary by number.  The parts catalog can help you find them.
    Anyway, that's about it.  After having done this for the 3rd time, I figured there might be others out there with this problem on the brink of tossing out the laptop or selling it for parts on the cheap.  It's salvageable!
    "If you keep an open mind, life will give you more possibilities."

    Thank you for your information and support. I may have to replace my touch pad and keyboard and you have given me hope and confidence. Thank you again,
    Jackson Gal

  • Left touchpad is broken

    my left touchpad button is shaking and i need to press it hard.i think the springs inside are shaken.i bought this laptop 2 months ago and it has started creating problems for me.i bought this from India but right now i am in Uk for a year.where do i get it repair from???please guide me asap.

    Sorry for the wrong info..
    I overlooked it as without touchpad.. mistake
    You can order it..
    Although I am an HP employee, I am speaking for myself and not for HP.

  • W520 Paint Rubs Off

    Hello everyone!
    My W520 is only a couple weeks old, and already the paint on all four top corners has completely rubbed off (the corners are shiny) and there is a smudge on the top of my computer of permanently rubbed-off paint. I'm EXTREMELY careful with my laptop and the only wear and tear it gets is when I carefully place it in my Northface backpack (with a soft built-in laptop sleeve) for transportation. After hearing so much about Thinkpad quality and durability, I'm really surprised the paint began rubbing off after a couple days.
    Has anyone else had these problems (so quickly after purchasing)? Is there a possibility that the paint on my W520 is a bad batch?
    Thank you!
    - Michael
    P.S. Other than the bad paint, the laptop is amazing and I would definitely recommend it to others. I've been an Apple user for 10 years and this is my first PC since then and I'm very happy with the performance... Just not the build quality. If Lenovo uses better quality materials, I would probably try to talk the entire applied mathematics deparment at my university to switch away from Apple. Seriously, this thing is blazingly fast and cuts through numerical computations on MATLAB and C!

    Hi Michael:
    I've had about half a dozen ThinkPads over the last 15 years.  My experience has been that there will be a very tiny amount of 'rubbing off' (wear) of the paint in the corners after about 3 years of use.  By 'tiny amount', I mean maybe a small spot that is about 1 mm in diameter in each corner.
    I just purchased a new W520 (got it about 6 weeks ago) and I have been carring it around in a fairly tight-fitting Targus bag that I keep in the saddlebag of my motorcycle.  In the last 6 weeks, I have ridden about 3,000 kilometers around Hungary, Romania, Bulgaria, Turkey and Greece with the ThinkPad in my saddlebag - and there is no evidence of any wear at all on the ThinkPad.  The roads are pretty poor in some of these countries, with lots of potholes and bumps...
    What I am getting at is this:  If you are seeing paint coming off of the top corners of your ThinkPad (this implies the top corners of your screen), then your laptop must be abrading (rubbing) against the inside of the sleeve that you carry it in, and the material on the inside of the sleeve is kind of working like sandpaper against the finish on the outside of the screen.
    When we (as users) think about protecting our laptops with sleeves, bags, backpacks, etc., I think we normally think about protecting them from impact and from 'bumps' - but, if the sleeve is even a tiny bit bigger than the laptop itself, or if the laptop is not held securely (unable to move) in the bag or backpack, the corners of the laptop are going to rub against the protective container.  Depending on what the material is inside the protective container, the results may be nothing at all (if the material is soft and smooth) or abrasion of the paint (if the material has texture to it, or especially if the material is a woven synthetic fibre).
    Because of the rather extreme conditions my laptop experiences (in the motorcycle saddlebag), I have made sure that it is a snug fit into the protective bag, and can't move around inside the protective bag.  Hence - no abrasion, no wearing off of the paint.
    Hope this information provides you with useful food for thought.
    Michael
    W520 (4270 CTO), which replaced a W500 (4062-27U), which replaced a T42P, which replaced an A21P...

Maybe you are looking for

  • "Optional" Paremeter/Prompts in report selection.

    Post Author: heathdallison CA Forum: Crystal Reports I've been going through the forum looking for someone who has solved my particular problem but I haven't found it. I'm using crystal server XI and crystal reports design tool. I have a report that

  • Wrapping text with web dynpro ALV

    Hi there, I have got an web dynpro ALV and have set the SET_FIXED_TABLE_LAYOUT value to abap_true. This provides what i need apart from instead of not showing the text that can not be fit into the available column width I would like it to wrap the te

  • HP ENVY TouchSmart 15-j009wm Doesnt read USB Flash Drive After Downgrade to Windows 7

    I Have Downgraded Installed Windows 7 Through Flash Drive But i need help. Windows 7 Doesnt read my Flash Drive anymore? It can read my USB Keyboard but doesnt read USB Flash Drive.  I Have no Internet On The Computer, So that means i cant update my

  • Phone Line Across The Street Has Branches On It

    Whom should I contact to get some branches removed from a Verizon phone line across the street? I don't think it's a hazard, but something will give sooner or later. I'm not a Verizon customer, so I can't easily access anyone online. And it seems all

  • Huge performance difference for this?

    So I was optimizing a large piece of code and found that looping through a 2-dimensional array by row is a LOT faster than by column. If you look at the code below, the accessor to the row is moved from the outer loop to the inner loop in the second