Edit: these modifications below sometimes help a little bit but DOES NOT FIX ANYTHING
@devs please close this thread.
Hi,
just found a thread at sony about the touchscreen issues. Since that post also references some XDA-Threads I guess it has been published before in some other Xperia threads, but I did not searched for it.
I tested this running stock Xperia ROM (.402) and also CM11 and these issues are gone for me. The touchscreen is much more responsive now and I never noticed that complete touch freeze again.
What's about your device? Does this fix help?
Note: You need root to apply this fix!
Change these two lines in /system/usr/idc/clearpad.idc
R/W-Mount /system (mount -o remount,rw /system)
In /system/usr/idc/clearpad.idc change the values of
touch.pressure.scale to 0.001 (original value: 0.1)
Code:
touch.pressure.scale = 0.0001
touch.filter.level (original value: 2)
Code:
touch.filter.level = 1
reboot
Is this for fixing my z2t screen sometimes just not respond to my fingers pressing keys or stuff?
Sent from my SGP511 using XDA Premium HD app
Just try and report. You can revert if you dont like
Sent from my D6502 using XDA Premium 4 mobile app
markusmuster said:
...The touchscreen is much more responsive now and I never noticed that complete touch freeze again.
What's about your device? Does this fix help?
Click to expand...
Click to collapse
schurgatzi said:
Is this for fixing my z2t screen sometimes just not respond to my fingers pressing keys or stuff?
Click to expand...
Click to collapse
As said above: I never noticed that complete touch freeze again
This is hasenbein1966's suggested fix, unfortunately didn't seem to make a difference to me. But then again, I don't have the issue where the screen completely freezes, only occasional unregistered touches and some glitchy two-finger gestures, when the tablet is resting on a stand or some other surfaces.
degraaff said:
This is hasenbein1966's suggested fix, unfortunately didn't seem to make a difference to me. But then again, I don't have the issue where the screen completely freezes, only occasional unregistered touches and some glitchy two-finger gestures, when the tablet is resting on a stand or some other surfaces.
Click to expand...
Click to collapse
Thanks for the hint!
According to this I searched a little bit and found another thread from hasenbein1966 on the german Android-Forum
There he reports that this TS issue is gone when he replaced the library in /system/lib/touchfilter/tftype.so with one from the Z1.
The complete thread is in german but google translate can do the (or tell me the #msg and I'll translate it for you if it's not too much
I didn't tried it since my Z2 is currently @home, but I think it's worth a try if the issue ever comes back to me.
markusmuster said:
Thanks for the hint!
According to this I searched a little bit and found another thread from hasenbein1966 on the german Android-Forum
There he reports that this TS issue is gone when he replaced the library in /system/lib/touchfilter/tftype.so with one from the Z1.
The complete thread is in german but google translate can do the (or tell me the #msg and I'll translate it for you if it's not too much
I didn't tried it since my Z2 is currently @home, but I think it's worth a try if the issue ever comes back to me.
Click to expand...
Click to collapse
Just tried the tftype4.so fix and while it doesn't fix the touch issue 100%, I definitely do see a noticeable improvement.
Update: never mind, the touch screen just went back to its usual behavior. The improvement was probably purely due to rebooting.
Update 2: yup, just got the same temporary post-reboot improvement after restoring the backup of the original touch filter file.
I suppose I will just wait until they finally start to roll-out that latest certified firmware, and see if that brings any improvement. But I don't have my hopes high since it's obviously a grounding issue, which of course is hardware-based.
I tried the "fix" involving the clearpad.idc changes, too.
It did not fix anything, I regret.
Touchscreen response is still a pain in the you-know-where.
Haha, this whole touchscreen thing is bordering on hocus-pocus...
Yes, I suggested this "fix" here weeks ago because it seemed to improve the issue back in the days when I still had the .36 firmware.
It wast just a suggestion for people to try it, I didn't claim it to be a definitive "fix" or so.
Meanwhile I had to reset the clearpad.idc values to 0.1 and 2, because annoyingly the tablet often recognized double taps when I only tapped once which made, for instance, inputting passwords nearly impossible. Now I haven't this problem anymore, so obviously clearpad.idc DOES make a difference - it's only mysterious what clearpad.idc values really do, there is no documentation available anywhere.
The touch screen is also rather dependent on weather - here in Germany it's now hot and humid, and touchscreen operation, especially with greasy hands, is less reliable than in cooler, drier weather.
hasenbein1966 said:
Haha, this whole touchscreen thing is bordering on hocus-pocus...
Yes, I suggested this "fix" here weeks ago because it seemed to improve the issue back in the days when I still had the .36 firmware.
It wast just a suggestion for people to try it, I didn't claim it to be a definitive "fix" or so.
Meanwhile I had to reset the clearpad.idc values to 0.1 and 2, because annoyingly the tablet often recognized double taps when I only tapped once which made, for instance, inputting passwords nearly impossible. Now I haven't this problem anymore, so obviously clearpad.idc DOES make a difference - it's only mysterious what clearpad.idc values really do, there is no documentation available anywhere.
The touch screen is also rather dependent on weather - here in Germany it's now hot and humid, and touchscreen operation, especially with greasy hands, is less reliable than in cooler, drier weather.
Click to expand...
Click to collapse
Double taps are painful experiences! I can hardly stand it.. So you completely fixed double taps problem? May I have your clearpad.idc code? And one more question is what's your rom region and version? I want to flash my tablet if your rom and method can solve this problem
Thanks a lot!!
xjoewoo said:
Double taps are painful experiences! I can hardly stand it.. So you completely fixed double taps problem? May I have your clearpad.idc code? And one more question is what's your rom region and version? I want to flash my tablet if your rom and method can solve this problem
Thanks a lot!!
Click to expand...
Click to collapse
He only restored his clearpad to factory default, so your clearpad is most likely the same as his.
Related
Hi All,
My HD2 just came back from repair.
I sent it in a hope that they will change my buggy screen (like lot of people, the touch function is buggy. Sometimes doesn't react, sometimes it feels a pressure while i don't press it, sometimes it works well... ).
Anyway, of course they didn't change any screen...and i just missed my HD2 for 2 weeks.
They did a Hard reset and installed all the HotFIx. Which i bet won't fix any issue that i have with the screen.
However, i do notice they installed a hotfix i never heard about yet:
LEO08787.exe
Does anyone have ever heard about it and what it does ???
send it back again and demand a replacement screen since it is a known fault with the original screens. They are just trying to get out of paying for the new screen.
regarding the hotfix nope, havent heard of it, but I dont track the hotfix versions so it may be a known one
ok lets install this and see how it goes..
hope its not a bogus file with some virus inside ...
HTC repair center SUCKS big time.
@kaemon: i also had that problems (sometimes the screen just wouldn't react to my touch) and i brought it to my reseller so they sent it to repair center and it come back untouched, they've only done the screen calibration which i have done dozen times. And it took them 16 days to do that. i'm definitely buying an iphone next time.
Unreleased hotfix
Apparently this is an (as yet) unreleased HotFix for the HD2, that is designed to correct some issues with the touchscreen. POCKETNOW.COM have tested this hotfix and found that it "drastically improved" the typing on the touchscreen, and also cured the HD2s alleged inability to draw a straight line when in Notes.
(Please note, I have not tested this yet, as I havn't suffered any such problems on my HD2, but I'm sure a quick check on their website will find you the page in question, which contains a link to the hotfix).
Pocketnow seem to think it's pretty decent. I'll give it a go.
Just installed it.. And I got to say i reckon typing maybe more accurate! not completely sure as time will tell. Installed on a Euro version about 5 months old, certainly the lines in Note are not like an ECG any more so
direct link for those who want it
http://www.mediafire.com/?kjmeyleaewz
IMO this is by far the best HotFix I ever installed. Typing works massively improved for me (also on the PIN-unlock-screen). I'm currently on German stock ROM.
So what do you reckon? Worth installing? Can it be uninstalled?
** Edit **
Just seen the two replies above - sounds good! I'm going to give it a try and will report back.
Tried it but didnt like it, it made my screen unresponsive and the ui jerky.
Installed after reading the Pocketnow tweet but uninstalled about 5 minutes later.
Screen became very unrespsonsive and massive slow down in scrolling.
Seems to be a 50/50 split.
Give it a try though
ROM: 1.66 WWE
madpete said:
Tried it but didnt like it, it made my screen unresponsive and the ui jerky.
Click to expand...
Click to collapse
definately a little less responsive to some touches, i'm just tweaking slightly with HD2tweak and see if that makes a difference....
UpDate:
I wonder if this hotfix is just changing a reg key, the same as BsB tweaks to decrease the screen sensitivity or if it is actually a driver?
Ive just changed the screen sensitivity in HD2tweak to very high and it seems to have eliminated the unresponsive touches but remains much better with typing accuracy? I would love to know what this .exe actually does within the system..maybe someone more clever than me can take it apart and see whats inside.
oh yeah running a tmous 2.13 Rom on a euro Leo if thats any help
Well I tried it....
EVen though I didn't suffer from any problems with the touchscreen on my HD2, I thought I'd give it a go, and set myself a couple of tests.
1) I used "notes.exe" and tried to draw 5 straight lines, and got five slightly curved and wavy lines.
2) I typed a message "this will test how accurate my keypad is or how bad my typing is", and had to correct three mistypes/mistakes.
I then installed the hotfix, and tried both tests again....
1) Five pretty straight lines, certainly better than before
2) typed the same message, and only one correction.
So, based on the 5 mins since I installed, it seems that this fix DOES make an improvement. I'll keep monitoring it and report back to let you know.
too bad it doesn't work for the US version
josemedina1983 said:
too bad it doesn't work for the US version
Click to expand...
Click to collapse
i just tried the same thing...
after the latest update from TMOUS, my typing has been terrible. swype is unstable too.
gonna flash the latest energy rom. that should help.
if we're going to be posting feedback, can i suggest that those who try it also report the manufacturing dates of their devices (if known to them)? at the very least, do report what screen type is on the device. what i am referring to is the fact that the hd2 ships with TWO kinds of screens. earlier models shipped with a screen with fewer "dots" while the newly manufactured devices ship with a screen with noticeably more "dots" (these additional brighter dots are visible on the intersections of the criss-cross "lines").
i personally have the newer model and i have no problems whatsoever. notes always draws straight lines and typing is accurate out of the box.
"This hotfix is not compatible with your device."
"This hotfix is not compatible with your device."
Using NRGZ28 EnergyROM.
it work very well for me
sure it's less responsive :/
madpete said:
Tried it but didnt like it, it made my screen unresponsive and the ui jerky.
Click to expand...
Click to collapse
Same here, might give it a little bedding in period but I'm already thinking about uninstalling it
I just installed this and it has improved the accuracy of typing on the keyboard especially at speed. I can touch type (badly) so with any qwerty keyboard i can do 100 ish words a minute. Before every other word had to be corrected but my test sentence "this is a test to see if the keyboard accuracy has been improved at speed" needed not one. Line drawing is still too accurate (that was the problem before. it is impossible for a human to draw a perfect straight line free hand) but it is better. I've also noticed in my typing test that the contact i used to test the htc messaging app load speed (contact has currently 2481 messages associated with it) was massively improved. I have no idea if this is related but this patch appears to have done something to it. I'll keep an eye on that just to see if the effect is because my phone just had it's first reboot in 8 days or not.
Done some quick further testing on the Messaging app load speed and it appears that either the way the message database is loaded has been changed (instead of loading them one by one it seems to loading them all in one big chunk) or the graphics driver has been updated (reading this i'm not sure if it's not the undefined option 3) but something is definitely different there because whether it's 2500 messages or 10 the load time is now the same and faster than before.
Something weird is defintely up with this hotfix and i bet it includes more than just a touch screen update too.
Hi, I made a video of the problem here:
http://www.youtube.com/watch?v=sRXcBcpSD1w
It's minor, but I'd still like it fixed.
I heard about this as well... does look annoying. What application did you use to test that?
Timmmmmm said:
Hi, I made a video of the problem here:
http://www.youtube.com/watch?v=sRXcBcpSD1w
It's minor, but I'd still like it fixed.
Click to expand...
Click to collapse
I think "Yet Another Multitouch Tester" or something. There are loads of them in the market.
Yea I was just curious. I use multitouch visible test which shows coordinates as well and I tried to replicate this on my Nexus S... doesn't have that threshold though, it's similar to the Nexus One. Wonder why samsung would add that...
BTW could you tell me how many simultaneous touch inputs the screen can register? The original SGS and Nexus S can register 5 according to multitouch visible test. Nexus One as you know can do 2 but when you cross each axis they flip.
Timmmmmm said:
I think "Yet Another Multitouch Tester" or something. There are loads of them in the market.
Click to expand...
Click to collapse
I got up to 10 and then ran out of fingers...
There's no axis flipping problem.
Ok so the physical touchscreen technology is very good... it's just samsung has written in this threshold movement delay, that's a bummer lol.
Timmmmmm said:
I got up to 10 and then ran out of fingers...
There's no axis flipping problem.
Click to expand...
Click to collapse
I think the touchscreen is so extremely sensitive they decided to fool-proof the phone.
without this "sticking" there would be no way for an average person with shaky fingers to register a TAP not a micro-SWIPE.
kreoXDA said:
I think the touchscreen is so extremely sensitive they decided to fool-proof the phone.
without this "sticking" there would be no way for an average person with shaky fingers to register a TAP not a micro-SWIPE.
Click to expand...
Click to collapse
I doubt it. It's virtually impossible to perfectly tap on other phones and it's not a problem. I'm pretty sure 'micro-swipes' are detected by the software layer as taps.
Well does it affect the phone usage otherwise?
I just checked on 3Gs (havent got the S2 yet, damn these late release dates ) and sure enough it has the exact same delay and skip when I slowly try to scroll say web pages. Its always been good enough for me though.
I would be more interested in an accuracy test to see if there are any major issues with the hardware itself. Last test I saw showed everyone but the iPhone digitizer having abysmal performance, I remember the Droid loosing the finger signal all the time.
Any links to the touchscreen performance test you mention?
As for the "deadzone" for touch input, CyanogenMod7 for the SGS has this aswell. Furthermore, it also has a "feature" where if you move your finger slower than a certain speed across the screen, homescreens/browser pages etc will just ignore the touch input. So if you want to minimally correct the framing of a webpage, if maybe the text is just cut off on the side, you need to quickly swipe a very short swipe to get any movement on the screen. Trying to slowly change framing is not possible.
Hardware is fine though, multitouch tests has no filtering like deadzones or speed thresholds.
I have this problem to, Its definitely software I think.
I wonder if its easy to mod to get rid of this deadzone/minimum threshold for scrolling. Anyone able to take a look. Its quite annoying in some things and my old android phone didnt do this.
Angry birds doesn't bypass the problem. It's quite hard to see underneath your finger but the problem is definitely there in "Angry Birds Rio".
Scrolling in some views don't show the problem so badly, presumably because they use the relative movement of each move event, rather than the absolute distance from the down event.
Yeah problem is still there in angry birds my mistake.
Its quite annoying in nova hd when you want to move the crosshair a tiny amount. You can't because of this problem
Anyone know what file in the source could be edited to maybe stop this ?
sorrowuk said:
Yeah problem is still there in angry birds my mistake.
Its quite annoying in nova hd when you want to move the crosshair a tiny amount. You can't because of this problem
Anyone know what file in the source could be edited to maybe stop this ?
Click to expand...
Click to collapse
my hunch is this source is not available, and somewhere in samsung's closed framework or similar.
i know on cyanogen rom, you can go look at the source code for ADW launcher, and you can locate the touch input source code. and you can find all the algorithms like dX, dY, that are used to register swipes, motion, scrolls, etc. its all pretty complicated and impressive code actually.
i'm sure samsung has equivalent code somewhere.
So if we got rid of touchwiz and used ADW launcher would the problem still be there?
sorrowuk said:
So if we got rid of touchwiz and used ADW launcher would the problem still be there?
Click to expand...
Click to collapse
Good question. I'm curious.
Still same problem with adw launcher
This looks more like a kernel thing to me in the touchscreen driver...
Are we able to edit/mod/patch the touchscreen driver in the kernel or is this only something samsung can do ?
sorrowuk said:
Are we able to edit/mod/patch the touchscreen driver in the kernel or is this only something samsung can do ?
Click to expand...
Click to collapse
We have the sources. I'm checking out the frameworks first though in case it's obvious.
Has anyone had an issue with the keyboard thinking that keys are being held down even though they are not? Not sure if this is an android issue but it had never happened when I ran Winmo on the phone.
Running latest kernel, ryannnathans sd setup and highlandsuns ril addition.
I will be typing along and suddenly get like 80 a's in a row with no way to stop it.
It may be the physical keyboard dying but I thought I would ask before I attack it with compressed air and a screwdriver.
FireRaider said:
Has anyone had an issue with the keyboard thinking that keys are being held down even though they are not? Not sure if this is an android issue but it had never happened when I ran Winmo on the phone.
Running latest kernel, ryannnathans sd setup and highlandsuns ril addition.
I will be typing along and suddenly get like 80 a's in a row with no way to stop it.
It may be the physical keyboard dying but I thought I would ask before I attack it with compressed air and a screwdriver.
Click to expand...
Click to collapse
Nothing physically wrong with the hardware, definitely an issue with our port. Not sure if anyone has nailed down the reason, but it seems to be if you're typing and some background process starts up, it can screw with the phone. I've also seen it where the keyboard appears to completely 'cut out' - nothing will be typed.
For both issues, sliding the kbd closed & reopening usually fixes it. This has fixed my issues 100% of the time when the kbd cuts out - however, it has not always resolved the repeat key bug...
I will try the keyboard slide. thanks.
I just had over 200 w's. LOL.
As long as I can stop it its tolerable.
FireRaider said:
Has anyone had an issue with the keyboard thinking that keys are being held down even though they are not? Not sure if this is an android issue but it had never happened when I ran Winmo on the phone.
Running latest kernel, ryannnathans sd setup and highlandsuns ril addition.
I will be typing along and suddenly get like 80 a's in a row with no way to stop it.
It may be the physical keyboard dying but I thought I would ask before I attack it with compressed air and a screwdriver.
Click to expand...
Click to collapse
Yep, I've seen it several times. It seems to happen when the CPU seems to be maxed out for whatever reason. My phone is usually sluggish and on screen buttons are slow to respond too when it's going on. I'm guessing the CPU is getting overloading and missing some of the hardware polling cycles. As a result it doesn't pick up the change in the button state and proceeds as if the button is still being held down. Aside from arrrghhh's suggestion of opening/closing the keyboard, pressing another key seems to interrupt the process (but it will happen again). For me, the main times I have run into the problem was when my phone was NOT overclocked. Certain apps (e.g. Super Manager) seemed to cause the issue more than others too.
Yeah, I have noticed that it only repeats a letter if I hold it. Now I only tap a letter a few times, for example if I want a few 2's I would push 2 a few times instead of holding it.
If it starts repeating what solves it for me is what arrrghhh said, slide the keyboard in and then back out.
I'm still not sure why this occurs though. Maybe the method it uses to emulate keyboard needs a bit of tuning
i believe the stuttering letter bug (hope this name will catch on ) is caused by something in the keyboard backlight commit as that is where is started. In gingerbread when you hold down a key it doesnt repeat it instead gives an option to use variations of that letter, because of this maybe in gingerebread this bug is not as annoying
iv used gingerbread but havnt taken any notice of wether i had the bug or not, its not as bad lately on the kernal i use but i will take not next time
That's an interesting observation, I thought the bug always existed but I can easily believe it has to do with the keyboard backlight. I was looking at that code the other day, it definitely looks suspicious.
Sent from my FRX06+ TP2 using Tapatalk
i have been getting this for quite sometime now...it only started when the backlight in the keyboard started working..
coolwater22 said:
i have been getting this for quite sometime now...it only started when the backlight in the keyboard started working..
Click to expand...
Click to collapse
It does *seem* like the bug was introduced around then. Not positive tho, wish there was a way of tracing/reproducing this issue.
Perhaps trying files from before backlight was added?
If I had the time to look back I would.... Maybe in the next few nights.
I always hit home and let the maelstrom of letters work itself out and then return to what i was doing (texting usually).
gallahad2000 said:
I always hit home and let the maelstrom of letters work itself out and then return to what i was doing (texting usually).
Click to expand...
Click to collapse
Also I have recently noticed that closing/opening the keyboard again seems to stop the progressing letters.
And when you open/close the keyboard the backlights go off then on. This is another observation which hints that the keyboard backlight commit is at fault. It also may be useful to note that when you shut the keyboard it doesn't stop the letters, it is upon re-opening when it stops.
This bug has always been worth putting up to have keyboard bl but it still would be nice to have someone clean ir up and see if they could remove the bug
Jandyman said:
This bug has always been worth putting up to have keyboard bl but it still would be nice to have someone clean it up and see if they could remove the bug
Click to expand...
Click to collapse
We look forward to your patch!
I guess I'll save Jandyman the trouble. I've worked out the patches for userland keyboard and buttonlights. I also now have a kernel with the keyboard light stuff disabled. Will be testing on my phone for the next couple of days and see how it behaves. (So far so good, while entering this post...)
Sent from my FRX06+ TP2 using Tapatalk
highlandsun said:
I guess I'll save Jandyman the trouble. I've worked out the patches for userland keyboard and buttonlights. I also now have a kernel with the keyboard light stuff disabled. Will be testing on my phone for the next couple of days and see how it behaves. (So far so good, while entering this post...)
Click to expand...
Click to collapse
Awesome. I'm sure he'll appreciate that .
FYI, I was going to bug you about this - if the caps/FN and kbd hooks should be in userland anyways, perhaps that rewrite should begin...?
I'm not so sure about caps/fn. I don't think there are any userland hooks for them. Or, haven't found them yet.
Sent from my FRX06+ TP2 using Tapatalk
highlandsun said:
I guess I'll save Jandyman the trouble. I've worked out the patches for userland keyboard and buttonlights. I also now have a kernel with the keyboard light stuff disabled. Will be testing on my phone for the next couple of days and see how it behaves. (So far so good, while entering this post...)
Sent from my FRX06+ TP2 using Tapatalk
Click to expand...
Click to collapse
That's great to hear thank you highlandsun.
Anyone have an issue with their touchscreen where there is a "dead spot"? I don't know how to describe it other than that. There is a spot if I touch it, nothing happens. It is right where the Accept and Download button is on the market in portrait orientation. It seems to be all the way across the screen in a horizontal line. Pixels and color are not affected just the touch effect. If i reboot, it goes away for a while. Switching ROMs makes no difference, happens on every one I have tried though, so it seems to be a hardware issue. Any help would be great.
nicktheqwik82 said:
Anyone have an issue with their touchscreen where there is a "dead spot"? I don't know how to describe it other than that. There is a spot if I touch it, nothing happens. It is right where the Accept and Download button is on the market in portrait orientation. It seems to be all the way across the screen in a horizontal line. Pixels and color are not affected just the touch effect. If i reboot, it goes away for a while. Switching ROMs makes no difference, happens on every one I have tried though, so it seems to be a hardware issue. Any help would be great.
Click to expand...
Click to collapse
If you had searched the forums, you would have come across this, which will solve your problem.
Also, it's not flashable so unzip it and put the apk on your phone, install it, then run.
nicktheqwik82 said:
Anyone have an issue with their touchscreen where there is a "dead spot"? I don't know how to describe it other than that. There is a spot if I touch it, nothing happens. It is right where the Accept and Download button is on the market in portrait orientation. It seems to be all the way across the screen in a horizontal line. Pixels and color are not affected just the touch effect. If i reboot, it goes away for a while. Switching ROMs makes no difference, happens on every one I have tried though, so it seems to be a hardware issue. Any help would be great.
Click to expand...
Click to collapse
Try to find the HTC Calibrate.apk and push it to System/Apps... It'll Definitely Help!
Twolazyg said:
If you had searched the forums, you would have come across this, which will solve your problem.
Also, it's not flashable so unzip it and put the apk on your phone, install it, then run.
Click to expand...
Click to collapse
I ran the advanced search and couldn't find anything for the E3D. But thanks for the help and for the hand-slap dude.
nicktheqwik82 said:
I ran the advanced search and couldn't find anything for the E3D. But thanks for the help and for the hand-slap dude.
Click to expand...
Click to collapse
Really? After about 1.4 seconds I had 4 touchscreen issue threads (including this one.) pop up after searching "touchscreen issue" in the "search this forum" bar. Did you fix your problem?
No go.
Well the HTC Calibrate app did not work. I must say that it did help for sure, but the same dead spot issue keeps happening. OK, so now I have begun to look at replacement parts on Ebay. So just to get this straight, it is the digitizer/front glass assembly that registers touch, correct? As I said, there are no missing pixels or colors, so does that rule out the LCD? Or should I but both to be on the safe side? I really want this issue done and over with, so help me get this thing taken care of guys. Thanks to all you guys for the help. Also, if anyone has a digitizer and LCD assembly for a good price, let me know.
I had the same issue where the bottom quarter of my e3d hboot 1.5 didn't work I didn't have insurance so I took it in and the sprint manager said I wasnt the only one with the issue it's a htc issue I tried the calibration on different roms bit it would only give you calibration on the top half of the screen, spent swapped it out and I got a new e3d with hboot 1.5 of course but at least the touch screen is working.....hoped that helped you out cuz I searched everywhere and couldn't find a solution.
I was toying with that idea. Will the "watermark" from unlocking a 1.50 hboot version be a problem? Obviously I need to unroot. And also, I bought this phone from an individual just a few weeks ago after I got my first one stolen, will this be a problem? Any other thoughts on taking it back to sprint?
Yeah, it is really weird, it is exactly where the "Accept & Download" button is when making a market purchase. So, yeah it sucks, I have to rotate it horizontal every time I want to buy something
I have been having lots of touchscreen issues as well. Tried lots of different roms and kernels but no luck. Someone suggested formatting the SD card. I haven't had access to a computer so i just removed the card about an hour ago to test and so far i haven't had any issues.
Sent from my PG86100 using xda premium
Like many other ZU owners i'm experiencing phantom touches now and then. My culprit is for example some dirt, like a fingerprint, on the screen. If I clean it the issue is gone for a while.
I'm convinced this is a software issue, and I've read at several places about other users with the same idea.
I've found some tips, like tweaking the touch pressure scale in clearpad idc and the touch filter level in max1187x_pen_0.idc but nothing seems to completely fix the problem.
So, I would like to know if someone made some more digging?
There is one file which loads the touchscreen firmware at boot called pre_hw_config.sh
It loads the touchscreen drivers in /sys/devices/virtual/input
Can we find something here?
The firmware version of the touchscreen drivers can be found at:
/sys/devices/virtual/input/max1187x/few_ver
I'm on:
fw_ver (1.4.13) chip_id (0x75)
config_id (0x0010) customer_info[1:0] (0xFFFF, 0xFFFF)
Are you on a more recent firmware without issues?
If you feel for joining me in the search for a fix please do so,
Thanks
Per
Sent from my C6833 using Tapatalk
I had those problems too, but since i removed (it takes a lot of time because it is glued :X) the screenprotector, the problems are gone.
When i used another screenprotector, the isues returned. So now I work on the glass, and have no isues at all.
I don't want to remove this as I think it's glued for a reason.
But if there's no other way to solve the touchscreen issue I might consider it
Sent from my C6833 using Tapatalk
fw_ver (1.4.13) chip_id (0x75)
config_id (0x0012) customer_info[1:0] (0xFFFF, 0xFFFF)
Your config_id is 10 while mine's 12.
Can't say I have any serious cases of phantom touching.
Sent from my C6833
LordManhattan said:
fw_ver (1.4.13) chip_id (0x75)
config_id (0x0012) customer_info[1:0] (0xFFFF, 0xFFFF)
Your config_id is 10 while mine's 12.
Can't say I have any serious cases of phantom touching.
Sent from my C6833
Click to expand...
Click to collapse
This is interesting. I suppose we're on the exact same hardware but with different config. If there is any way to upgrade this config I want to know. Will do some searching.
Sent from my C6833 using Tapatalk
I get this too. I have to keep my screen really really clean. The false touches tend to be nearer the home button. When it starts to happen I quickly press power/sleep and clean the screen, because it can cause chaos!
I too think it can be tuned in software, because I rarely experienced phantom touches when I first got my XZU on Jellybean 4.2; it started becoming a lot worse and the only reason I can ascribe is the upgrade to Jellybean 4.3.
I only just took the plunge and upgraded to KK/4.4.2, so it will be interesting to see whether it solves the problem.