Touchscreen calibration missing

[GoogleCodeExporter]

What steps will reproduce the problem?
1. open settings
2. sounds and display
3. no touchscreen calibration like in zacpods image

What is the expected output? What do you see instead?

What version of the boot.img and system.img are you using?
systemV2.img

Can you provide logcat output during that error?

Please provide any additional information below.
the calibration is not that important but if possible it would be nice to have

Original issue reported on code.google.com by frankmai...@gmail.com on 15 Jul 2010 at 12:55

[GoogleCodeExporter]

The code for that is in
korean-v10t/app/Settings/com/android/settings/TSCalibratio
n.smali,
and is called in 
korean-v10t/app/Settings/com/android/settings/SoundAndDisplaySettings.smali by
[...]
new-instance v2, Landroid/content/Intent;
invoke-direct {v2}, Landroid/content/Intent;-><init>()V
.local v2, intent:Landroid/content/Intent;
const-string v9, "com.android.settings"
const-string v10, "com.android.settings.TSCalibration"
invoke-virtual {v2, v9, v10}, 
Landroid/content/Intent;->setClassName(Ljava/lang/String;Ljava/lang/String;)Land
roid/content/Intent;
invoke-virtual {v7, v2}, 
Landroid/preference/PreferenceScreen;->setIntent(Landroid/content/Intent;)V
invoke-virtual {v6, v7}, 
Landroid/preference/PreferenceCategory;->addPreference(Landroid/preference/Prefe
rence;)Z
iput-object v7, p0, 
Lcom/android/settings/SoundAndDisplaySettings;->mTouch:Landroid/preference/Prefe
rence;

but I don't know if there is anything like that in aosp.
I hope there is anyone who can translate that code into java. Should not be so 
hard, but its a lot of code.

Original comment by polyth...@gmail.com on 16 Jul 2010 at 2:39

• Added labels: Priority-Low, Type-Enhancement
• Removed labels: Priority-Medium, Type-Defect

[GoogleCodeExporter]

In V2,the hidden menu contains this function.
Just enter hidden menu,find device test->touch test->calibration.

Original comment by walteron...@gmail.com on 17 Jul 2010 at 4:06

[GoogleCodeExporter]

what's the hidden menu code right now?

Original comment by elmagi...@gmail.com on 4 Aug 2010 at 8:44

[GoogleCodeExporter]

Wonder is there something in CyanogenMod to calibrate the touch screen.

Original comment by Tetsuo6...@gmail.com on 5 Oct 2010 at 11:05

• Changed state: Accepted

[GoogleCodeExporter]

Have you tested if there's something about calibration using AnyCut?

Original comment by oldm...@gmail.com on 5 Oct 2010 at 11:27

[GoogleCodeExporter]

Touchscreen calibration would be a great addition and make my life way easier. 
Touch calibration in stock 1.5 totally fixed my screen problems.

Original comment by justinse...@gmail.com on 6 Oct 2010 at 7:29

[GoogleCodeExporter]

How you got Touch Calibration in stock 1.5 justinselig ? I´m with out of 
calibration problem with my touch.

Original comment by trysta...@gmail.com on 7 Oct 2010 at 7:47

[GoogleCodeExporter]

In stock 1.5, in the "Dialer" enter: 3845#*620#
(This accesses the hidden menu)

Choose "Device test"
Choose "Touch test"
Choose "Calibration"

Original comment by justinse...@gmail.com on 7 Oct 2010 at 7:52

[GoogleCodeExporter]

http://github.com/rmcc/android_packages_apps_TSCalibration
there's something here.

Original comment by saxand...@gmail.com on 20 Oct 2010 at 2:14

[GoogleCodeExporter]

I calibrated my touchscreen on 1.5 and so had a quick look at how it worked 
before moving. I haven't done a lot since because the calibration seems to be 
ok with 2.2. I'll share what I found though, as it doesn't look like it'd be a 
lot of effort to implement it if you needed to...

The HiddenMenu app calibration tool creates a file /data/misc/ts_cal that 
contains 5 comma separated integers (xscale, xtrans, yscale, ytrans, 
scale_factor). I did try running it on 2.2 and it ran but for some reason 
didn't write out the file - probably something simple but in the end I didn't 
bother to dig further as I didn't need it. Maybe it doesn't have permission to 
write to this directory as I installed it as a normal user app.

com/android/server/InputDevice is modified to read (and watch for updates then 
reread) the ts_cal file. The values are them used in generateMotion(...) in 
com/android/server/InputDevice$MotionState to adjust the position. This method 
no longer exists, there are now 2 methods (one absolute and one relative) 
instead. We are probably only interested in the absolute one for a touchscreen, 
probably.

Original comment by richarda...@gmail.com on 30 Oct 2010 at 11:01

[GoogleCodeExporter]

Issue 264 has been merged into this issue.

Original comment by polyth...@gmail.com on 1 Nov 2010 at 9:27

[GoogleCodeExporter]

Original comment by trmfrei...@gmail.com on 7 Feb 2011 at 4:19

• Changed state: NeedVolunteer

[GoogleCodeExporter]

Hidden Menu is inaccessible using the 3845#*620# code with 2.0 or later. Anyone 
know any other code to get at the hidden menu??

Original comment by houc...@gmail.com on 8 Feb 2011 at 9:19

[GoogleCodeExporter]

Touchscreen calibration
Please see:
http://tslib.berlios.de/
http://gitorious.org/0xdroid/packages_apps_tscalibration

check values in com/android/server/InputDevice 

It appears that all resistive touchscreens of the same brand and model should 
react the same way. 
The correct values can be set in com/android/server/InputDevice

It would be nice if this values could be read from a file on the card/system so 
it's easy to change so if there is one screen with a different behaviour one 
could use the ts_calibration application. (if it works)

Could we include ts_calibration/ts_lib?

(of course I might be completely wrong)

Original comment by trmfrei...@gmail.com on 14 Feb 2011 at 2:04

[GoogleCodeExporter]

I have found that TSCalibration is already included in the repository.

Isn't it an App?
Why isn't it visible on the applications list?
How to run it?

Original comment by trmfrei...@gmail.com on 14 Feb 2011 at 9:47

[GoogleCodeExporter]

Hi guys I have a serious screen calibration problem which stops me from using 
more than half of the screen's surface. Can you please give me a hand with that 
as I had to buy a second phone. First bacame useless I did a downgrade back to 
1.5 but the calibration tool in the hidden menu force closes. By a mistake I 
sitched the Android launcher with the LG one and that helped to improove 
considerably the acuracy of the touch screen. Today I installed the last 
version of Openetna and after 20 minutes of use it is decalibrated again badly. 
Can you help please I have seen that on other systems (the one used for 
sat-nav,s for ex.) they have a calibration tool which prooves to be very handy. 
Thank you.

Original comment by rae...@googlemail.com on 22 Feb 2011 at 7:30

[GoogleCodeExporter]

Analogically (
Need to solve the problem. Otherwise I will be forced get rid of the phone (

Original comment by groupZI...@gmail.com on 14 Apr 2011 at 6:20

[GoogleCodeExporter]

I have the same issue.  The touch area is 30% smaller than the screen.  So I 
touch 3cm down the screen to select something at the top, 3 cm from the bottom 
to select something from the bottom.

The stock ROM had a TS calibration tool that fixed the issue, but there is no 
such tool in this ROM.

Beside the TS issue, this ROM is AWESOME.  It makes an old phone work almost as 
well as my GalaxyS.

Original comment by cmille...@gmail.com on 24 Apr 2011 at 2:48

[GoogleCodeExporter]

Issue 453 has been merged into this issue.

Original comment by trmfrei...@gmail.com on 5 May 2011 at 1:43

[GoogleCodeExporter]

Check out this forum posting as well:

http://androidforums.com/eve-support-troubleshooting/105594-gw620-touch-screen-o
ut-calibration.html

Post #13 refers to a utility called moduleap.apk (Module AP).
I believe this is a utility to calibrate the touchscreen on the Vega tablet.

Maybe it works on the Eve too.
I tried it on mine, and at least nothing seems to have gotten worse...

Original comment by rais...@gmail.com on 5 May 2011 at 5:13

Attachments:

• moduleap.apk

[GoogleCodeExporter]

I tried to use the moduleap.apk.

ERROR!
Can NOT detect IT7260 device.

Original comment by Katzen...@gmail.com on 11 May 2011 at 8:38