So I continue to use my second day of my long weekend to deal with one that kept irritating me: EeeSlate 121. I mean, the specification of this device is not great, but it should be good enough as daily use tablet and laptop, but as I mentioned in my last blog, there were 2 things that kept irritating me:
- Bluetooth keyboard and mouse discounted to work all the sudden.
- Inaccurate digitizer.
The bluetooth problem seemed to be solved when I realized that, under Bluetooth Settings, the following items are ON:
- Allow bluetooth devices to send you PIM items such a business cards ...
- Allow remote device to browse, send and recieve pictures, music ...
After I turned the above 2 items OFF, the lost bluetooth connection suddenly comes back. And both the keyboard and mouse were working fine since then.
As for digitizer, it turns out the trick of increasing recognition point DOES work. I proved that by intentionally did a horrible job on setting those track points, and sure enough the digitizer went nuts.
So here's the procedure I used to make digitizer working resonably well (there are still some spots on the screen that didn't get perfectly right, but I am a bit lazy and those spot didn't affect my work, so I let them slide and maybe re-calibrated later.)
- To clean up all the previous setting
- Make sure all the related entries in the system registry are gone.
- Use Regedit, and then find "Linearity". You should be able to find 2 pairs of tries:
- One under the key "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TabletPC\LinearityData" (and a corresponding "HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\TabletPC\LinearityData")
- One under something similar to "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\HID\VID_056A&PID_0090&Col02\7&1ae9605e&0&0001\Device Parameters" (and a corresponding "HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\HID\VID_056A&PID_0090&Col02\7&1ae9605e&0&0001\Device Parameters", with a name "LinearityData".) (the "VID_056A&PID_0090&Col02\7&1ae9605e&0&0001" part may not be exactly the same.
- To clean up all up the setting, you need to delete :
- "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TabletPC\LinearityData" the entry.
- Delete JUST THE ENTRY of "LinearityData" under "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\HID\VID_056A&PID_0090&Col02\7&1ae9605e&0&0001\Device Parameters". Do not delete the whole "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\HID\VID_056A&PID_0090&Col02\7&1ae9605e&0&0001\Device Parameters" key,
- After deleted these CurrentControlSet entries, the ones under "ControlSet001" will automatically got deleted.
- You need to delete these Regedit entries when:
- You need to do the hack re-calibration again.
- You need to do the NORMAL re-calibration and thus need to "RESET" the old calibration data. You WILL NOT able to cleanly RESET (by clicking the reset button in the control panel re-calibration property screen) unless these system registry entries are gone.
- To do the hack reclibration properly (at least on Asus EeeSlate EP-121:
- Open Command Line and run this command "tabcal devicekind=pen lincal novalidate XGridPts=5,15,30,50,70,90,120,259,400,513,600,767,900,1021,1180,1210,1240,1260,1275 YGridPts=5,15,50,100,163,223,321,479,640,740,760,780,795" . Some older post about this hack omitted "devicekind=pen" which caused the trouble least on my Windows 8 EeeSlate. Also, if you got syntax error, that is because some spaces are being added by the cut and paste process. Get rid of those spaces and it should be fine.
- The command will trigger a calibration screen with 100+ recognition point. You need to properly set each of them. If you failed, you will need to clean the registry and redo everything again.
- My experience told me that when you redo the calibration, how messy (or how well) you did the last time will affect your process (sometimes gives you hard time by refuse to take your new one because the new one seemed too far off from the old one). So in that sense, the more do re-calibrate, the smoother the calibration process should be.
So that's it. I wasted enough time on this mess. But at least I got a reasonable good result at the end, and now I no longer have incentive to buy Surface Pro, which is good.
No comments:
Post a Comment