Jump to content


Photo

Screen calibration issue


  • Please log in to reply
26 replies to this topic

#1
Arucarde

Arucarde

    Newbie

  • Members
  • Pip
  • 21 posts
Hi,

I have some annoying problem with my racer, if I flash ANY rom or ANY kernel or simply wipe data, my screen become very descalibrated... I can only get it right if I install some 2.1 Rom and do a calibration. Can some one help me please? :(

  • 0

#2
GuyOverThere

GuyOverThere

    Enthusiast

  • Members
  • PipPipPip
  • 176 posts
  • Gender:Male
  • Location:Caracas, Venezuela
  • Interests:Gaming, Linux, Tech and other stuff
  • Devices:ZTE Racer x850
  • Twitter:@netalien
Hi,

stocks roms base their calibration on pointercal/tslib, if I'm not mistaken, directly hardcoded in the kernel but zte didn't provide the sources for such modified driver so there have been only attemps to make similar calibration with some success (other have failed as well). Also, stock roms have either patched files to support calibration or use input device calibration files which isn't something easy to integrate in other roms so you have only two options regarding to calibration, either use stock or try rexchun rom (it has other problems though, battery drain being the most talked about)

However, I don't know what roms you've tried but most stable ones are not heavy descalibrated, there's descalibration but is usable (for some at least), vamshi's kernel has good calibration (not perfect compared to stock), deadlink is slightly more accurate but due to sensitivity at kernel level it has many ghost clicks. Most people seem happy or at least happy enough with vamshi's kernel but if this isn't your case then as I said: either stock or rexchun

  • 0

#3
Arucarde

Arucarde

    Newbie

  • Members
  • Pip
  • 21 posts
Hi, thanks for reply

I tried rexchun rom and still heavy descalibrated... Every time I wipe factory it goes back to the heavy descalibrated, and when I say heavy descalibrated I mean middle screen until the bottom is very offset, I cant even use the back key or menu key. I think that´s not a rom´s problem but maybe some hardcode of the device is bugged. I don´t know what I can do anymore, I already installed almost every rom from racerrom´s and every kernel but still the same...

Can someone give me a full restore of some 2.3 rom to try please?

Edited by Arucarde, 05 September 2012 - 02:18 PM.

  • 0

#4
Arucarde

Arucarde

    Newbie

  • Members
  • Pip
  • 21 posts
Need help on this please!... I have already tried almost 4Gb of roms :unsure:
EDIT: Even with any 2.2 ROM I cant calibrate it proper

Edited by Arucarde, 07 September 2012 - 06:58 PM.

  • 0

#5
redhawkuk

redhawkuk

    Enthusiast

  • Members
  • PipPipPip
  • 164 posts
  • Gender:Male
  • Devices:ZTE Racer debranded Three UK
Some CM7.2 based ROMs do come with a "Touch calibration" tool some don't however if your build is missing you should be able to extract it from a build that does (/system/app/com.android.TSCaibration.apk ??).
As for Android 2.2 did you run the calibration tool? I remember doing this to my handset when I had 2.2 I certainly don't recall having any serious touch screen issues.

Richard S.

  • 0

#6
Arucarde

Arucarde

    Newbie

  • Members
  • Pip
  • 21 posts
Thanks for reply

Can you tell me wich CM7.2 have the Touch calibration?

I tried to import the TSCalibration from a stock rom and installed in a custom ROM but I can´t execute it.

If I calibrate with the 2.2 calibration I can´t do it proper

  • 0

#7
GuyOverThere

GuyOverThere

    Enthusiast

  • Members
  • PipPipPip
  • 176 posts
  • Gender:Male
  • Location:Caracas, Venezuela
  • Interests:Gaming, Linux, Tech and other stuff
  • Devices:ZTE Racer x850
  • Twitter:@netalien
woah sorry to be late xD

I'm not really sure what your phone's problem is D: maybe touchscreen anomallies? (this would explain why it does work only with vendor's rom), seriously, you're the very first to have calibration issues with rexchun rom's and that is a rom with perfect calibration using calibration pointercal from stock! mind blown, also, touchscreen calibration should not affect back or menu key =S those are virtualkeys, meaning: You have a touchscreen area of 320x240, back and menu keys are virtual keys that actually span a little beyond the touchscreen area (at 350 of X axis) and those coordenates are controlled (hardcoded) in the kernel using an array so even if there's heavy descalibration it shouldn't affect those keys unless the kernel reports something that it shouldn't, again, touchscreen anomallies aren't rare (especially resistive ones) and it might be possible that yours is one in a million.

Anyway, I don't think TSCalibration is installed in cm7.2 roms anymore (because most phones have captative I think), you could compile it, though I'm not sure if'll work

  • 0

#8
Arucarde

Arucarde

    Newbie

  • Members
  • Pip
  • 21 posts
Nop

I can´t understand my problem too=( and the must abstruse fact is this started happening when I tried to play some game with an higher resolution, since then, every time I wipe/reset factory, the bottom of the screen seems to be almost on the call keys and the only "virtual key" that works is the home and a little down from its original spot. Is there any way of wipe everything of the phone, or overyde everything? I even tried an tpt, but stil the same. I don´t know, but I still thinking this is an software bug.

Thanks for the reply

  • 0

#9
equiliym

equiliym

    Hardcore

  • Members
  • PipPipPipPipPipPip
  • 1,346 posts
  • Gender:Male
  • Location:Novi Sad
  • Devices:ZTE Racer
  • Twitter:@equiliym
you flashed a tpt backup? odd.. in cwm you can actually format everything, not just wipe, its in the mounting section.. also check advanced, wipe battery, fix permissions etc etc, you should check all of those, might move you from the spot, who knows

  • 0
Suffering-oriented programming.. "First make it possible. Then make it beautiful. Then make it fast."
if i helped please press the vote up button :3

#10
Arucarde

Arucarde

    Newbie

  • Members
  • Pip
  • 21 posts
Yes with that odd tool in chinese, I did format everything in cwm and still the same

EDIT: Can someone please give me an restore of any version higher then 2.1? Or some one have any ideia how to diagnose my problem?

Edited by Arucarde, 20 September 2012 - 06:25 PM.

  • 0

#11
equiliym

equiliym

    Hardcore

  • Members
  • PipPipPipPipPipPip
  • 1,346 posts
  • Gender:Male
  • Location:Novi Sad
  • Devices:ZTE Racer
  • Twitter:@equiliym
issues with B02 rexchuns rom?

  • 0
Suffering-oriented programming.. "First make it possible. Then make it beautiful. Then make it fast."
if i helped please press the vote up button :3

#12
Arucarde

Arucarde

    Newbie

  • Members
  • Pip
  • 21 posts
Just the same :unsure:
EDIT: Another weird thing is that I have to disable toggle signature verification to install any thing, is this normal?

Edited by Arucarde, 20 September 2012 - 06:59 PM.

  • 0

#13
equiliym

equiliym

    Hardcore

  • Members
  • PipPipPipPipPipPip
  • 1,346 posts
  • Gender:Male
  • Location:Novi Sad
  • Devices:ZTE Racer
  • Twitter:@equiliym
totally odd.. afaik there is no calibration tool for 2.3 roms and the ones that can be used usually dont work at all.. its odd that tpt cant solve your problem.. and on stock rom it works properly?

  • 0
Suffering-oriented programming.. "First make it possible. Then make it beautiful. Then make it fast."
if i helped please press the vote up button :3

#14
Arucarde

Arucarde

    Newbie

  • Members
  • Pip
  • 21 posts
On stock rom it works good but only after calibration!
On 2.2 rom I cant even calibrate it propre...
But if I restore to the stock rom it's propre calibrated

Edited by Arucarde, 26 November 2012 - 09:41 PM.

  • 0

#15
Arucarde

Arucarde

    Newbie

  • Members
  • Pip
  • 21 posts
I still need help on this badword problem please .... I just tried RacerMod 1.2 [17/11/12] CM7.2 unofficial port with kernel 2.6.35.7 and Recovery CWM since it has a calibration tools, but I'm having the same problem,...

I'm sure my problem comes from any of the "wrong" things I did like:
I already got phone bricked before it happened and could retrieve it,
tried many costum ROMs with and without problems,
did things like try to install the CF Racer II,
flash ROM with virtually no battery and not some not compatible,
not compatible games,
messing around with governators, and a lot more like this that I can´t even remember,

that I manage to fix it aside of this "little" problem that I can not managed to solve.

Can someone get me a backup of any clean ROM so I can test my "theory" please?
I think the problem "starts" whenever I do a wipe, and I already "managed" to solve the problem with a backup, but I only have a few of my backup files 2.1 ...

EDIT: new symptom, with CWM Recovery 5.0.2.8 the problem is present since this CWM uses home and return key.

Edited by Arucarde, 26 November 2012 - 10:06 PM.

  • 0

#16
Arucarde

Arucarde

    Newbie

  • Members
  • Pip
  • 21 posts
And another clue, maybe, I have instaled one of the 2.1 backup files and after, WITHOUT wiping s***, instaled RacerMod 1.2 [17/11/12] CM7.2 unofficial port with kernel 2.6.35.7 and Recovery CWM and it works good. Any clue about this lunatic problem or am I discussing this all alone on in this topic? xD

  • 0

#17
GuyOverThere

GuyOverThere

    Enthusiast

  • Members
  • PipPipPip
  • 176 posts
  • Gender:Male
  • Location:Caracas, Venezuela
  • Interests:Gaming, Linux, Tech and other stuff
  • Devices:ZTE Racer x850
  • Twitter:@netalien
Not alone :)

So I don't know if I follow you correctly, you installed racermod, (let's keep cwm out for the moment), and then you installed your 2.1 rom over racermod without data wipe and your calibration works, is that correct?

Also, what racer is this again? I'm guessing gen1 since it uses eclair, but where it was sold/bought?

Again, a thing about eclair roms, the calibration on those roms is done by an app (TSCalibration.apk iirc) which means, tslib is integrated into InputDevice.java which also means it modifies /etc/pointercal, this hasen't being done by any 2.3 rom beyond rexchun BO2 and no one knows the modifications they did, so my best offer if you want a 2.3 rom would be this: use your 2.1 rom, do the calibration, take a copy of the /etc/pointercal file and post it here, that way I might be able to give you a kernel with those calibration values hardcoded in the kernel for you to test.

  • 0

#18
Arucarde

Arucarde

    Newbie

  • Members
  • Pip
  • 21 posts
Thanks

No, it was the other way, installed racermod over the 2.1 r2_update_de-threed_racer_signed (because with the stock one it doesn´t work the same way)
Yes it´s gen 1, bought in Portugal

Oh man that is alot of work to you, no? I have checked the pointercal after and before the calibration and it´s the same, neither way here it is.

Attached Files


  • 0

#19
GuyOverThere

GuyOverThere

    Enthusiast

  • Members
  • PipPipPip
  • 176 posts
  • Gender:Male
  • Location:Caracas, Venezuela
  • Interests:Gaming, Linux, Tech and other stuff
  • Devices:ZTE Racer x850
  • Twitter:@netalien
If it's the same before and after calibration is possible that there's a second pointercal file in /data/local/pointercal but tslib in eclair roms by default uses /etc/pointercal, check anyway if you have that second copy (or somewhere else) in the rom. I can't use the values of the pointercal you posted since those values are the same used on mike's racermod kernel and deadlink's kernel which for whatever odd reason mess your calibration.

You could take a logcat while doing the calibration, maybe that would give some other hints.

  • 0

#20
mikeioannina

mikeioannina

    Regular

  • Members
  • PipPip
  • 147 posts
  • Gender:Male
  • Location:Ioannina, Greece
  • Devices:ZTE Carl
After you do calibration in racermod, a new file is generated /data/system/pointercal

  • 0

If you like my work, don't forget to press the vote up button!
Current phones:
SE Xperia x10 mini - MiniCM10 & nAa-jb kernel
Using custom built roms by me:
SE Xperia mini - CyanogenMod 10 & FXP kernel

ZTE Carl - CyanogenMod 7 & 2.6.35.7 kernel





1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users