Related
Is anyone else having a slight misalignment on the touch screen?
For me touch is shifted about a millimeter or two to the right.
I've checked on both my N4 and my sister's N4 and both of us seem to be having this slight misalignment.
Both of us have REV 11 N4's. One was obtained through T-Mobile in January, the other was obtained through Google Play just last month.
I've checked on a few roms. I've tried CM, PA, and Stock with a multitude of different kernels (Franco, Faux, Trinity, CM, and stock).
To check:
1. Enable "Show touches" under the Developer menu.
2. Touch a part of the screen where you'll be able to see the touch bubble and hold it there.
3. Look at the screen at angle to see under your finger.
It's not a big deal, just something I've noticed when I had difficulty trying to use PIE on the left side of the screen. Although, I still would love to be able to get the screen recalibrated to have more accurate touch sensitivity to eliminate the difficulty that I have with CM's PIE.
Another question: Is anyone aware of any LG diagnostic tool to calibrate the screen? I remember back on the HTC sensation there was a file that you could load through HBOOT and get your screen calibrated from there.
Photo attached.
Oh wow I never noticed this , I have the same thing, never really had problems with it
Btw I have an older model , so its not just a Rev11 thing
Sent from my Nexus 4
Mine looks like its right on when I test. Maybe just a hair over to the right but nowhere near as far off as yours. Rev11 302K
-Sent from that.... you know.... thing that sends these things-
I'm pretty sure you have OCD. So, take some medicine. Your phone is fine, stop crying. :crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::good:
Nope...
I thought I was just trippin when I noticed the same thing last week
Just tested and confirmed, pretty significant misalignment by about 1 cm, which is a LOT when you're talking about a <5" touch screen..
My next thought is, is this a software issue?
We need more people to test and confirm. But I believe that is what we will find. Software issue.
Anyone with a Nexus 7 on stock 4.2.2, please also test and report.
Wow never thought anyone else was experiencing this, mine seems to be off since I always have to touch a little higher than what I'm going for even nav bar.
Sent from my Nexus 4 using xda premium
Notified the same thing while playing Draw Something, I thought I was mad
Tapalked with my iNexus 4S
Nobody tested a Nexus 7 yet?
I'll test my wife's when I get home and post the results
Could not reproduce the issue on the Nexus 7. Looks like it's specific to the Nexus 4
Sent from my Nexus 4 using xda premium
ingenious247 said:
I thought I was just trippin when I noticed the same thing last week
Just tested and confirmed, pretty significant misalignment by about 1 cm, which is a LOT when you're talking about a <5" touch screen..
My next thought is, is this a software issue?
We need more people to test and confirm. But I believe that is what we will find. Software issue.
Anyone with a Nexus 7 on stock 4.2.2, please also test and report.
Click to expand...
Click to collapse
I would think that it's a software issue. My HTC sensation was able to have it's screen recalibrated. I think LG would have some kind of tool to be able to do it.
Same exact issue here but I wouldn't even notice if I didn't try
Sent from my Nexus 4 using xda app-developers app
For me its OK all stock
Mines fine, right where it should be.
This is with me too and cannot use the letter "cue" because of it
Sent from my Nexus 4 using Tapatalk 2
I recently upgraded from the Nexus S to the Nexus 4 and already I've been finding myself making a lot of spelling errors when texting and have been regularly entering my pin incorrectly 4-5 times before getting it right.
At this point I don't know if the screen is just slightly different in terms of sensitivity when compared to the Nexus S or if the larger screen is throwing me off and I'm just a hair shy each time of pressing the right button because I'm use to the smaller Nexus S.
If anyone understand what I'm getting at could it be one or the other, both or something else?
Comments and suggestions are appreciated,
Thank you
Hah, I'm in exactly the same boat as you (rip Nexus s).
The bigger screen is definitely a factor, but i feel the scroll speed is a little slow
Sent from my Nexus 4 using Tapatalk 2
I had the same problem, coming from a OneX.
The screen sensitivity sucks. There is a workaround for it, where it installs the old touchscreen drivers at every system-bootup: http://forum.xda-developers.com/showthread.php?t=2163924
It's MUCH better with that old driver.
Thanks for the responses and suggestions. I'll give em a look and see if it helps me.
D4rkSoRRoW said:
I had the same problem, coming from a OneX.
The screen sensitivity sucks. There is a workaround for it, where it installs the old touchscreen drivers at every system-bootup: http://forum.xda-developers.com/showthread.php?t=2163924
It's MUCH better with that old driver.
Click to expand...
Click to collapse
It can be done done better and to the best. All it needs the best tweaking in a decent kernel.
faddyie said:
It can be done done better and to the best. All it needs the best tweaking in a decent kernel.
Click to expand...
Click to collapse
Surely it can be done better by kernel tweaking. but I want to use francos kernel wich does still have crappy screen sensitivity, so I'm using this workaround.
Hey guys, I was wondering if anyone may know if the new 4.4 Kit Kat will fix all of the Nexus 7 2013 touch screen problems.
Maybe Asus and Google knows it fixes the issue. That's why they didn't rush to help us in the last few months.
Cross your fingers people and hope this fixes all of our issues. That would be sweet.
Oct 28 4.4 I'm thinking.
I hope that... it's been a headache, and that's the only flaw mine has, the fix here fixes it just temporally.
Can't say whether it will or won't but I can say I really doubt they have the fix already in hand and are holding it back waiting for kit kat.
They've never been shy about putting out releases to fix things and a touchscreen fix is very contained and isolated, not something that touches many areas requiring long code reviews.
Can I just ask what kinde of problems you are reffering to? Multitouch problem has been fixed with the latest update. At least mine was. With a multitouch program I placed all 10 fingers on screen and was moving it arround, and it registrated all fingers and arrows were moving very very smoothly. 60fps+. Also, there is no problem with GPS anymore. The only problem which is actually not a problem, is smal buzz from speakers when watching of listening to something at very low volume, but that is reported for all nexus 7 devices because that is how the speakers are made.
You are saying like nexus 7 2013 is forgotten and this 4.4 is our last hope for the device otherwise its useless to use. Which is far from truth. I have absolutely no problems with it.
I don't know, maybe I use the device too much? But I can definitely say ghost touchs and some multi-touch issues are there and persistent. In fact right now as I was writting this the keyboard went crazy, it's really annoying and I don't even want to start with the horrible experience I'm getting with PS Touch(which I use a lot) thanks to this problem. Sometimes I have to reboot the device when it goes crazy zooming while navigating the internet.
For you guys that your tablet is "perfect", fascinating, good for you, but that doesn't mean the problem doesn't exists anymore, you just got lucky.
I personally have no more touchscreen issues since JSS15Q, but if there is another touchscreen fix in KitKat that would be good to the few unlucky ones still having issue with theirs..
neo5468 said:
Can I just ask what kinde of problems you are reffering to? Multitouch problem has been fixed with the latest update. At least mine was. With a multitouch program I placed all 10 fingers on screen and was moving it arround, and it registrated all fingers and arrows were moving very very smoothly. 60fps+. Also, there is no problem with GPS anymore. The only problem which is actually not a problem, is smal buzz from speakers when watching of listening to something at very low volume, but that is reported for all nexus 7 devices because that is how the speakers are made.
You are saying like nexus 7 2013 is forgotten and this 4.4 is our last hope for the device otherwise its useless to use. Which is far from truth. I have absolutely no problems with it.
Click to expand...
Click to collapse
The few that had touchscreen problems initially were fixed. 75% of working units were broken in the process. Its a big issue. We have a fix but nothing from Google. There are several screen variances which make it impossible for a single 1 fix all solution.
Google will have to detect each variance and patch accordingly. Probably why it hasn't been released yet because it probably will take a larger testing period then previously mentioned. Even using the XDA fix, some versions can cause several FCs and bugs. Similar to the specific pattern freakout.
With 4.4 on the horizon, it would be best to include it in that. Google probably isn't going to create an OTA and then another one in a few weeks.
Just cross your fingers and hope for an official fix.
GPS was fixed though. I'm not sure about the kernel reboots though. I haven't used the stock kernel nor had reboots since I flashed CM Kanged.
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
player911 said:
The few that had touchscreen problems initially were fixed. 75% of working units were broken in the process. Its a big issue. We have a fix but nothing from Google. There are several screen variances which make it impossible for a single 1 fix all solution.
Click to expand...
Click to collapse
Any source for that 75% number? Without a proper source it is hard to not consider that as a case of the loud minority.
If it were that serve of a problem we would hear the tech press clamoring about it by now. But nothing was said about N7 touchscreen by the tech press since JSS15Q.
I can't tell you what the real percentages are, but the touchscreen issue is definitely a much bigger problem than your standard problems.
Standard run-of-the-mill issues get a thread with maybe 20 posts. Touchscreen is producing 1000 post threads. So relative to normal problems it is a big problem, but whether that is a 5% vs 1% problem or a 75% vs 1% problem I could not tell you.
There are at least 3 huge threads on Google support forums about this problem:
Multi-touch - reports of improvement, no improvement, and some worse
Multi-touch (continued) - more reports of fixed / not fixed for JSS15R
Multi-touch (continued 2) - more reports of touchscreen issues
BTW I created the xda fix for touchscreen so I'm very familiar with the fixes Google put out and whether they have fixed the issue. JSS15R fixed it for some screens but made it much worse for others.
That's the main reason I haven't sent my Nexus for repair, is not hardware related, or at least that's what I think, please someone correct me if I'm wrong.
NekroWolfen said:
That's the main reason I haven't sent my Nexus for repair, is not hardware related, or at least that's what I think, please someone correct me if I'm wrong.
Click to expand...
Click to collapse
Well, actually it is hardware related, but you can't tell if your hardware is one type or another without using Sfhub's process.
Well, thanks for confirming
I personally don't think that all of the touchscreen issues will be fixed with Kit Kat. I feel that Google will he focusing more on a fully operational OS, and that we'll need a dedicated fix to solve our problems.
But I surely hope that I'm wrong.
______________________________
HTC Evo 4G LTE
any word of usb audio coming via kitkat. ive been waiting for this feature to come to the nexus 7 forever because its keepingme outof my car
Lockeskidney said:
any word of usb audio coming via kitkat. ive been waiting for this feature to come to the nexus 7 forever because its keepingme outof my car
Click to expand...
Click to collapse
At this point, questions to me are almost meaningless to ask. We night as well wait for tomorrow. It took long enough to arrive.
It just sucks that I don't have my tablet. I went back to Radio Shack and ordered the 32gb through them, since none of their stores had that version on their shelves, and 16gb was not working out for me. At least I'll get to download it as soon as I get my new device!
______________________________
HTC Evo 4G LTE
GPS isn't solved to me.
diogobuique said:
GPS isn't solved to me.
Click to expand...
Click to collapse
That's a hardware issue, I suggest you to send it back to Google.
Kitkat gave me phantom touch issues, have none before kitkat. :-\
Sent from my SM-N900P via TapaTalk PRO
Elite Tester
This process doesn’t wipe the tablet, so your settings, apps and everything else should stay in tact whenever you get back to the system. Remember that you will have lost root at this point, but it’s easy enough to get that back.. Cool resource!
But before kitkat my GPS worked very well
So I updated to 4.4 yesterday with adb sideload. Since that I was using my Nexus 7 "heavily" and I always had "buttons stucked" on keyboard, but now it's gone and I havent experienced any other touchscreen bug.
I don't think I have had any buttons sticking since I updated as well. That was my only issue with my Nexus 7 when in was still running 4.3. It would usually have a keystroke stick several times while typing things and I haven't experienced it once while typing this entire post, which is also why it keeps going because I'm trying to keep typing to see if it'll happen, and instead I just keep making spelling mistakes.
It did not fix the touch issues that may be related to grounding. In a case or stand, both Nexus 7 devices I have still fail to see any touch on numerous occasions, even single finger touch events. Manufacturing issue I guess, but we all know how G & Asus deal with those.
Let's hope it lasts... some issues are fixed temporally.
touchscreen is definitely improved for me too.
Yeah but multitouch still fails, playing dead trigger 2 could be an impossible mission.
bokoy said:
Yeah but multitouch still fails, playing dead trigger 2 could be an impossible mission.
Click to expand...
Click to collapse
Never had multitouch issues, only single touch problems like quad touches innstead of one etc. (As u can see it happened again lol)
They poped up after the R update, and im waiting for CM11
I had single touch issues even after sending my tablet in for service. I had called yesterday to send it back again when I noticed the update was available for side loading.
After the update my screen is behaving!
I'm going to hold off on claiming that my issues are completely resolved but it is looking promising.
Sent from my Nexus 7 using Tapatalk 4
I was going to make a thread about this same thing my keyboard is good now.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Hi all,
as stated in the past days by oneplus, a new touch firmware has been released and will be in cluded in 5/15 cm12.1 nightly. this should (i hope so) resolve all the remaining touch issues that affects many opo
Here is the coomit: http://review.cyanogenmod.org/#/c/98287/
05/18: The touch firmware has been reverted to the old one because of battery drain caused by dt2w
sub.
Looks like working very good. Flashing Nightly and screen is more responsible ever sinde the failure occured. waitung für Lord Boefla or slimkat to include it
Tested and feeling much better
bigheadlyf said:
Tested and feeling much better
Click to expand...
Click to collapse
can you please test if two finger on the same X axys are now registered correctly? my opo is through the RMA process so i can't test
Certainly seems to be working for me. Typing fine, and x-axis multitouch is working great.
effry said:
can you please test if two finger on the same X axys are now registered correctly? my opo is through the RMA process so i can't test
Click to expand...
Click to collapse
Yes, working fine for me.....
The question now is.... will be forever?
multi touch on mine phone on x axis is still jerking from time to time
sometimes it works normally, detects 2 fingers, then on the other hand detects one or none
will see how it will perform through the day, but since i made a clean flash, i doubt that it will be better...
I have the grounding issue with my ONE. No problems with higher temperatures though.
I flashes Franco Kernel r43 boot.img on my stock cm12s. Fo rme the issues are gone.
x-axis touching is working good. Swiping texts is finally possible again!
Thanks to synaptics!!
I will probably switch to cm12.1 nightlies again when I have some spare time left.
Any way this could be a flashable zip for all ROMs or is this something that is baked into the ROM/Kernel?
JJHunterx said:
Any way this could be a flashable zip for all ROMs or is this something that is baked into the ROM/Kernel?
Click to expand...
Click to collapse
You can flash Franco's kernel below if you are on CM12s/CM12 (5.0.2). Or the alternative is to flash the 5/15 nightly (5.1) or wait for it to be rolled out OTA.
http://forum.xda-developers.com/showpost.php?p=60747459&postcount=8989
gsmyth said:
You can flash Franco's kernel below if you are on CM12s/CM12 (5.0.2). Or the alternative is to flash the 5/15 nightly (5.1) or wait for it to be rolled out OTA.
http://forum.xda-developers.com/showpost.php?p=60747459&postcount=8989
Click to expand...
Click to collapse
No chance for CM11s? I'm just not a fan of 5.x right now.
JJHunterx said:
No chance for CM11s? I'm just not a fan of 5.x right now.
Click to expand...
Click to collapse
I think you may be in luck! If you take the plunge let us know how you find it.
http://forum.xda-developers.com/showpost.php?p=60755103&postcount=4637
gsmyth said:
I think you may be in luck! If you take the plunge let us know how you find it.
http://forum.xda-developers.com/showpost.php?p=60755103&postcount=4637
Click to expand...
Click to collapse
Nice! Thanks for the link. Flashing now.
I had only mild touchscreen issues so I'll see if it gets rid of them.
I've never had touch issues thus far, but I am a bit disappointed at the fix. Although I do notice a better touch response, the fix isn't a fix and is a workaround. PPPreferences has a huge battery drain (com.qualcomm.display) which basically, like I've seen written somewhere, means they're just keeping an app open to recalibrate the screen constantly.
Spider-Vice said:
I've never had touch issues thus far, but I am a bit disappointed at the fix. Although I do notice a better touch response, the fix isn't a fix and is a workaround. PPPreferences has a huge battery drain (com.qualcomm.display) which basically, like I've seen written somewhere, means they're just keeping an app open to recalibrate the screen constantly.
Click to expand...
Click to collapse
Not for me. Nothing changed in terms of battery usage with today's nightly. Also it isn't even listed under Apps in the battery screen on my device.
This app is only used for post processing (Live Display) and has nothing to do with the new firmware.
I was suffering from pretty bad heat related issues, all gone now.
I just flashed Boeffla-Kernel for CM11s. I can definitely tell a difference. There was one app that I could make it jump when swiping up or down and holding it toward the bottom-middle of the screen, no longer have that issue. I also constantly had trouble with it "clicking" things when all I wanted to do was scroll up or down on something. Have not had that issue since flashing.
AcmE85 said:
Not for me. Nothing changed in terms of battery usage with today's nightly. Also it isn't even listed under Apps in the battery screen on my device.
This app is only used for post processing (Live Display) and has nothing to do with the new firmware.
I was suffering from pretty bad heat related issues, all gone now.
Click to expand...
Click to collapse
Hmm that's pretty interesting then, but I don't seem to be the only one reporting a difference in the CPU time of something which includes the Qualcomm services. We'll see with more usage though.
Do you need root to install?
nokmond said:
Do you need root to install?
Click to expand...
Click to collapse
Yes, until it gets pushed officially, as you need to either flash a custom kernel or the latest nightly.