Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,804,274 Members 38,131 Now Online
XDA Developers Android and Mobile Development Forum

Fix for Nexus 7 2013 (flo) Touchscreen Glitches

Tip us?
 
RandomRanger
Old
(Last edited by RandomRanger; 6th March 2014 at 12:15 AM.) Reason: disproved
#1  
Junior Member - OP
Thanks Meter 0
Posts: 2
Join Date: Mar 2014
Default Fix for Nexus 7 2013 (flo) Touchscreen Glitches

For a long time now my Nexus 7 2013 (flo) 32gb has had this annoying touchscreen glitch where it will get false readings causing it to push buttons I didn't want to press, zoom when I wanted to scroll, and generally make it unusable unless I rebooted (which on some occasions didn't fix the problem). After doing some research, I found that it seems to be a common enough problem, but there was only one thread that claims to have fixed it. Now, to be honest I didn't try his method, as frankly it looked long, complicated, and I never found the time. Yesterday the thought occurred to me that the screen may actually be picking up real interference, and that it may just simply be to sensitive, so I set about to decrease the sensitivity on the device. To decrease the sensitivity ( THIS REQUIRES ROOT) I used root explorer (you may use any file explorer that can access root files) and went to the folder "/system/usr/idc" and opened the file "touch_dev.idc" in a text editor. In this file I found the line "touch.pressure.scale = 0.0125" and changed the value from 0.0125 to 2.5. I then saved the file and rebooted. Since doing this I have not had the touchscreen glitch, and I have been using the device for a little over 24 hours now. I used to get the glitch about 3 times a day. I will continue to test this config, to see if it actually does fix the problem, but due to the nature of the problem, the only way to know if this fix works, is to use it over a long period of time. I will remove this post if the issue ever returns and I am not able to fix it using a similar method.

Notes:
* the directory is "/system/usr/idc/touch_dev.idc"
* increase the value of "touch.pressure.scale" to decrease the screen sensitivity
* make sure you have write privileges (in root explorer, don't forget to hit the R/W button before opening the .idc file in a text editor)
* don't forget to save the file
* after saving the file, reopen it to make sure the change took place, if it didn't make sure you have write privileges and actually saved it
* don't forget to reboot for the changes to apply (I'm not sure if its necessary, but am willing to bet that it is)
* this should work with other versions of the nexus 7 flo, not just the 32gb
* I am not liable for any damages caused to your device (you should know this by now)
*I have only tested this on one device, as it is the only one I have access to with this problem
* If this fix works for you, please let me know below, feedback is appreciated

* I didn't return the device, simply because I lost the receipt, and don't know if the warranty is still in place

Edit:
This does not work, after more testing issues returned. But I will continue to try different values to see if this can fix the problem.
 
kirev
Old
#2  
Member
Thanks Meter 8
Posts: 51
Join Date: Feb 2008
Location: Skopje
 
Solaris81
Old
#3  
Member
Thanks Meter 15
Posts: 95
Join Date: Dec 2008
Don't bother adjusting any further, it's a very well known problem and has nothing to do with this, put it back to it's default and then use the fix mentioned in this forum, (the software touchscreen driver fix). It's simple, takes about 5 mins, doesn't require root and actually works. TS10 solved 99% of my problems, which were pretty severe before.
 
RandomRanger
Old
#4  
Junior Member - OP
Thanks Meter 0
Posts: 2
Join Date: Mar 2014
Quote:
Originally Posted by Solaris81 View Post
Don't bother adjusting any further, it's a very well known problem and has nothing to do with this, put it back to it's default and then use the fix mentioned in this forum, (the software touchscreen driver fix). It's simple, takes about 5 mins, doesn't require root and actually works. TS10 solved 99% of my problems, which were pretty severe before.
Ok, yeah I'll have to do that. I posted this a bit early, as I was seeing positive results at first and got excited. Thanks.
 
318sugarhill
Old
#5  
Senior Member
Thanks Meter 134
Posts: 381
Join Date: Aug 2010
yes, there are 3 different fixes posted, ts10, ts20 and ts30.....and there are a couple of others in that thread too. I found the experiment ts18 worked best for me. ts10 was an improvement, ts20 better, and and ts30 too sensitive. after sticking with ts20 I decided to try the additional ones and so far 18 is best for me.

try the 3 main ones....and use the one that works best......if you still see little bugs in it, then try the experimental ones closest the 10 or 20 or 30 that worked best for you. I feel like I have a brand new device since running this fix on mine. You don't have to be rooted, but you do have to be unlocked.

I have a wifi 32 gb model manufactured Sept 2013
HTC Incredible (AMOLED) rooted S-off
HTC Rezound unlocked & rooted
Unlocked MDK Rooted Galaxy S4

If it ain't broke....fiddle with it to try to make it better.
 
GSLEON3
Old
#6  
GSLEON3's Avatar
Retired Senior Moderator
Thanks Meter 1,321
Posts: 2,452
Join Date: Dec 2006
Location: NSA Black Site Whiskey Tango Foxtrot One Niner

 
DONATE TO ME
Quote:
Originally Posted by Solaris81 View Post
Don't bother adjusting any further, it's a very well known problem and has nothing to do with this, put it back to it's default and then use the fix mentioned in this forum, (the software touchscreen driver fix). It's simple, takes about 5 mins, doesn't require root and actually works. TS10 solved 99% of my problems, which were pretty severe before.
Okay, but you do know there are SEVERAL different issues with the touchscreen & that thread only will fix (partially fix as everyone I know that has tried it, still has occasional issues) one of three or more issues. There is also a grounding issue, that your reference WILL NOT FIX. There are also issues with the ribbon cable placement, which was my issue & several others, which requires opening the case & either reattaching the cable or reinforcing the connection at the terminal, which fixed mine & a few others. Just saying, I wouldn't blindly state that "this fix" will solve all your issues.
Ingress Resistance - Rainbow6


Click HERE to buy me a cheeseburger if I helped you! Or even better, find a charity or local family fighting childhood cancer & help out however you can!

A brief & incomplete timeline of my love affair with mobile technology:

 
 
tsimitsangaz
Old
#7  
tsimitsangaz's Avatar
Senior Member
Thanks Meter 43
Posts: 120
Join Date: May 2013
Location: Manchester
can anyone provide a flashable patch to try? Thanks
 
だんご94
Old
#8  
だんご94's Avatar
Junior Member
Thanks Meter 0
Posts: 4
Join Date: Apr 2014
Location: Singapore
This problem is starting to annoy me really badly D:
 
MrRedPants
Old
(Last edited by MrRedPants; 9th May 2014 at 03:07 PM.) Reason: Found my own answer
#9  
MrRedPants's Avatar
Senior Member
Thanks Meter 14
Posts: 103
Join Date: Nov 2009
Can you (or someone) please post a direct link to the main thread (or others) - I am having a little trouble locating. Thanks. By that I mean main thread mentioned in 2nd post regarding T10 etc

This seems to be it:
http://forum.xda-developers.com/show....php?t=2428133
 
pre4speed
Old
#10  
pre4speed's Avatar
Senior Member
Thanks Meter 340
Posts: 1,553
Join Date: Apr 2011
Location: lancaster

 
DONATE TO ME
Question, I originally bought a n7 lte (deb) in November 2013. Don't know manufacture date. Had to return for hardware failure in the touchscreen and the replacement was manufactured in November 2013. So far I have not seen the same touchscreen issues I had with my original (ghost touches, touches not registering etc). Should I try to use the fix in that thread or leave well enough alone? Tia
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes