So do I just run the patch like this? Sorry I'm not familiar with patching in linux. Can you help me out with what you'd use?
[type] "patch frameworks-base.patch" [ENTER] Othersise I'll just manually make the changes since there are multiple files to edit. But what does the +++ and --- mean in the patch file? I understand the file names and line numbers and stuff, but I'm not sure what some of the meta data means or is intended. Thanks for any help! On Wednesday, November 28, 2012 6:18:00 PM UTC-7, Alvin Wong wrote: > > If you want to use 5-point calibration like tslib does, you can implement > in the kernel driver, or patch InputReader. > > My patch for Gingerbread (not well-formatted): > > https://sourceforge.net/p/ipaq214android/android/ci/54a6fa53224ddd033728ab8423475e1f4108e3cb/tree/patches/frameworks-base.patch > My idc file: > > https://sourceforge.net/p/ipaq214android/android/ci/54a6fa53224ddd033728ab8423475e1f4108e3cb/tree/ipaq214/wm97xx-touchscreen.idc > > The values are from a calibrated pointercal file with each values divided > by 65536. > > Dave Hartman於 2012年11月27日星期二UTC+8下午5時01分45秒寫道： >> >> Hey have you gotten anywhere on this? >> >> >> On Wednesday, November 30, 2011 6:55:17 PM UTC-5, fuzzy7k wrote: >>> >>> I'm working on a build that has a wacom device (Pen and Finger are >>> separate events). The Pen does not need calibration, but the Finger >>> will not reach the edges of the screen. I've found the documentation >>> (http://source.android.com/tech/input/touch-devices.html#touch-device- >>> classification) but can't seem to make any changes that affect the >>> pointer location. I've mainly been focusing on touch.size.calibration >>> and touch.size.scale. I've verified that the idc file is being loaded >>> for the device. >>> >>> Does anyone have any insight? >>> >> -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
