I don't have a prebuilt APK since the client opted to go the calibration during manufacturing route as opposed to the application. So I can only point you the application for you to build. The application is set to load on system load, but the first thing it does is check for the existence of /etc/pointercal and if the file exists it just quits, if it doesn't exist it goes ahead with the calibration.
You can definitely reference this from the Settings application if you wish.. Regards -- Ashwin On Mon, Jan 17, 2011 at 2:34 PM, Zdravko Stoychev <zdravko.stoyc...@gmail.com> wrote: > Thanks, could you share a compiled .apk please? > > Question: If calibration data is built-in on compile-time, what's the > point of having calibrate application anyway? > And if you have it be generate the first time you boot up the device, > you should have it as an option under settings, because of human error > on first run, etc. > > Regards, > Dako > > On Jan 12, 6:28 pm, Ashwin Bihari <abih...@gmail.com> wrote: >> While it's true that the touchscreen calibration should only be done >> once during the initial development, it might be nice to have it be >> generate the first time you boot up the device. To that end, check out >> [1] which is a calibration application by 0xdroid that does just >> that.. >> >> [1] -http://gitorious.org/0xdroid/packages_apps_tscalibration >> >> -- Ashwin >> >> >> >> >> >> >> >> On Wed, Jan 12, 2011 at 9:49 AM, Chinmay S <cvs...@gmail.com> wrote: >> > Hi, >> >> > AFAIK, calibration using TSLIB is done before compilation in code >> > (i.e. during building/testing support for the device's touchscreen). >> >> > The values generated in the file pointercal by TSLIB are used to code the >> > static-constants in the file: >> > frameworks/services/java/com/android/server/InputDevice.java >> >> > As such this cannot be used during run-time (i.e by the end user) >> >> > Absense of runtime calibration of the touchscreen on android should not be >> > an issue as the touchscreen doesn't get altered during the lifetime of the >> > device and the values it returns are always the same and do not change with >> > time/usage. >> >> > Also, change of co-ordinate axes due to change in orientation is >> > automatically handled by the android framework and no callibration is reqd >> > in that case too. >> >> > Regards >> > CVS >> >> > -- >> > unsubscribe: android-porting+unsubscr...@googlegroups.com >> > website:http://groups.google.com/group/android-porting > > -- > unsubscribe: android-porting+unsubscr...@googlegroups.com > website: http://groups.google.com/group/android-porting > -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
